Create Content

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added warning

...

Info
titleDescription

This article describes how to create a DRS Consistency Group. Consistency Groups are the core construct of the DRS for Cloud service and consist of a series of "paired" Cloud Servers. Cloud Servers are added to Consistency Groups in pairs - one "source" server and one "target" server. All of the Source Servers must be in the same location and all of the Target Servers must be in the same location.

For more information on Consistency Groups, see Introduction to DRS for Cloud


Warning
titleImportant Note

Unlike most CloudControl functions, only Primary Administrators or sub-administrators with the DRS role will even see the DRS for Cloud menu that is needed to view and manage the DRS for Cloud functions. Ensure your users have the proper roles assigned - see How to Manage the Primary Administrator User and other Sub-Administrators as the Primary Administrator

Note that even when the roles are assigned, the menu appears only where the feature is available

Prerequisites:

  1. Only the Primary Administrator or a user with the DRS role can create a Consistency Group
    1. For instructions on how to add Roles to a Sub-Administrator, see How to Manage the Primary Administrator User and other Sub-Administrators as the Primary Administrator
  2. All proposed Source Server(s) must be in the same MCP 2.0 Network Domain or MCP 1.0 Network (note this implies the same location)
  3. All proposed Target Server(s) must be in the same MCP 2.0 Network Domain or MCP 1.0 Network (note this implies the same location)
  4. Both the Source and Target Locations (implied from the MCP 2.0 Network Domain or MCP 1.0 Network above) are:
    • In different Locations 
    • Not in Hypervisor maintenance
    • Not in DRS maintenance
    • Enabled for the vendor for DRS
  5. The Target Location must be an available Target for the Source Location
  6. All proposed Source Server(s) must be running
  7. All proposed Target Server(s) must be DRS eligible – see How to Manage DRS Eligibility of a Cloud Server for more information
  8. Journal Size must be within the range supported in both the Source and Target Locations
  9. Target Server(s) must match their paired Source Server(s) in terms of the following parameters:
    1. Target Servers must have the same number of SCSI, IDE, SATA, and Floppy Controllers in the same Bus ID as those on the paired Source Server
      1. In addition, for SCSI Controllers, the "adapter" type (BUS_LOGIC, LSI_LOGIC_PARALLEL, etc) on each controller must also match
    2. All of the Target Server local disks must be the same Size and be placed in the SCSI/SATA/IDE Controller and position as the paired Source Server
      1. However, the Disk Speeds on the Target Server do NOT need to match Source Server
    3. NIC Configuration
    4. NIC Key/NIC ID - To identify the NIC Key/NIC ID, see: Navigating the Server Dashboard
    5. Network Adapter - See: How to Change the Network Adapter of a NIC on a Cloud Server
  10. It is NOT required that Target Servers match their Source servers in terms of the following parameters:
    1. The same CD-ROM devices do not need to exist in the same slots on any IDE/SATA controller of the Target Server as exist on the paired Source Server
    2. ISO files do not need to exist on any CD-ROM of the Target Server to match what exists on the Source Server
    3. FLP files do not need to exist on any Floppy Drive of the Target Server to match what exists on the Source Server
  11. IMPORTANT NOTE - REPLICATION LIMITATIONS RELATED TO CD-ROM AND FLOPPY:
    1. CD-ROM devices and any attached ISO are NOT replicated. Any devices or ISO on the Target Server remain unchanged after Failover.
      1. It does not matter if these devices exist in matching slots in the Target Server
    2. Floppy controllers and any attached FLP are NOT replicated. Any FLP on the Target Server remain unchanged after Failover
      1. It does not matter if these devices exist in matching slots in the Target Server
  12. You can not create a Consistency Group if the Cloud Server Snapshot Feature is enabled on the Target Server. See How to Disable Cloud Server Snapshots on a Server
    1. However, you CAN create a Consistency Group if the Cloud Server Snapshot Feature is enabled on the Source Server.
  13. A Server cannot be a Source Server or a Target Server if it is in Snapshot Preview. You must first migrate the Snapshot Preview Server to a Normal Server. See Introduction to Cloud Server Snapshot Feature
  14. You cannot create a Consistency Group if one (or more) of the Servers are in a state which requires it to be restarted. See the "Adding and Managing Disks" section of Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds
  15. DRS Journal Size must be between 100 GB and the lesser of the maxSizeGb in the Source and Target Location
    1. Sizes must be specified in 100 GB increments

...