IBM Tivoli Storage Manager, Version 7.1

Preparing the environment for full backups of VMware virtual machines

Complete the following steps to prepare the VMware environment for backing up full VMware virtual machines. The vStorage backup server can run either a Windows or Linux client.

To configure the storage environment for backing up, complete the following steps:
1. Configure your storage environment so that the vStorage backup server can access the storage volumes that are in your ESX server farm.
2. If you are using network-attached storage (NAS) or direct-attach storage, ensure that the vStorage backup server is accessing the volumes with a network-based transport.
3. Optional: For data access, make the following settings:
  - Create storage area network (SAN) zones that your vStorage backup server can use to access the storage logical units (LUNs) that host your VMware data stores.
  - Configure your disk subsystem host mappings so that all ESX servers and the backup proxy can access the same disk volumes.
To configure the vStorage backup server, complete the following steps:
1. Set and export the LD_LIBRARY_PATH environment variable to point to the client installation directory. For example:
  export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin
2. Add the client installation directory to the path of each account that uses backup-archive client commands, for example, dsmc, dsmcad, or dsmj.
3. When the backup-archive client runs on a vStorage backup server, this client configuration is called the Tivoli® Storage Manager data mover node. A Windows system that is a data mover must have the 64-bit Windows client installed on it. A data mover node typically uses the SAN to back up and restore data. If you configure the data mover node to directly access the storage volumes, turn off automatic drive letter assignment. If you do not turn off letter assignments, the client on the data mover node might corrupt the Raw Data Mapping (RDM) of the virtual disks. If the RDM of the virtual disks is corrupted, backups fail. Consider the following conditions for restore configurations:
  The data mover node is on a Windows Server 2008 or Windows Server 2008 R2 system:
  If you plan to use the SAN to restore data, you must set the Windows SAN policy to OnlineAll. Run diskpart.exe and type the following commands to turn off automatic drive letter assignment and set the SAN policy to OnlineAll:
```
diskpart
  automount disable
  automount scrub
  san policy OnlineAll 
  exit
```
  The backup-archive client is installed in a virtual machine on a Windows Server 2008 or Windows Server 2008 R2 system:
  If you plan to use the hotadd transport to restore data from dynamically added disks, the SAN policy on that system must also be set to OnlineAll.
  Whether the client uses the SAN or hotadd transport, the Windows SAN policy must be set to OnlineAll. If the SAN policy is not set to OnlineAll, restore operations fail, and the following message is returned:
  ANS9365E VMware vStoragee API error. TSM function name: vddksdk Write TSM file : vmvddkdsk.cpp (2271) API return code : 1 API error message : Unknown error ANS0361I DIAG: ANS1111I VmRestoreExtent(): VixDiskLib_Write FAILURE startSector=512 sectorSize=512 byteOffset=262144, rc=-1
  For a description of the vStorage transport settings and how you can override the defaults, see the following topic:
  
  Vmvstortransport
4. Install the Tivoli Storage Manager client on the vStorage backup server. At the custom setup page of the installation wizard, select VMware vStorage API runtime files.
  Important: If you are moving the backup data by using backups that are not in a LAN, the SAN must have separate connections for tape and disk.
To modify Tivoli Storage Manager, complete the following steps:
1. Access the administrative command line of Tivoli Storage Manager client.
2. From the Tivoli Storage Manager client of the vStorage backup server, run the following command to register the node:
```
register node my_server_name my_password
```
  Where my_server_name is the full computer name of the vStorage backup server and my_password is the password to access the server.
  Tip: On Windows systems, you can get the server full computer name by right-clicking on My Computer. Click the Computer Name tab and look at the name listed next to Full computer name.
3. From the Tivoli Storage Manager client of the vStorage backup server, run the following command to register the node:
```
register node my_vm_name my_password
```
  Where my_vm_name is the full name of the virtual machine that you are backing up.
If you back up a virtual machine where volumes are mounted to directories rather than drive letters, files might not be stored in the correct location. An error might be caused because the mount point does not correspond to the actual mount points of backed up files. An error is caused because the mount points for a virtual machine that is running Windows do not have a drive letter assignment. When you use the VMware vStorage APIs for Data Protection, a filespace name is created that includes a number assignment. The filespace names that are created for the mount point do not correspond to the actual mount points of the backed up file.
To back up or restore files to their original location, use the following steps:
1. To restore files to their original location, map the drive or assign a drive letter to the mount point from the virtual machine.
2. If you restore a file that the vStorage API renamed, select a different restore location.
3. When using mount points without drive letter assignments, use an include or exclude statement for that volume. See the following example of an exclude statement:
```
exclude \\machine\3$\dir1\...\*.doc
```

Feedback