Veritas™ Resiliency Platform 2.2 Solutions for Microsoft Hyper-V

Last Published:
Product(s): Resiliency Platform & CloudMobility (2.2)
  1. Section I. Overview of Resiliency Platform
    1. Overview of Resiliency Platform
      1.  
        About Veritas Resiliency Platform
      2.  
        About disaster recovery using Resiliency Platform
      3.  
        About Resiliency Platform features and components
      4.  
        About Resiliency Platform capabilities
      5.  
        About managing Hyper-V virtual machines using Resiliency Platform
      6.  
        About permissions for operations in the console
    2. Overview of recovery to on-premises data center
      1.  
        About recovery to premises using third-party replication
      2.  
        Using third-party replication for recovery to premises- an overview
    3. Overview of Amazon Web Services
      1.  
        About recovery to AWS using Resiliency Platform Data Mover
      2.  
        Using Resiliency Platform Data Mover for recovery to AWS- an overview
    4. Overview of vCloud
      1.  
        About recovery to vCloud using Resiliency Platform Data Mover
      2.  
        Using Resiliency Platform Data Mover for recovery to vCloud- an overview
  2. Section II. Preparing your environment
    1. Using array-based replication
      1.  
        Protecting Hyper-V virtual machines using array-based replication - an overview
      2.  
        Configuring Hyper-V virtual machines for disaster recovery using Hyper-V Replica
      3.  
        Configuring Hyper-V virtual machines for disaster recovery using EMC SRDF
      4.  
        Configuring Hyper-V virtual machines for disaster recovery using EMC RecoverPoint
      5.  
        Configuring Hyper-V virtual machines for disaster recovery using Hitachi TrueCopy Universal Replicator
      6.  
        Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
      7.  
        Configuring Hyper-V virtual machines for disaster recovery using IBM SVC Global Mirror
      8.  
        Configuring Hyper-V virtual machines for disaster recovery using IBM XIV Remote Mirror
    2. Managing disaster recovery network mapping
      1.  
        Viewing and configuring network settings for a data center
      2.  
        Editing network settings for a data center
      3.  
        Removing network settings for a data center
      4. Configuring DNS server settings for a data center
        1.  
          Sample command for Windows keytab file
      5.  
        Setting up network mapping between production and recovery data centers
  3. Section III. Working with resiliency groups
    1. Managing resiliency groups
      1. About resiliency groups
        1.  
          Guidelines for organizing resiliency groups
      2.  
        About service objectives
      3.  
        Managing virtual machines for basic monitoring
      4.  
        Starting a resiliency group
      5.  
        Stopping a resiliency group
      6.  
        Displaying resiliency group information and status
      7.  
        Viewing resiliency group details
      8.  
        Editing a resiliency group
      9.  
        Deleting a resiliency group
    2. Configuring resiliency groups for remote recovery
      1.  
        Understanding the role of resiliency groups in disaster recovery operations
      2.  
        How Resiliency Platform configures disaster recovery protection for virtual machines
      3.  
        Prerequisites for configuring Hyper-V virtual machines for disaster recovery
      4.  
        Limitations for virtual machine disaster recovery
      5. Managing virtual machines for remote recovery (DR) using 3rd party replication technology
        1.  
          Target asset selection options
        2. Network customization options
          1.  
            Prerequisites for network customization
      6. Managing virtual machines for remote recovery (DR) in Amazon Web Services
        1.  
          AWS Customization options panel
      7.  
        Managing virtual machines for remote recovery (DR) in vCloud
  4. Section IV. Managing disaster recovery
    1. Rehearsing DR operations to ensure DR readiness
      1.  
        About ensuring the disaster recovery readiness of your assets
      2.  
        Rehearse operations - array-based replication
      3.  
        Prerequisites for rehearsal operation
      4.  
        Performing the rehearsal operation
      5.  
        Performing cleanup rehearsal
    2. Performing disaster recovery operations
      1.  
        Migrating a resiliency group of virtual machines
      2.  
        Taking over a resiliency group of virtual machines
      3.  
        Performing the resync operation
  5. Managing resiliency plans
    1.  
      About resiliency plans
    2. Creating a new resiliency plan template
      1. About manual task
        1.  
          Using manual tasks in resiliency plans
      2. About custom script
        1.  
          Using custom scripts in resiliency plans
    3.  
      Editing a resiliency plan template
    4.  
      Deleting a resiliency plan template
    5.  
      Viewing a resiliency plan template
    6.  
      Creating a new resiliency plan
    7.  
      Editing a resiliency plan
    8.  
      Deleting a resiliency plan
    9.  
      Executing a resiliency plan
    10.  
      Viewing a resiliency plan
    11.  
      Creating a schedule for a resiliency plan
    12.  
      Editing a schedule for a resiliency plan
    13.  
      Deleting a schedule for a resiliency plan
    14.  
      Viewing a schedule for a resiliency plan
  6. Monitoring risks, reports, and activites
    1.  
      About the Resiliency Platform Dashboard
    2.  
      Understanding asset types
    3.  
      Displaying an overview of your assets
    4.  
      About risk insight
    5.  
      Displaying risk information
    6.  
      Predefined risks in Resiliency Platform
    7.  
      Viewing the current risk report
    8.  
      Viewing the historical risk report
    9.  
      Viewing reports
    10.  
      Managing activities
    11.  
      Viewing activities
    12.  
      Aborting a running activity
  7. Managing evacuation plans
    1.  
      About evacuation plan
    2.  
      Generating an evacuation plan
    3.  
      Regenerating an evacuation plan
    4.  
      Performing evacuation
    5.  
      Performing rehearse evacuation
    6.  
      Performing cleanup evacuation rehearsal
  8. Appendix A. General troubleshooting
    1.  
      Viewing events and logs in the console
    2.  
      Events in Hyper-V virtual machines disaster discovery
    3.  
      Configure DR operation fails with an integration services error
    4.  
      Manually cleaning up virtual machines
    5.  
      Troubleshooting delete resiliency group operation
  9. Appendix B. Sample policy and trust relationships for AWS
    1.  
      Sample policy statement for AWS
    2.  
      Sample trust relationship for AWS
  10.  
    Glossary

Troubleshooting delete resiliency group operation

While performing the delete resiliency group operation, if any of the sub-tasks fail, you can perform the following steps to reclaim the resources.

Perform the following tasks on Replication Gateways on the production and Cloud data center

  1. Check for participating consistency groups.
    /opt/VRTSsfmh/bin/xprtlc -l http://localhost:8080/ConsistencyGroup
  2. Verify that replication is stopped on the gateway.
    /opt/VRTSsfmh/bin/xprtlc -l 
    http://localhost:8080/ConsistencyGroup/<CG_ID>/state
  3. Abort replication on gateway if replication is not stopped.
    /opt/VRTSsfmh/bin/xprtlc -m POST -l
    http://localhost:8080/ConsistencyGroup/<CG_ID>/abort
  4. Delete the consistency groups.
    curl -X DELETE 
    http://localhost:8080/ConsistencyGroup/<CG_ID>/delete

Perform the following tasks on the hosts on the production data center

  1. Verify that the consistency groups are deleted.

    Linux host:

    /opt/VRTSitrptap/bin/vxtapinfo status

    Windows host:

    C:\Program Files\Veritas\VRTSitrptap\cli\vxtapinfo status
    
  2. Delete the consistency groups if the state is active.
    • Linux host:

      /opt/VRTSitrptap/bin/vxtapaction stop -cg <CG_ID>
      /opt/VRTSitrptap/bin/vxtapconfigure delcg -cg <CG_ID> -force
    • Windows host:

      C:\Program Files\Veritas\VRTSitrptap
      \cli\vxtapaction stop -cg <CG_ID>
      C:\Program Files\Veritas\VRTSitrptap
      \cli\vxtapconfigure delcg -cg <CG_ID> -force
  3. Verify that the journal disk is removed from each of the virtual machines on the production data center.

    Size of the journal disk is usually 1 GB and naming format is:

    [<datastore-name>] <vm-hostname>/drl-<uuid>/ITRPSRDRLDisk.vmdk

    Remove the journal disk using vSphere client or Hyper-V UI.

    Ensure that the file is deleted.

  4. Unconfigure network setting on the virtual machines on the production data center.
    • Linux host:

      /opt/VRTSsfmh/bin/perl
       /opt/VRTSsfmh/util/reconfig_vm_settings_on_prim  -unconfigure
    • Windows host:

      C:\Program Files\Veritas\VRTSsfmh\bin\perl.exe
       C:\Program Files\Veritas\VRTSsfmh\util
       \reconfig_vm_settings_on_prim -unconfigure
  5. For physical machines, you need to unsign the DRL disk:
    • Linux host:

      Get the device name of DRL disk by executing the following command:

      /opt/VRTSitrptap/bin/vxtapdrlfind

      Execute the following command to unsign DRL disk:

      /opt/VRTSitrptap/bin/vxtapdrlsign clear -drl_dev device_name

      Where, device_name is the device name of the DRL disk.

    • Windows host:

      Get the device name of DRL disk by executing the following command:

      C:\Program Files\Veritas\VRTSitrptap\cli\vxtapdrlfind.exe

      Execute the following command to unsign DRL disk:

      C:\Program Files\Veritas\VRTSitrptap\cli\vxtapdrlsign clear
       -drl_dev device_name

      Where, device_name is the device name of the DRL disk.

  6. Refresh the virtualization server if the resiliency group contains virtual machines.

Perform the following on cloud virtual machines:

  • Verify that the migrated cloud virtual machines are terminated and their volumes are deleted, including the Replication block tracking disk.

    Note that the naming convention for Replication block tracking disk is DRLVolume_RaaS_<GUID> whereas for other disks the name starts with resiliency-group-name_virtual-machine-name.

  • Delete any snapshots for cloud volumes.

  • Detach the cloud volumes from the cloud gateway.

  • Remove the cloud virtual machines from the cloud IMS.