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

Preventive Service Planning


Abstract

This document details the Known Issues & Limitations for IBM Tivoli Manager for Virtual Environments V6.3.x.

Content

This document is divided into linked sections for ease of navigation. You may use the links below to jump to the desired section of the document.
Issues related to upgrading from earlier releases
vCenter Plug-in GUI Issues and Limitations
Snapshot related Issues and Limitations
Recovery Agent Issues and Limitations
VMware Backup Issues and Limitations

Issues related to upgrading from earlier releases

  • Start Menu Programs listed twice with different names

    When viewing the Start Menu path of:
      Start -> Programs -> Tivoli Storage Manager -> Data Protection for VMware

    after upgrading from TSM for Virtual Environments V6.2 to V6.3, you will see entries for:
    • Mount
    • Command Line
    • Data Protection for VMware Recovery Agent
    • Recovery Agent CLI

    The "Mount" menu option and the "Data Protection for VMware Recovery Agent" menu option both launch the same program.

    The "Command Line" menu option and the "Recovery Agent CLI" menu options both launch the same program.

    Workaround: None. This issue is cosmetic. (11607)

  • Host is displayed as UNKNOWN on VMware vSphere plugin

    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.

    Workaround: None. This is issue does not impact the restore functionality and will be addressed in a future release.(89150)


vCenter Plug-in GUI Issues and Limitations

  • "Select All" button not visible in the Source Step of the Backup Wizard

    This button's function does exist even though the button is not visible. This button is on the same level as the "Quick Filter" entry field. Clicking in the area above the left corner of the table displayed in the Source Step of the Backup Wizard will trigger the action. (75517_1)

  • Resizing Backup Wizard can omit scroll bar

    When using the backup wizard, if the panel is resized to a much smaller size, the panel may get displayed without a scroll bar that would allow the entire panel contents to be seen.

    Workaround: Resize panel until scroll bar appears or is unnecessary.
    Use up and down keys (see APAR IC84039)

  • The English word “item” appears in the border of some panels in the Plug-in GUI

    The word “Item” is not translated in the border area of some panels.

    Workaround: None. This is a cosmetic issue that will be addressed in a future release. (77085)

  • In the Edit Plug-in Domain panel, it is possible to drag and drop datacenter names between list boxes even though the Manage All Datacenters checkbox is selected.

    When the “Manage All Datacenters” checkbox is selected on the Edit Domain panel, the contents of the list boxes should not be changeable because the checkbox takes priority over the list boxes. The buttons to move the datacenters between lists are disabled, but due to a defect it is still possible to drag and drop datacenters between the list boxes. Doing this has no effect on the actual datacenters managed because the checkbox has priority, but allowing this drag and drop gives the impression that the list box contents are being changed.

    Workaround: None. The intended function of the “Manage All Datacenters” checkbox works as expected. (77342)

  • F5 key does not cause refresh of Summary Log Display (FCM ONLY)

    On the Reports panel, the action “View Summary Log” launches a secondary window to show the most recent summary log data. Some users may expect that pressing the F5 key will cause this panel to be refreshed, but in fact this does not cause a refresh.

    Workaround: If a refresh is needed, the user can press the View Summary log action on the Reports panel and this will cause the secondary panel to be refreshed. (77530)

  • Plug-in GUI not accessible from vSphere client after apparent successful installation.

    There are 2 defects that result in the plug-in GUI not being accessible (no Icon shown) from the vSphere client even though installation was reported as being successful. Both of these are caused by failed registration of the plug-in to a valid vCenter.
      1) During install of the plug-in GUI, the user must enter a vCenter userid and password to accomplish registration of the plug-in to the vCenter. This userid must have sufficient authority in vCenter in order to perform the registration. However, due this defect, if the userid does not have sufficient authority, the registration will fail but the install process will proceed without notifying the user about this failure. Later, when a user tries to use the plug-in GUI from the vSphere client, the plug-in GUI Icon will not appear because registration failed. (77761)

      2) During install of the plug-in GUI, the user gives the hostname/IP address of the vCenter where the plug-in should be registered, and a userid/password to use for the registration process. Due to this defect, if the machine identified as the vCenter is not actually configured to be a vCenter, but happens to have the specified userid/password defined such that login these credentials is allowed, the install process will end successfully. But since the machine was not a vCenter, there was not successful plug-in registration so the GUI will not be accessible in the vSphere client. (78023)

    This scenario was seen in the case where the user specified an ESX host for the vCenter address instead of an actual vCenter, and was using a userid/password combination that was valid in the ESX host.

    Workaround: If either of the above scenarios occur, then after install manually use the registration tool to register the plug-in, being sure to choose a userid that does have sufficient authority in the vCenter and that the vCenter specified is functioning as a valid vCenter.



Snapshot related Issues and Limitations
  • Snapshots may fail when the virtual volume is mounted inside of a guest VM

    When a virtual volume is mounted inside a guest VM, the snapshot of that VM may fail with the following error:
      Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

    After the virtual volume is dismounted, snapshot is able to complete successfully. This problem has been observed with Windows 2008 R2 and Windows 7.

    Workaround: Dismount the virtual volume if this problem occurs. (11380)



Recovery Agent Issues and Limitations
  • Linux System hang during Recovery Agent operations with certain Linux kernel levels
    Attempts to perform mount or instant restore operations via the TSM for Virtual Environments Recovery Agent may cause a system hang on systems running Linux kernel versions 2.6.27 - 2.6.29.

    The system hang is caused by a SCSI related bug in these kernel levels which is exposed as the Recovery Agent uses the iSCSI protocol to access LUNs.

    Workaround: Ensure that your Linux system is not using kernel levels 2.6.27 - 2.6.29. (11168)

  • The Data Protection for VMware Recovery Agent component does not support instant restore or file level restore operations over a wide area network (WAN).
    (11565)
  • Combo box of Virtual Machine is disabled after selecting "-Select vm-"

    If the "-Select vm-" entry in the "Tivloli Storage Manager Server" list was selected, the drop down list to select a virtual machine is still disabled when selecting a valid TSM server again.

    Workaround: Click the refresh button to refresh the TSM server, the combo box will then be enabled again. (12660)

  • Recovery Agent does not support restoring logical volumes or a VMDK larger than 2 TB
    Attempts to perform mount or instant restore operations of VMs on a logical volume or VMDK with the Tivoli Storage Manager for Virtual Environments Recovery Agent fails in these situations:
    • the logical volumes are greater than, 2 TB
    • the VMDK is greater than, 2 TB

    To perform mount or instant restore operations of VMs on a logical volume or VMDK with the Tivoli Storage Manager for Virtual Environments Recovery Agent, the logical volume size must be less than 2 TB and each VMDK size must be less than 2TB.

    Workaround: Specify the vmskipmaxvmdks yes option in the Tivoli® Storage Manager backup-archive client options file during a backup operation. This option setting ensures that VMware VMDKs that are 2 TB (or smaller) are backed up and omits any VMDKs that are larger than 2 TB.

VMware Backup Issues and Limitations
  • VMware backup operations are a function of the TSM for Virtual Environments "Data Mover". This functionality is enabled by the separately installed prerequisite: Tivoli Storage Manager (TSM) Backup-Archive Client 6.3. The Known Issues and Limitations for this product are documented in the following tech notes by platform:

    Windows: http://www.ibm.com/support/docview.wss?uid=swg21508259
    Linux: http://www.ibm.com/support/docview.wss?uid=swg21508174

    Please refer to the section titled "VMware backup known problems and limitations" in each tech note for information specific to this capability.

  • 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
    (IC87174)

  • Concurrent backup of the same VM guest is not supported
    In this scenario, a VM guest backup operation is running. Before backup processing completes, a second backup operation of the same VM guest is started. This type of concurrent backup of the same VM guest is not supported. This is a known limitation.

    Workaround: Verify that the VM guest to be backed up is not in an active backup session before you attempt a backup

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager for Virtual Environments
Data Protection for VMware

Software version:

6.3

Operating system(s):

Linux, Windows

Reference #:

1507325

Modified date:

2014-06-24

Translate my page

Machine Translation

Content navigation