Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated for July 2019 release - added re-ip section


  • Cloud Server usage for servers involved in a DRS for Cloud Consistency Group
    • Source Server is attributed usage “normally” for resources used
    • Target Server is attributed usage for resources used:
      • When in "DRS Mode"
        • 1 x “Standard” vCPU, 1 x GB RAM and all storage with the appropriate disk speed 
        • No Priced Software charges apply in this state.
      • When In "Preview" mode and after "Failover" is initiated:
        • “Standard” vCPU / RAM usage for the running configuration (that matches Source Server) and all storage with the appropriate disk speed 
        • Priced Software charges that match the paired Source Servers.
  • DRS for Cloud usage in addition to the usage above
    • Storage allocated to the recovery journals for the Consistency Group in the Source and Target locations contribute usage equal to their size under the DRS Storage Hours usage element, computed as hourly usage based on the amount of journal storage. This usage is attributed to each Source/Target location where the journal storage is used.
    • DRS Source Server Hours usage element is incurred hourly for each Source Server in the Consistency Group. This usage is allocated to the Source Data Center location

Re-IP Address Rules for DRS Target Servers

When a DRS Consistency Group Failover Preview is initiated, the system copies the VMDKs from the Source Server to the Target Server across all server pairs. Since the underlying disks in Target Servers are the same as Source Servers, each Target Server NIC will inherit the same IPv4 and IPv6 addresses as the Source Server in that pair. In the case of IPv4 addresses, this may be undesirable because the target Network Domain and VLAN architecture may not be the same as the source environment, in which case, the Target Server NIC's IPv4 addresses will not work as intended. IPv6 addresses should never work on the Target VLAN since IPv6 addresses are globally unique.

To address this limitation, the system includes a feature which allows users to define NIC configurations to be applied to Target Servers after the Preview is complete. With this feature, the user can also adjust DNS and few other guest-level settings. For each Server Pair in a Consistency Group, the user can view, and optionally change NIC configurations for all Target Server NICs. Following is a list of settings that can be changed on a Target Server:

  1. Hostname - Text field, for the hostname to be applied to the Target Server. Required for Linux OS. 
  2. Domain - Text field for the Domain to be applied to the Target Server. Required for Linux OS.
  3. DNS Server - Text field, a series of IPv4 or IPv6 addresses to be applied to the Target Server. Required for all OS types.
    1. On Linux, DNS is a server level setting. On Windows, there is a DNS entry per NIC. DRS follows this convention, and while DNS Server Addresses have a single field for the entire server, DRS will apply them to each NIC for Windows servers.
  4. DNS Suffix Search Order - Determines the DNS suffixes to attach to an unqualified single-label name before submission of a DNS query for that name.
    1. This entry can be blank.
  5. NetBIOS - Selector, which defines whether NetBIOS is enabled or disabled on the Target Server.

The following settings can be changed for each NIC on the Target Server:

  1. Re-IPv4 - new IPv4 address that will be set for that NIC on the Target Server.
  2. Prefix - new IPv4 Suffix that will be set for that NIC on the Target Server.
  3. Re-IPv4 Gateway - new IPv4 Gateway address that will be set for that NIC on the Target Server.

titleImportant Note

These settings will be available to edit as of July 9, 2019. At that time, these settings will only be editable via API. UI support for editing these settings will be available in late August, 2019.

See API 2

Recently Updated

Content by Label
cqllabel in ("intro-mcp-2-0","drs")
labelsdrs intro-mcp-2-0