11:11 Systems Disaster Recovery as a Service (DRaaS) was designed to provide end-to-end solutions and technology to meet organizations' recovery requirements.
N/A
Zerto
Score 8.2 out of 10
Enterprise companies (1,001+ employees)
Zerto, a Hewlett Packard Enterprise company, aims to enable customers to run an always-on business by simplifying the protection,
recovery, and mobility of on-premises and cloud applications. Zerto’s cloud
data management and protection platform is designed to eliminate the risks and complexity of
modernization and cloud adoption across private, public, and hybrid
deployments. The software-only platform uses continuous data protection
at scale to converge disaster recovery, backup, and data…
Sungard seems to be well-suited for those companies still doing traditional disaster recovery - replicating data (or shipping tapes), building out the servers/mainframe/AS400, restoring data/databases, then loading the applications and testing. We have limited exposure to their cloud offerings. For the most part, they can also take on or assist in the initial builds of client environments - we used them for building the OS only.
Zerto is well suited for disaster recovery and virtual machine replication between multiple data centers. DR testing for audit or regulations is much easier with Zerto, great reporting, dashboard etc. It is not well suited for physical server replication for disaster recovery or as a primary backup solution.
Sungard does a good job dispersing risk. Even though the equipment we subscribe to is also subscribed by many other companies, they do a good job spreading those subscriptions across multiple industries and geographies, so that it is highly likely they'd have the equipment you'd need in the event of declaring a disaster
Sungard has also done a good job working with us to break out costs, so that we are able to allocate our invoices amongst multiple products and clients.
Sungard does a good job with security - physical security in the facilities, ensuring our interactions with them through their help desk or portal are secure, maintaining good access control, and providing us with options for ensuring our data is encrypted during testing activities
Anyone with a large disk (VMDK) knows the issues of VMware snapshots. Most backup software is a "point in time backup" that uses snapshots. While the backup can be run multiple times per day the stress of the snapshot on the host and storage is eliminated by the continuous protection of Zerto log replication.
A client had a the disks on a VM go missing for some reason. We had them "flip the switch" for a real fail over and press the fail over button. The VM on our DR site started to come alive as the VM at the customer site was brought down. When the DR VM was fully up, automatic reverse replication started. The DR machine was available in a few minutes (to take into account different host hardware) for access. One the vm at both sites were in sync, we had the customer again repeat the fail over process and the DR site VM was turned off and the Production site VM was brought back on line. This was a 200 GB VM and the whole process was finished in about 3 hours.
Zerto also allows for "Test" fail overs that can be configured on many different functions, such as host, datastore, network and IP usage. Configuring the IPs is crucial to avoid inadvertent site cross contamination of the same VM.
Zerto can also retrieve files from any VM disk on the DR site without starting a VM. Very handy for retrieving files or directories.
Since Zerto is running continuous log replication, changes on the production VM are nearly instantaneously copied to the DR site. As with any data process, having sufficient bandwidth for "churn" peaks minimizes the delay in updating the DR site.
We really like the easy setup of this replication solution, as well as the ease of management. Not to mention, our internal IT Economist determined that the Zerto solution would provide the best ROI out of the competing solutions we analyzed. So far, his calculations have been spot on, and we have saved substantially
Zerto is very easy to implement and support. Uses are broad, only issues are once something doesn't sync it is difficult to get assistance until your reach tier 2 or tier 3 support. Basic file and folder recovery is great. Live and test fail overs are also easy to implement without issue.
Overall support is very good. We sometimes get pushback when asking Level 1 support to escalate to Level 2. This causes undue frustrations when you need a more knowledgeable support person to get involved. We've had to escalate to account reps a few times for this scenario. Zerto is very responsive and normally handles our requests very quickly.
I had used IBM Disaster Recovery Services in a previous job. While I found IBM much quicker to work with in terms of updating our equipment reservations, I've found Sungard much easier to conduct testing with. Specifically, they are much more adaptable and client-focused.
We started out using Backup Exec which was in service until we virtualized our environment where it didn't perform as well at the time. Then we switched to Veeam which worked well, but then as we started needing to do migrations and off-site DR, we found ourselves relying on Zerto more often.
For my organization, the pricing model was an upfront investment for the Zerto licenses. My organization prefers to pay upfront and not deal with month-to-month or year-to-year pricing models that most companies are moving to. But for some, the investment may be more than they can afford, and would prefer the year-to-year pricing model.
I mean, it was 6 years ago, but we were up and going with all applications synchronizing in short order. The longest tasks was getting the 30 TB of application data synchronized between the datacenters.
Zerto is like having the best possible insurance ... it just works, and often provides the backups taken overnight that are key in recovering data/work between overnight backups.
Zerto easily enabled the move of primary datacenters by allowing easy failover to a secondary site, and failback to the primary site.
