More about Hyper-V Off-host Backups

Article:TECH183154  |  Created: 2012-03-07  |  Updated: 2012-03-09  |  Article URL http://www.symantec.com/docs/TECH183154
Article Type
Technical Solution


Issue



Off-host backup is the process of initiating/creating a backup from an alternate NetBackup client to reduce the backup load from the primary Hyper-V host.

  • Off-load Hyper-V VM backup to the alternate host
  • Alternate Client/Media Server combination reduces need for Media Server installation on Hyper-V Client

Environment



Prerequisites:

  • VSS provider used for snapshot must support transportable snapshot involving Hyper-V writer
    (Check with VSS provider vendor/documentation for above support.)
  • All VM files MUST lie on Host Volume(s) for which transportable snapshot involving Hyper-V writer is supported.
  • Alternate client should be at same or higher level compared to the primary (OS, Storage stack)
  • VSS provider should be installed on both primary and alternate client.
  • Use vshadow to confirm the support with VSS provider intended to be used

Validate Configuration for Off-host Backup

Snapshot creation with transportable option:

  • On Primary host, run snapshot creation with transportable option. Snapshot information is maintained as part of backup component document (BCD).

Example: If the VM to be backed up resides on M:\ and N:\, the following vshadow command will take a H/W snapshot (plex) for M:\ N:\ involving Hyper-V writer:
 > vshadow -p -ap -t=c:\bcd1.xml M:\ N:\

Note: vshadow is a VSS test tool supplied along with the VSS SDK.

-----------------------------------------------------------------------------------------------------------------------------
Select explicitly included components...
 * Writer 'Microsoft Hyper-V VSS Writer':
   - Add component \279E8343-33A9-4122-88EA-51636ACB7F50
Creating shadow set {c67b0a96-5952-4f48-a6d7-33062f1def74} ...
- Adding volume \\?\Volume{1c5170b9-0249-11de-b47c-001aa03ba288}\ [M:\] to the
shadow set...
- Adding volume \\?\Volume{1c5170b3-0249-11de-b47c-001aa03ba288}\ [N:\] to the
shadow set...
...
Shadow copy set successfully created.
-----------------------------------------------------------------------------------------------------------------------------

Snapshot import with import option:

  • On Secondary host, copy the BCD xml generated from primary. Run snapshot import specifying location of BCD on secondary host.

 > vshadow -i=c:\bcd1.xml
 


Solution



Policy Creation: 

 
Provider Type configuration parameter:
 
The ProviderType configuration parameter determines the type of VSS snapshot provider that creates the snapshot. Attempts to select the available provider in this order: hardware, software, system.
 
Auto: Attempts to select the available provider in this order: hardware, software, system.
 
System: Uses the Microsoft system provider, for a block-level copy on write snapshot.
                Unlike the Hardware type, the System provider does not require any specific hardware.
 
Software: Not certified in this release.
 
Hardware: Uses the hardware provider for a disk array. A hardware providermanages the VSS  snapshot at the hardware level by working with a hardware storage adapter or controller.
 
For example, to back up the data that resides on anEMCCLARiiON or HPEVAarray by means of the array’s snapshot provider, select Hardware. Depending on your array and on the snapshot attribute you select, certain preconfiguration of the array may be required.  

Provider Type
Configuration parameter
System
Uses the Microsoft system provider, for a block-level copy on write snapshot.
Unlike the Hardware type, the System provider does not require any specific hardware
Software
Not certified in this release
Hardware
Uses the hardware provider for a disk array. A hardware providermanages the VSS                  snapshot at the hardware level by working with a hardware storage adapter or controller.
 
For example, to back up the data that resides on anEMCCLARiiON orHPEVAarray by means of the array’s snapshot provider, select Hardware. Depending on your array and on the snapshot attribute you select, certain preconfiguration of the array may be required

 
Snapshot Attribute configuration parameter:
 
The Snapshot Attribute configuration parameter determines the type of VSS snapshot that is created.
 
Unspecified: Uses the default snapshot type of the VSS provider.
 
Differential: Uses a copy-on-write type of snapshot. For example, to back up an EMC CLARiiON array with an EMC CLARiiON SnapView Snapshot, select Differential.
 
Plex: Uses a clone snapshot or mirror snapshot. For example, to back up an HP EVA array with an HP EVA Snapclone snapshot, select Plex.
 
Tabular format:

Snapshot Attribute
Configuration parameter
Unspecified
Uses the default snapshot type of the VSS provider
Differential
Uses a copy-on-write type of snapshot. For example, to back up an EMC CLARiiON array with an EMC CLARiiON SnapView Snapshot, select Differential
Plex
Uses a clone snapshot or mirror snapshot. For example, to back up an HP EVA array with an HP EVA Snapclone snapshot, select Plex

Log Entries:
bpfis logs on primary (oigtwin20 is alternate client):
12:30:36.707 [4460.2868] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpfis.exe create -nbu -owner NBU -rhost oigtwin20 -id rtp_vm1.example.com_1251356422 -bpstart_to 300 -bpend_to 300 -backup_copy 0 -ru root -pt 29 -vm_type 1 -vm_client rtp_vm1.example.com -clnt oigqewin02 -st FULL -rg other -fim Hyper-V:Virtual_machine_backup=1,prov_type=3,snap_attr=0,allow_offline_backup=1,csv_timeout=0,nameuse=0 -class offhost_backup -sched full -fso -S oigqewin02

bpfis logs on alternate client (oigewin02 is primary client)

12:32:41.943 [6072.7600] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpfis.exe create -nbu -dptgt -id rtp_vm1.example.com_1251356422 -rhost oigqewin02 -clnt oigtwin20 -S oigqewin02 -vnet_ipc 49472 -exclude C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.rtp_vm1.example.com_1251356422.0.exclude -pt 29

 




Article URL http://www.symantec.com/docs/TECH183154


Terms of use for this information are found in Legal Notices