Updates for IBM Tivoli Storage Manager for Virtual Environments Data Protection for VMware Installation and User's Guide V6.2

Installation and upgrading updates
Incorrect command for installing Data Protection for VMware on a Linux system in silent mode
Clean installation required for Linux restart
Linux system requirements
Temporarily disable SELinux before installing
iSCSI target does not function properly
Snapshots not appearing in the snapshot list of a virtual machine
Expired incremental snapshots
Manual intervention for mount
Mount cannot connect to multiple servers or nodes simultaneously
Avoid concurrent mount sessions on the same tape volume
Unmounting an iSCSI target during a file-level restore
Mount cannot be started while mounted volumes exist
Destination volume for instant restore
Limitations restoring volumes to partitions on the same disk
Slow instant restore progress
TDPVMwareShell.exe
Access Control List Issues
File System Support
Mount and dynamic disks
Configuring systems for iSCSI mount
Java Runtime Environment (JRE) is not part of the setup.exe

Installation and upgrading updates

• Chapter 3. Installing, upgrading, and uninstalling Data Protection for VMware
• Sections: Installing Data Protection for VMware on a Windows 32-bit system in silent mode, Upgrading Data Protection for VMware on a Windows 32-bit system in silent mode

The following note should have been included after step 5 in Installing Data Protection for VMware on a Windows 32-bit system in silent mode but it was not included.
Note: Specify an absolute path. Using a relative path can result in unpredictable results.

The note was included after step 5 in Upgrading Data Protection for VMware on a Windows 32-bit system in silent mode, but it should not have been included.

The command in step 5 of Upgrading Data Protection for VMware on a Windows 32-bit system in silent mode should be:
setup.exe /s /f1"<path_to_the_upgrade.iss_file>"

Back to top

Incorrect command for installing Data Protection for VMware on a Linux system in silent mode

• Chapter 3. Installing, upgrading, and uninstalling Data Protection for VMware
• Section: Installing Data Protection for VMware on a Linux system in silent mode

Step 2b. of the procedure is this:
For a custom installation, enter the following command into the command prompt window:
./install-Linux.bin -i silent -f <full path to_install.properties file>
The command is incorrect. The correct command is this:
./install-Linux.bin -i silent -f <full_path> <properties_file_name>

Back to top

Clean installation required for Linux restart

• Chapter 3. Installing, upgrading, and uninstalling Data Protection for VMware
• Section: Performing a clean installation of Data Protection for VMware on Linux

The following section should have been in Chapter 3. Installing, upgrading, and uninstalling Data Protection for VMware:

If a Linux installation is interrupted, you can usually restart it. However, if the installation fails to restart, a clean installation is required. Before starting a clean installation, ensure that product is completely removed. Perform following steps to ensure a clean environment:
1. Remove all files from the failed installation:
a. Remove <USER_INSTALL_DIR> which is the path where the failed installation was performed. For example: /opt/tivoli/tsm/TDPVMware/
b. Remove <user.home>/IA-TDPVMware-00.log. The <username> is the ID of the user who performed the installation.
a. Remove the /var/ibm/common directory. b.
b. Remove the /usr/ibm/common directory.
c. Clean up the /tmp directory by removing the acu_de.log file, if there is one.
d. Remove the /tmp directory that contains the ID of the user that installed the Deployment Engine. ("root").
e. Remove all Deployment Engine entries from the /etc/inittab system file. The entries are delimited by #Begin AC Solution Install block and #End AC Solution Install block. Remove all text between those delimiters, and remove the delimiting text itself.
f. Remove all Deployment Engine references from the /etc/services system file
After you have completed the previous steps, you can start the clean installation.

Back to top

Linux system requirements

• Chapter 2. Planning
• Section: Operating systems for Data Protection for VMware Recovery Agent

The lsscsi command and iscsiadm utility should have been included in the list of system requirements for Linux systems.

Operating system and supported release	Support details
Red Hat Enterprise Linux 5.2, 5.3, 5.4 servers	Supports the x86 (32 bit) instruction set architecture Supports 32-bit and 64-bit processors The following kernels are supported: RedHat-i386: 2.6.18-92.e15.i686 and 2.6.18-92.e15.i686 PAE RedHat-x86_64: 2.6.18-92.el5-x86_64 Perl version 5 on Linux systems mdadm tool for managing Linux Software RAID arrays iSCSI Initiator for Linux package iscsi-initiator-utils-6.2.0.868-0.7.el5 lsscsi command iscsiadm utility Secure Shell (SSH) client for Linux
SUSE Linux Enterprise Server 10, Service Pack 2	Supports the x86 (32 bit) instruction set architecture Supports 32-bit and 64-bit processors The following kernels are supported: SUSE-i386: 2.6.16.60-0.21default, 2.6.16.60-0.21smp, and 2.6.16.60-0.21bigsmp SUSE-x86_64: 2.6.16.60-0.21default and 2.6.16.60-0.21smp For all kernel versions, auto mount is not supported. Perl version 5 on Linux systems mdadm tool for managing Linux Software RAID arrays iSCSI Initiator for Linux lsscsi command iscsiadm utility Secure Shell (SSH) client for Linux

Back to top

Temporarily disable SELinux before installing

• Chapter 3. Installing, upgrading, and uninstalling Data Protection for VMware
• Section: Installing Data Protection for VMware

The following text should have been in the "Installing Data Protection for VMware" section:

Installing Data Protection for VMware SELinux only: Temporarily disable SELinux before running the installation program. To temporarily disable SELinux, enter the following command: /usr/sbin/setenforce 0

Back to top

iSCSI target does not function properly

• Chapter 6. Restoring virtual machine data
• Section: Restoring files

The following text should have been in the "Restoring files" section:

When snapshot data is stored on tape or on a virtual tape library, and Mount is not set up to run under Tape Mode, the "choose mount destination" dialog erroneously states that the disk or partition type is not supported. The user can create an iSCSI target but the created target will not function properly and cannot be used.

Back to top

Snapshots not appearing in the snapshot list of a virtual machine

• Chapter 6. Restoring virtual machine data
• Sections: Restoring files (Windows), File-level restore (Linux)

The following text should have been added to step 4 "Restoring files (Windows)" and step 2 of "File-level restore (Linux) sections:

"A virtual machine might appear in the virtual machines list, but if you select it, the snapshots list might be empty. The reason is that no snapshots have yet completed successfully for that virtual machine."

Back to top

Expired incremental snapshots

• Chapter 6. Restoring virtual machine data
• Section: Mounting snapshots

The following text should have been in the "Mounting snapshots" section:

Expired incremental snapshots might be included in a Mount snapshot list. However, you cannot restore data from these snapshots. Any attempt to mount or perform an instant restore from these snapshots fails.

Back to top

Manual intervention for mount

• Chapter 6. Restoring virtual machine data
• New Section: Responding to a timeout during a file level restore or an instant restore (Linux)

The following text should have been in the "Restoring virtual machine data" chapter:

During a file level restore or an instant restore, a timeout might occur. If a timeout does occur, the user interface displays a message saying that manual intervention might be needed.

Follow this procedure if the timeout occurs during a file level restore (Mount operation):
1. 1. Stop the recovery process by commenting out the one line in /etc/cron.d/tsmmount_recover Ensure that the recovery process is not running by issuing this command:
ps -ef | grep tsmRecover
2. 2. Ensure that the required snapshot is mounted in the Data Protection for VMware Recovery Agent Windows backup server. If the snapshot is not mounted, mount it manually.
3. 3. Ensure that the iSCSI target is connected to the Linux machine by using iscsiadm -m session. If the iSCSI target is not connected to the Linux machine, perform a manual login to the target by issuing this command:
iscsiadm -m discovery -t sendtargets -p <windows_server_ip> --login
4. 4. Mount the iSCSI device locally by using the Linux mount command. For example:
mount /dev/sde1 /Mount1
Ensure that you use the same mount point as was requested in the user interface. This operation can take long time to complete depending on the consistency of the snapshot
5. 5. When the mount operation is completed, uncomment the line in /etc/cron.d/tsmmount_recover.
6. 6. When you want to unmount, do so first locally by using umount. Then use the Linux user interface to unmount the session.

For an instant restore operation the manual intervention is to halt and then retry the restore session

Back to top

Mount cannot connect to multiple servers or nodes simultaneously

• Chapter 6. Restoring virtual machine data
• Section: Mounting Snapshots

The following text should have been in the "Mounting Snapshots" section:

Mount cannot connect to multiple servers or nodes simultaneously. Connecting to the same server by using different names such as shortname/FQDN/ IP address fails, because Mount treats each one as a different server.

Back to top

Avoid concurrent mount sessions on the same tape volume

• Chapter 6. Restoring virtual machine data
• Section: Mounting snapshots

The following text should have been in the "Mounting snapshots" section:
Mounting a snapshot from the same tape storage pool by two instances of Mount can cause one of these results:

• The second Mount instance is blocked until the first instance is complete.
• The second Mount instance interrupts the first instance activity. For example, it interrupts a file copy process on the first instance.

Avoid concurrent mount sessions on the same tape volume.

Back to top

Unmounting an iSCSI target during a file-level restore

• Chapter 6. Restoring virtual machine data
• Section: File-level restore (Linux)

The following text should have been in the "File-level restore (Linux)" section:

If, during a file restore on a Linux machine, the iSCSI target is unmounted, the file level restore fails, and the restored data is left incompleted.

Back to top

Mount cannot be started while mounted volumes exist

• Chapter 6. Restoring virtual machine data
• Section: Data Protection for VMware Recovery Agent on Windows

The following text should have been in the "Data Protection for VMware Recovery Agent for Windows" section:

If you are running Windows 2008 and you try to start Mount from the Start menu, this message might appear: "TDPVMWare Mount cannot be started while mounted volumes exist. Do you wish to dismount all volumes?" If the volumes are currently in use and you select Yes, dismounting the volumes might fail. For example: A Linux virtual machine is using the Windows Mount as a backend, and has mounted a snapshot and is using it. In this case, launching Mount from the Start menu fails. Instead, you should dismount the snapshot from the Linux virtual machine that originally mounted it

Back to top

Destination volume for instant restore

• Chapter 6. Restoring virtual machine data
• Section: Instant restore

The following text should have been in the "Instant restore" section:

When you select a destination volume for instant restore, ensure that the volume resides on a physical disk and not on a virtual iSCSI disk.

Back to top

Limitations restoring volumes to partitions on the same disk

• Chapter 6. Restoring virtual machine data
• Section: Restoring files

The following text should have been in the "Restoring files" section:

There is a limitation when restoring several volumes to several partitions on the same disk. Only one volume can be active. The other volumes remain in the DELAYED state. Their progress as shown on the user interface remains at 0% until they move out of the DELAYED state and after the active synchronization completes.

Back to top

Slow instant restore progress

• Chapter 6. Restoring virtual machine data
• Section: Instant restore

The following text should have been in the "Instant restore" section:

In some cases, the instant restore progress can be slow. This condition can be due to such things as connectivity issues, large volumes, restore from tape, or high I/O operations. The recovery process identifies no progress was made on the MDADM device (/dev/md0) for the last 5 minutes and responds to it as a potential problem. As a result, a cleanup is performed, and the restore restarts itself, continuing from the point at which it stopped. The cleanup can cause I/O operations to fail. To fix this problem, you can increase the recovery process period by editing the /etc/crn.d/tsmmount_recover file. Increase the recovery process period to 10 minutes or to 20 minutes if the volume is large or the I/O is intense."

Back to top

TDPVMwareShell.exe

• Chapter 7. Command line interface
• Section: Starting the Command line

The occurrences of TDPVMareShell.exe in this section are misspellings of TDPVMwareShell.exe.

Back to top

Access Control List (ACL) Issues

• Chapter 6. Restoring virtual machine data
• Section: Restoring files (Windows)

The following text should have been in the "Restoring files (Windows)" section:

The ACL values associated with the folders and files that are restored in a file level recovery operation are not transferred to the recovered files. In order to maintain ACL values, use the XCOPY command when copying files from the target in Step 7.

• Chapter 6. Restoring virtual machine data
• Section: File-level restore (Linux)

The following text should have been in the "File-level restore (Linux)" section:

The ACL values associated with the folders and files that are restored in a file level restore operation are not transferred to the restored files. In order to maintain ACL values, use the cp -p command when copying files.

Back to top

File System Support

• Chapter 6. Restoring virtual machine data
• Section: File-level restore (Linux)

The following text should have been in the "File-level restore (Linux)" section:

File-level restore on Linux is available for snapshots of disks that use any of the following:

• Master boot record-style partition tables.
• Partitions formatted using one of these file systems:
• NTFS
• FAT
• FAT32
• EXT2
• EXT3
• RaiserFS

File restore from snapshots of GPT-based disks, dynamic disks, and LVM partitions is possible by using iMount technology. This technology exposes an iSCSI target. iSCSI initiator commands are then used to discover the iSCSI target.

Back to top

Mount and dynamic disks

• Chapter 6. Restoring virtual machine data
• Section: Restoring files (Windows)

The following text should have been in the "Restoring files (Windows)" section:

The mount function cannot be used to mount snapshots of dynamic disks as a virtual volume. Only partitions from an MBR-based, basic disk can be mounted as virtual volumes. File-level recovery from GPT, dynamic, or any other non-MBR or non-basic disk is possible by creating a virtual iSCSI target and using an iSCSI initiator to connect to your system.

Back to top

Configuring systems for iSCSI mount

• Chapter 6. Restoring virtual machine data

The following procedure should have been in "Chapter 6. Restoring virtual machine data":

Configuring systems for iSCSI mount

Back to top

Java Runtime Environment (JRE) is not part of the setup.exe

• Chapter 3. Installing, upgrading, and uninstalling Data Protection for VMware

The following prerequisite should have been in the "Preparing for installation" section:

The Java Runtime Environment (JRE) is not part of the setup.exe, and it resides outside the install package under the Extra directory. In order to install the JRE, you must have the product DVD. If you did not install the JRE (it is installed if you install Mount), you need to run the setup.exe from the DVD so that the JRE can be copied to C:\Program File\Tivoli\TSM\TDPVMware.

Back to top