Documentation updates for IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.x

Product Documentation

Abstract

This document contains updates for IBM Spectrum Protect™ for Virtual Environments: Data Protection for VMware 7.1.x documentation.

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.

V7.1.0 Updates for Tivoli Storage Manager for Virtual Environments

This section contains updates for the following IBM Tivoli Storage Manager for Virtual Environments publications:

-Data Protection for VMware 7.1.0 Installation Guide
-Data Protection for VMware 7.1.0 User's Guide
-Data Protection for VMware Recovery Agent 7.1.0 GUI Online Help
-Tivoli Data Protection for VMware Information Center for Version 2.1 (vSphere GUI, vCloud GUI)

Mount operation considerations

Before undertaking a mount operation observe the following conditions when using Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.1, 7.1.2, and 7.1.3 :

Multipathing must be disabled on the Linux mount proxy system before you attempt a mount operation.
Be aware that Logical Volume Manager (LVM) filtering might block iSCSI connections.
The Linux mount proxy system does not support LVM auto activation.

These considerations also apply in Data Protection for HyperV environments.

For additional instructions that describe how to set up your environment for full virtual machine instant restore and instant access operations, see the Configuring Tivoli Storage Manager for Virtual Environments 7.1.x for full virtual machine instant restore operations technote at http://www.ibm.com/support/docview.wss?uid=swg21683643.

Clarification regarding Target IP parameter in TDPVMwareMount.conf file

Knowledge Center:
(1) Configuring Data Protection for VMware > Configuring systems for iSCSI mount (following Step 2e)
(2) Configuring Data Protection for VMware > Configuring the Data Protection for VMware Recovery Agent GUI (following Step 5)
(3) Recovery Agent command-line interface > Recovery Agent command-line interface overview > Mount command
(add -target)

Installation Guide:
(1) Page 65 (following Step 2e)"cgrace@tw.ibm.com"
(2) Page 71 (following Step 5)

User's Guide:
(3) Page 73 (add -target "iSCSI target")

The Target IP parameter (in the C:\ProgramData\Tivoli\TSM\TDPVMware\mount\TDPVMwareMount.conf file) identifies the IP address of the network card on the system that exposes the iSCSI targets. This system is typically the data mover system. The Target IP parameter must be specified when you use an iSCSI network with your Data Protection for VMware Recovery Agent operations.

To clarify this parameter requirement, the following statement belongs in the locations identified under "Knowledge Center", "Installation Guide", and "User's Guide" for this documentation update:

When you use the Data Protection for VMware Recovery Agent in an iSCSI network, go to the
C:\ProgramData\Tivoli\TSM\TDPVMware\mount\TDPVMwareMount.conf file and specify
the [IMOUNT config] tag and Target IP parameter:

[IMOUNT config]
Target IP=<IP address of the network card on the system that exposes the iSCSI targets.>

For example:

[General config]
param1
param2
...
[IMount config]
Target IP=9.11.153.39

After you add or change the Target IP parameter, restart the Recovery Agent GUI or Recovery Agent CLI.

Instant access and instant restore operations fail when using NFS data stores

Knowledge Center: Protection for VMs > Full VM instant restore environment requirements
User's Guide: Page 15

The following statement belongs at the end of the bulleted list:

NFS data stores are not supported as a temporary data store or target data store for instant access and instant restore operations. This restriction is due to a VMware limitation 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)"
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1001856.

Application protection supported on Microsoft Exchange Server 2013

Knowledge Center: Self-contained application protection overview > Application protection for Microsoft Exchange Server and SQL Server
User's Guide: Page 33

Microsoft Exchange Server 2013 is missing from the list of applications that Data Protection for VMware V7.1 supports for application protection. The correct list is shown below:

Data Protection for VMware V7.1 backs up VM guests with both guest level application consistency and log truncation for the following applications:
- Microsoft Exchange Server 2010
- Microsoft Exchange Server 2013
- Microsoft SQL Server 2008
- Microsoft SQL Server 2008 R2
- Microsoft SQL Server 2012

Upgrade step to uninstall Tivoli Storage Manager backup-archive client V6.1 applies only to Linux systems

Knowledge Center: Upgrading Data Protection for VMware > Upgrading Data Protection for VMware from Version 6.x
Install Guide: Page 50

Step 3a (provided below) applies only to Linux systems. Step 3a does not apply to Windows systems:

a. Uninstall Tivoli Storage Manager backup-archive client V6.x. Detailed
backup-archive client uninstall instructions are described in the Tivoli
Storage Manager Knowledge Center at:
http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1

Alternatively, first upgrade the Tivoli Storage Manager API and Tivoli Storage Manager backup-archive client with the following command:

rpm -Uhv TIVsm-API64.x86_64.rpm TIVsm-BA.x86_64.rpm

Then upgrade Tivoli Storage Manager for Virtual Environments by running the install-Linux.bin file.
Note: Upgrade with the rpm command is available with V6.3 (or later).

Windows 64-bit system silent installation example contains incorrect character

Knowledge Center: Installing Data Protection for VMware > Installing Data Protection for VMware in silent mode > Installing selected Data Protection for VMware features on a Windows 64-bit system in silent mode
Install Guide: Page 38

The example of installing the Tivoli Storage Manager backup-archive client data mover features in Step 5b (provided below) is incorrect. It contains an extraneous character ( \ ) after the AdministrativeCmd parameter:

setup.exe /s /a /s /v"/qn ADDLOCAL=BackupArchiveGUI,BackupArchiveWeb,Api64Runtime,AdministrativeCmd\" /L1033

The correct example is provided below:

setup.exe /s /a /s /v"/qn ADDLOCAL=BackupArchiveGUI,BackupArchiveWeb,Api64Runtime,AdministrativeCmd" /L1033

Set access command examples missing a dash before the TYPE parameter

Knowledge Center: Configuring Data Protection for VMware > Configuring the Data Protection for VMware Recovery Agent GUI
Install Guide: Page 68

The set access examples (in the description of the Fromnode option) are missing a dash ( - ) before the TYPE parameter. The TYPE parameter requires a dash ( - ) to precede the parameter. The correct set access examples are provided below:

set access backup -TYPE=VM vmdisplayname mountnodename

set access backup -TYPE=VM myTestVM myMountNode

Incorrect reference to "IBM Tivoli Storage Manager FastBack for Microsoft Exchange" when recovering an Exchange mailbox item

Knowledge Center: Mount, file-level restore, and instant restore of volumes overview > File-level restore overview > File-level restore guidelines for Windows systems
User's Guide: Page 28

The following statement incorrectly references the "IBM Tivoli Storage Manager FastBack for Microsoft Exchange" product:

In order to recover Microsoft Exchange Server mailbox items, you must use the IBM® Tivoli Storage Manager FastBack® for Microsoft Exchange product and documentation. As a result, IBM Tivoli Storage Manager FastBack for Microsoft Exchange must be purchased separately with a valid license. For more information, see the following product website:
http://www.ibm.com/software/tivoli/products/storage-mgr-fastback-exchange/

"IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server" is required when recovering an Exchange mailbox item, not "IBM Tivoli Storage Manager FastBack for Microsoft Exchange." As a result, the correct statement is provided below:

In order to recover Microsoft Exchange Server mailbox items, you must use the IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server product and documentation. As a result, IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server must be purchased separately with a valid license. For more information, see the following product website:
http://www.ibm.com/software/products/en/tivostormanaformail/

Knowledge Center: Restoring VMware vSphere or vCloud data > Full VM recovery with application protection > Recover a Microsoft Exchange mailbox item from a VM backup
User's Guide: Page 107

The following statement incorrectly references the "IBM Tivoli Storage Manager FastBack for Microsoft Exchange" product:

To recover Microsoft Exchange Server mailbox items from a VM backup, you must use both Data Protection for VMware and the IBM® Tivoli Storage Manager FastBack® for Microsoft Exchange product and documentation. As a result, IBM Tivoli Storage Manager FastBack for Microsoft Exchange must be purchased separately with a valid license. For more information, see the following product website:
http://www.ibm.com/software/tivoli/products/storage-mgr-fastback-exchange/

A mailbox item recovery scenario uses the products in the following order:

1. Access the VM backup by using the Data Protection for VMware Recovery Agent.
2. Recover mailbox items by using FastBack for Microsoft Exchange.

To recover Microsoft Exchange Server mailbox items from a VM backup, you must use both Data Protection for VMware and the IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server product and documentation. As a result, IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server must be purchased separately with a valid license. For more information, see the following product website:
http://www.ibm.com/software/products/en/tivostormanaformail/

A mailbox item recovery scenario uses the products in the following order:

1. Access the VM backup by using the Data Protection for VMware Recovery Agent.
2. Recover mailbox items by using IBM Tivoli Storage Manager Mail: Data Protection for Microsoft
- Exchange Server.

Knowledge Center: Restoring VMware vSphere or vCloud data > Restoring files and instant restore of volumes > Restoring files (Windows)
User's Guide: Page 113

The following statement incorrectly references the "IBM Tivoli Storage Manager FastBack for Microsoft Exchange" product:

In order to recover Microsoft Exchange Server mailbox items, you must use the IBM® Tivoli Storage Manager FastBack® for Microsoft Exchange product and documentation. As a result, IBM Tivoli Storage Manager FastBack for Microsoft Exchange must be purchased separately with a valid license. For more information, see the following product website:
http://www.ibm.com/software/tivoli/products/storage-mgr-fastback-exchange/

In order to recover Microsoft Exchange Server mailbox items, you must use the IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server product and documentation. As a result, IBM Tivoli Storage Manager Mail: Data Protection for Microsoft Exchange Server must be purchased separately with a valid license. For more information, see the following product website:
http://www.ibm.com/software/products/en/tivostormanaformail/

VE_DATACENTER_NAME examples show incorrect syntax in vmcli -f set_password command

Knowledge Center: Tivoli Storage Manager for Virtual Environments>Data Protection for VMware command-line interface>Set_password
User's Guide: Page 58, 59

The following VE_DATACENTER_NAME examples (in the in vmcli -f set_password command) contain incorrect syntax:

(Linux page 58)
VE_DATACENTER_NAME: DataCenter1:TSM_DC1
VE_DATACENTER_NAME: DataCenter2:TSM_DC2
VE_DATACENTER_NAME: DataCenter3:TSM_DC3
VE_DATACENTER_NAME: DataCenter4:TSM_DC4

(Windows page 59)
VE_DATACENTER_NAME: DataCenter1:TSM_DC1
VE_DATACENTER_NAME: DataCenter2:TSM_DC2

The correct syntax is shown below:
(Linux page 58)
VE_DATACENTER_NAME DataCenter1::TSM_DC1
VE_DATACENTER_NAME DataCenter2::TSM_DC2
VE_DATACENTER_NAME DataCenter3::TSM_DC3
VE_DATACENTER_NAME DataCenter4::TSM_DC4

(Windows page 59)
VE_DATACENTER_NAME DataCenter1::TSM_DC1
VE_DATACENTER_NAME DataCenter2::TSM_DC2

Clarification regarding VMDK 2 TB restriction

Knowledge Center: Preparing to install Data Protection for VMware > Hardware requirements
User's Guide: Page 12

The following restriction requires clarification:

Restriction: Each individual VMDK involved in a backup operation cannot exceed 2 TB. If a VMDK exceeds 2 TB, the backup operation fails. To prevent a failure, you can skip processing the VMDK by specifying the vmskipmaxvmdks yes in the Tivoli® Storage Manager backup-archive client options file or during the dsmc invocation.

The following statement is the clarified restriction:

Restriction: Starting with vCenter 5.5 and ESXi 5.5 hosts, VMware supports VMDKs larger than 2 TB. However Tivoli Storage Manager cannot back up VMDKs that are 2 TB or larger in size. Each individual VMDK involved in a backup operation cannot exceed 2 TB. If a VMDK exceeds 2 TB, the backup operation fails. To prevent a failure, you can skip processing the VMDK by specifying the vmskipmaxvmdks yes in the Tivoli® Storage Manager backup-archive client options file or during the dsmc invocation.

Instructions regarding how to silently install language packs on Windows are missing

To install a language pack on a supported Windows operating system in silent mode, complete the following steps:

1. Either download the code package or insert the Data Protection for VMware product DVD into the DVD drive.

2. From the Windows Start menu, select Run and enter the following command for your operating system (where X represents the DVD drive):
(32-bit)
X:\DVD\tsm4ve\LanguagePack\x86\setup.exe /s /v"/qn ADDLOCAL=LanguageNameLP"
(64-bit)
X:\DVD\tsm4ve\LanguagePack\x64\setup.exe /s /v"/qn ADDLOCAL=LanguageNameLP"

LanguageNameLP is one (or more) of the following values:

ChineseS_LP
ChineseT_LP
Czech_LP
German_LP
French_LP
Hungarian_LP
Italian_LP
Japanese_LP
Korean_LP
Polish_LP
Portugese_LP
Russian_LP
Spanish_LP

When multiple LanguageNameLP values are specified, separate each value by a comma. Do not include a space between the comma or the value. For example:

X:\DVD\tsm4ve\LanguagePack\x64\setup.exe /s /v"/qn ADDLOCAL=German_LP,French_LP,Czech_LP"

3. Click OK after you enter the setup.exe command and LanguageNameLP value.

Data Protection for VMware vSphere GUI user role information not available in IBM Knowledge Center

User roles describe available GUI functions based on the authority level that is assigned to the Tivoli Storage
Manager administrator ID. The Data Protection for VMware 7.1.x collections in IBM Knowledge Center do not contain
this user role information. However, this information is available in the online help system that is delivered with
the Data Protection for VMware 7.1.x vSphere GUI.

To access the user role information, complete these steps:
1. Open the Data Protection for VMware 7.1.x vSphere GUI.
2. Click the Help icon ("?"). The online help system opens in a web browser.
3. In the online help system, go to "Getting started in a vSphere environment > Configuring
the Data Protection for VMware vSphere GUI > Data Protection for VMware vSphere GUI
roles".

Clarification of supported environments for in-guest application protection

Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.0, 7.1.1, 7.1.2, and 7.1.3
supports in-guest application protection for VMware VMs in a VMware vSphere environment only. In-guest application
protection is not supported for VMware vApps in a vCloud environment.

V7.1.0.2 Updates for Tivoli Storage Manager for Virtual Environments

When a user does not have sufficient permissions for any datacenter, access to the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware GUI is blocked. The Tivoli Storage Manager for Virtual Environments: Data Protection for VMware GUI issues error message GVM2013E to advise that the user is not authorized to access any managed datacenters due to insufficient permissions:

GVM2013E The user User_Name is not authorized to any managed datacenters. Contact your system administrator.

Other new messages are also available that inform users of issues that result from insufficient permissions.

To resolve permissions issues, system administrators can assign the required permissions to VMware users as documented in the following web page:
http://www.ibm.com/support/docview.wss?uid=swg21659544

V7.1.1 Updates for Tivoli Storage Manager for Virtual Environments

This section contains updates for the following IBM Tivoli Storage Manager for Virtual Environments publications:

-Data Protection for VMware 7.1.1 Installation Guide
-Data Protection for VMware 7.1.1 User's Guide
-Tivoli Storage Manager Recovery Agent 7.1.1 GUI Online Help
-Tivoli Data Protection for VMware Information Center for Version 2.1.1 (vSphere GUI, vCloud GUI)

Updated VMware vCenter Server user privilege requirements

Knowledge Center: Data Protection for VMware>Protection for VMs>VMware vCenter Server user privilege requirements
User's Guide: Page 9
Installation Guide: Page 10

The following objects and privileges are missing from "Table 1. Required privileges vCenter Server user ID and data mover":
Table 1. Required privileges vCenter Server user ID and data mover

vCenter Server objects	Associated privileges that are required
Global	Licenses, Log Event, Cancel Task, Set custom attribute
Virtual machine > Configuration	Add existing disk, Add new disk, Add or remove device, Advanced, Change CPU count, Change resource, Disk change tracking, Disk Lease, Host USB device, Memory, Raw device, Reload from path, Remove disk, Rename, Reset guest information, Settings, Swap file placement, Upgrade virtual hardware
Virtual machine > Guest operations	Guest Operation Modifications, Guest Operation Program Execution, Guest Operation Queries
Virtual machine > Inventory	Create new, Register, Remove, Unregister
Virtual machine > Provisioning	Allow disk access, Allow read-only disk access, Allow virtual machine download
Virtual machine > Snapshot management	Create snapshot, Remove snapshot, Rename snapshot, Revert to snapshot

Clarification regarding Microsoft Windows operating system support for application protection

Knowledge Center: Data Protection for VMware > Self-contained application protection overview > Application protection for Microsoft Exchange Server and SQL Server
User's Guide: Page 37

Application protection for Microsoft Windows operating systems applies to Microsoft Windows 64-bit operating systems only. This 64-bit clarification is missing from the list of Microsoft Windows operating systems that Data Protection for VMware V7.1.1 supports for application protection. The clarified list is shown below:

Application protection for VM guests is supported on the vStorage Backup server for the following platforms:
- Microsoft Windows 2008 (64-bit)
- Microsoft Windows 2008 R2 (64-bit)
- Microsoft Windows 2012 (64-bit)
- (Windows) VMware ESX 5.x (or later)
- Linux 64-bit platforms
- (Linux) VMware ESX 5.x (or later)

Clarification regarding Full VM instant restore iSCSI network requirements

Knowledge Center: Protection for VMs > Full VM instant restore environment requirements > Full VM instant restore iSCSI network requirements
User's Guide: Page 24

The following statement belongs at the beginning of this section:

For additional instructions that describe how to set up your environment for full virtual machine instant restore and instant access operations, see the Configuring Tivoli Storage Manager for Virtual Environments 7.1.x for full virtual machine instant restore operations technote at http://www.ibm.com/support/docview.wss?uid=swg21683643.

Typo in vmdk and -vmdk keyword examples

Knowledge Center: Data Protection for VMware > Data Protection for VMware command-line interface > Restore
User's Guide: Page 48-49

In the following vmdk and -vmdk examples, the first vmname keyword entry is incorrect ("vmanme"):

backupid:26801107 vmanme:myvm:vmdk=Hard Disk 1::vmname:newname

backupid:26801107 vmanme:myvm:-vmdk=Hard Disk 4::vmname:newname

The correct examples are shown below:

backupid:26801107 vmname:myvm:vmdk=Hard Disk 1::vmname:newname

backupid:26801107 vmname:myvm:-vmdk=Hard Disk 4::vmname:newname

Clarification regarding Target IP parameter in RecoveryAgent.conf file

Knowledge Center:
(1) Configuring Data Protection for VMware > Manually configuring an iSCSI device on a Windows system (following Step 2e)
(2) Configuring Data Protection for VMware > Configuring the Tivoli Storage Manager Recovery Agent GUI (following Step 5)
(3) Recovery Agent command-line interface > Recovery Agent command-line interface overview > Mount command
(add -target)

Installation Guide:
(1) Page 76 (following Step 2e)
(2) Page 72 (following Step 5)

User's Guide:
(3) Page 81 (add -target "iSCSI target")

The Target IP parameter (in the C:\ProgramData\Tivoli\TSM\RecoveryAgent\mount\RecoveryAgent.conf file) identifies the IP address of the network card on the system that exposes the iSCSI targets. When you use the Tivoli Storage Manager Recovery Agent with an iSCSI network, and the Recovery Agent does not use a data mover, you must specify the Target IP parameter.

To clarify this parameter requirement, the following statement belongs in the locations identified under "Knowledge Center", "Installation Guide", and "User's Guide" for this documentation update:

When you use the Tivoli Storage Manager Recovery Agent in an iSCSI network, and the Recovery Agent does not use a data mover, go to the C:\ProgramData\Tivoli\TSM\RecoveryAgent\mount\RecoveryAgent.conf file and specify the [IMOUNT config] tag and Target IP parameter:

[IMOUNT config]
Target IP=<IP address of the network card on the system that exposes the iSCSI targets.>

For example:

[General config]
param1
param2
...
[IMount config]
Target IP=9.11.153.39

After you add or change the Target IP parameter, restart the Recovery Agent GUI or Recovery Agent CLI.

Clarification regarding "Date/Time of the last backup" field

Data Protection for VMware vSphere GUI / Tivoli Storage FlashCopy Manager for VMware GUI Online Help:

"Backing up VM data with Tivoli Storage FlashCopy Manager (Step 8d)"
"Backing up VM data with Tivoli Storage FlashCopy Manager and Tivoli Storage Manager for Virtual Environments (Step 9d)"

The following step is incorrect:

Optional: In the Date and time of the last backup field, specify when you want to stop the schedule from running. If you do not specify the date and time of the last backup, the schedule continues to run indefinitely.

The step is not optional. A date and time must be specified (as correctly documented in the hover help). The correct step is provided below:

In the Date and time of the last backup field, specify when you want to stop the schedule from running. If you do not specify the date and time of the last backup, the schedule creation cannot continue.

Clarification regarding Windows 32-bit directory for silent uninstall

Knowledge Center: Installing Data Protection for VMware> Uninstalling Data Protection for VMware> Uninstalling Data Protection for VMware for a
Windows 32-bit system in silent mode
User's Guide: Page 42

The following statement in Step 1 is incorrect:

To uninstall Data Protection for VMware with an uninstall.iss file, go to
the X64 folder.

The correct statement is provided below:

To uninstall Data Protection for VMware with an uninstall.iss file, go to
the X86 folder.

V7.1.2 Updates for Tivoli Storage Manager for Virtual Environments

This section contains updates for the following IBM Tivoli Storage Manager for Virtual Environments publications:

-Data Protection for VMware 7.1.2 Installation Guide
-Data Protection for VMware 7.1.2 User's Guide
-Tivoli Storage Manager Recovery Agent 7.1.2 GUI Online Help
-Data Protection for VMware Online Help (vSphere GUI, vCloud GUI)

(v7.1.2 only) Data Protection for VMware > Protection of Microsoft Exchange Server data hosted in VMware environments > Installing and configuring for Microsoft Exchange Server data protection in a VMware environment > Configuring Data Protection for Microsoft Exchange Server

Update starting with step 3 through the end of the topic. Correction to step 3 through the end of the topic is provided here:

3. Configure Data Protection for Microsoft Exchange Server using the Tivoli Storage Manager configuration wizard. When you navigate to the Tivoli Storage Manager Node Names page of the wizard, enter the datacenter node name, Exchange node name, and VSS requestor node name. If the datacenter node name field is disabled, the Data Protection for VMware recovery agent is not installed correctly.

4. After Data Protection for Microsoft Exchange Server is configured, verify that the Configuring Recovery Agent rule status indicates Passed. Configure Recovery agent CLI to work Recovery agent on your vm:

a. Open Recovery Agent CLI:Start->Tivoli Storage Manager->Tivoli Storage For Virtual Environments->Recovery Agent CLI b. Run the following command: RecoveryAgentShell.exe -c set_connection mount_computer vm_name

Sample: RecoveryAgent\shell>RecoveryAgentShell.exe -c set_connection mount_computer vm_exc10

5. Log on to one of the data mover instances and complete the following steps. Do not repeat these steps for all data mover instances.

a. For backup-archive client that has been configured as the VSS requestor node on TDP for Exchange, give access to the virtual machine backups using the backup-archive client command-line interface command 'set access'. This step is required because the VSS requestor node acts on behalf of Data Protection for Microsoft Exchange Server node, when it accesses vm backups.

This command is run directly from one of the data mover nodes (datamover10 and datamover20). Create a temporary options file dsm.setaccess.opt from dsm.opt and run 'set access' command using the following steps:

1) Copy the dsm.opt file to the dsm.setaccess.opt file.

2) Edit the dsm.setaccess.opt file. For any line that contains ASNODE, delete the line.

3) Edit the dsm.setaccess.opt file to set the NODENAME to your data center node name NODENAME datacenter_node

Sample: NODENAME datacenter10

b. Run 'set access' command:

dsmc set access backup -type=VM vm_name vss_requestor_node -optfile=dsm.setaccess.opt

Sample: dsmc set access backup –type=VM vm_exc10 EXC10_VSS –optfile=dsm.setaccess.opt

ANS1148I “Set Access” command successfully completed.

c. Run 'query access' command to verify that VSS requestor node obtained access to VM backups:

dsmc query access -optfile=dsm.setaccess.opt

Node name: datacenter10
Type Node User Path
-------------------------------------------------------

Backup EXC10_VSS * \VMFULL-vm_exc10\*\*

ANS1148I “Query Access” command completed successfully

If the datacenter node name password is unknown, the Tivoli Storage Manager server administrator has to reset the password to run the set access command.

-------------------------------------------------------------------------------------------------------------------------------------------------------------

(v7.1.2 only) Data Protection for VMwarer > Protection of Microsoft Exchange Server data hosted in VMware environments > Backup management > Verifying backups

For individual mailbox restore and database restore, VMVSS restore is not supported if database path changed after the virtual machine backup was taken. Old virtual machine backups can not be used to restore the moved database.

This same limitation should be remembered when you read the Restoring and recovering data > Recovering data by using the command-line interface topic.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
(v7.1.2 only) Clarification to the Data Protection for VMware > Mailbox restore guidelines

The options TEMPLOGRestorepath and TEMPDBRestorepath are not supported with individual mailbox restore from a virtual machine backup.

Remove these options from the TDP configuration file to ensure successful individual mailbox restore from a virtual machine backup.

To override the default TSMRDB location for recovery from VMVSS backups, use Windows System environment variable TSMMOUNT instead of TEMPLOGRestorepath and TEMPDBRestorepath.

Recycle the virtual machine after setting the TSMMOUNT variable. Recycling the virtual machine gives the 'Remote Client Agent' service access to this environment variable.

Example:
TSMMOUNT=C:\MyCustomVMMountPoint

Note that there is no no trailing directory separator.

The virtual machine volume is mounted and the TSMRDB is created at the location specified by TSMMOUNT. The
TEMPLOGRestorepath and TEMPDBRestorepath options cannot coexist with TSMMOUNT.

This information is also applicable when you reference the following commands ->
Commands for Exchange Server >

Restore
Restoremailbox
Set

-------------------------------------------------------------------------------------------------------------------------------------------------------------
(v7.1.2 only)
Updated VMware vCenter Server user privilege requirement

Knowledge Center: Data Protection for VMware>Configuring Data Protection for VMware>VMware vCenter Server user privilege requirements
User's Guide: Page 8
Installation Guide: Page 66

The "Set custom attribute" privilege is missing from the "Global" object section in "Table 1. Required privileges vCenter Server user ID and data mover". The correct "Global" object section is shown below:
Table 1. Required privileges vCenter Server user ID and data mover

vCenter Server objects	Associated privileges that are required
Global	Licenses, Log Event, Cancel Task, Set custom attribute

-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Application protection not supported on Microsoft Exchange Server 2007
Knowledge Center: Self-contained application protection overview > Application protection for Microsoft Exchange Server and SQL Server
User's Guide (PDF): Page 33 (7.1.0), Page 37 (7.1.1), Page 35 (7.1.2)

The Data Protection for VMware V7.1.0, V7.1.1, and V7.1.2 documentation incorrectly states that the application protection feature is supported on Microsoft Exchange Server 2007. This statement is incorrect. Data Protection for VMware V7.1.0, V7.1.1, and V7.1.2 do not support application protection on Microsoft Exchange Server 2007.

V7.1.3 Updates for IBM Spectrum Protect for Virtual Environments

Installing the device driver after the recovery agent is installed
By default, the device driver is not installed when you install the recovery agent. You must manually select the device driver when installing the recovery agent. To install the device driver after the recovery agent is already installed, complete the following steps:

1. In the tsm4ve folder, go to the appropriate directory (x64 or x86) and double-click the setup.exe file.
2. In the Program Maintenance dialog, click Modify.
3. In the Custom Setup dialog, expand the Tivoli Storage Manager Recovery Agent feature and select the device driver.
4. Proceed through the remaining dialogs until installation completes.

Incorrect statement regarding firewall settings
The following statement in the "File restore prerequisites" topic is incorrect:

VMware virtual machine prerequisites
- The virtual machine firewall access must be off.

The virtual machine firewall access can remain on.

Missing silent installation parameters
The "Upgrading Data Protection for VMware on a Linux system in silent mode" procedure is missing the following parameters:

Parameter	Description	Default value
DVCENTER_HOSTNAME	The vCenter Server IP address or name.	None
DVCENTER_USERNAME	The vCenter user ID. This user ID must be a VMware administrator that has permission to register and unregister extensions.	None
DVCENTER_PASSWORD	The vCenter password.	None
DDIRECT_START	To access the Data Protection for VMware vSphere GUI in a web browser, specify DDIRECT_START=YES. The Data Protection for VMware vSphere GUI is accessed through a URL bookmark to the GUI web server. If you do not want to access the Data Protection for VMware vSphere GUI in a web browser, specify DDIRECT_START=NO.	`YES` Important: After upgrade completes, the DDIRECT_START value cannot be changed except by reinstalling the product.
DREGISTER_PLUGIN	To access the Data Protection for VMware vSphere GUI as an extension in the Solutions and Applications panel of your vCenter Server System, specify DREGISTER_PLUGIN=YES. This plug-in access method is the same method as provided in prior versions of Tivoli® Storage Manager for Virtual Environments. If you do not want to access the Data Protection for VMware vSphere GUI as an extension, specify DREGISTER_PLUGIN=No.	`NO`
DREGISTER_EXTENSION	To access the Data Protection for VMware vSphere GUI as an extension in the vSphere Web Client, specify DREGISTER_EXTENSION=1.	0

Step 5 is incomplete. The complete Step 5 is below:

5. From a command prompt window, enter the ././install-Linux.bin -i silent -DLICENSE_ACCEPTED=true command with the preferred parameters.
For example:
././install-Linux.bin -i silent -DLICENSE_ACCEPTED=true -DVCENTER_HOSTNAME=hostname -DVCENTER_USERNAME=username -DVCENTER_PASSWORD=password -DREGISTER_PLUGIN=yes -DDIRECT_START=yes -DREGISTER_EXTENSION=yes

Clarification of supported environment for file restore operations
The following Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.3 Knowledge Center topics require clarification regarding the supported environment for file restore operations when using the Tivoli Storage Manager file restore interface:

Tivoli Storage Manager file restore interface

The example URL that is introduced by the following text is incorrect:
- Accessing the Tivoli Storage Manager file restore interface
  To access the file restore interface, open a web browser and enter the URL provided by your administrator. For example:
The URL contains backslashes (\) and should contain forward slashes (/)

Installable components

File restore interface:
- The checkmark in the Linux column is incorrect. The checkmark applies to Windows only and the following note is missing:
  - "Although the file restore interface component must be installed and enabled on a Windows system, you can use this interface to restore files on both Windows and Linux guest virtual machines."

File restore prerequisites

The following statement is missing from this topic:
- "To enable the file restore feature, Data Protection for VMware must be installed on a Windows system."

Multipathing must be disabled on the Linux mount proxy system before you attempt a mount operation.
Be aware that Logical Volume Manager (LVM) filtering might block the iSCSI connections.
The Linux mount proxy system does not support LVM auto activation.

V7.1.4 Updates for IBM Spectrum Protect for Virtual Environments

Register the Recovery Agent device driver after installing the Recovery Agent device driver in silent mode
The "Installing Data Protection for VMware on Windows 32-bit systems in silent mode" and "Installing Data Protection for VMware on Windows 64-bit systems by using the Suite Installer in silent mode" topics are missing the following information:

After installing the Recovery Agent device driver ("Mountdriver" 32-bit; "mountdriver" 64-bit) in silent mode, you must 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.

Learn more links do not work in Data Protection for VMware vSphere GUI "Add new Device Class" dialog
In the Tivoli Storage FlashCopy Manager for VMware configuration wizard, when editing the "Device Hostname or IP Address" field in the "Add new Device Class" dialog on the "Storage System" page, a hover help message displays a restriction. This hover help contains a "Learn more" link that does not load the user assistance.

The user assistance information is provided in the following two topics:

Device class parameters for dynamic target allocation
You can configure for dynamic target allocation, when you add or edit a device class. The values that you enter are saved to the device
class section of the profile file. Restriction: You cannot use both device types at the same time on the same storage system. Each device
type is considered to be a unique storage device adapter and only one device type can be specified.
Table 1. Device class parameters for Storwize and SAN Volume Controller systems for dynamic target allocation

Parameter name	Description
Device Class Name	The name of the device class, specify a unique name for the device class. You can use alphanumeric characters, hyphens (-), and underscores (_), but the name must not contain spaces. The maximum length of this name is 20 characters.
Device Type Profile parameter name: `COPYSERVICES_HARDWARE_TYPE`	The storage system type. Select IBM Storwize family/IBM System Storage SAN Volume Controller: Dynamic target allocation from the Device Type list.
Device host name or IP address Profile parameter name: `COPYSERVICES_SERVERNAME`	The host name or TCP/IP address of the storage system.
User name Profile parameter name: `COPYSERVICES_USERNAME`	The user name that is used to authenticate to the storage system.
SSH key file Profile parameter name: `SVC_SSHKEY_FULLPATH`	The full path name to the private SSH key file that is used to authenticate for the user name that is entered.

Device class parameters for static target allocation
You can configure for static target allocation, when you add or edit a device class. The values that you enter are saved to the device class section of the profile file.
Restriction: You cannot use both device types at the same time on the same storage system. Each device type is considered to be a unique storage device adapter
and only one device type can be specified.
Table 1. Device class parameters for Storwize and SAN Volume Controller systems

Parameter name	Description
Device Class Name	The name of the device class, specify a unique name for the device class. You can use alphanumeric characters, hyphens (-), and underscores (_), but the name must not contain spaces. The maximum length of this name is 20 characters.
Device Type Profile parameter name: `COPYSERVICES_HARDWARE_TYPE`	The storage system type. Select IBM Storwize family/IBM System Storage SAN Volume Controller from the Device Type list.
Device Hostname or IP Address Profile parameter name: `COPYSERVICES_PRIMARY_SERVERNAME`	The host name or TCP/IP address of the storage system.
User Name Profile parameter name: `COPYSERVICES_USERNAME`	The user name that is used to authenticate to the storage system.
Password	The password that is used to authenticate to the storage system.
Remote Server Name Profile parameter name: `COPYSERVICES_REMOTE_SERVERNAME`	The host name or TCP/IP address of the storage system at the secondary site. This parameter is applicable only if the Use Remote Mirroring check box is selected.
Remote User Name Profile parameter name: `COPYSERVICES_REMOTE_USERNAME`	The user name that is used to authenticate to the storage system at the secondary site. This parameter is applicable only if the Use Remote Mirroring check box is selected.
Remote Password	The password that is used to authenticate to the storage system at the secondary site. This parameter is applicable only if the Use Remote Mirroring check box is selected.
Target Naming Pattern Pattern `%SOURCE_%TARGETSET` Profile parameter name: `TARGET_NAMING` Target sets `1 2 3` Profile parameter name: `TARGET_SETS` To define target sets, you can select either the target naming pattern option or the target set definition file option.	The naming pattern and the number of target sets that you want to create. 1. You can edit the `%SOURCE_%TARGETSET` pattern. You can replace the underscore (_) with a schema for example, `%SOURCEVolA_%TARGETSET`. The schema that you enter can contain alphanumeric characters, hyphens (-), and underscores (_), but must not exceed 15 characters in length. Where: The `%SOURCE` variable represents the name of the source volume. The variable is substituted by the actual volume name at backup time and must not be modified. The `%TARGETSET` variable represents the name of the current active target set. The variable is substituted by the name of the current active target set and is retrieved from the Target Set list. This variable must not be modified. 2. Edit the `Target Sets` list, where each target set represents one backup generation. For example, to create four target sets enter: `1 2 3 4`
Target Set Definition file Profile parameter name: VOLUMES_FILE	The full path and file name of the target set definition file.

Clarification of Linux mount proxy system requirements
The Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.1, 7.1.2, and 7.1.3 Knowledge Center topic, "Mount proxy node and data mover node requirements", requires clarification regarding the requirements for Linux mount proxy systems. The following requirements are missing from the "Mount operations" section of this topic:

1. Multipathing must be disabled on the Linux mount proxy system before you attempt a mount operation.
2. Be aware that Logical Volume Manager (LVM) filtering might block the iSCSI connections.
3. The Linux mount proxy system does not support LVM auto activation.

Clarification of VMware vCenter Server user privilege requirements
There are inconsistencies among the list of required privileges in the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.0, 7.1.1, 7.1.2, and 7.1.3 Knowledge Center topic, "VMware vCenter Server user privilege requirements" topic. A comprehensive list of required privileges for each version of the product is available in technote 7047438.

*Clarification of port requirements* The Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.3 and 7.1.4 Knowledge Center topic, "Required communication ports", is missing the following information in the table: TCP Port: 135 Initiator (Out-Bound From Host): Windows mount proxy Target: In-Bound (To Host): VMware virtual machine that contains the files to be restored with the Tivoli Storage Manager file restore interface *Clarification for manually configuring the mount proxy nodes*

The following topics in the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.3 and 7.1.4 Knowledge Center are missing information:

The topic "Manually configuring the mount proxy nodes on a Linux system" is missing the following information:

Restriction: Do not enable the LAN-free option (ENABLELANFREE YES) in the dsm.sys file. This option is not supported for mount proxy nodes.

The topic "Manually configuring the mount proxy nodes on a remote Windows system", is missing the following information:

Restriction: Do not enable the LAN-free option (ENABLELANFREE YES) in the options file. This option is not supported for mount proxy nodes.

Clarification about empty directories not being restored
In the Tivoli Storage Manager file restore user interface, empty directories are not restored. If you selected a directory that has no contents, the empty directory is not restored.

Knowledge Center: http://www.ibm.com/support/knowledgecenter/SS8TDQ_7.1.4/ve.user/t_ve_res_frui.html
User's Guide: Page 26: Chapter 2. Getting started with file restore > Restoring files from a virtual machine backup

The following text has been updated:
3c. Select one or more files and directories to restore. If you select a directory that has no contents, the empty directory is not restored.

Clarification of tape media recovery guidelines

The topic "Tape media guidelines" in the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.1 and later Knowledge Center has been updated with the following information:

Consider moving target virtual machine backup data from tape media to disk
storage before you attempt a file restore operation. Do not move the virtual
machine control data because this data should already be in separate disk storage
pool. Also, do not move backup data to the disk storage pool on which the control
data resides. If you move backup and control data to the same pool, you will have
to complete an IFFULL backup to move the backup and control data to separate
pools.

To move backup data, use the Tivoli Storage Manager server MOVE NODEDATA
command and ensure that the FROMstgpool and TOstgpool parameters do not
specify pools that contain control data.

V7.1.6 Updates for IBM Spectrum Protect for Virtual Environments

Documentation contains misleading information on upgrading Data Protection for VMware

The IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.6 installation documentation includes a topic entitled "Upgrading Data Protection for VMware," which contains misleading information.

The topic includes a step in the procedure that states "If the system you are upgrading to has both the Data Protection for VMware vSphere GUI and Tivoli Storage Manager backup-archive client installed, install the backup-archive client V7.1.6.” This information is misleading as the customer will not need to install the backup-archive client first as the Virtual Machine installer will upgrade the product. This misleading information will be removed from this topic.

Documentation contains misleading information about the requirements for tagging support for Data Protection for VMware

The IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.6 user documentation includes a topic entitled "Setting a data mover node as a tag-based node," which contains misleading information.

The topic contains the following requirement::
This requirement is misleading because customers can easily misinterpret this requirement as being only the data mover running on the GUI server can support tags. When in fact, the data mover installed on the same machine as the GUI is a requirement for the GUI to function correctly. Other data movers, running on VMs or physical machines as additional data movers, do not require the GUI be installed for the data mover to work correctly as a tag data mover. Customers also can easily miss the last statement "Other data movers can be installed elsewhere."

This misleading requirement is replaced by the following requirement:

V7.1.x Updates for IBM Spectrum Protect for Virtual Environments

Clarification for -the vmname parameter for the Data Protection for Microsoft Hyper-V Restore VM command

The "Restore VM" command topic in the IBM Spectrum Protect 7.1.x and later Knowledge Centers should contain the following information:

The -vmname parameter is valid only for restoring virtual machines that were
backed up by using iffull or ifincremental modes. This parameter is ignored for
virtual machines that were backed up by using the full or incremental modes that
were provided in previous product releases.

Correction of the maximum characters allowed for the directory path when downloading the Data Protection for VMware installation package

The topic "Obtaining the Data Protection for VMware installation package" in the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware version 7.1.3 and later Knowledge Center should contain the following information:

Download the package file to the directory of your choice. The path must contain no more than 40 characters. Be sure to extract the installation files to an empty directory. Do not extract to a directory that contains previously extracted files, or any other files.

The topic incorrectly states that the path must contain no more than 128 characters.

Documentation contains misleading information on upgrading Data Protection for VMware

The IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.x installation documentation includes a topic entitled: Upgrading Data Protection for VMware, which contains misleading information.

The topic includes a step in the procedure that states "A message displays this text: The Existing Data Protection for VMware is going to be upgraded. If you confirm the upgrade, the installer updates the files.” This information is misleading as this message text does not display. This misleading information will be removed from this topic.

The topic also includes a step in the procedure that states "If the system you are upgrading to has both the Data Protection for VMware vSphere GUI and Tivoli Storage Manager backup-archive client installed, install the backup-archive client V7.1.6.” This information is misleading as the customer will not need to install the backup-archive client first as the virtual machine installer will upgrade the product. This misleading information will be removed from this topic.

Documentation contains incomplete information on installing Data Protection for VMware on Windows systems in silent mode

The IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.x installation documentation includes a topic entitled: Installing Data Protection for VMware on Windows systems in silent mode, which contains incomplete information.

The topic includes a table on the Data Protection for VMware silent installation parameters but excludes the details for the parameter SUITE_MODE, including the settings required for the data mover portion of the install in order to stop the NetAppsLibs feature from being installed.

The complete information is published with the IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 8.1.0 installation documentation. The updates are located in the topic entitled: Installing Data Protection for VMware on Windows systems in silent mode (https://www.ibm.com/support/knowledgecenter/SSERB6_8.1.0/ve.inst/t_ve_install_silent_suite64.html).

Documentation missing required communication port number for the Platform Services Controller

The Required communication ports topic in the IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.6 and 7.1.8 Knowledge Centers should contain the following information for the Platform Services Controller:

TCP Port Initiator:	Out-Bound (From Host)	Target: In-Bound (To Host)
443	vStorage Backup Server	Platform Services Controller
443	Data Protection for VMware vSphere GUI Server	Platform Services Controller
443	Windows mount proxy	Platform Services Controller

Clarifications for the VE_DATACENTER_NAME parameter in the Data Protection for VMware command-line interface profile

The "Profile parameters" topic in the IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.0 and later Knowledge Center should include the following notes:

Important: The Data Protection for VMware vSphere GUI does not support datacenters with the same name in the vCenter.

Restrictions: Data Protection for VMware does not support a one-to-many or many-to-one relationship between the datacenter name and the datacenter node. For example, the following relationships are not supported:

VE_DATACENTER_NAME DataCenter1::Fin_Datacenter1
VE_DATACENTER_NAME DataCenter1::Fin_Datacenter2
VE_DATACENTER_NAME DataCenter1::Fin_Datacenter3

Or

VE_DATACENTER_NAME DataCenter1::Fin_Datacenter1
VE_DATACENTER_NAME DataCenter2::Fin_Datacenter1
VE_DATACENTER_NAME DataCenter3::Fin_Datacenter1

Considerations added for using the vmdk=disk label option with the vmcli Restore command

The Restore command topic in the IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.1 and later Knowledge Center should show the following information for the vmdk=disk label option:

In vSphere mode, specify the disk label of a virtual disk to include in the restore operation. Use this parameter only if you want to restore one or more specific disks, but not all disks. Repeat this parameter for each disk that you want to restore.

For example, this entry in restoreObjectListFile restores the VMDKs named Hard Disk 1 and Hard Disk 2 as a new virtual machine.

backupid:26801107 vmname:myvm:vmdk=Hard Disk 1:vmdk=Hard Disk 2::vmname:newname

The following considerations apply to each disk that you want to restore:
Only the specified disks are restored. Other disks on the VM are not altered.

The VM whose disk you are restoring must be powered off before you initiate the restore operation.

"A data mover and the Data Protection for VMware vSphere GUI must be installed on the same server. The data mover node must be configured so that the vCenter server credentials are saved by running the configuration wizard to save the data mover node password. Other data movers can be installed elsewhere."
In order for the Data Protection for VMware vSphere GUI to function correctly with tagging support, ensure that the following requirements are met during the installation of the GUI:
- At least one data mover and the Data Protection for VMware vSphere GUI must be installed on the same server. This data mover node must be configured so that the vCenter server credentials are saved. You can save the credentials by running the configuration wizard to save the data mover node password, or by using the dsmc set password command in the data mover command line.
- If you use other data movers, running on virtual machines or physical machines as additional data movers, you can install them on other servers. For tagging support, all these data movers must also be configured with the vmtagdatamover yes option. These additional data movers do not require the Data Protection for VMware vSphere GUI to be installed on the same server in order for them to work correctly as tag-based data movers.
The disk must exist on the VM before you initiate the restore operation. If the disk does not exist, you must create it. You can run the dsmc dsmc restore vm command with the -preview parameter to identify the original disk label, capacity, and datastore. The -preview output does not include provisioning information.
The existing disk must be at least as large as the disk you want to restore.
The existing disk label must be the same as the disk you want to restore.
Any data on the existing disk is overwritten.

V7.1.8.10 Update for IBM Spectrum Protect for Virtual Environments

Changes in tracing and logging functionality

The following changes are specific to Tivoli Storage Manager for Virtual Environments 7.1.8.10 and subsequent versions.

Tracing and logging are now handled in the same way as in Spectrum Protect for Virtual Environments V8.1.11.

Changes in enabling tracing
In the topic, Enabling Tracing, (https://www.ibm.com/support/knowledgecenter/SS8TDQ_7.1.8/ve.user/t_ve_dpext_tshoot_enable_tracing.html) the procedure is now the same as in the equivalent topic for Spectrum Protect for Virtual Environments V8.1.11 (https://www.ibm.com/support/knowledgecenter/SSERB6_8.1.11/ve.user/t_ve_dpext_tshoot_enable_tracing.html).

Procedure

To view more detailed trace information for the common VMware vCloud Suite layer, change the following property value from INFO to TRACE in the corresponding log4j.properties file:
logger.ve.level = TRACE
To view more detailed trace information for the common vCloud Suite layer, VMware vCloud Suite SDK, and associated .jar files, change the following property value from WARN to TRACE, in the corresponding log4j.properties file:
rootLogger.level = TRACE
Rerun the actions or commands that caused the error.
If the error occurred in the IBM Spectrum Protect vSphere Client plug-in, you must restart the server that hosts the Data Protection for VMware vSphere GUI.

Changes in logging

In the topic, Log file activity, (https://www.ibm.com/support/knowledgecenter/SS8TDQ_7.1.8/ve.inst/r_ve_arch_restore.html) the file locations are now the same as in the equivalent topic for Spectrum Protect for Virtual Environments V8.1.11 (https://www.ibm.com/support/knowledgecenter/SSERB6_8.1.11/ve.inst/r_ve_arch_restore.html).

For Windows, logs are placed in the following directory:
%ALLUSERSPROFILE%\Tivoli\TSM
The directories contain a subdirectory for each Data Protection for VMware component. For example, the recovery agent subdirectory is \mount, and the Recovery Agent command-line interface subdirectory is \shell.
You can search for log files from the Windows > Start menu, by selecting Control Panel > Search and entering *.log.

For Linux, logs are placed in both of the following paths:
/opt/tivoli/tsm/tdpvmware/mount/log

/opt/tivoli/tsm/tdpvmware/mount/engine/var

You can search for log files by entering this command:

find /opt/tivoli/ -name "*.log"

Related Information

7.1.0 Knowledge Center

7.1.1 Knowledge Center

7.1.2 Knowledge Center

7.1.3 Knowledge Center

7.1.4 Knowledge Center

7.1.6 Knowledge Center

7.1.8 Knowledge Center

[{"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.3;7.1.4;7.1.6;7.1.8","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

Tips

Documentation updates for IBM Spectrum Protect for Virtual Environments: Data Protection for VMware 7.1.x

Product Documentation

Abstract

Content

Procedure

Related Information

Was this topic helpful?

Document Information

UID

Share your feedback

Need support?