Integrated replication / recovery plan ease of use and creation.
Running Production out of DR site
Integrated replication / recovery plan ease of use and creation.
Running Production out of DR site
This product allows organizations to have a solid BC business continuity plan in place in case of disaster. By running regularly scheduled simulated test fail overs a business can realistically plan accordingly and customize their DR strategy.
Perhaps the array replication or vm guest customization features. Perhaps more features are needed to allow
For recovering VMs in situations where replication on production site has been paused for (ie: 1 week or more)
4 years.
Deployment is fairly straight forward but it still requires a good amount of VMware experience on the architecture side to properly deploy and scale.
No issues. Product is fairly stable.
No issues. This product scales according to licenses purchased.
SRM 5.8 scales very well as compared to v5.5
VMware customer service is great.
Technical Support:VMware technical support really delivers.
Previously used Netbackup and Avamar.
Initial setup is straight-forward but you need to really do some research on prerequisite environment config needed for this product to work as developed.
It was implemented in-house and on-site in customer environments.
100% ROI.
Other options evaluated were EMC Avamar and Symantec Netbackup.
You should aspire to be really well versed on supporting this product you need to have in-house engineers that are well rounded in the networking, storage and operational aspects of vSphere/vCenter/SRM. I would recommend getting hands-on training through a VMware a Partner before implementing this product in your environment.
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.
It’s expensive, and we also use Zerto, but good for disaster recovery testing.
Business continuity and disaster recovery, although it’s not fully storage agnostic like Zerto, and we’ve moved away a bit because we use other services for our clients.
I haven’t yet checked out latest version because we’ve been moving away from it, stuck using it for replication clients and it doesn’t work with all storage vendors. There are issues with versioning.
It works great, and does what it’s supposed to. Easy to do disaster revovery test without affecting production.
It's easy to scale, just limited to storage vendors.
Never needed it.
It’s a little complex. Just follow the instructions, but it’s not too complicated once you get connectivity, and it requires multiple vCenters, so that can make it more costly.
Zerto may be more cost efficient, so I’m not 100% sold, and may not need it at all.
SRM is for more higher end customers that can afford to pay for DRaaS. I would think Zerto is much more affordable. For most part Netapp and EMC storage work well with replication. Failover when pre-planned out properly can be seamless recovering some customers entire business in less than 2 hours in some cases. Customers have shown confidence in SRM but its often because the 3rd party DR provider has the expertise to bring out all the value in using SRM.
Originally published in Spanish at https://www.rhpware.com/2015/09/vmware-site-recovery-manager-61
It is well known that VMware Site Recovery Manager is a high availability solution for applications and data transfer in private cloud environments. This is accomplished using isolation and encapsulation of virtual machines, resulting in simplified automation of the processes involved in replication to remote sites. Thus, SRM reduces the costs associated with obtaining efficient Recovery Time Objectives (RTO), providing a robust and standardized solution for business continuity and dramatically reduce the risk of data loss in our VMware virtualized data centers.
Among the features offered by SRM is the ability to create and maintain disaster recovery plans more effective, which do not use written procedures and maintenance costs that this entails, as well as automated processes generate maintenance and testing, which allows our environment thoroughly tested before the event of a disaster.
But these are general skills that we already know and VMware Site Recovery Manager, now is time to see that brought back the brand new version 6.1 of the product. We are going to analyze in further detail what is each of them.
SRM 6.1 incorporates a new type of group policy-based protection. These groups use Storage Profiles provided by vSphere to identify and protect the datastores and virtual machines. This automates the process of adding or removing the protection of VMs and datastores fully integrated and allowing these tasks to monitor vRealize Automation, for example.
Protection groups based storage policies uses vSphere tags (ability to attach metadata inventory of vSphere) with policies, allowing vSphere administrator automate the provisioning of virtual machines meeting the requirements of performance, availability and protection.
The way to do this is:
• Create a tag and associate with datastores in each protection group
• Then, an associate for each protection group policy is created using this tag
• Finally, the protection group is created and associated with the storage policy created in the previous step
Thus, when a virtual machine is associated with this policy it will automatically be protected by SRM. Just simple.
Site Recovery Manager 6.1 is now a complete solution optimized for both the multi-storage as well as to migrate from one place to another, and can also fulfill the function of disaster recovery. In previous versions this was not possible in one product simultaneously. SRM 6.1 supports vMotion between remote vCenters with stretched storage, with the benefits this brings.
This integration allows you to integrate SRM with stretched storage, which could previously only be achieved using vSphere Metro Storage Clusters. The advantages of this new system are:
• Maintenance downtime is eliminated. Recovery plans and orchestration between sites allow vMotion migration of workloads completely transparent to the end user and applications
• Disaster downtime is eliminated. Hot migration of using vMotion between remote sites allows Site Recovery Manager 6.1 eliminate downtime associated with recovery
Having stretched storage added to the deployment of Site Recovery Manager exponentially reduces recovery time in the event of disasters, as workloads are migrated hot, uninterrupted by presenting the same storage architecture at both sites by using synchronous replication, allowing registered and lighted move VMs transparently.
It is no surprise that VMware leads the integration of network virtualization with NSX to all its products, and SRM is no exception. But let's see why.
As in every event of disaster recovery it should be taken into account and fine-tuned the specifics of the network, such as maintaining consistency in IP addresses, firewalls and routing rules previously set, opening ports and other vital aspects. To this we must add that the use of vMotion between vCenters remote requires a Layer 2 network complexity increases significantly.
Now with the availability of newly released NSX 6.2 and many new features were added, Site Recovery Manager is benefited greatly. Now you can use both products together quickly to maintain perfect consistency and efficient networking between sites and perform the migration automatically without worrying about specific aspects of the network, as it has resolved NSX.
In NSX 6.2 can create Universal Logical Switches. Such switches can create Layer 2 networks that exceed the limits of vCenter, which means that when these switches are used with NSX will create a protected port groups connected to the same Layer 2 network.
Thus, when virtual machines are connected to these port groups of a Universal Logical Switch, SRM 6.1 will automatically recognize and not the manual mapping of networks between protected sites will be required. Site Recovery Manager intelligently recognize that it is the same logical network connecting both sites maintain cohesion by creating a single network protected.
This ability to create a Layer 2 network beyond the limits of vCenter eliminates the need to reconfigure IP addresses in case of failure reducing by more than 40% recovery time. In addition, security policies and security groups, firewall rules and edge configurations are preserved in the virtual machines recovered, gaining even more time after a recovery event.
We now know that NSX 6.2 also supports synchronization rules firewalls as well as routing information. This makes it easy to ensure that the configurations in a production network and recovery are kept synchronized making it much easier to create a safe isolation between sites non-disruptively for testing recovery plans.
The implicit network resources mapping, extended capabilities of layer 2 and the testing capacity provided by NSX in conjunction with Site Recovery Manager, added to protection groups based policies radically simplify the administration and operation, low costs associated operations, increased testing capabilities and dramatically reduces recovery times.
As you can see, Site Recovery Manager 6.1 introduces fundamental characteristics that achieve levels of automation until now never seen on the platform, as well as a detailed and comprehensive policy-based control that seamlessly integrate with NSX offer really amazing capabilities face events and disaster recovery between them and turn everything can be done in half the time it took before. We must also not forget the support on extended storage vMotion, which also significantly reduces time and can achieve much lower RTO.
Thanks for reading the article and if you wish you can collaborate sharing on your social networks.
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.
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.
Technical Support: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.
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.
Key feature for me is the ability to test recovery plans with zero impact to the production running environment, this is key for 'what-if’ type analysis and to provide confidence that the platform can be recovered with minimal intervention.
Organisations that have implemented SRM in my experience have confidence that their mission critical systems will be recovered within the given SLA in the event of a planned or unplanned availability event. This avoids costly and time consuming DR recovery tests which are also often unrepresentative of the real scenario.
Smaller sites or sites with mixed storage platforms rely on vSphere replication for DR purposes so additional scalability in this tool would benefit from this.
I have designed and implemented 3 solutions with this product over the last 3 years.
No issues
More around vSphere replication than SRM
VMware Tech Support is excellent.
For VMware environments there is no other option for integrated/automated DR other than 'roll your own.'
SRM setup is straight forward, SRA (storage integration) can be more complex depending on the array in question.
I was working for the vendor.
Consider your storage design and replication policy first and as always make sure you review VMware documentation and HCL for compatibility.
I found implementation very straightforward and configuration as well. This is a great product and has helped us to further our DR strategy. Array based replication is great with our Nimbles.