Wednesday, January 22, 2014

Configuring Veeam Offhost Backup Proxy for Hyper-V and IBM V3700 SAN

After migrating our development VMware environment to a Hyper-V infrastructure, the last thing involved to do on this project was the configuration of the backups. Here is the environment that I was dealing with:

  • Hyper-V 2012 hosts (non R2)
  • IBM V3700 SAN (this procedure should work for any SVC/Storwize SAN such as the IBM V7000)
  • Veeam Backup and Replication 7

In order to obtain the fastest and best performing backup speeds with Veeam, an offhost backup proxy with fiber channel connectivity is required. Unfortunately, this process is significantly more difficult in a Hyper-V environment which is why I decided to document this process down. Here are the documentation resources that I referred to for the configuration of this environment.

  1. http://helpcenter.veeam.com/backup/70/hyperv/index.html?offhost_proxy_advanced.html
  2. http://pic.dhe.ibm.com/infocenter/storwize/v3700_ic/index.jsp?topic=%2Fcom.ibm.storwize.v3700.710.doc%2Fsvc_vssinstall_20m3ec.html

 Here are the pre-requisites for the offhost backup proxy:

  1. The role of an offhost backup proxy can be assigned only to a Microsoft Windows 2008 Server R2 machine with the Hyper-V role enabled, Microsoft Windows Server 2012 with the Hyper-V role enabled or Microsoft Windows Server 2012 R2 with the Hyper-V role enabled. Note that the version of the Hyper-V host and offhost backup proxy should coincide. For example, if you use a Microsoft Windows 2008 Server R2 machine with the Hyper-V role enabled as a Hyper-V host, you should deploy the offhost backup proxy on a Microsoft Windows 2008 Server R2 machine with the Hyper-V role enableThe source Hyper-V host and the offhost backup proxy must be connected (through a SAN configuration) to the shared storage that supports VSS hardware providers.
  2. To create and manage volume shadow copies on the shared storage, you must install and properly configure a VSS hardware provider that supports transportable shadow copies on the offhost proxy and Hyper-V host. The VSS hardware provider is usually distributed as a part of client components supplied by the storage vendor.
  3. If you plan to perform offhost backup for a Hyper-V cluster with CSV, make sure you deploy an offhost backup proxy on a host that is not a part of a Hyper-V cluster. If the offhost backup proxy is deployed on a node of a Hyper-V cluster, the cluster will fail during backup and replication.
  4. If you plan to perform offhost backup for a Hyper-V cluster with CSV, make sure you deploy an offhost backup proxy on a host that is not a part of a Hyper-V cluster. If the offhost backup proxy is deployed on a node of a Hyper-V cluster, the cluster will fail during backup and replication.

So to begin, install the Hyper-V role onto the OS as it is a requirement.







Next, the Multipath-IO feature needs to be enabled.



 
For the rest of the Hyper-V configuration, I selected the defaults (no features/NICs).









Install the vendor specific MPIO drivers. For an IBM V3700/V7000 SAN, I installed the SDDDSM which can be obtained from the IBM website.





Restart the computer if prompted. Once restarted, the VSS hardware provider needs to be installed and configured. Run the installer.






Enter the information associated with the V3700/V7000 SAN.


Note: Sometimes the installer freezes at the last step where you enter the credentials. In that case, restart the installer and accept the defaults. Then open up a command prompt and navigate to the VSS Hardware Provider directory and run the following commands:

  • ibmvcfg set cimomHost SAN_IP
  • ibmvcfg set username san_username
  • ibmvcfg set password san_password

Next open up a command prompt and navigate to C:\Program Files\IBM\Hardware Provider for VSS-VDS\ or where ever the VSS hardware provider is installed. Set the cluster ID for the SAN as follows:

  • ibmvcfg.exe set targetSVC cluster_id


The cluster ID can be found in the Monitoring > System Details of the SAN management interface.





Restart the IBM hardware provider services as indicated. The MPIO drivers and the VSS Hardware provider will have to be installed on every Hyper-V host as well.

 
Once that is done, log into the SAN management interface. From here, a few snapshot LUNs and host records need to be created and masked for the VSS snapshot to work.

First, create two FC host entries with the information as follows:
  1. Host name: VSS_FREE, WWPN: 5000000000000000
  2. Hostname: VSS_RESERVED, WWPN: 5000000000000001



Next allocate the snapshot LUNs. The size of these LUNs must be equal to or larger than the largest LUN in the Hyper-V environment. In my scenario, all the CSVs where my VMs are stored are 2TB in size so my snapshot LUNs are 2 TB as well. I created a total of 4 LUNs as there will be 4 simultaneous backup jobs running. These LUNs were thin provisioned in order to save space.




Map all the snapshot LUNs to the VSS_FREE host created earlier.



Go back to the command prompt and verify you can see the newly created snapshot LUNs:

  • ibmvcfg.exe list free



Lastly, go to the Veeam Backup Proxy server and add an offhost backup proxy and then create the backup jobs as needed


3 comments:

  1. Hi, Great post.
    Quick question - should i use the same procedure for Iscsi?

    ReplyDelete
  2. Your this blog is very informative and interesting. Keep doing this type of great work.
    access 1337x in UK

    ReplyDelete