KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : How to understand FSHA to Hyper-V

Last Update: 2016-04-25 13:51:45 UTC

Products Applicable: CA ARCserve RHA r15.3

Note: There are some different in some steps and files between r15.3 and other build

Description:

This document explains some knowledge about FSHA to Hyper-V

  1. What is in this file 'signatures.dat' under “C:\Program Files\CA\ARCserve RHA\Engine\vm\signatures.dat” on replica?

The file is a temp file used when generate disk signature. We generate a random signature, and store the signature to this file. When we generate a new disk signature, we will compare the signature to the ones in this file, make sure no duplicate signature used.

2.Do we use znet protocol to transfer metadata?

The disk metadata is transferred to replica as a z_file_c, so that, we use znet protocol to transfer that.

3.What is vpdata folder  under “C:\Program Files\CA\ARCserve RHA\Engine\vm\scenarioid\”?

The folder  is used as a data_path for the virtual platform information.
The path is never used after RHA r15.3 build. Virtual platform information was stored in a file named scenarioid_vps.dat under C:\Program Files\CA\ARCserve RHA\Engine\vm\scenarioid\

4. What are the exact steps done by RHA when an AR test is run?

  1. Create snapshot for volumes 
  2. Create VM if not already existed
  3. Change the following in VHD:
  •     Modify disk signature in registry HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
  •    Update disk signature in BCD file if OS >= Vista
  •    Update IDE driver, this includes the registry node  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services
  •    Disable cdrom auto run. Just change the value “Autorun” in regidtry node “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\cdrom” to 0.
  •    Disable RHA engine
  •    Enable CA Full system HA helper
  •    Delete config_25000
  1. Detach VHD file from the physical machine
  2. Attach the vhd file to VM
  3. create a internal  virtual network for AR
  4. Attach Integration tool disk cdrom, it is “C:\\windows\\system32\\vmguest.iso” for Hyper-V
  5. Turn on VM, and Service CA Full system HA helper started automatically. It will:
  • Online disks if they are not online.
  •  Install integration tools, start integration service,
  •  remove Service CA Full system HA helper from SCM.

         i. after AR stopped, first stop VM, then disconnect inter network, then revert to snapshot if any, detach the vhd file from VM, unregister VM, and attach the VHD on the physical machine.

5.What are the exact steps done by RHA when a failover is initiated?

      a.Save customized network settings to folder “C:\Program Files\CA\ARCserve RHA\Engine\vm\\C\p2v_config.dat”, this file will be used for ws_rep.exe.

  1. Create VM if not already existed

       c. Change the following in VHD:

  •     Modify disk signature in registry HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
  •    Update disk signature in BCD file if OS >= Vista
  •    Update IDE driver, this includes the registry node  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services
  •    Disable cdrom auto run. Just change the value “Autorun” in regidtry node “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\cdrom” to 0.
  •    Disable RHA engine
  •    Enable CA Full system HA helper
  •    Delete config_25000
  1.  Detach VHD file from the physical machine
  2.  Attach the vhd file to VM

        f.read the network mapping infomation, and attach network adapter to VM

        g.Attach Integration tool disk cdrom, it is “C:\\windows\\system32\\vmguest.iso” for Hyper-V

         h.Turn on VM, and Service CA Full system HA helper started automatically. It will:

  • Online disks if they are not online.
  • Install integration tools, start integration service
  • remove Service CA Full system HA helper from SCM.

More Information:

How to configure a Full System HA Scenario: Video

https://arcserve.zendesk.com/hc/en-us/articles/202805925

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments