One View and Disaster Recovery Considerations and Requirements
You should be aware of the following important One View and Disaster Recovery considerations and requirements.
System and Configuration Requirements
- If you plan to enable Disaster Recovery, do not install the One View appliance, or virtual machine (VM), on the everRun system where your primary VMs are running. Otherwise, the One View Console will be unavailable for DR failover operations in the event of a failure at the primary site. Instead, install the One View appliance on the everRun system (or on an Avance or Virtual Box system) at the DR site.
- Do not enable DR protection for the One View appliance.
- Only one-to-one Disaster Recovery configurations are supported. An everRun system's DR protected VMs must all be protected on the same everRun system at the DR site. The DR site system can protect VMs from only one other everRun system.
- The physical machine (PM) on which a DR VM is running must have the same amount of resources as one of the two source PMs.
- The everRun system at the DR site must be a simplex system with only a single PM.
Software Configuration Limits and Considerations
- One View supports the monitoring of only everRun 7.2 systems.
- The Stratus One View Console supports the monitoring of up to 64 systems.
-
One everRun system can have a maximum of 6 DR protected VMs.
Note: Although the system will allow you to configure more than the maximum number of DR protected VMs, do not configure more than 6 .
-
A DR protected VM can have a maximum of 6 volumes.
Note: Although the system will allow you to configure more than the maximum number of volumes, do not configure more than 6.
-
The default RPO is 1 hour. The minimum RPO is 15 minutes. The maximum recommended RPO is 24 hours.
- A DR VM can retain a maximum of 12 snapshots.
-
You cannot reprovision a DR protected VM.
Related Topics
Disaster Recovery Terminology
Configuring and Maintaining Disaster Recovery
Installing the Stratus One View Console