All How do I protect Virtual Machines hosted on Hyper-V Clusters with ARCserve?

How do I protect Virtual Machines hosted on Hyper-V Clusters with ARCserve?

| Written by some jerk | Print | Email | Hits: 270
A ARCserve Backup Version: This document is applicable to all versions of ARCserve Backup unless you find content which is version specific.
CA ARCserve Backup Agents and Options: Agent For Virtual Machines
CA ARCserve Backup Task: Configuration, Backup Operation

 

Document ID:    TEC504017

Tech Document
Title:  FAQs with regards to Hyper-V clustered environment and the CA ARCserve agent for Virtual Machines.

  1. How do I protect Virtual Machines hosted on Hyper-V Clusters?
    • Install the VM agent on both the nodes of the Hyper -V Cluster Nodes.
    • Populate the VMs from the Hyper -V Configuration Tool.

      Figure 1

      Figure 2
    From the screenshot, HYPER-V-NODE-A and HYPER-V-NODE-B are the physical nodes of the Hyper -V cluster, and the VMs are present under the tree.
  2. Will the Virtual Machines that move between the nodes of the Hyper-V cluster be populated/ enumerated automatically by the VM agent?
    • Both the nodes of the Hyper -V cluster have to be selected dynamically.
    • The VMs will be populated automatically based on the "Auto-populate VM" available in the Hyper- V configuration tool. This can be set as required.
    Note: When this auto-populate occurs, by default it uses the 'Retain VM information' in the ARCserve Database. To disable the 'Retain VM information', fix T5OV007 can be incorporated. (CA Support needs to be contacted for this fix). This fix is applicable for 12.5 only and it has been included in newer versions.
  3. How to protect Virtual Machines residing on a CSV (Clustered Shared Volume) in a Hyper-V clustered environment?

    CSV is a feature available with Windows 2008 R2 provides. To protect the VMs in CSV:
    • Install VM agent on both nodes of the cluster.
    • Populate the VMs from the Hyper-V Configuration tool.
    • The Hyper V cluster physical nodes (HYPER-V-NODE-A and HYPER-V-NODE-B) have to be selected dynamically.
    • The Hyper V cluster nodes (HYPER-V-NODE-A and HYPER-V-NODE-B) have to be backed up sequentially ie. They mustnot be backed up concurrently via multiplexing or streaming jobs.
  4. Is the Hyper -V cluster virtual name of any relevance?

    Some clients pose this question since for database agents we recommend backing up via the Virtual Node name of the Cluster.

    With VM agent only the physical node names of the Hyper-V cluster are of relevance and the virtual node names of the Hyper- V cluster are not relevant.

 

 More Information

 

Overview and Limitations of Cluster Shared Volumes (CSV)

http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=1229