Site Recovery Manager can be used in different scenarios based on customer objectives.
1. Active - Passive
In a Active-passive scenario there is a production site running applications and services and a secondary or recovery site that is idle until needed for recovery. In this scenario, Dedicated resources in DR site such as Server and Storage aren't that utilized much of the time.
2. Active - Active
Site Recovery Manager can be used in a configuration where low-priority workloads such as test and development run at the recovery site and are powered off as a part of the recovery plan. This allows for the utilization of recovery site resources.
3. Bi-directional
Production applications are operating at both sites Site Recovery Manager support protecting virtual machines in both directions. (eg. Virtual machines at Site A protected at Site B and virtual machines at site B protected at site A)
4. Stretched Storage
Site Recovery Manager supports using stretched storage. A stretched cluster offers the advantage of enabling easy migration of virtual machines from one geographic location to another while maintaining network connections with the other servers within the cluster.
5. Multi-Site
Site Recovery Manager is capable of supporting additional configurations like shared Recovery, where multiple remote sites are protected by a single recovery site.
Comments