Power On Virtual Standby Virtual Machines › How to Power On Remote Virtual Standby Virtual Machines › Protect Remote Virtual Standby Virtual Machines After it is Powered On

Protect Remote Virtual Standby Virtual Machines After it is Powered On

After a Remote Virtual Standby virtual machine is powered on, the CA ARCserve D2D backup job and the Virtual Standby job do not run as they were scheduled. If you want to resume the jobs after the Remote Virtual Standby virtual machine is powered on, do the following actions:

1. Modify the VM Name Prefix in the Virtual Standby policy.

   When CA ARCserve Central Virtual Standby powers on Remote Virtual Standby virtual machines, the application defines the virtual machine names of the powered on remote virtual machines as the concatenation of the VM Name Prefix option specified in the Virtual Standby policy and the host name of the source node.

   Example:

   • VM Name Prefix: AA_
   • Host name of the source node: Server1
   • Virtual machine name of the Virtual Standby virtual machine: AA_Server1

   After the Remote Virtual Standby virtual machines are powered on, virtual machine name conflicts can occur when you do not modify the VM Name Prefix in the Virtual Standby policy. Problems of this type occur when the source nodes and the Remote Virtual Standby virtual machines reside on the same hypervisor.

   For information about modifying the VM Name Prefix in the Virtual Standby policy, see Edit Policies. If necessary, you can update other Virtual Standby policy settings. Optionally, you can create a new Virtual Standby Policy to protect the Remote Virtual Standby virtual machine. For information about creating new policies, see Create CA ARCserve Central Virtual Standby Policies.

2. After you update the policy or create a new policy, deploy the policy to the Remote Virtual Standby virtual machine. For more information, see Deploy Policies.
3. After you deploy the policy to the Remote Virtual Standby virtual machine, resume the Virtual Standby job. For more information, see Pause and Resume Virtual Standby Jobs.
4. After you deploy the policy, log in to CA ARCserve D2D on the Remote Virtual Standby virtual machine and schedule a repeat method for the CA ARCserve D2D backup job. For more information, see the CA ARCserve D2D User Guide.

Note: CA ARCserve Central Protection Manager and CA ARCserve Central Virtual Standby have a mechanism that lets you automatically resynchronize the policies to the managed CA ARCserve D2D nodes on a weekly basis. This mechanism lets CA ARCserve Central Protection Manager restart the backup jobs on the Remote Virtual Standby virtual machines by redeploying the policy that was in effect on the CA ARCserve D2D node to the Remote Virtual Standby virtual machine. The policy deployment process behaves in this manner because the source node and the Remote Virtual Standby virtual machine have the same host name, which lets CA ARCserve Central Protection Manager resynchronize the policy. The only limitation to this behavior is the CA ARCserve Central Protection Manager server and the Remote Virtual Standby virtual machine must be able to communicate with each other through the network. After CA ARCserve Central Protection Manager resynchronizes and deploys the policy to the Remote Virtual Standby virtual machine, you then resume the Virtual Standby job on the Remote Virtual Standby virtual machine. For more information, see Pause and Resume Virtual Standby Jobs.