Policies Dialog
■ Failover/Move Commit Policy: The commit policy to use during a failover or move operation. The value set here is the default for all failover or move operations from this point on but can be changed when defining a failover or move operation. The following options are available:
■ None: The failover or move operation must be manually committed or rolled back by the user.
■ Commit: After the time specified in the Default Timeout field, the failover or move operation is committed. During the specified time you can check the recovered VPG virtual machines, and you can manually commit or roll back.
■ Rollback: After the time specified in the Default Timeout field the failover or move operation is rolled back, unless you manually commit it or roll it back before the time out value is reached. During the specified time you can check the recovered VPG virtual machines.
■ Default Timeout: The time-out in minutes after which a Commit or Rollback is performed. A value of zero indicates that the system automatically performs the commit policy, without waiting for any user interaction.
■ Virtual Machine Series: The virtual machine series from which to select the size. Azure virtual machine series are optimized for different types of applications. The default is set to DSv2. You can choose the virtual machine series appropriate for the application being protected in the VPG.
■ Virtual Machine Size: The virtual machine size, within the virtual machine series, to assign to recovered virtual machines. Different sizes within a virtual machine series vary, for example in a number of cores, RAM, and local storage size. The default is set to Standard_DS1_v2. You can choose the virtual machine size appropriate for the application being protected in the VPG. The price per virtual machine is related to the virtual machine configuration.
■ Default Script Execution Timeout: The length of time in seconds after which a script times out.
■ Replication Pause Time: The time to pause when synchronizing a VPG if continuing the synchronization will cause all the checkpoints in the journal to be removed.
