VMware Live Recovery Reviews

The primary use for us is to replicate without automatization.

The AC replication is integrated with a software base, set up cost, and easy installation and configuration.

When starting up the replication and converting it to the virtual machine I had some problems. I had to start the process again and that is inconvenient.

I have been using VMware Disaster Recovery for the past five years.

The initial setup is easy depending on the environment you are working with.

I would rate Speaker VMware Disaster Recovery a ten out of ten.

It gives us a disaster recovery solution for different sites.

It looks good, but synchronization is, sometimes, a problem. Hence it should be totally dependent on storage.

I've used it for three years.

We faced issues as it is highly dependent on the platform in use.

It's very good.

It was complex as it does not include a good, extensive feasibility and compatibility guide.

We used a vendor team who were very good.

It is quite good on ROI and year on year it is about 50%.

vCloud SRM is a good solution, but it is costly when compared to other solutions like Nutanix.

We didn't evaluate other solutions.

Choosing VMware in general, is best in terms of functionality, but it is not necessarily cost effective, as their licensing and setup costs are too hight. Maybe we will see more products for cloud and automation.

Cost

We have had some customers that were hit with some random wear and we were able to restore the files from SRM with minimal downtime.

Nothing I have run into as of yet.

About 8 months.

It was deployed prior to my arrival with the company.

None encountered.

None encountered.

We use several solutions. We determine what is best for the customer and present them with the solutions we believe fit their needs best.

Do an analysis of what you need. Weigh the pros and cons of each solution and use what is going to work best for you.

Ability to support DR.

We have a fully functioning DR environment.

The setup documentation needs to be improved greatly.

Only the fact that I had scour the Internet to find the proper setup information.

No issues encountered.

No issues encountered.

Average.

Well the tech I spoke to did not know how the setup should be implemented, until I found the literature myself.

Did not use a previous solution.

Complex - settings for the sql db were not documented - had to search a lot for those.

I implemented the product.

Very good - we have a DR platform that we've tested with a live production workflow.

No others were evaluated.

Gather the proper setup information.

We use VMware Cloud Disaster Recovery as a disaster recovery service and backup as a service.

The most valuable features are the backup and disaster recovery services.

VMware Cloud Disaster Recovery could improve by enhancing the network bandwidth from the storage.

In a future release, I would like to see new functionality or current feature enhancements.

I have been using VMware Cloud Disaster Recovery for a few years.

I have found VMware Cloud Disaster Recovery to be stable.

The scalability of VMware Cloud Disaster Recovery is very good.

We have customers in the medium to large-scale enterprise companies.

The technical support provided by VMware is one of the best I have used.

I have used many similar solutions to VMware Cloud Disaster Recovery, such as Veeam and Citrix.

The installation is normally simple for users to fully implement.

The price of VMware Cloud Disaster Recovery should be lowered in order to compete better in the market.

I rate VMware Cloud Disaster Recovery a nine out of ten.

• Fast recovery time
• Ease of use

• Easy to use
• Easy to document
• Easy to report
• Easy access to history

I can’t think of any right now, honestly.

I would give it a 7/10 for stability. It can be really bad, but generally fine, and we look at the availability when choosing new products.

It does have some limitations, but I would give it a 6/10.

Sometimes it’s good, sometimes it’s bad. It’s just luck of the draw.

We previously used Zerto. We switched because VMware only has a single point of support, as we needed to move forward with better products.

It was fairly straightforward, I would give it a 7/10.

Cisco – I’m not sure, it was there before I was there.

You have to pick whatever it best for their environment and their applications. That solution has to be able to fit, and VMware fit into ours.

Test run in protected environment

More confidence over DR services

vSphere Replication feature

Four years.

We had an issue with the Array SRA.

We had a problem connecting to the SRM plug-in.

No issues encountered.

Good.

Average.

No previous solution used.

Initial set-up was straightforward.

We used a vendor that was good.

Do a POC whilst keeping the environmental constraints in mind.

Disaster recovery of a failed site.

None, I implement this product for customers.

Storage integration.

5 years.

The integration (SRA’s) with storage and it’s versions.

None encountered.

None encountered.

9 out of 10.

9 out of 10.

Just a regular backup product. But this wasn't a disaster recovery solution.

A SRM implementation is not difficult. Getting the business requirements is more of a challenge.

I was the implementor.

For most customers about 2 years.

I don’t know as it depends on the customer.

Nope, I was asked to implement this solution.

Know your business requirements.