Known Issues and Limitations: Version 6.4 Tivoli Storage Manager for Virtual Environments

Data Protection for VMware vCenter plug-in Issues and Limitations

• Different times display in Backup tab and Restore tab

When viewing the time stamp for the same task, the time displayed in the "Last Ran" column in the Backup tab is different from the time displayed in the "Restore Point" column in the Restore tab.

This situation occurs when the system where the Data Protection for VMware vCenter plug-in is installed and the Tivoli Storage Manager server have different time zone settings.

Workaround: Synchronize the time zone settings. (86211)

• Backup operation on Linux and Windows continues although error message displays

When the VMCLI service stops during a backup operation, the backup operation displays an error in the Data Protection for VMware vCenter plug-in; however, the backup operation continues on the Tivoli Storage Manager server until complete.

When the current backup operation continues on the Tivoli Storage Manager server, and you restart the VMCLI service, the following message displays in the Data Protection for VMware vCenter plug-in:

ERROR ANS5176W(RC4383) The requested virtual machine operation cannot be performed because a virtual machine backup or restore operation is already in progress. Please retry the operation after the first operation completes.

This is a known issue regarding how the error is processed in the Data Protection for VMware vCenter plug-in when the VMCLI service stops.

Workaround: Ignore the error message as the backup operation continues until complete. (84730)


• Data Protection for VMware vCenter plug-in help page is inconsistent with the server locale
  
  When the Data Protection for VMware vCenter plug-in help page is accessed through the "Learn more" link for the first time, the help displays in the language specified by the locale setting of the processor that runs the Data Protection for VMware vCenter plug-in, not the language specified by the locale of the VMware vSphere Client. In this situation, after the Data Protection for VMware vCenter plug-in help page displays, click at least two links within the help, then close the help. The next time the help is started from the "Learn more" link, it displays in the language specified by the locale setting of the VMware vSphere Client.
  
  This is a known issue caused by inconsistent locale settings among the processor that runs the Data Protection for VMware vCenter plug-in and the VMware vSphere Client. The Data Protection for VMware vCenter plug-in does not support running in an environment that contains inconsistent locale settings among the processor that runs the Data Protection for VMware vCenter plug-in, the VMware vSphere Client, and the Tivoli Storage Manager server.
  
  Workaround: Specify the same locale settings among the processor that runs the Data Protection for VMware vCenter plug-in, the VMware vSphere Client, and the Tivoli Storage Manager server. (86543)
  
  
• Reports tab shows incomplete number of virtual machines being processed

During a backup operation, the Reports tab shows two numbers in the Details category of the table. For example:

Processing virtual machine: 10 / 11

The first number (10) is the number of virtual machines that have been processed (backed up). The second number (11) is the total number of virtual machines to be processed in the backup operation.

During a backup operation, the total number of virtual machines is routinely refreshed by the Data Protection for VMware vCenter plug-in during backup processing. This refresh action changes the numbers that are shown. Depending on the number of virtual machines being backed up, additional time is needed until the total number of virtual machines stabilizes. Then, the number of virtual machines that have been processed changes until the backup operation completes.

This issue is working as designed.

Workaround: Understand the refresh action changes both numbers until the backup operation completes. (86961)

• Data Protection for VMware vCenter plug-in displays in two vCenters

The Data Protection for VMware vCenter plug-in is displayed in two vCenters because it is registered to both vCenters. Although the Data Protection for VMware vCenter plug-in supports operations in only one vCenter, it is possible for it to be registered to two vCenters.

This situation occurs because of the following scenario:
1. The Data Protection for VMware vCenter plug-in was uninstalled.
2. During the uninstall process, when prompted to unregister the Data Protection for VMware vCenter plug-in, this unregister task was skipped.
3. The Data Protection for VMware vCenter plug-in was reinstalled and registered to a different vCenter.

As a result, the Data Protection for VMware vCenter plug-in is registered (and displays) in two vCenters.

Workaround: During the uninstall process, when prompted to unregister the Data Protection for VMware vCenter plug-in, make sure to select this task so that the Data Protection for VMware vCenter plug-in does not display in two vCenters. (88668)

• Host is displayed as UNKNOWN in Data Protection for VMware vCenter plug-in

When restoring Virtual Machines that were backed up with Data Protection for VMware 6.2.x, the Virtual Machine's ESXi host name is not displayed, and instead the host shows the name as "UNKNOWN".
However, the Virtual Machine can be restored without issues. (89150)


Data Protection for VMware Issues and Limitations

• VMCLI Derby database is corrupted

When the VMCLI Derby database (VMCLIDB) becomes corrupted, the service.properties file in the ${DERBY_HOME}/VMCLIDB folder is deleted. In this situation, the VMCLI daemon cannot start the Derby database.

This is a known issue that can occur when the Derby database is shutting down.

Workaround: To to recover a corrupted VMCLI Derby database (VMCLIDB), complete one of the following procedures:

Copy the service.properties file from the latest Derby database backup located on your file system.
1. Locate the latest Derby database backup located on your file system. The default location is <install_dir>/derby_backups. For example, on Linux, the default location is /opt/tivoli/tsm/tdpvmware/common/derby_backups.
2. Copy the service.properties file from the backup (located on your file system) to the corrupted VMCLI Derby database (VMCLIDB). For example, on Linux, issue a command similar to the following:
cp /opt/tivoli/tsm/tdpvmware/common/derby_backups/20120903000020157/VMCLIDB/service.properties /home/tdpvmware/tdpvmware/VMCLIDB

Use the service.properties file from a new VMCLI Derby database
1. Rename the corrupted VMCLIDB.
2. Start the VMCLI daemon.
3. Stop the VMCLI daemon.
4. Copy the service.properties file from the new VMCLIDB to the corrupted VMCLIDB.
5. Delete the new VMCLIDB.
6. Rename the corrupted VMCLIDB to its original name.

After completing either of these workaround procedures, the VMCLI daemon should start successfully. (86868)

• Backup of the Windows 2008 R2 virtual machine with a hidden and/or off-line Microsoft System Reserved (MSR) partition fails

Data Protection for VMware is unable to process a hidden or off-line Microsoft System Reserved (MSR) partition. VMware vStorage API calls require that the partition is online and visible (not hidden) before it can be backed up.

The following VMware knowledge document describes the requirement for visible MSR partitions:
http://kb.vmware.com/kb/2008012

If you try to back up a partition that is hidden or off-line, the backup fails. The following errors are recorded in the dsmerror.log file:

ANS9365E VMware vStorage API error.
TSM function name : visdkWaitForTask
TSM file : vmvisdk.cpp (3754)
API return code : 60
API error message : An error occurred while quiescing the
virtual machine. See the virtual machine's event log for
details.
An unexpected error was encountered.
TSM function name : vmVddkFullVMOpenVMDKs
TSM function : snapMoRefP is null
TSM return code : 115
TSM file : vmbackvddk.cpp (7436)
ANS4151E Failure mounting Virtual Machine '<MachineName>'.
RC=115

Workaround: Enter the following diskpart commands from a command prompt window:

C:\>Diskpart
C:\Diskpart> List volume
C:\Diskpart> Select volume 1 (volume 1 contains the system reserved partition)
C:\Diskpart> Online volume (This brings the volume online)
C:\Diskpart> detail partition

The output of the "detail partition" option reveals the partition attributes. For example, it lists the selected volume's partition number, partition type (07=NTFS), and its hidden and active status:

Partition 1
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576

If the partition type is "07" and if the hidden attribute is "no", type EXIT to close diskpart and try backing up the disk again.

If the partition type is not "07", type the following to set the type to 07 and unhide the partition:

C:\Diskpart> set id=07 override

Type EXIT to close diskpart and try backing up the disk again.

• Guest VM operating system that is displayed in Data Protection for VMware Recovery Agent GUI might be incorrect

The operating system for the guest VM (that displays in the "Select snapshot" field) is determined by the operating system assigned to that guest VM in the vCenter. Therefore, if the guest VM operating system is assigned incorrectly in the vCenter, the guest VM operating system in the "Select snapshot" field also displays incorrectly.

Workaround: Assign the correct guest VM operating system in the vCenter. (88729)

• FULL VM vStor backup (IFFULL, IFINCR, FULL, INCR) failures

Consistent backup failures have been experienced with some Tivoli Storage Manager version 6.4 Backup-Archive Client Linux installations on all supported Linux platforms, that are used as the data mover for VMware backups.

Workaround: Download and install the Tivoli Storage Manager Backup-Archive Client 6.4.0.1 interim fix (IC88237).