HOWTO: How to Perform a Test Failover to Bring Up the Target VM in Production

  • 7005622
  • 02-Apr-2010
  • 21-Oct-2013


NetIQ PlateSpin Forge
NetIQ PlateSpin Protect


If a Test Failover is run in a production environment there is a possibility that the source server's computer account in Active Directory (AD) will be moved to the target virtual machine being restored. This can cause problems in a production domain.

NOTE: It is recommended to run Test Restores for DR contracts in an isolated network to prevent adverse effects to the production environment.


Solution 1:
Specify a hostname, within the Network Identification section, that is different from the source hostname when setting up the protection contract.  This hostname will be used by the target VM for testing.
Solution 2:
When configuring the workload do not enter DNS information in the Test Failover settings.
To configure the target VM to be failed over to a specific Organizational Unit (OU) within AD there are two options:
1. Prior to the first Test Failover, create a computer account within the appropriate OU in AD with the same hostname as specified for the target VM in the protection contract. Failovers and Test Failovers will use and update this account.
2. After the Test Failover has run and created the new computer account in AD, move the computer account to the required OU.
The account specified in the Test Restore must have the appropriate permissions on the OU in question to create, modify, and remove objects from the OU.
NOTE: If a Full Restore is required in DR situation, set the hostname same as the hostname of source machine when configuring the final restore job. This will ensure that the source server's domain registration is brought over to the target virtual machine as it replaces the source in production.