Documentation updates for IBM Tivoli Storage Manager for Virtual Environments 6.3

Updates and corrections regarding Windows operating system support for the Data Protection for VMware vCenter plug-in

Information Center: Planning -> Supported operating systems for Data Protection for VMware vCenter plug-in
Install. and User's Guide: Page 10-11

The following Microsoft Windows 7 statement is incorrect:

-Microsoft Windows 7 for all editions

This statement should reads as follows:

-Microsoft Windows 7 Enterprise, Professional, and Ultimate editions are supported.
-Microsoft Windows 7 Home Premium and Starter editions are not supported.

In addition to the existing operating system content, the following operating system editions are also supported:

-Windows Server 2003 R2 Standard and Enterprise editions
-Windows Server 2008 Datacenter edition
-Windows Server 2008 R2 Datacenter edition

Tivoli Storage Manager data mover nodes and deduplication

Information Center: Using the Data Protection for VMware vCenter plug-in -> Configuring the Data Protection for VMware vCenter plug-in -> Setting up the Tivoli Storage Manager Backup-Archive Client on the vStorage Backup Server for each datamover node
Install. and User's Guide: Page 44-45

The following statement belongs at the beginning of this task:

In a standard Data Protection for VMware environment, a separate dsm.opt file
(Windows) or dsm.sys file stanza (Linux) is used for each Tivoli Storage Manager
data mover node. When multiple data mover nodes on a vStorage Backup Server
are used for deduplication, and these nodes have authority to move data for the
same data center node, then each dsm.opt file or dsm.sys file stanza must include a
different value for the dedupcachepath option. It is also recommended to specify a
different schedlogname and errorlogname option for each dsm.opt file or dsm.sys
file stanza.

In Step 2, the -optfile parameter should also be specified. As a result, the updated Step 2 is shown here:

2. Specify the -asnodename and -optfile parameters when starting the
backup-archive client command-line interface:
dsmc -asnodename=VC1_DC1 -optfile=dsm_DM1.opt

In Step 3, the following text (for Windows) is incorrect:

Start the Tivoli Storage Manager Client Configuration wizard on
the system where the Data Protection for VMware vCenter plug-in is
installed:

Since this action occurs on the vStorage Backup Server, the correct text is shown here:

Start the Tivoli Storage Manager Client Configuration wizard:

Data Protection for VMware and LAN-free operations

Information Center: Planning -> Hardware requirements
Information Center: Using the Data Protection for VMware Recovery Agent -> Restoring virtual machine data -> Mounting snapshots
Install. and User's Guide: Page 13 and 77

The following statement:

Data Protection for VMware does not support operations in a LAN-free environment.

is referring specifically to the Data Protection for VMware Recovery Agent component. As a result, the statement should read as follows in both locations:

The Data Protection for VMware Recovery Agent component does not support operations in a LAN-free environment.

Information about LAN-free operations is available in the following IBM developerWorks Wiki article: Recommendations for Using LAN-free with TSM for Virtual Environments


Exclude write cache path from antivirus software

Information Center: Using the Data Protection for VMware Recovery Agent > Restoring virtual machine data -> Mounting snapshots -> Setting options
Information Center: Using the Data Protection for VMware Recovery Agent > Restoring virtual machine data > Restoring files and instant restore of volumes -> Configuring Data Protection for VMware Recovery Agent for restore operations (Linux)
Install. and User's Guide: Page 79 and 92

The following statement belongs in the description of the write cache path:

Restriction: To prevent any interruption during restore processing, exclude the write cache path from all antivirus software protection settings.

Use of vmhost option with domain.vmfile and domain.vmfull

Information Center: Using the Data Protection for VMware Recovery Agent > Backing up VMware virtual machine data -> Running full virtual machine backups
Install. and User's Guide: Page 73

The following statement belongs in Step 1e:

When the Virtual Center contains multiple ESX servers, the Host value (or vmhost in dsm.opt) does not determine the ESX server from which a snapshot is taken. The ESX server from which a snapshot is taken is determined by the VMware Virtual Center Web service.

Extraneous step in " Running full virtual machine backups" procedure

Information Center: Using the Data Protection for VMware Recovery Agent > Backing up VMware virtual machine data -> Running full virtual machine backups
Install. and User's Guide: Page 73

In the following step (Step 1f.):

f. In VM Full Backup Type section, select VStorage.

The VStorage option is not available to select. As a result, this step does not belong in this procedure; it can be ignored.


The vmcliprofile requires unique data center names

Information Center:
Configuring the Data Protection for VMware vCenter plug-in -> Configuring the Data Protection for VMware command-line interface

Using the Data Protection for VMware command-line interface -> Profile example

Install. and User's Guide: Pages 51, 72

The values of the VE_DATACENTER_NAME in the examples are incorrect:

VE_DATACENTER_NAME MyDatacenter::VC1_DC1
VE_DATACENTER_NAME MyDatacenter::VC1_DC2

That is because these values incorrectly show that you can specify the same data center (MyDatacenter) but with different node names (VC1_DC1, VC1_DC2). The data center names specified in the vmcliprofile must be unique. The correct VE_DATACENTER_NAME values should read as follows:

VE_DATACENTER_NAME MyDataCenter1::VC1_DC1
VE_DATACENTER_NAME MyDataCenter2::VC1_DC2

The data mover node requires the TCP/IP communication method

Information Center:
Using the Data Protection for VMware vCenter plug-in -> Configuring the Data Protection for VMware vCenter plug-in -> Setting up the Tivoli Storage Manager Backup-Archive Client on the vStorage Backup Server for each data mover node

Install. and User's Guide: Page 49

When updating the Backup-Archive Client options file (dsm.opt or dsm.sys) on the vStorage Backup Server, TCP/IP is the only supported communication method. Operations fail if another communication method is specified. As a result, the example dsm.opt file should also contain this setting:

commmethod tcpip

Updates and corrections regarding Linux operating system support for the Data Protection for VMware vCenter plug-in

Information Center:
Planning -> Supported operating systems for Data Protection for VMware vCenter plug-in
Install. and User's Guide: Page 11-12

The correct packages and minimum levels for RedHat Enterprise Linux 5.x and 6.x are as follows:

mdadm 2.6
iSCSI Initiator 6.2
lsscsi command 0.23
iscsiadm 0.10
OpenSSH 0.1

The following kernel information is incorrect and can be ignored:

RedHat-i386: 2.6.18-92.e15.i686 and 2.6.18-92.e15.i686 PAE
RedHat-x86_64: 2.6.18-92.el5-x86_64

Updates and corrections regarding Linux operating system support for the Data Protection for VMware Recovery Agent

Information Center:
Planning -> Supported operating systems for Data Protection for VMware Recovery Agent
Install. and User's Guide: Page 8-9

The correct packages and minimum levels for RedHat Enterprise Linux 5.x and 6.x are as follows:

mdadm 2.6
iSCSI Initiator 6.2
lsscsi command 0.23
iscsiadm 0.10
OpenSSH 0.1

The following kernel information is incorrect and can be ignored:

RedHat-i386: 2.6.18-92.e15.i686 and 2.6.18-92.e15.i686 PAE
RedHat-x86_64: 2.6.18-92.el5-x86_64

Data Protection for VMware on Linux requires a Windows proxy host

Information Center:
Planning -> Hardware requirements
Install. and User's Guide: Page 13

The following statement is missing from this section:

A Windows proxy host is required for Data Protection for VMware on Linux. This
proxy host must have Data Protection for VMware installed.

Incomplete steps in Cygwin configuration procedure

Information Center:
Planning -> Software requirements and prerequisites -> Setting up Cygwin for use when restoring files from a Linux system
Install. and User's Guide: Page 13

Step 6 and Step 7 are incomplete. The complete steps are as follows:

Step 6: On the Linux host, SSH to the windows host without using a password:
ssh Administrator@windows_machine.xyz.com

Step 7: After logging in to the Windows host using SSH, issue the TDPVMwareShell
command under the SSH shell:
cd "/cygdrive/c/Program Files/tivoli/tsm/tdpvmware/shell"
./TDPVMwareShell.exe -c command type tag parameter

Notes:
(a) c:\WINDOWS\system32 must be set the Windows host PATH.
(b) To display help information for all of the supported Recovery Agent CLI
commands, issue this command:
./TDPVMwareShell.exe -h
(c) The "/cygdrive/c/Program Files/tivoli/tsm/tdpvmware/shell" path is based on the default value of the Data Protection for VMware installation path (c:\Program
Files\tivoli\tsm\tdpvmware). If your Data Protection for VMware installation path is different (non-default), then make sure you specify the correct path for your installation.

Instant Restore requires the Data Protection for VMware Recovery Agent to be installed on the VM Guest Machine

Information Center:
Using the Data Protection for VMware Recovery Agent > Restoring virtual machine data > Restoring files and instant restore of volumes > Using instant restore (Windows)
Install. and User's Guide: > Using instant restore (Windows)" Page 93

The following statement is missing from this section:

Instant restore works only with local volumes. The term "local" is used in reference
to the Data Protection for VMware Recovery Agent. The Data Protection for VMware
Recovery Agent must be installed on the guest machine that contains the volume to be
restored. A volume cannot be restored from the proxy system with the instant restore feature.

Installation might fail if ports are not available in the eWAS portdef.props file

Information Center:
Using the Data Protection for VMware vCenter plug-in > Troubleshooting
Install. and User's Guide: > "Troubleshooting" Page 58

The following content is missing from this section for both Linux and Windows:

The Data Protection for VMware vCenter plug-in was installed successfully on the vCenter node. However, when viewing the Data Protection for VMware vCenter plug-in in the vSphere Client Plug-in Manager (Menu > Plug-ins > Manage Plug-ins), the following message is shown:

Tivoli Data Protection for VMware
IBM Tivoli Storage Manager 1.1
Disabled
Tivoli Data Protection for VMware Plug-in
The following error occured while downloading the script plugin from
http://finapps.mycompany.com:9080/TsmVMwareUI/plugin/ config.xml:
The request failed because of a connection failure. (Unable to connect
to the remote server)

Complete these tasks to resolve this issue:
1. On the system where the Data Protection for VMware vCenter plug-in is installed, go to the Extra\ewas\profileTemplates\default\actions\portsUpdate directory.
2. Open the portdef.props file to view the eWAS port settings. For example:
WC_defaulthost=9080
WC_adminhost=9060
WC_defaulthost_secure=9443
WC_adminhost_secure=9043
BOOTSTRAP_ADDRESS=2809
SOAP_CONNECTOR_ADDRESS=8880
IPC_CONNECTOR_ADDRESS=9633
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9401
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9403
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9402
ORB_LISTENER_ADDRESS=9100
DCS_UNICAST_ADDRESS=9353
SIB_ENDPOINT_ADDRESS=7276
SIB_ENDPOINT_SECURE_ADDRESS=7286
SIB_MQ_ENDPOINT_ADDRESS=5558
SIB_MQ_ENDPOINT_SECURE_ADDRESS=5578
SIP_DEFAULTHOST=5060
SIP_DEFAULTHOST_SECURE=5061
3. Issue the netstat -a command to view all active connections and ports. Compare the results with the port settings in the portdef.props file. If any of the ports (specified in the portdef.props file) are not open, complete either of the following tasks to resolve this connection issue:
-Open the closed ports.
-Update the portdef.props file with ports that are available.
4. Restart the vSphere Client and start the Data Protection for VMware vCenter plug-in.



Instructions regarding how to start the client acceptor service are missing

Information Center:
Using the Data Protection for VMware vCenter plug-in > Setting up the Tivoli Storage Manager Backup-Archive Client on the vStorage Backup Server for each data mover node
Install. and User's Guide: > "Setting up the Tivoli Storage Manager Backup-Archive Client on the vStorage Backup Server for each data mover node" Page 53

The following instructions are missing from Windows Step 3a:
1) In the "When do you want the service to start?" option, select
"Automatically when Windows boots."
2) In the "Would you like to start the service upon completion of
this wizard?" option, select "Yes."
The following instructions are missing from Windows Step 3b:
1) When entering the scheduler name, make sure to select the "Use the
Client Acceptor daemon (CAD) to manage the scheduler" option.
2) In the "When do you want the service to start?" option, select
"Automatically when Windows boots."
3) In the "Would you like to start the service upon completion of
this wizard?" option, select "Yes."
The following instructions are missing from Linux Step 3:
c. Start the client acceptor by issuing the following command:
./dsmcad



Incorrect set access command example

Information Center:
IBM Tivoli Storage Manager for Virtual Environments > Planning > Virtual environment configurations > In-guest file-level restore and instant restore for Windows and for Linux
Install. and User's Guide: "In-guest file-level restore and instant restore for Windows and for Linux"
Page 20

The following command is incorrect:

set access backup "{\\VMFULL-vmdisplayname}\*\*" * mountnodename

The correct command is shown below:

set access backup "{\VMFULL-vmdisplayname}\*\*" * mountnodename



Set LD_LIBRARY_PATH environment variable instructions incomplete

Information Center:
Using the Data Protection for VMware Recovery Agent > Backing up VMware virtual machine data > Preparing the environment for VMware backup processing
Install. and User's Guide: Page 74

To configure the vStorage backup server, set and export LD_LIBRARY_PATH environment variable to point to the client installation directory before issuing any backup-archive commands such as dsmc, dsmcad, or dsmj. This set and export task can be completed by using either of the following methods:

- Issue the following command in a shell window:

export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin

- Create aliases for the backup-archive client command. For example:

alias dsmc='LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin dsmc'
alias dsmj='LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin dsmj'

Add the following statement to the top of the /etc/init.d/dsmcad startup script:

export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin

Then, restart the Client Acceptor Service (dsmcad) by issuing this command:

service dsmcad restart



Multiple Data Protection for VMware vCenter plug-ins can be registered on a single vCenter Server

Information Center: Installing, upgrading, and uninstalling Data Protection for VMware > Preparing for installation
Install. and User's Guide: Page 26

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

You can register multiple Data Protection for VMware vCenter plug-ins to a single vCenter Server. This scenario reduces the number of data centers (and their VM guest backups) that are managed by a single Data Protection for VMware vCenter plug-in. Each plug-in can then manage a subset of the total number of data centers that are defined on the vCenter Server. For each plug-in that is registered to the vCenter Server, one Data Protection for VMware package must be installed on a separate host.

To update the managed data centers, go to Configuration->Edit Configuration. In the Plug-in Domain page, reduce the list of data centers managed by the plug-in. Managing a subset of all available data centers reduces the query and processing time required by the plug-in to complete operations.