SALES: 1-800-867-1380

Step 3: Configure protection settings for VMM clouds

Updated: September 10, 2014

After you’ve installed the Provider on Virtual Machine Manager (VMM) servers and registered the servers in the vault, you can configure protection settings for the VMM clouds that appear in the Protected Items tab.

  1. Read Deployment prerequisites to verify that clouds are configured correctly.

  2. Check that clouds appear in the vault. Clouds are detected either by selecting to synchronize all clouds when you install the Provider, or by selecting to synchronize a specific cloud on the General tab of the cloud properties in the VMM console.

  3. During cloud configuration, you set up initial replication of virtual machine data over the network or offline. The network option copies data over the network, and can be time consuming and resource intensive. Use this option if virtual machines have fairly small virtual hard disks and sites are connected with sufficient bandwidth. Schedule the initial replication at an off-peak time.

    Offline replication—Offline replication uses external media and is useful for low bandwidth and geographically remote locations. . To configure, see Prepare for offline initial replication.

  1. On the Quick Start page, click Set up protection for VMM clouds.

  2. In the Protected Items list, select the cloud that you want to configure and go to the Configuration tab.

  3. In Target, select VMM server.

  4. In VMM Server, select the VMM server in the secondary site.

  5. In Target cloud, specify the target cloud that will be used for failover of virtual machines in the source cloud.

  6. In Copy frequency, specify how frequently data should be synchronized between source and target locations. This setting is relevant only for Hyper-V host servers that are running on System Center 2012 R2. For other servers a default setting of five minutes is used.

  7. In Additional recovery points, specify whether you want to create additional recovery points (from 0-15). Additional recovery points contain one or more snapshots, and they enable you to recover a snapshot of a virtual machine from an earlier point in time.

    With a setting of zero, only the latest recovery point for a primary virtual machine is stored on a replica host server. If you configure a setting greater than zero, the number of recovery points will be created in accordance with this value. Note that enabling multiple recovery points requires additional storage for the snapshots that are stored at each recovery point. By default, recovery points are created every hour, so that each recovery point contains an hour’s worth of data. The recovery point value that you assign for the virtual machine in the VMM console should not be less than the value that you assign in the Azure Site Recovery console.

  8. In Frequency of application-consistent snapshots, specify how often to create application-consistent snapshots. Hyper-V uses two types of backups—a standard backup that provides an incremental backup of the entire virtual machine, and an application-consistent snapshot that takes a point-in-time snapshot of the application data inside the virtual machine. Application-consistent snapshots use Volume Shadow Copy Service (VSS) to ensure that applications are in a consistent state when the snapshot is taken. Note that if you enable application-consistent snapshots, it will affect the performance of applications running on source virtual machines.

    Cloud settings - on-premises to on-premises
  9. In Data transfer compression, specify whether replicated data that is transferred should be compressed.

  10. In Authentication, specify how traffic is authenticated between the primary and recovery Hyper-V host servers. If you select HTTPS, the host servers will authenticate each other using a server certificate, and traffic is encrypted over HTTPS. If you select Kerberos, a Kerberos ticket will be used for mutual authentication of the host servers. By default, port 8083 and 8084 (for certificates) will be opened in the Windows Firewall on the Hyper-V host servers. Note that traffic will be sent over HTTP. This setting is relevant only for VMM servers running on Windows Server 2012 R2.

  11. In Port, modify the port number on which the source and target host computers listen for replication traffic. For example, you might modify the setting if you want to apply Quality of Service (QoS) network bandwidth throttling for replication traffic. Check that the port isn’t used by any other application and that it’s open in the firewall settings.

  12. In Replication method, specify how the initial replication of data from source to target locations will be handled, before regular replication starts:

    • Select Over the network to copy initial replication data over your network. You can specify that the copy should start immediately, or select a time. We recommend that you schedule network replication during off-peak hours.

    • Select Offline to perform the initial replication using external media. You specify the export location on the source cloud, and the import location on the target cloud. When you enable protection for a virtual machine, the virtual hard disk is copied to the specified export location. You send it to the target site, and copy it to the import location. The system copies the imported information to the replica virtual machines.

    • Select Delete replica virtual machine to specify that the replica virtual machine should be deleted if you stop protecting the virtual machine by selecting the Disable protection for the virtual machine option on the Virtual Machines tab of the cloud properties. With this setting enabled, when you disable protection the virtual machine is removed from Azure Site Recovery, the Site Recovery settings for the virtual machine are removed in the VMM console, and the replica is deleted.

Cloud settings

After you configure cloud protection settings, all clusters and host servers that are configured in the source and target clouds are configured for replication. You can modify cloud settings on the Configure tab. To modify the target location or target cloud, you must remove the cloud configuration and then reconfigure the cloud.

You’ll need to do a number of actions to prepare for initial replication offline:

  • On the source server, you’ll specify a path location from which the data export will take place. Assign Full Control for NTFS and Share permissions to the VMM service on the export path. On the target server, you’ll specify a path location from which the data import will occur. Assign the same permissions on this import path.

  • If the import or export path is shared, assign Administrator, Power User, Print Operator, or Server Operator group membership for the VMM service account on the remote computer on which the shared is located.

  • If you are using any Run As accounts to add hosts, on the import and export paths, assign read and write permissions to the Run As accounts in VMM.

  • The import and export shares should not be located on any computer used as a Hyper-V host server, because loopback configuration is not supported by Hyper-V.

  • In Active Directory, on each Hyper-V host server that contains virtual machines you want to protect, enable and configure constrained delegation to trust the remote computers on which the import and export paths are located, as follows:

    1. On the domain controller, open Active Directory Users and Computers.

    2. In the console tree, under DomainName, click Computers.

    3. Right-click the Hyper-V host server name, and then click Properties.

    4. On the Delegation tab, click Trust this computer for delegation to specified services only.

    5. Click Use any authentication protocol.

    6. Click Add, and then click Users and Computers.

    7. Type the name of the computer that hosts the export path, and then click OK.From the list of available services, hold down the CTRL key and click cifs, and then click OK. Repeat for the name of the computer that hosts the import path. Repeat as necessary for additional Hyper-V host servers.

After you configure cloud protection settings, proceed to Step 4: Configure network mapping: On-premises to on-premises.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft