Known Issues and Limitations: IBM Spectrum Protect for Virtual Environments: Data Protection for VMware V7.1

Preventive Service Planning

Abstract

This document details the Known Issues & Limitations for Data Protection for VMware V7.1.

Content

Beginning with Version 7.1.3, IBM Tivoli® Storage Manager for Virtual Environments is now IBM Spectrum Protect™ for Virtual Environments. Some applications such as the software fulfillment systems and IBM License Metric Tool use the new product name. However, the software and its product documentation continue to use the Tivoli Storage Manager for Virtual Environments product name. To learn more about the rebranding transition, see technote 1963634.

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.
Data Protection for VMware vSphere GUI Issues and Limitations
Installation Issues and Limitations
Other Issues and Limitations
7.1.2 Issues and Limitations
7.1.3 Issues and Limitations
7.1.4 Issues and Limitations
7.1.6 Issues and Limitations
7.1.8 Issues and Limitations

Note: Known issues and limitations for file restore operations that are run from the Tivoli Storage Manager file restore interface are documented in the following technote:
http://www.ibm.com/support/docview.wss?uid=swg21964753

Data Protection for VMware vSphere GUI Issues and Limitations

Invalid schedule name when creating a scan schedule using Data Protection for VMware vSphere GUI leads to error message ANR2600E (internal reference #130076)

Problem: Defining a Scan schedule using the Data Protection for VMware vSphere GUI, the schedule creation may fail reporting the following error messages:

GVM0125E: An error occurred while making the Web server request. If this error persists, check the network connection with the Web server and verify that the Web server is running.

Error: ANR2600E DEFINE SCHEDULE: Invalid schedule name - TEST-VCENTER01. MGMT.TESTENVIRONMENT_VMCLI_SCAN.

Problem Verification: None

Workaround: The following commands will rename the vmcli so that it would be possible to update the schedule using the Data Protection for vSphere GUI. Run the following commands using the Server Administrative Command Line (dsmadmc):
1. define the „vmcliNode_SCAN“ Scan schedule
   for Windows:
    - define sched polDom vmcliNode_SCAN desc='TSM4VE scan schedule' action=command starttime=00:00:00 dayofweek=sat per=2 perunits=weeks objects='C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VMwarePlugin\scripts\vmcli.cmd -f start_guest_scan -dcscan ALL_DC -o data_mover_node'
    - define sched polDom vmcliNode_SCAN desc='TSM4VE scan schedule' action=command starttime=00:00:00 dayofweek=sat per=2 perunits=weeks objects='C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VMwarePlugin\scripts\vmcli.cmd -f start_guest_scan -dcscan „Local DC,SVC,XIV“ -o data_mover_node'

   for Linux:
   - define sched polDom vmcliNode_SCAN desc='TSM4VE scan schedule' action=command starttime=00:00:00 dayofweek=sat per=2 perunits=weeks objects='/opt/tivoli/tsm/tdpvmware/common/scripts/vmcli' -f start_guest_scan -dcscan ALL_DC -o data_mover_node'
- define sched polDom vmcliNode_SCAN desc='TSM4VE scan schedule' action=command starttime=00:00:00 dayofweek=sat per=2 perunits=weeks objects='/opt/tivoli/tsm/tdpvmware/common/scripts/vmcli -f start_guest_scan -dcscan „Local DC,SVC,XIV“ -o data_mover_node'

2. define the association between the „vmcliNode_SCAN“ schedule and vmcliNode: define association polDom vmcliNode_SCAN vmcliNode
IBM Data Protection GUI dialog can become inaccessible from the browser window (internal reference #73199)

Problem: When you use the IBM Data Protection GUI (an extension within the VMware vSphere Web Client), a dialog (such as the Restore VM dialog) can be moved by the user out of the VMware vSphere Web Client viewing area. As a result, the dialog can become inaccessible to the user.

Workaround: If a dialog becomes inaccessible, log out of the VMware vSphere Web Client. Then, log in again.
Data Protection for VMware vSphere GUI attempts to back up invalid VMs (internal reference #146643)

Problem: A VM must be in the 'connected' state to be accessed for backup by the Data Protection for VMware vSphere GUI. A VM that is not in the 'connected' state cannot be accessed for backup and is considered an invalid VM. When an invalid VM exists in the VMware vCenter, the Data Protection for VMware vSphere GUI attempts to back up this invalid VM anyway, even when the invalid VM is not selected. Pending any unforeseeable issues with the VMs selected for backup, the Data Protection for VMware vSphere GUI completes the backup operation but the following error message is returned:

ANS2721E (RC4400) The virtual machine backup operation completed. However, one or more virtual machine backups failed.

Workaround: Check the console output and error logs for information about why the connection state was invalid. For example, an error message similar to the following is returned in the dsmerror.log file:
ANS2713E The virtual machine 'vmonion-rest' is in an invalid connection state 'inaccessible'. As a result, it cannot be backed up.

In this scenario, the invalid VM 'vmonion-rest' was not originally selected; however, the Data Protection for VMware vSphere GUI attempted to back it up anyway.
Existing VMCLI node registers as a Data Mover Node (internal reference #146647)

Problem: After successfully installing and configuring the Data Protection for VMware vSphere GUI, the GUI is uninstalled and unregistered from the vCenter. Then, the Data Protection for VMware vSphere GUI is installed and configured again on the same system. During this second configuration, an existing Tivoli Storage Manager node is used for either the data center node or the data mover node. After configuration completes, the table in the Configuration Status page incorrectly shows an old (or legacy) VMCLI node as a data mover node.

This scenario is a known issue and is working as designed. The table in the Configuration Status page shows the topology for all nodes associated with the Data Protection for VMware vSphere GUI configuration. If there are old (or legacy) VMCLI nodes attached to the vCenter, these VMCLI nodes are shown as data mover nodes in the new configuration.
Data Protection for VMware vSphere GUI and VMCLI show failed VMs with large VMDKs (internal reference #146648)

Problem: After successfully installing and configuring the Data Protection for VMware vSphere GUI, two or more VMs are selected for backup. One of the VMs has a VMDK that exceeds 2 TB. The backup operation succeeds for one VM but fails for the VM that has a VMDK that exceeds 2 TB. However, the failed VM displays in the list of backed up VMs.
This scenario is a known issue and is working as designed. Although the failed VM displays in the list of backed up VMs, the failed VM does not display with a restore point. Therefore, the failed VM should cause no additional issues or confusion.
Feedback link does not work in the IBM Tivoli Data Protection for VMware Version 2.1 Information Center (internal reference #152789)

Problem: The Feedback link in the footer of each page in the Tivoli Data Protection for VMware Version 2.1 Information Center does not load the correct page. Instead of displaying the IBM Documentation Feedback form, the Feedback link displays a Not Found message. This is a known problem in all languages.

Workaround: To submit a comment regarding the Tivoli Data Protection for VMware Version 2.1 Information Center, complete the following tasks:
1. Go to the following page in the Tivoli Storage Manager Information Center:
  http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/topic/com.ibm.itsm.ve.doc/welcome.html
2. Click Feedback.
3. In the IBM Documentation Feedback form, replace the "Tivoli Storage Manager for Virtual Environments V7.1 documentation" text in the Topic or page field with the appropriate Tivoli Data Protection for VMware Version 2.1 Information Center topic or page.
4. Complete the IBM Documentation Feedback form and click Submit.
Data Protection for VMware vSphere GUI help page is inconsistent with the server locale (internal reference #146651)

Problem: When the Data Protection for VMware vSphere GUI 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 vSphere GUI, not the language specified by the locale of the VMware vSphere Client. In this situation, after the Data Protection for VMware vSphere GUI 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 vSphere GUI and the VMware vSphere Client. The Data Protection for VMware vSphere GUI does not support running in an environment that contains inconsistent locale settings among the processor that runs the Data Protection for VMware vSphere GUI, 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 vSphere GUI, the VMware vSphere Client, and the Tivoli Storage Manager server.
Data Protection for VMware vSphere GUI NLS help pages display in English for FlashCopy Manager for VMware (internal reference #152803 )

Problem: When the following Data Protection for VMware vSphere GUI help pages are accessed for the first time from the wizard in an NLS language:

Create Schedule wizard: Welcome page -> Task: Backing up VM data with Tivoli Storage FlashCopy Manager

Restore Datastores wizard: Welcome page -> Task: Restoring datastores instantly with Tivoli Storage FlashCopy Manager for VMware

The page displays in English and not the NLS language. This is a known issue. The NLS version of the page is available in the NLS version of the IBM Tivoli Data Protection for VMware Version 2.1 Information Center that is installed with the Data Protection for VMware vSphere GUI.

Workaround: To access the NLS version of this page, complete the following tasks:

Create Schedule wizard:
1. In the "Welcome" page of the Create Schedule wizard, click "Task: Backing up VM data with Tivoli Storage FlashCopy Manager"
2. In the top of the "Backing up VM data with Tivoli Storage FlashCopy Manager" English page, click "IBM Tivoli Data Protection for VMware 2.1". The complete information center opens.
3. You can view the NLS version of "Backing up VM data with Tivoli Storage FlashCopy Manager" by navigating to that page in the Table of Contents:
Getting started with the IBM Data Protection for VMware vSphere GUI -> Data Protection for VMware vSphere GUI tasks -> Backing up VMs -> Backing up VM data with Tivoli Storage FlashCopy Manager (97397)

Restore Datastores wizard:
1. In the "Welcome" page of the Restore Datastores wizard, click "Task: Restoring datastores instantly with Tivoli Storage FlashCopy Manager for VMware"
2. In the top of the English "Restoring datastores instantly with Tivoli Storage FlashCopy Manager for VMware" page, click "IBM Tivoli Data Protection for VMware 2.1". The complete information center opens.
3. You can view the NLS version of "Restoring datastores instantly with Tivoli Storage FlashCopy Manager for VMware" by navigating to that page in the Table of Contents:
Getting started with the IBM Data Protection for VMware vSphere GUI -> Data Protection for VMware vSphere GUI tasks -> Restoring VMware data -> Restoring datastores instantly with Tivoli Storage FlashCopy Manager for VMware

Data Protection for VMware vSphere GUI Application Configuration Status report might contain inaccurate guest operating system information (internal reference #146652)

Problem: In the Application Configuration Status report, the full name shown in the Guest Operating System column is based on objects that are managed by VMware vSphere. The Application Configuration Status report cannot validate the full name that is managed by VMware vSphere. As a result, the full name might be inaccurate.
This is a known issue caused by VMware users that must enter a guest operating system full name for a new operating system release when the predefined full name text is not yet available.

Workaround: Specify or select the correct full name when configuring the guest operating system.
Determining which datacenter to select in the "Instant Access/Instant Restore Status" dialog (internal reference #146653)

Problem: In the "Instant Access/Instant Restore Status" dialog of the Data Protection for VMware vSphere GUI, when using the "Select a datacenter" drop-down list, the information provided in the dialog does not clarify which datacenter to select. Determining which datacenter to select might be particularly confusing when the same data mover node is used for the VM's original datacenter and the datacenter where the VM was restored.

Workaround: This scenario is a known problem and is working as designed. To solve this problem, select the VM's original datacenter and not the datacenter where the VM was restored.
Scan schedule defined using the Data Protection for vSphere GUI on a Linux system cannot run without prompting the user for the VMCLI node password (internal reference #146659)

Problem: This situation occurs when the following two conditions exist:
- The Data Protection for vSphere GUI and Tivoli Storage Manager backup-archive client are installed on the same Linux system.
- The backup-archive client scheduler uses the VMCLI node.

When the VMCLI password is updated, the backup-archive client password is invalidated. Likewise, when the backup-archive client password is updated, the VMCLI password is invalidated. As a result, the user is continually prompted for a new password, and cannot set up a working scheduler.

This is a known problem that is caused by the inability of the Data Protection for vSphere GUI and the backup-archive client scheduler to use the same VMCLI node when both applications are installed on the same Linux system.

Workaround: To enable the Data Protection for vSphere GUI and the backup-archive client scheduler to use the same VMCLI node when both applications are installed on the same Linux system, create a stanza for SERVERNAME TSMCLIWRAPPER in the dsm.sys file with the following settings:

SERVERNAME TSMCLIWRAPPER
TCPSERVERADDRESS <same TSM server as VMCLI node>
PASSWORDACCESS generate
MANAGEDSERVICES webclient schedule
NODENAME <VMCLI node name>

The stanza must specify SERVERNAME TSMCLIWRAPPER to be successful.

Caution: When the passworddir option is used to specify an alternate directory location for TSM.PWD, this workaround is unsuccessful. TSM.PWD must be in the default location for this workaround to be successful.
Data Protection for VMware vSphere GUI configuration wizard might display data mover node with incorrect datacenter node (internal reference #152806)

Problem: In this scenario, datacenters with similar names are added to the Managed Datacenters list in the GUI Domain page of the configuration wizard or configuration notebook. However, in the Data Mover Nodes page, one of the created data mover nodes is shown as mapped to the wrong datacenter node. As a result, it appears that the data mover node was not created for the desired datacenter node. This is a known issue.

Workaround: To resolve this issue, complete the following tasks:
1. In the Data Mover Nodes page, select the data mover node and click Edit Node Name in the toolbar.
2. Add an ampersand (&) at the beginning of the data mover node name.
Datastore restore wizard provides registration checkbox for ineligible VMs
This behavior is described with IT09305
Problem: When using the Data Protection for VMware vSphere GUI with Tivoli Storage FlashCopy Manager for VMware to restore datastores, you can use the restore wizard to select which VMs to register at the completion of the restore process. VMs that are not eligible for registration are identified with a yellow warning icon. However, the restore wizard allows you to select VMs that are not eligible for registration. Even though these VMs are selected, they still will not be registered. This is a known problem.

Workaround: To resolve this issue, ignore the selection box for VMs that are not eligible for registration. View the Registration Exceptions page in the restore wizard to see the complete list of VMs that will not be registered.
Initial configuration with Data Protection for VMware vSphere plug-in does not display link to vCenter information (internal reference reference #152795)

Problem: When using the Data Protection for VMware vSphere plug-in configuration wizard for an initial configuration, the product generates default data mover nodes and datacenter nodes. During this process, a link to the VMware vCenter is provided in the "Data Mover Nodes" page. This link directs you to a dialog where you enter the vCenter credentials. These credentials enable the local services to communicate with the vCenter. In this scenario, the link to the VMware vCenter is not provided. This is a known problem.

Workaround: To resolve this issue, complete the following tasks:
1. On the system where the data mover is installed, navigate to the backup-archive client installation directory: C:\Program Files\Tivoli\TSM\baclient

2. Issue the following command to set the vCenter credentials: dsmc SET PASSWORD -type=VM <hostname> <administrator> <password>
   - hostname: Specify the VMware VirtualCenter or ESX server that you want to backup, restore, or query.
   - administrator: Specify the account that is needed to log on to the vCenter or ESXi host.
   - password: Specify the password that is associated with the login account that you specified for the vCenter or ESXi administrator.
Cannot change an existing backup schedule from a weekly or daily interval to a monthly interval (internal reference # 152796)

Problem: In this scenario, the Data Protection for VMware vSphere GUI or plug-in Create Schedule wizard is used to create a "Schedule for later" type of backup schedule. In the Repetition page of the Create Schedule wizard, the "Back up weekly" or "Back up on the following days of the week" option is selected for this schedule. However, after the schedule is created and available to edit in the Backup Schedules window, the Properties Notebook does not allow a number to be entered in the "Back up every __ months" option. This is a known problem.

Workaround: To resolve this issue, create a schedule with the same content and select the "Back up every __ months" option. Then, specify a number in the months field.
English characters in web browser GUI NLS login page (internal reference #152797)

Problem: When the Data Protection for VMware vSphere GUI or Data Protection for VMware vCloud GUI login page is accessed by a web browser in one of the following languages: Brazilian Portuguese, Japanese, Spanish

The login page displays text in English characters. This is a known problem.
Attach VM dialog does not display second ESX host when first ESX host contains large number of VMs (internal reference #152798)

Problem: In this scenario, a backup task is selected for restore using the Data Protection for VMware vSphere GUI with Tivoli Storage FlashCopy Manager for VMware. In the Attach VM dialog, an ESX host is selected and expanded to view the VM backups that are available to attach. When a second ESX host is selected and expanded, the VM backups on the second ESX host do not display. This display issue occurs when the first expanded ESX host contains a large number of VMs. This is a known issue.

Workaround: To resolve this issue, complete one of the following tasks:
- When this scenario occurs, collapse the first ESX host, then expand the second ESX host.
- When the ESX host where the VM resides is already known, only expand that ESX host.
Incorrect default date displays for an existing schedule in the Schedule Notebook(internal reference #152800)

Problem: In this scenario, a "Run Now" backup task was created using the Data Protection for VMware vSphere GUI with Tivoli Storage FlashCopy Manager for VMware. However, when changing the task to a "Scheduled" backup task ("Schedule for later" option) with the Properties Notebook, the "Date and time of the last backup" value (on the Repetition page) incorrectly displays the default date of 01/01/1970. This is a known problem.

Workaround: To resolve this issue, manually enter a date according to your locale (MM/DD/YYYY or YYYY/MM/DD) or use the calendar tool to set the date.
Invalid incremental backups display in Data Protection for VMware vSphere GUI (internal reference #152801)

Problem: The Data Protection for VMware vSphere GUI Restore Points table displays invalid incremental backups. When an invalid incremental backup is selected for a restore operation, the operation completes as successful. However, no restore action occurred and the virtual machine cannot start.
This situation exists when you run an incremental forever backup to a node that contains only periodic full backups. The number of periodic full backups on this node exceed the number that is allowed by the policy. The oldest FULL restore point does not display in the Data Protection for VMware vSphere GUI. The invalid INCR restore points (that correspond to the FULL restore point) display in the GUI, which is incorrect. When these invalid INCR restore points are selected for restore, the restored virtual machines do not start. These invalid INCR restore points no longer display when expiration processing completes on the Tivoli Storage Manager server.

For example, in the following scenario, the Tivoli Storage Manager server policy specifies verexists=2. Only these periodic full backups exist on the node:

1. FULL
2. INCR
3. INCR
4. FULL
5. INCR
6. INCR

After running an incremental forever backup (IFFULL), the Data Protection for VMware vSphere GUI displays these restore points:
1. INCR
2. INCR
3. FULL
4. INCR
5. INCR
6. IFFULL

Restore points #1 and #2 are invalid.

After expiration processing completes on the Tivoli Storage Manager server, the Data Protection for VMware vSphere GUI displays these correct restore points:
1. FULL
2. INCR
3. INCR
4. IFFULL

Workaround: To resolve this issue, allow the Tivoli Storage Manager server expiration process to complete. Invalid restore points are removed from the Restore Points table after the server expiration processing completes.
Date displays incorrectly in Data Protection for VMware vSphere GUI
This behavior is solved with v7.1.2 (internal reference #73084)

Problem: The Data Protection for VMware vSphere GUI Mount Status pane displays the Start Date and Snapshot Date incorrectly when the following conditions exist:
- The language environment is set to Japanese, Korean, Simplified Chinese, or Traditional Chinese.
- The date and time format of the system is set to a format that contains the abbreviated name of the month (MMM) or the AM/PM designator (tt).

Workaround: Complete the following tasks to resolve this issue:
1. Set the date and time format in the 'Region and Language' settings as follows:
Short date: Any date format that uses the month as a number. Do not use the abbreviated name of the month (MMM).
Long date: Not affected. Any format is good.
Short time: Any time format that does not use the AM/PM designator (tt).
Long time: Any time format that does not use the AM/PM designator (tt).

2. Set the value of the TIMEformat option to 1. For example: timeformat 1
Set the TIMEformat option in the Tivoli Storage Manager backup-archive client dsm.opt file on the data mover system.

Installation Issues and Limitations

Un-installation does not remove all files and directories
This behavior is solved with v8.1.2 (internal reference #139990)

Problem: With each installation of IBM Spectrum Protect for Virtual Environments a directory is created in C:\Windows\Downloaded Installations\. The names of the directory are arbitrary GUIDs like {F5999A64-42AF-4DDF-AB56-F3445714C4AB}. Each directory contains files, like 1033.MST and IBM Spectrum Protect for Virtual Environments Data Protection for VMware.msi where the msi file is around 100 MB. After uninstall, these directories and files are left around in the system. Performing multiple installs and uninstalls of the product will eventually take up a large amount of space on the system.

Workaround: Go to C:\Windows\Downloaded Installations\ and delete the directories where IBM Spectrum Protect for Virtual Environments Data Protection for VMware.msi or IBM Tivoli Storage Manager for Virtual Environments Data Protection for VMware.msi is present.

Modify option (in maintenance mode) does not modify the selected feature on Windows 64-bit systems (internal reference #146627)

Problem: In this scenario, after you completed the initial installation of a Data Protection for VMware feature (such as the Data Protection for VMware Enablement File or Data Mover), you restart the installation process and select Modify to modify an installed feature. However, after you select the feature and click Next, the installation program displays the InstallShield Wizard Complete page. It does not display the installation process for the selected feature. This is a known problem.

Workaround: To modify an installed feature, first clear the check box for this feature, then select the check box for this feature again. Click Next to proceed with the modification.

Un-selecting during GUI upgrade or not specify plugin and Web Extension during silent upgrade will not un-register either (internal reference #121811)

Problem: When doing a upgrade of Data Protection for VMware if the user has the GUI plugin and/or Web Extension registered and deselects either during the GUI upgrade or does not specify them in the command line of the silent install, the unregister will fail and a popup warning message will be displayed informing the user to manually unregister them. The GUI plugin and/or Web Extension will remain registered after upgrade

Workaround: The customer can manually remove the GUI plugin and/or Web Extension.
From and elevated command window change directory to:
C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\VMwarePlugin

Run the following command to remove the plugin:
C:\IBM\tivoli\tsm\tdpvmware\webserver\jre\jre\bin\java -jar
unreg.jar VCENTER_HOSTNAME VCENTER_USERNAME VCENTER_PASSWORD HOST_NAME

Run the following command to remove the web extension:
C:\IBM\tivoli\tsm\tdpvmware\webserver\jre\jre\bin\java -jar unreg.jar -wc_ext VCENTER_HOSTNAME VCENTER_USERNAME VCENTER_PASSWORD HOST_NAME
Error message in vCloud Director GUI is meaningless when trying to create backup schedule and TSM Administrator credentials are unavailable for use (internal reference #121334)

Problem: In the IBM Data Protection for VMware vCloud Director GUI, a problem can occur if TSM Administrator credentials are unavailable for use. If the Create Schedule action is selected and the TSM Administrator credentials are unavailable, an error message dialog with the text “Undefined” will be shown instead of the correct message, which would state that Create Schedule action is not possible when TSM Administrator credentials are unavailable.

Workaround: Go to the Configuration Tab, select action Edit Configuration, and enter the TSM Administrator ID and password. It will then be possible to create a schedule.

Other Issues and Limitations

VM BACKUPS FAIL WITH ANS4174E AND RC=-72 (internal reference #150501)

Problem: While attempting to backup a VM, IBM Spectrum Protect for Virtual Environments reports a failed backup due to an unrecoverable error and RC=-72. For scheduled backups with multiple VM's, this causes a failure only for the backup of the particular VM that reports the error. The issue may not be seen with every backup for a particular VM or every VM being processed in a schedule.

The dsmerror.log file for the datamover will report messages similar to the following:
07/20/2017 04:29:09 ANS4174E Full VM backup of VMware Virtual Machine 'VMNAME' failed with RC=-72 mode=Incremental Forever - Incremental, target node name='TSMVE', data mover node name='Datemover1'
07/20/2017 04:29:09 ANS1228E Sending of object 'VMNAME' failed.
07/20/2017 04:29:09 ANS1235E An unknown system error has occurred from which TSM cannot recover.

In addition the following may also be seen:
07/20/2017 04:29:06 ANS1235E An unknown system error has occurred from which TSM cannot recover.
07/20/2017 04:29:06 ANS5250E An unexpected error was encountered.
   TSM function name : vcmLogger::trace
   TSM function      :
VolumeControlManager::remove_volume_from_cache: Volume not in cache, nothing to remove (id='Path:'C:\mnt\tsmvmbackup\fullvm\CDF_Local\VMNAME\Hard Disk 2' Job: 67002')

   TSM return code   : 115
   TSM file          : ..\..\common\vm\vmbackvcm.cpp (218)

The issue is caused by a long delay in VMware VDDK Open or Close disk call.
The delay can be caused by network a network issue or vCenter/ESXi load.

Workaround: Reduce vCenter/ESXi load and restart the backup.
Data Protection for VMware Recovery Agent on Linux fails to complete a second restore operation (internal reference #152786)

Problem: In this scenario, the Data Protection for VMware Recovery Agent successfully restored a snapshot into the target volume. However, when a second restore operation is issued to restore the snapshot into the same target volume, the restore operation fails with the following error message:
TDP0060E Restore is not allowed on raid device.

This is a known problem.

Workaround: If you plan to restore another snapshot into the same target volume, complete the tasks described in the "Restoring to the same volume again" section at the following URL: http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/topic/com.ibm.itsm.ve.doc/t_ve_mount_irlnx.html
Windows 2012 backup proxy error
This issue solved with FCM for VMware v4.1.3 (internal reference #98499)

Problem: When performing a file level back up of a Windows 2012 VM using a Windows 2012 backup proxy, the operation will fail with return code 4 and a four access denied messages. The customer will see the following type of errors for four different directories, one which will look like this:

ANS1228E Sending of object '\\vm3a\c$\Windows\System32\LogFiles\WMI\RtBackup' failed.
ANS4007E Error processing '\\vm3a\c$\Windows\System32\LogFiles\WMI\RtBackup': access to the object is denied.

Even though the backup is reported as failed, everything is backed up successfully with the exception of four directories and the backup may be used for restore.

Workaround: Perform the file level backup of the Windows 2012 VM using a Windows 2008 or Windows 2008 R2 backup proxy (data mover).
Instant access and instant restore operations fail when using NFS data stores (internal reference #152739)

Problem: In this scenario, an instant access or instant restore operation specifies an NFS data store as the target data store or as the temporary data store. When an NFS data store is specified, the instant access or instant restore operation fails with the following error messages:
Operations:
- Instant access
- Instant restore with NFS data store specified as the target data store

Task Details pane in vSphere GUI:
ERROR ANS2411E Instant Restore/Access of virtual machine '<virtual machine name>' failed with rc= 4389
ERROR ANS9404E (RC4389) Error creating the specified Virtual Machine. See log files for more information.

Progress History pane in vSphere GUI:
VM '<virtual machine name>': Creating a virtual machine on the ESX host...
VM '<virtual machine name>': ** Unsuccessful **

VMware vSphere Client:
A general system error occurred: Error creating disk Function not implemented

dsmerror.log file on data mover:
ANS2411E Instant Restore/Access of virtual machine '<virtual machine name>' failed with rc = 4389
12/13/2013 12:48:09 ANS4904E Instant access of VMware Virtual Machine '<virtual machine name>' failed. target node name='<target_node_name>', data mover node name='<data_mover_node_name>'

Operation:
- Instant restore with NFS data store specified as the temporary data store

Task Details pane in vSphere GUI:
ERROR ANS2411E Instant Restore/Access of virtual machine '<virtual machine name>' failed with rc = 6534
ERROR ANS2419E (RC6534) The datastore does not have enough free space for the instant restore operation.

Progress History pane in vSphere GUI:
VM '<virtual machine name>': Creating a virtual machine on the ESX host...
VM '<virtual machine name>': ** Unsuccessful **

VMware vSphere Client: No error message displays.

This is a known limitation. VMware does not support iSCSI or vMotion operations with NFS data stores as described in the following VMware Knowledge Base Article:
"Unable to add a physical mode disk mapping (RDM) to a virtual machine stored on an NFS datastore (1001856)" https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1001856

As a result, Data Protection for VMware does not support instant access or instant restore operations when using NFS data stores.

Workaround: Do not specify an NFS volume as a temporary data store or as a target data store. Specify only supported volumes as a temporary data store or as a target data store.
Concurrent backup or restore of the same VM guest is not supported (internal reference #152740)

Problem: In this scenario, a VM guest backup or restore operation is running. Before processing completes, a second backup or restore operation of the same VM guest is started. This type of concurrent backup or restore of the same VM guest is not supported. If you attempt to run multiple concurrent operations of the same VM guest, the second operation fails. In addition, the first operation might also fail. This is a known limitation.

Workaround: Run only one operation of a VM guest at a time. For example, if you are backing up a given VM guest, do not attempt to run another backup or restore operation of that same VM guest. Likewise, if you are restoring a given VM guest, do not attempt to run another backup or restore operation of that same VM guest.
Data mover cannot back up itself (internal reference #145568)

Problem: In this scenario, the data mover that runs the backup operation attempts to back up its own disks. This scenario is not supported. As a result, the backup operation fails. A data mover must be backed up by a different data mover.

Workaround: Verify that the data mover that runs the backup operation does not attempt to back up its own disks.

Canceling a "Back Up Now" operation logs duplicate warning message (internal reference #152741)

Problem: In this scenario, a "Back Up Now" operation in a vCloud environment is canceled with the Data Protection for VMware vCloud GUI Cancel Task button. Although the backup operation stops, the ANS5053W message is duplicated in the dsmerror.log file. For example:
08/15/2013 14:22:34 ANS5053W The operation was stopped by the user.
08/15/2013 14:22:36 ANS5053W The operation was stopped by the user.

Workaround: Ignore the duplicated entry if the time stamps match the time of the cancel action.

Backup VM exit code is "0" although a failure occurred (internal reference #152742)

Problem: In this scenario, a backup VM or restore VM operation might exit with code 0 even though a problem occurred during the operation. This is due to a known issue related to VMware VDDK and described in the following VMware release notes under "Error code may not be set correctly before VDDK exit": http://www.vmware.com/support/developer/vddk/vddk-550-releasenotes.html
- On Linux, add "testflag SHOWALLCONSISTENTRC" to the client system options file. This testflag prints the exit code.
- On Windows, prepend the call to dsmc with "start /wait".
For example: start /wait dsmc backup vm vmname

Workaround: Alternatively, add "testflag SHOWALLCONSISTENTRC" to the client options file. This testflag prints the exit code.
Version 7.1.1 Recovery Agent renamed to new name on Windows operating systems only (internal reference #152787)

Problem: The "Data Protection for VMware Recovery Agent" is renamed to "Tivoli Storage Manager Recovery Agent" on Windows operating systems in version 7.1.1. This rename impacts the following files and directories:

Problem: The "Data Protection for VMware Recovery Agent" is renamed to "Tivoli Storage Manager Recovery Agent" on Windows operating systems in version 7.1.1. This rename impacts the following files and directories:
Recovery Agent command-line interface:
7.1.1: RecoveryAgentShell.exe
7.1.0: TDPVMwareShell.exe

Recovery Agent command-line interface default directory:
7.1.1: C:\Program Files\Tivoli\TSM\RecoveryAgent\shell
7.1.0: C:\Program Files (x86)\Tivoli\TSM\tdpvmware\shell

Recovery Agent GUI:
7.1.1: RecoveryAgent.exe
7.1.0: tdpvmwaremount.exe

Recovery Agent GUI default directory:
7.1.1: C:\Program Files\Tivoli\TSM\RecoveryAgent\mount
7.1.0: C:\Program Files (x86)\Tivoli\TSM\tdpvmware\mount

However, "Data Protection for VMware Recovery Agent" is not renamed on Linux operating systems. The Recovery Agent GUI and default directory on Linux remain unchanged:

7.1.1 Recovery Agent GUI: TDPVMwareMountRestore.sh
7.1.1 Recovery Agent GU: default directory: /opt/tivoli/tsm/tdpvmware/mount
Mount of RAID volume requires significant temporary storage space (internal reference #146608)

Problem: When the Recovery Agent mounts a volume on a Windows system, it stores volume-related metadata as write cache in a temporary directory under C:\ProgramData\Tivoli\TSM\RecoveryAgent\mount. This temporary directory requires nominal storage space. However, when the Recovery Agent mounts a RAID volume on a Windows system, this temporary directory requires greater storage space. For example, if you have a RAID volume on four 5 GB disks, the temporary directory requires 5 GB of storage space.
This space requirement is a known issue that is related to RAID volumes.

Workaround: If you plan to mount a RAID volume on a Windows system, you can resolve this issue with either of the following methods:
- Increase available space on the system drive so that sufficient storage space is available in C:\ProgramData \Tivoli\TSM\RecoveryAgent\mount to accommodate the RAID volume-related metadata.
- Configure the Recovery Agent to store temporary volume-related metadata on a different drive with sufficient space. Click Settings in the Recovery Agent GUI, then specify a different drive in the Folder for temporary files field.
Transport mode does not failover (internal reference #145451)

Problem: In this scenario, the vmvstortransport option is specified during a backup vm and restore vm operation. The specified transport mode becomes unavailable during processing and the operation fails. The Tivoli Storage Manager backup-archive client does not failover to another transport mode when the specified transport mode becomes unavailable during an operation.

When this occurs, the dsmerror.log contains a reference to "VixDiskLib_Write" or VixDiskLib_Read".
Recovery Agent does not support restoring logical volumes or VMDKs 2 TB or larger
This behavior is solved with v7.1.3 (internal reference #152788)

Attempts to perform mount or instant restore operations of VMs on a logical volume or VMDK with the Tivoli Storage Manager Recovery Agent fails in these situations:
- the logical volumes are equal to, or greater than, 2 TB
- the VMDK is equal to, or greater than, 2 TB

To perform mount or instant restore operations of VMs on a logical volume or VMDK with the Tivoli Storage Manager 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.
VM backup with application protection VSS unfreese failure due to 10 seconds flush and hold timeout (internal reference #124111)

Problem: VMware guest backups with application protection for Microsoft Exchange or Microsoft SQL servers may fail with:
ANS2330E Failed to unfreeze the VSS writers because the snapshot time exceeded the 10 second timeout limitation
This behavior may have different root causes and is described in APARs IT15552 or IT15991 (additionally VMware KB https://kb.vmware.com/kb/2150648)

Workaround: When this occurs, proceed with one of the following:
- stop VM backup with data protection on and continue backup VM without data protection or install data protection product inside the VM.
- apply the workaround from IT15991 (https://kb.vmware.com/kb/2150648 )
Restoring a large number of emails using the Mailbox Restore Browser MMC GUI may result in an MAPI_RC_FAILURE.(internal reference #121376)

When using Mailbox Restore Browser to restore large number of emails from a VE backup, it fails with MAPI_RC_FAILURE. Messages similar to the following will show up in the Restore Progress window:
Restore Mailbox Messages Error: MAPI_RC_FAILURE
Operation Failed
Operation ended on: 5/23/2016 2:23 PM
Total messages: 0 (1 errors)
Total restore time: 00:22:16

In reality, all the items are restored successfully and these error messages may be ignored.

Workaround: Verify that all emails that were selected for restore, were in fact restored. If so, then the error message may be ignored. If not all emails were restored, then retry the operation with a smaller subset of emails selected for restore.
Segmetation fault on some Linux distributions when set LD_LIBRARY_PATH in the shell window or globally (internal reference #121689)

Problem: Setting LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin in a shell window or globally can make system calls, such as su, have a segmetation fault on some Linux distributions. This is due to version mismatches between the local system libraries and those included in /opt/tivoli/tsm/client/ba/bin directory.

Workaround: Do not set LD_LIBRARY_PATH in the shell window or globally. Instead do the following:

1. Create the following aliases for dsmc and dsmj
alias dsmc='LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin dsmc'
alias dsmj='LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin dsmj'

2. Add a 'export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin' line to the top of /etc/init.d/dsmcad and restart dsmcad, e.g.: service dsmcad restart
Restore fails if storage lease on the vApp is not set to Never Expire (internal reference #121285)

Problem: A restore of a vCloud vApp will fail if a storage lease for the vApp and organization is set to something other the Never Expire. The following messages will be displayed:

ERROR ANS2138E Failed in restoring the vApp properties to vApp: 'Original_vApp'.

Workaround: To successfully backup and restore vApps ensure the storage lease is set to never expire for both the vApp and organization.

7.1.2 Issues and Limitations

Backup of VM with disk size not multiple of 1MB may hang (internal reference #181115)

Problem: Backing up a disk with size not multiple of 1MB may hang during VDDK disk Open call. The issue is due to a Vmware VDDK defect described in https://kb.vmware.com/kb/66936.

Workaround: Increase the disk size to a multiple of 1MB.
Data Protection for VMware vSphere GUI plug-in 7.1.2 not supported in vSphere 6 environment (intrenal reference #154481)

Probelm: The Data Protection for VMware 7.1.2 vSphere GUI plug-in access method is not supported in a vSphere 6 environment.

Workaround: To avoid this issue in a vSphere 6 environment, do not select Register GUI as vCenter Plug-in during installation.
VM restored directly to ESXi 6.0 host does not display in VMware vSphere 6 Client inventory(internal reference #154482)

Problem: In this scenario, a VM was restored directly to an ESXi 6.0 host. The ESXi 6.0 host was specified with either of the following methods:
The vmchost parameter on the backup-archive client command-line:
dsmc restore vm <vmname> -vmchost=<ESXi 6.0 hostname>

The vmchost option in the backup-archive client options file (dsm.opt):
VMCHost <ESXi 6.0 hostname>

The restore operation completed successfully. However, the restored VM does not display in the VMware vSphere 6.0 Client inventory.
This is a known VMware issue. (PR# 1363606)
Single sign-on (SSO) is not available when VMware vCenter 6.0 Server specifies a non-default domain (internal reference #154488)

Problem: In this scenario, Tivoli Storage Manager for Virtual Environments Version 7.1.2: Data Protection for VMware is configured to authenticate using Single sign-on in a vSphere 6.0 environment. However, the vCenter Server domain specifies a non-default domain. As a result, the SSO attempt fails and displays the following message:
ANS2309I Single Sign On login to the vSphere
Server failed in function <visdkGetSecurityToken - Issue.> <"HTTP Error"
Detail: HTTP/1.1 404 Not Found>
A credential login is now attempted.

This is a known VMware issue. (PR#1387340)

Workaround: For SSO login to work in a vSphere 6.0 environment, make sure the vCenter Server domain specifies vsphere.local (default).
Backup of a VM located on a VMware Virtual Volume (VVOL) datastore fails
This behavior is solved with v7.1.4 (internal reference #154489)

Problem: A VM that is located on a VVOL datastore in a vSphere 6.0 environment cannot be
backed up with Tivoli Storage Manager for Virtual Environments Version 7.1.2: Data Protection for VMware. A backup attempt fails and displays the following message:
ANS2713E The virtual machine 'vmname' is in an invalid connection state 'vvol_unsupported'. As a result, it cannot be backed up

Workaround: None
In-guest domain credentials must be enclosed in quotation marks (internal reference #154493)

Problem: When setting domain credentials on a Linux system for an in-guest virtual machine application, you must enclose the domain credentials in quotation marks ("). For example:
dsmc set password -type=vmguest VMGUEST-Part-of-domain "domainname\Administrator" Admin-password
OR
dsmc set password -type=vmguest VMGUEST-Name "Admin-Id" Admin-password
Failure to do so can cause the backup operation to fail. Error messages ANS9398E, ANS1228E, ANS9493E, and ANS4174E typically display when encountering this issue.
Clocks must be in sync to prevent failure of security token request (internal reference #154496)

Problem: The clocks on the data mover and the ESXi host must be in sync within 10 minutes to satisfy the requirements of the Platform Services Controller single-signon (SSO). An informational message is generated that is similar to the following example:
ANS2309I Single Sign On login to the vSphere Server failed in function visdkGetSecurityToken - Issue.

"The time now Tue Feb 24 11:14:29 UTC 2015 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Tue Feb 24 14:11:41 UTC 2015; Tue Feb 24

14:41:41 UTC 2015). This might be due to a clock skew problem."
Detail: [no detail]
A credential login is now attempted.

Workaround: When installing the vCenter Server, synchronize the ESXi clock with a Network Time Protocol (NTP) server. Note that the amount of time that the clocks can be out of sync is configured in the vSphere Web Client.
Remote Platform Services Controller (PSC) unavailable for Single Sign On (SSO) (internal reference #154499)

Problem: In this scenario, the data mover cannot communicate with the PSC for SSO. An informational message is generated that is similar to the following example:
ANS2309I Single Sign On login to the vSphere Server failed in function

visdkTestSSOEndpoint - .
hostname/sts/STSService
"No connection could be made because the target machine actively refused it."
Detail: connect failed in tcp_connect()

A credential login is now attempted.

Workaround: Open a command prompt on the data mover and ping the PSC to make sure communication is active and that a firewall is not interfering. By default, the PSC uses port 80 (http) and port 443 (https). You can customize the port settings in the PSC installer.
Issues with virtual machines hosted on an ESXi host upgraded to vSphere 6.0 (internal reference #154500)

Problem: In this scenario, the virtual machine is on an ESXi host that was upgraded from vSphere 5.x to vSphere 6.0. After the upgrade, the following issues occur:
- Change Block Tracking (CBT) does not work. As a result, Data Protection for VMware 7.1.2 forces a full VM backup.
- Virtual machine quiescing fails. As a result, the snapshot and the backup fail.

Messaging is generated that is similar to the following example:
2015-03-23T22:22:45.267Z| vcpu-0| I120: DISKLIB-CTK : Could not open change tracking file "/vmfs/volumes/51c4ef65-ee5af035-6d95-00145e575bc2/win2008r2x64 -
small/win2008r2x64 - small_1-000002-ctk.vmdk": Change tracking invalid or disk in use.
2015-03-23T22:22:45.269Z| vcpu-0| I120: DISKLIB-CTK : Re-initializing change tracking.
2015-03-23T22:22:45.269Z| vcpu-0| I120: DISKLIB-CTK : Auto blocksize for size
10485760 is 128.
2015-03-23T22:22:45.269Z| vcpu-0| I120: OBJLIB-FILEBE : Error creating file
'/vmfs/volumes/51c4ef65-ee5af035-6d95-00145e575bc2/win2008r2x64 -
small/win2008r2x64 - small_1-000002-ctk.vmdk': 3 (The file already exists).
2015-03-23T22:22:45.271Z| vcpu-0| I120: DISKLIB-CBT : Initializing ESX kernel change tracking for fid 2756465.
2015-03-23T22:22:45.271Z| vcpu-0| I120: DISKLIB-CBT : Creating cbt node 2a0f71-cbt failed with error Cannot allocate memory (0xbad0014, Out of memory).
2015-03-23T22:22:45.271Z| vcpu-0| W110: DISKLIB-LIB : Could not attach vmkernel change tracker: ESXi tracking filter failed (0x143c). Disk will be opened, but change tracking info vill be invalidated.

Workaround: Make sure that the ESXi host memory use does not exceed 75%.
Backup of a VM with application protection fails when one (or more) Microsoft Exchange Server 2013 databases are dismounted (internal reference #154505)

Problem: In this scenario, a virtual machine with application protection enabled was backed up with Data Protection for VMware 7.1.2. However, the virtual machine contained one (or more) Microsoft Exchange Server 2013 databases that were dismounted. As a result, the backup operation fails with the following warning message:
ANS9432W IBM Tivoli Storage Manager application protection failed to truncate application logs on virtual machine 'VM-name'.

Workaround: Mount the Exchange Server 2013 database, then run the backup operating again.
Memory leak is observed when backing up a virtual machine (internal reference #154501)

Problem: In this scenario, a virtual machine was backed up with Data Protection for VMware 7.1.2 in loop mode. The loop command starts an interactive command line session that is maintained until you enter quit. When the backup operation completes, a loss of available memory occurs. The loss of memory can be viewed by starting the Windows system Task Manager and going to Performance -> Available Memory after each backup operation completes. However, the memory is freed after the dsmc loop mode exits. This is a known issue.

Workaround: To prevent memory leaks, back up the virtual machine without using loop mode. This is the best practice when using Data Protection for VMware 7.1.2.
Restoring virtual machines backed up with Data Protection for VMware 7.1.2 from down-level clients is not supported (internal reference #145571)

Problem: Virtual machines backed up with Data Protection for VMware 7.1.2 cannot be restored from down-level clients. This includes prior levels of the Tivoli Storage Manager backup-archive client, as well as prior levels of Data Protection for VMware.
Backing up a virtual machine that has a Data Protection for VMware volume mounted (internal reference #145574)

Problem: When the virtual machine being backed up is running Data Protection for VMware and has a Data Protection for VMware volume mounted, the backup of that virtual machine might fail with the following message:
"Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine".

Workaround: To allow the backup of this virtual machine to continue, unmount the volume from Data Protection for VMware and try the operation again.
Unsupported restore tasks when the Microsoft Exchange Server database changes after virtual machine backup (internal reference #154506)

Problem: An Exchange Server database restore or user mailbox restore from the backed up virtual machine are not supported when either of the following issues occur after the virtual machine is backed up:
-The database is relocated to a different volume.
-The database path changes.
Microsoft Exchange Server mailbox history not collected (internal reference# 154504)

Problem: When Data Protection for VMware creates an application consistent backup of a virtual machine that hosts Microsoft Exchange Server, the mailbox history is not collected.
Upgrading a vCenter Server from 5.5 to 6.0 may result in incomplete IBM Tivoli Storage Manager task messages in the vCenter Client Task Panel (internal reference #154502)

Problem: It is unclear if an error occurred during the upgrade process or not but in one instance incomplete messages were observed. The messages look like the following:
- XXX com.ibm.tsm.tasks.backup_vm_scheduled.label not found XXX
- XXX com.ibm.tsm.tasks.backup_vm.label not found XXX
- XXX com.ibm.tsm.tasks.restore_vm.label not found XXX

Workaround: The issue can be corrected by logging into the vCenter Managed Object Browser and removing the old IBM Tivoli Storage Manager extensions. The extensions will be added back during the next backup or restore.
1. Go to (vCenterServer)/mob/?moid=ExtensionManager
2. You should see the following extensions:
- "com.ibm.tsm.tasks"
- "com.ibm.fcm.tasks"
3. In the "Methods" section select the method "UnregisterExtension"
4. Enter the extension names "com.ibm.tsm.tasks" and "com.ibm.fcm.tasks" one at a time and press "Enter".

7.1.3 Issues and Limitations

Known issues and limitations for file restore operations that are run from the Tivoli Storage Manager file restore interface are documented in the following technote:
http://www.ibm.com/support/docview.wss?uid=swg21964753

7.1.4 Issues and Limitations

Direct mount and restore functions unavailable after installing the Recovery Agent device driver in silent mode (internal reference #109537)

Problem: In this scenario, the Recovery Agent device driver ("Mountdriver" 32-bit; "mountdriver" 64-bit) was installed in silent mode. However, the Recovery Agent cannot mount directly or restore data.

Workaround: To resolve this issue, register the Recovery Agent device driver and restart the system by completing the following steps:
1. Open a command prompt in administrator mode.
2. Issue the following command from the Recovery Agent "mount" folder:
install.exe C:\\Windows\\system32\\drivers\\fbvv.inf fbvv >> installFBVV.log 2>&1
3. Restart the system.
Intermittent backup failure of VMs on vVol datastores (internal reference #108537)

Problem: In this scenario, a backup VM operation using the scheduler service fails with the following error messages:
ANS4174E
ANS1228E
ANS5283E
However, the same VMs can be backed up successfully by starting the operation manually (dsmc backup vm), or by starting the scheduled backup manually using dsmc sched. The failure occurs when all of the following conditions exist:
- The VMs are on vVol datastores.
- A different userid account is used for the scheduler service. For example, a Local Administrator account versus the Active Directory Administrator account.

Workaround: This is a known issue. To avoid this issue, make sure that the same account is used for all backup operations. If the problem still exists, change the temp working directory in the dsmvddk.opt file by setting the tmpDirectory option. Create this temp working directory using the same account that will be used for performing backups.
An error is returned during an install or uninstall on RHEL 6.8 and later versions (internal reference #114081, #121574)

Problem: On Red Hat Enterprise Linux 6.8 and later versions, when you run the Data Protection for VMware 7.1.4 or Data Protection for VMware 7.1.6 installer (install-Linux.bin) or uninstaller (/opt/tivoli/tsm/tdpvmware/_uninst/TDPVMware/Uninstall_Tivoli_Data_Protection_for_VMware), you get the following error in the terminal:

strings: '/lib/libc.so.6': No such file

You can ignore this error.
FlashCopy Manager offload operations do not support VMDKs greater than 2 TB(internal reference #115239)

Problem: For FlashCopy Manager offload operations, a VMDK involved in a backup operation must be 2 TB or less in size. If a VMDK is greater than 2 TB, the backup operation fails.

7.1.6 Issues and Limitations

Ad-hoc backups completed from the IBM Data Protection view are displayed in the Data Protection for VMware vSphere GUI browser view (internal reference #121396)

Problem: If you complete ad-hoc backups by using the IBM Data Protection extension view in the vSphere Web Client, the backup tasks are displayed on the Backup Schedules page of the Data Protection for VMware vSphere GUI browser view.

Workaround: You can manually remove the backup tasks from the page.
Modifying the install may cause the installation to attempt to unregister the vCenter plugin and or the Web Client Extension (internal reference #124918)

Problem: If the user goes into Programs and Features on Windows and chooses to modify the install, the installation will attempt to unregister the vCenter plugin and or Web Client Extension. A pop up message will appear stating the component being unregistered failed. The vCenter plugin and Web Client extension will continue to work after the modify install completes.

7.1.8 Issues and Limitations

Upgrade from 7185 to 810 would fail (internal reference #182424)

Problem: When performing upgrade from Data Protection for VMware v7.1.8.5 to v8.1.0, would ran into failure with a prompt saying "Downgrade not allowed"

Workaround: Please upgrade 7185 to most current Data Protection for VMware versions: 8.1.7 or 8.1.6
Adding Deleted Mount Proxy Node Results in Blank Error Dialog (internal reference #154162)

Problem: When a user attempts to add a Mount Proxy node that already exists in the Spectrum Protect server, they should received a dialog box with an error indicating the node already exists. Instead of seeing the error text, they will still see a dialog, but without any text. This will only occur if a 7.1.8+ Spectrum Protect server or a 8.1.4+ Spectrum Protect server is being used. Older 7.1.x and 8.1.x Spectrum Protect servers show the correct message. The text that should be displayed is:
"ANR2147E REGISTER NODE: Node XYZ is already registered.

Workaround: The user will correctly get an error message, it will just be empty.
Recent Tasks Refresh Button Intermittently Inoperative in Internet Explorer (internal reference #153006)

Problem: The refresh button on the table in the recent tasks tab in the Data Protection Virtual Environments web user interface occasionally does not respond when clicked from an Internet Explorer browser. The issue is present when a period of inactivity occurs. The button can be clicked, but the "loading table" message does not appear. The table is never updated.

Workaround: Refresh the entire page or navigate from and back to the page. To avoid the issue, use a browser other than Internet Explorer.
IBM Spectrum Protect for VMware 7.1.8 does not support VMware tagging. Tags made in previous versions will not work. (internal reference #151801)

Problem: Any IBM Spectrum Protect data mover client command like 'BACKUP VM' or 'RESTORE VM' that needs to leverage VMware Tagging support may fail connecting to the VMware Platform Service Controller (PSC). An error similar to this will be seen:
ANS2633E The vCloud Suite plug-in runtime library failed to log into the Platform Services Controller on 'mymachine.ibm.com' with user name 'administrator@vsphere.local': authentication failed.
The root cause is in the VMware environment: "JDK 1.8 Update 141 and 144 fails to make an SSO connection to the vSphere Management and the vSphere Automation API" https://kb.vmware.com/kb/2151706. Please see APAR IT22523 for details.
After successful installation of 7.1.8 Data Protection for VMware with vcloud mode, Web GUI does not function correctly (internal reference #154183)
This behavior is solved with v7.1.8.1 (internal reference # IT22690)

Problem: After successful installation of 7.1.8 Data Protection for VMware with vcloud mode and login Web GUI, customer will be unable to load /TsmVMwareUI/RPCAdapter and get error message: “Unable to load /TsmVMwareUI/RPCAdapter status:401”

Workaround: No work around.
"You do not have access rights to this file" or similar error during vm backup/restore with GPO configured user. (internal reference #162908)

Problem: If a user is configured using GPO backup/restore vm may fail with "You do not have access rights to this file" or similar permissions error. This is due to VMware VDDK expects user to be an administrator: https://kb.vmware.com/kb/52441
Backup fails with ANS9308E on a machine with the Windows Containers feature installed. (internal reference #177062)

Problem: When the Windows Containers feature is installed, DP for VMware mistakenly assumes that you are backing up Hyper-V VMs rather than VMware VMs, and fails with: "ANS9308E (RC7107) No match found for the Hyper-V VM name or VMList "*" entered."
To determine whether the Windows Containers feature is installed, run the following Powershell cmdlet:
PS C:\Users\Administrator> Get-WindowsFeature *container*
Display Name                                            Name                       Install State
------------                                            ----                       -------------
[X] Containers                                          Containers                     Installed

Workaround: Use the DP for VMware UI to set the backup type to 'VMware Full VM'. Alternatively, set the VMBACKUPType to FUllvm or simply delete the VMBACKUPType option as FUllvm is the default.

[{"Product":{"code":"SSERB6","label":"IBM Spectrum Protect for Virtual Environments"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data Protection for VMware","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.1","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}},{"Product":{"code":"SS8TDQ","label":"Tivoli Storage Manager for Virtual Environments"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data Protection for VMware","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Tips