What users are saying about
7 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.6 out of 101
3 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 9 out of 101

Add comparison

Likelihood to Recommend

ActiveBatch

I used to work in a company that only used SQL Server Agent to handle imports and exports of ETL data. ActiveBatch is far more powerful and easy to use, so I definitely would recommend it. I would think of three questions: (1) Do you handle a large volume of exports and imports in a given week? (2) Do you need a lot of configurable options, such as with scheduling? (3) Do you utilize a variety of ETL processing tools (such as GlobalScape EFT and Microsoft SSIS) but want one tool to work with them all? If yes to those questions, then ActiveBatch would well fit the bill for you then.
No photo available

vCenter Site Recovery Manager

All the vmware environments need a DRM to automate they DR process, its a must to save the cost of a total downtime for the enterprise.
Carlos Daniel Casañas Bertolo ஃ profile photo

Feature Rating Comparison

Workload Automation

ActiveBatch
6.9
vCenter Site Recovery Manager
8.8
Multi-platform scheduling
ActiveBatch
8.1
vCenter Site Recovery Manager
10.0
Central monitoring
ActiveBatch
8.4
vCenter Site Recovery Manager
8.0
Logging
ActiveBatch
5.0
vCenter Site Recovery Manager
8.0
Alerts and notifications
ActiveBatch
7.0
vCenter Site Recovery Manager
9.0
Analysis and visualization
ActiveBatch
5.4
vCenter Site Recovery Manager
8.0
Application integration
ActiveBatch
7.6
vCenter Site Recovery Manager
10.0

Pros

  • One good feature I already mentioned is that once you create a configuration object (such as a schedule object), you can reuse it as much as needed. This minimizes errors in scheduling because there's less opportunity to make a configuration error with future similar jobs that would follow the same schedule, makes it more efficient to schedule those new jobs, and makes it efficient to make scheduling changes--change the scheduling object once and all the related jobs' schedules are automatically changed.
  • Partial path execution is a good strength, especially for testing/debugging. I can have a decently sized tree of process nodes for a given job, but I can easily deactivate the nodes I do not want to include in my testing.
  • Being able to define test and production jobs in separate environments and easily change the settings of one without affecting the other is another strength. Often I would have a job set up in a test environment and after testing it, it would get ported to a very similar production environment with only having to change 3-4 parameter settings. And then I could easily deactivate the test job while still keeping it all set up in the event of needing it for future enhancement/troubleshooting.
No photo available
  • Provides enterprise level protection to all virtualized applications
  • Allows one to choose between built-in vSphere Replication and a wide range of supported storage replication products.
  • Provides non-disruptive testing and automated failback.
Carlos Daniel Casañas Bertolo ஃ profile photo

Cons

  • The manual could provide more examples of how to create certain jobs, otherwise you will need to check the site or call support to aid with creation.
  • Dashboard presentation could be worked on, to help present an overview for management.
Ron Zermeno profile photo
  • Better UI, and CLI functions
  • Too slow at some tasks, it will be nice to accelerate it
Carlos Daniel Casañas Bertolo ஃ profile photo

Alternatives Considered

N/A - It was already in place when I was on the scene, but like I said earlier it is much more powerful than SQL Server Agent and probably anything we would've come up with from scratch using .Net. However if your needs are small and traffic is light, then maybe SQL Server Agent or something smaller and less powerful (and less expensive) than ActiveBatch would work just fine.
No photo available
The choice betweem vCRM and Veeam is tight, and only the same manufacturer compatibility is the win key to vCRM.
Carlos Daniel Casañas Bertolo ஃ profile photo

Return on Investment

  • Saves employees time and sanity, from having to manually run tasks at certain times.
  • Cost is not overly expensive, considering the amount of platforms it integrates with "out of the box."
  • Takes control of sensitive processes, and runs them confidentially. Alerts management when completed.
Ron Zermeno profile photo
  • Good ROI, only for vmware enviroments
  • Veam its a real option in some enviroments
Carlos Daniel Casañas Bertolo ஃ profile photo

Pricing Details

ActiveBatch

General
Free Trial
Yes
Free/Freemium Version
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional
Additional Pricing Details

vCenter Site Recovery Manager

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details