TSM For VE 7.1.1 Installation Cookbook - Linux (v2) PDF

Tivoli Storage Manager for Virtual Environments
Version 7.1.1
Installation Cookbook
Linux vStorage Backup Server
VMware Environment
November 4, 2014
Art Roy
IBM Cloud & Smarter Infrastructure SW Advanced Technology/SWAT
ajroy@us.ibm.com
IBM Tivoli Software | © 2013 IBM Corporation

This cookbook was created as a step-by-step guide for customers to get started
with TSM for VE quickly and to augment the official product documentation. It is
not meant to cover every aspect of the product but only to get the customer up
and running as quickly as possible.
The document assumes that the customer will use the TSM for VE Web
Browser GUI or vCenter plug-in as well as the configuration wizard to configure
the TSM for VE environment.
IBM Confidential
2
Installation Step Summary
This is a summary of the steps which will be accomplished in this document
1. Verify Prerequisites
2. Install the TSM for VE software on the Linux vStorage Backup Server.
3. Configuration using the TSM for VE Web Browser GUI.
4. Install and Configure the datamover on the vStorage Backup Server.
5. Configure the Linux (Partner) Mount Proxy.
6. Install and Configure the Windows (Primary) Mount Proxy.
7. Configure and use the vSphere Web Client Extension.
IBM Confidential
3
Prerequisites
IBM Confidential
4
Communication Port Requirements
Before beginning installation, please verify that the following ports are
open on the vStorage Backup Server and not blocked by a firewall.
TSM for VE ports

443 – Communication to the vCenter Server and ESXi Hosts
902 – Communication to the vCenter Server and ESXi Hosts
3260 – File Level Recovery iSCSI mount
9080 – Access to TSM for VE GUI through the vCenter plugin
9081 – Access to TSM for VE stand-alone GUI via Web Browser
Standard TSM ports

1500 – Default port for datamover (BA Client) access to TSM server.
1501 – Default datamover TCPCLIENTADDRESS Port
1581 – Default datamover HTTPPORT Port
(additional TSM ports required for additional datamovers, 1502, 1582,
etc.)
IBM Confidential
5
Communication Port Requirements – Firewall Configuration
IBM Confidential
6
In a non-GUI Linux environment, the ports can be manually added to the

/etc/sysconfig/iptables file as shown.
IBM Confidential
7
After updating the iptables files, restart the iptables service.
IBM Confidential
8
TSM Server Requirements
Ensure that there is an available Policy Domain and Storage Pool set up
to hold the TSM for VE backups.
TSM for VE Control files should be stored in a disk based storage pool.
See the VMCTLMC parameter in the BA Client Installation and User’s
Guide.
IBM Confidential
9
Linux Server Software Requirements
Supported Linux versions for the mount proxy:
64-Bit RHEL 6.1 or higher

SLES11 SP3 or higher
Supported Windows versions for the mount proxy:
64-Bit Windows Server 2008 R2

64-Bit Windows Server 2012 R2
Ensure that the Linux iSCSI utilities (iscsiadm) are installed.
IBM Confidential
10
Mount Proxy Server Requirements
The IP of the network adapter configured on the Linux mount proxy

server used for iSCSI must be in the same subnet as the network
adapter on the Windows mount proxy server used for iSCSI.
The Linux mount proxy server can be a physical machine or a VM guest

and should only be used for mount operations and not for backup or
restore operations (should not be used as a datamover server).
IBM Confidential
11
Tivoli Data Protection for VMware
Installation - Linux
IBM Confidential
12
TSM for VE Installation - Linux
The installation screen prints in this document are captured from an X-Windows Linux
interface. The installation can also be completed in a Linux command line environment. Both
installation options will require the same inputs.
IBM Confidential
13
Change directory to the DataProtectionForVMware directory in the TSM for VE Media.
Run install-Linux.bin.
IBM Confidential
14
Click OK.
Click Next.
IBM Confidential
15
Click to accept the terms of the

license agreement.
Click Next.
The Deployment Engine will be

installed.
IBM Confidential
16
Click Next.
Click Next.
IBM Confidential
17
Uncheck the box for the Data Protection for VMware Recovery Agent.
Check the box for the Data Protection for Vmware GUI.
Leave the Documentation and DP for Vmware Enablement File options checked.
Click Next.
IBM Confidential
18
Three options are available for GUI access.

1) Access via the vCenter Plug-in. (Allows
TSM for VE configuration.)
2) Access via a Web Browser. (Allows TSM
for VE configuration.)
3) New integration with the vSphere Web
Client (current functionality is limited to
full guest restores. Does not allow TSM
for VE configuration)
Choose the desired option(s) and click Next.
Enter your vCenter Server address and

authentication information. The VMware role
requirements for this User can be found in
this Technote:
http://www-
01.ibm.com/support/docview.wss?uid=swg21
659544
IBM Confidential
19
Click Next.
IBM Confidential
20
Click OK.
IBM Confidential
21
Click Install.
IBM Confidential
22
Click Next.
Click Done.
IBM Confidential
23
TSM for VE Configuration
Run via the TDP for VMware Web Browser GUI
IBM Confidential
24
Access the GUI via web browser to URL https://hostname:9081/TsmVMwareUI/ .
Log in using vCenter Server credentials.
IBM Confidential
25
If you chose to Register the GUI as a vCenter Plug-in, you can also access the
GUI via the plug-in in the vSphere Client or vSphere Web Client. Whether you
use the stand-alone web browser, vSphere Client plug-in, or vSphere Web
Client access, the interface will look the same.
Click on Tivoli Data Protection for

VMware.
IBM Confidential
26
If you chose to Register the GUI as a vCenter Plug-in, you can access the GUI
via the plug-in in the vSphere Web Client.
Click on Tivoli Data Protection for

VMware.
IBM Confidential
27
Launching the GUI for the first time will automatically launch the Configuration
Wizard.
Click Next
IBM Confidential
28
Enter the required information to connect to your TSM server
Enter the DNS name or IP address

for the TSM Server.
Modify the TSM Server port

number if required. The default is
1500.
Enter a TSM server Admin ID and

Password.
Check the box to save the ID and

password.
Click Next.
IBM Confidential
29
TDP for VMware requires several nodes to be defined on the TSM server. The
configuration wizard will create the nodes. This screen gives the option to
assign a common prefix to these nodes as well as to select a TSM policy
domain.
Enter a prefix for the TSM

node names that will be
generated.
Note: The wizard will

automatically place an
underscore between what you
type here and the rest of the
node name.
Verify the Policy domain to be

used.
Click Next.
IBM Confidential
30
Create the vCenter Node in TSM.
This field will be pre-filled with a

node name for the vCenter node
in TSM. You may modify the
name if desired or use the
generated default name,
however best practice is to
include the vCenter name.
Check the ‘Register Node’ box

and enter a password for the
new node. The new node will be
registered in TSM with the
specified password.
Click Next.
IBM Confidential
31
Create the VMCLI Node.
This field will be pre-filled with a

node name for the VMCLI node
in TSM. It consists of the node
prefix, if specified earlier,
followed by ‘_VMCLI’. In this
example it results in the name of
VE711_VMCLI. Your name will
differ depending on the prefix
you entered. You may modify
the name if desired or use the
generated default name.
Check the ‘Register Node’ box

and enter a password for the
new node. The new node will be
registered in TSM with the
specified password.
Click Next.
IBM Confidential
32
Select the VMware Datacenters to be managed.
In this example Datacenter-1 was

chosen to be managed by this
GUI. By default, the box will be
checked to manage all
datacenters.
Click Next.
IBM Confidential
33
Create the Datacenter Node and Initial TSM Data Mover Node
TSM node names for the datacenter and Data

Mover are generated.
The datacenter node name consists of the
specified prefix followed by an underscore
followed by the datacenter name.
The Data Mover node name consists of the
datacenter node name with a suffix of ‘_DM’.
Each of these may be modified by highlighting

the line containing the name and then either
clicking on the node name or clicking on ‘Edit
Node Name’. This example uses the defaults.
Do not click Next yet.
IBM Confidential
34
Set the TSM node passwords for the Datacenter and Data Mover nodes
Note that the passwords for each

node have not been set.
To set the password for a node, either

highlight the line and click on ‘Set
Password’, or click on ‘Not Set’.
(see next page)
IBM Confidential
35
Enter a password for the

selected node and click OK.
IBM Confidential
36
Repeat the Set Password process

for the other node(s) until all nodes
show ‘Change’ in the Password
column.
Click Next.
IBM Confidential
37
New as of TSM for VE 7.1.1 is the creation of Mount Proxy Node Pairs to be used for file level recovery
as well as Full Guest Instant Access and Full Guest Instant Recovery. Two nodes are created, one for
Windows and one for Linux. For Linux file level restores, both nodes are used in conjunction.
IBM Confidential
38
By default, the node names are generated with the prefix entered earlier, followed by _’REMOTE_’
followed by ‘MP_WIN’ (for the Windows node) and ‘MP_LNX’ (for the Linux node).
By clicking on the generated Primary Node name, you

can modify the name. The ‘MP_WIN’ portion of the
name is required and should not be changed.
Any changes to the Primary Node will automatically be

reflected in the Linux Partner Node name also. The
‘MP_LNX’ portion of this node name is required.
IBM Confidential
39
Click on ‘View Settings’ for the Mount Proxy Node pair to view the suggested option settings for each
node. A node password is automatically generated for each. You can click on ‘Show’ to display the
password or on ‘Change’ to enter your own password choice. Remember the password for later
configuration. The Primary Node tab is for the Windows Mount Proxy node.
IBM Confidential
40
The Linux Partner Node tab is for the Linux Mount Proxy node. As with the Primary Node, you can
show the generated node password or change it to your preference. Remember the password for later
configuration steps.
Click Close
IBM Confidential
41
Click Next.
IBM Confidential
42
The Summary page shows the Node Names that will be created in TSM.
vCenter Node Name
VMCLI Node Name
Datacenter Node Name
Data Mover Node Name
Mount Proxy Node Name

for the Windows proxy
Mount Proxy Node Name

for the Linux proxy
Click Finish
IBM Confidential
43
The Wizard Tasks should all show a state of Successful. Click Close.
IBM Confidential
44
The Configuration Status screen shows the TSM node names. Notice the yellow warning symbol on
the datacenter.
IBM Confidential
45
Click on the virtual datacenter to view the status of the datamover and mount proxy nodes for that
datacenter. Notice the yellow warning symbol on the datamover and mount proxy nodes. The next
steps in the configuration are to install and configure the datamovers and mount proxies.
IBM Confidential
46
TSM Operations Center shows the nodes that were created on the TSM server.
IBM Confidential
47
The configuration wizard automatically creates the required proxy relationships for the Datacenter
and vCenter nodes.
IBM Confidential
48
Installing and Configuring the Datamover
IBM Confidential
49
Install the Datamover (TSM BA Client) on the Linux vStorage Backup Server per the “IBM Tivoli
Storage Manager for Virtual Environments Installation Guide”. Notice that the GSKit packages and
the TSM API indicate they are already installed. This is normal since they were installed as part of
the TSM for VE installation. Install the BA Client to complete the software requirements.
IBM Confidential
50
Change directory to /opt/tivoli/tsm/client/ba/bin. Copy the dsm.opt.smp file to a new file

name containing the datamover node name: dsm.<datamover node name>.opt
IBM Confidential
51
Edit the new file. The only non-comment entry should be the Servername parameter and
the datamover node name. This will point to the datamover stanza in the dsm.sys file.
IBM Confidential
52
Copy the dsm.sys.smp file to dsm.sys.
IBM Confidential
53
Edit the new file to include the parameters shown below. (see next page)
IBM Confidential
54
More information on these parameters can be found in the BA Client Installation and
User’s Guide.
SErvername VE711L_DATACENTER-1_DM <use the datamover node name>

nodename VE711L_DATACENTER-1_DM <use the datamover node name>
COMMMethod TCPip
TCPPort 1500
VMCHost vsphere-srv <host name of the vCenter Server>
TCPServeraddress 192.168.2.246 <TSM Server Address>
PASSWORDACCESS generate
HTTPPORT 1581
MANAGEDSERVICES schedule webclient
SCHEDMODE prompted
VMMAXParallel 4 <Maximum Concurrent Guest Backups>

VMCTLMC standard <Management Class for TSM VE Control Files>
<Include the datamover name in the log files>

ERRORLOGName "/opt/tivoli/tsm/client/ba/bin/dsmerror.VE711L_DATACENTER-1_DM.log"
SCHEDLOGName "/opt/tivoli/tsm/client/ba/bin/dsmsched.VE711L_DATACENTER-1_DM.log"
IBM Confidential
55
Copy the file rc.dsmcad file to a new file by appending the datamover node name,
rc.dsmcad.<datamover node name>
IBM Confidential
56
Edit the new file and insert two lines as shown. Use the newly created option file for the
DSM_CONFIG export.
export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.<datamover node name>.opt
IBM Confidential
57
Create a symbolic link in the /etc/init.d directory for the datamover DSMCAD service.
ln –s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad.<datamover node name>

/etc/init.d/dsmcad.<datamover node name>
IBM Confidential
58
1) Change directory back to /opt/tivoli/tsm/client/ba/bin.

2) Invoke the BA Client command line including the –optfile= parameter pointing to the
datamover option file: dsmc –optfile=dsm.<datamover node name>.opt
3) The User id should default to the datamover node name. Press Enter.
4) Enter the password for the datamover node name that was set during the configuration.
5) Quit from the BA Client command line.
IBM Confidential
59
Set the password for the vCenter Server.
dsmc set password –type=VM <vcenter server address> <vCenter admin> <vCenter
admin password> -optfile=dsm.<datamover node name>.opt -serv=<datamover node
name>
The vCenter admin ID must have the role permissions as specified in this Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21659544
IBM Confidential
60
Start the DSMCAD service for the datamover:
service dsmcad.<datamover node name> start
Set the DSMCAD service to start automatically after reboot.
chkconfig --add dsmcad.<datamover node name>
IBM Confidential
61
Return to the Configuration Status screen of the TSM for VE GUI.
Click on the Datacenter name to display the datamover and mount

proxy nodes.
Click on the Datamover node.
Click on ‘Validate Selected Node’.
IBM Confidential
62
Verify in the Status Details for the datamover node that the datamover is working properly. The TSM
for VE plug-in/GUI attempts to communicate with the datamover CAD service. If successful, then the
datamover will show as working properly.
IBM Confidential
63
Installing and Configuring the Windows (Primary)
Mount Proxy
IBM Confidential
64
Installing and Configuring the Windows (Primary) Mount Proxy
As shown during the initial configuration, the Mount Proxy Nodes are always created in pairs, with the
Primary Node always being on Windows. The Windows Mount Proxy Node is required for all file level
restores, whether they are from Windows guests or Linux guests.
IBM Confidential
65
The status of the Windows (Primary) and Linux (Partner) nodes are currently unknown. The Primary
mount proxy node must be configured correctly in order for the Partner node to validate.
IBM Confidential
66
Start the installation of the software from the TSM for VE media.
IBM Confidential
67
Note that the Windows Mount Proxy Node server must have the BA Client installed as well as
the Recovery Agent and VMware Enablement File from the TSM for VE installation media.
This can be accomplished by selecting ‘Advanced Installation’ and then ‘Install Tivoli Storage
Manager Instant Restore only’. This server could also be an existing or future datamover
server.
IBM Confidential
68
Complete the software installation.
Click Next
Accept the License. Click Next
Click Next
Click Next
Click Install
IBM Confidential
69
Complete the software installation
and reboot.
Click Install
Click OK
Click Finish
Click OK
Click Yes
IBM Confidential
70
After reboot, click Finish on the Wizard Completion screen.
IBM Confidential
71
From the Configuration Status screen of the TSM for VE GUI, select ‘Edit TSM Configuration’ from the
Tasks pulldown to display the Configuration Settings page.
On the Configuration Settings

page, select “Mount Proxy
Node Pairs”, and click on ‘View
Settings’ for the desired Mount
Proxy Node pair.
From the Primary Node tab,

copy the suggested
parameters for the option file.
IBM Confidential
72
Copy the settings to be used in the

dsm.<mount proxy node>.opt file.
These are the settings on the

‘Primary Node’ tab.
IBM Confidential
73
On the Windows Mount proxy server,

navigate to the
C:\Program Files\Tivoli\TSM\baclient
folder.
Create an option file for the mount proxy

node: dsm.<mount proxy node name>.opt
Edit the file and paste the copied

parameters.
If your TSM for VE backups are stored

in a VTL or Tape library, add the
VMSTORAGEType parameter and
specify VTL or TAPE. The default
value is DISK.
Save the file.
IBM Confidential
74
Open a Windows command prompt and change directory to

the C:\Program Files\Tivoli\TSM\baclient folder.
Invoke the TSM BA Client GUI with the –optfile= parameter

pointing to the new option file.
Ex: dsm -optfile=dsm.VE711L_REMOTE_MP_WIN.opt
Enter the TSM password for the node. This is the password
from the installation wizard that was generated or that you set.
IBM Confidential
75
Click on Edit and select Client Preferences.
IBM Confidential
76
Creating Additional Mount Proxy Node Pairs
Wait until the information in the Preferences Editor is refreshed. Click on the VM Backup tab. The
VMware Virtual Center address should already be filled in. Enter the User, and Password. Click OK.
IBM Confidential
77
Click on Utilities and select ‘Setup Wizard’.
IBM Confidential
78
Check the box to ‘Help me configure the TSM Web Client’. Click Next.
IBM Confidential
79
Click Next.
Select Install a new Web Client agent.

Click Next.
IBM Confidential
80
Append the Mount Proxy Node name to

the Client Acceptor name. Click Next.
Verify the option file name and click Next.
IBM Confidential
81
Click Next.
Enter the mount proxy node password.

Click Next.
IBM Confidential
82
Select ‘Automatically when Windows boots’

as the start option.
Click Next.
Append the mount proxy node name to the

agent name.
Click Next.
IBM Confidential
83
Click Next.
Select ‘Yes’ to start the service.

Click Next.
IBM Confidential
84
Click Apply.
Click Finish.
Close the BA Client GUI.
IBM Confidential
85
Return to the Configuration Status page of the TSM for VE GUI.
Click on the Datacenter name to display the datamover and mount

proxy nodes. Highlight the new mount proxy node and click on
‘Validate Selected Node’. The status of the Windows Mount Proxy
Node should now show it working properly.
IBM Confidential
86
Mount proxy nodes are always created in pairs, one for Windows and one for Linux. The Windows node is
the primary node and is the only node from the pair that will listed. By selecting the Windows mount proxy
node, the status for both nodes will be checked. The status details for the Windows mount proxy node
shows the node working properly but the Linux proxy node shows a TCP/IP communications failure. We
have not set up the Linux proxy node yet. If the site does not have any Linux file level restore
requirements, the Linux proxy node status can be ignored.
IBM Confidential
87
Completing the Linux Mount Proxy
Installation and Configuration
IBM Confidential
88
Completing the Linux Mount Proxy Installation and Configuration
The Linux Mount Proxy is a Linux server (likely a VM guest) that will be used to mount backup
images via iSCSI that have been mounted and presented as iSCSI targets by the Windows Mount
Proxy. It is only required if the site has Linux guests where file level recovery may be necessary.
The Linux Mount Proxy server is only required to have the Linux BA Client installed as well as the
Linux iSCSI utilities (iscsiadm). The BA Client should be at the same level as the BA Client running
on the Windows Mount Proxy and can also be installed from the equivalent release level of the Linux
TSM for VE media.
For a Linux file level restore, the Windows Mount Proxy is chosen in the GUI. The Windows mount
proxy will mount the VMDK backup images from the TSM server and present them as iSCSI targets.
The Windows Mount proxy will then communicate with the Linux Mount proxy via the DSMCAD
running on the Linux Mount proxy. The Linux Mount proxy will invoke the iSCSI utilities to attach to
the presented iSCSI targets, and mount those targets as filesystems from which the required files
can be copied. Optionally the Linux mount proxy can be instructed to export an NFS mount which
can be connected to the original guest to allow for file copy.
The Linux mount proxy server can be a physical machine or a VM guest and should only be used for
mount operations and not for backup or restore operations (should not be used as a datamover
server).
IBM Confidential
89
Install the TSM BA Client on the Linux mount proxy server per the “IBM Tivoli Storage Manager for
UNIX and Linux Backup-Archive Clients Installation and User’s Guide”. In this example, the Linux
TSM for VE media is being used to install the BA Client (datamover).
IBM Confidential
90
Configuring the Linux (Partner) Mount Proxy
The parameters for the dsm.sys file on the Linux Mount Proxy server can be found in
the TSM for VE GUI.
To retrieve the sample dsm.sys

entries, go to the Configuration
Status page of the TSM for VE
GUI. From the “Tasks”
pulldown, select “Edit TSM
Configuration”.
IBM Confidential
91
On the Configuration Settings

page, select “Mount Proxy
Node Pairs”.
Click on “View Settings” for the

desired node.
IBM Confidential
92
Click on the Linux Partner Node tab. Copy the settings.
Copy the settings to be used in

the dsm.sys file.
IBM Confidential
93
On the Linux Mount Proxy server, change directory to /opt/tivoli/tsm/client/ba/bin. Copy the
dsm.sys.smp file to dsm.sys and edit the file. Replace the sample stanza with the information copied
from the GUI. If you plan to run a firewall on the Linux proxy, then add the webports parameter as
shown.
IBM Confidential
94
Copy the dsm.opt.smp file to a new file, dsm.<mount proxy node name>.opt.
Edit the new file and set the SERVERName parameter to match the SERVERName entry in the
Mount Proxy Node stanza of the dsm.sys file. (Note the ‘MPNODE_’ prefix.)
IBM Confidential
95
Invoke the BA Command line, ‘dsmc’, using the –optfile= option to specify the Mount Proxy Node
option file. Verify the ‘user id’ is the mount proxy node name. Enter the password for the node which
was created during the configuration wizard. If you do not know the password, update the node
password on the TSM server and then enter that password here. Quit from the BA Client command
line.
IBM Confidential
96
Copy the ‘rc.dsmcad’ file to a new file by appending the mount proxy node name,
cp rc.dsmcad rc.dsmcad.<mount proxy node name>.
Edit the new file and insert two lines as shown. Specify the newly created option file for the DSM_CONFIG
export. Save the exit the file.
export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin
export DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.<mount proxy node name>.opt
IBM Confidential
97
Create a symbolic link in /etc/init.d for the mount proxy DSMCAD service.
ln –s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad.<mount proxy node name> /etc/init.d/dsmcad.<mount proxy

node name>.
Start the service as specified in the link command: service dsmcad.<mount proxy node name> start
Set the service to autostart upon reboot: ‘chkconfig --add dsmcad.<mount proxy node name>
IBM Confidential
98
Return to the Configuration Status screen in the TSM for VE GUI. Click on the datacenter name,
highlight the windows mount proxy node and click ‘Validate Selected Node’.
IBM Confidential
99
The status of the Linux Mount Proxy node should now be ‘Running’, and should be reported as working
properly.
Note that the Linux Mount Proxy status may show a warning message:
ANS3144W The ISCSI service is not running. File level restore mount operations will not work.
The iSCSI utilities do not normally run if there are no connections. You can force the iscsi daemon to start
on the Linux server by issuing the command “service iscsid force-start”, however the service will normally
start automatically when a file level restore is attempted.
IBM Confidential
100
When using the File Level Restore feature of the TSM for VE GUI, the user is presented the option of
creating an NFS share on the mount proxy server. The specified server can then connect to the NFS share
in order to copy files.
If you plan to use this option, start the NFS service and set it to start automatically upon reboot.
IBM Confidential
101
IBM Confidential
102
Additional Mount Proxy Node Pairs may be created by first using the TSM for VE GUI to add the nodes to
TSM. Rename the nodes appropriately to create unique names. Follow the instructions earlier in this
document to complete the Linux and Windows Installation and configuration steps.
IBM Confidential
103
Adding a Data Mover
IBM Confidential
104
Adding a Datamover
Additional Datamovers may be created by first using the GUI to add the nodes to TSM. Rename the nodes
appropriately to create unique names.
IBM Confidential
105
Adding a Datamover to an Existing vStorage Backup Server
Adding a second datamover to a vStorage Backup Server does not require any additional software
installation.
Simply follow the steps to create an option file for the new datamover node, add a stanza to the dsm.sys
file, create the rc.dsmcad.<datamover node name> file, create the link in /etc/init.d, start the dsmcad
service, and set the service to start automatically after reboot.
Instructions for each of these steps can be found earlier in this document.
IBM Confidential
106
Adding a Datamover to a New vStorage Backup Server
Follow the instructions earlier in this document to complete the Linux Installation and configuration steps.
1) Install TSM for VE as shown earlier. On the ‘Select Install Features’ page, do not check the Data
Protection for Vmware Recovery Agent or Data Protection for Vmware GUI options. This will install the
VMware Enablement File required to run the datamover.
2) Install the datamover (BA Client) software as shown earlier.
3) Validate the datamover node in the TSM for VE GUI.
Do not check these boxes when

deploying additional datamover
servers. An additional TSM for VE GUI
installation is not required.
IBM Confidential
107
Schedule a Backup
IBM Confidential
108
Schedule a Backup
Click the Backup tab in the web GUI or vCenter Plug-in to start scheduling backups.
Click Create Schedule to schedule a new backup.
IBM Confidential
109
TSM for VE vSphere Web Client Extension
IBM Confidential
110
If you checked the option ‘Register as an Extension in vSphere Web Client’ during the installation
process, the TSM for VE integration with the vSphere Web Client will be installed. This is the initial
offering of this integration which allows authorized users to invoke full guest restores via the vSphere
Web Client.
NOTE: The integration requires vSphere to be at version 5.5 update 1.
IBM Confidential
111
Two new VMware administrator role privileges are installed. The first is under the Global privilege group
and is called ‘Configure IBM Data Protection’. This privilege is required for the administrator to be able to
create a connection to a vStorage Backup Server.
IBM Confidential
112
The second is under the Datacenter privilege group and is called ‘IBM Data Protection’.
This privilege is required for the administrator to be able to use the TSM for VE integration
features.
IBM Confidential
113
To create a connection from the vSphere Web Client to the vStorage Backup Server, click
on ‘IBM Data Protection’.
IBM Confidential
114
Click on ‘Set up a connection’ or on the ‘Connections’ tab.
IBM Confidential
115
Highlight the vCenter name and click ‘Edit’.
IBM Confidential
116
Enter the DNS name or IP Address for the vStorage Backup Server where the TSM for VE
GUI is installed. Click Save.
IBM Confidential
117
A message should be displayed indicating a successful update. Click Close.
IBM Confidential
118
Note that the ‘Connection Status’ column should indicate ‘Verified Connection’.
IBM Confidential
119
The current integration allows full guest restores. To restore a guest to a new name, right
click on the guest name, select ‘All IBM Data Protection Actions’, then select ‘Restore’.
IBM Confidential
120
The restore sequence will then begin.
IBM Confidential
121
IBM Confidential
122
IBM Confidential
123
Restores can also be initiated from the ‘IBM Data Protection’ tab of the Datacenter ‘Manage’ tab.
The restore of a guest that no longer exists would be invoked using this method.
IBM Confidential
124

TSM For VE 7.1.1 Installation Cookbook - Linux (v2) PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TSM For VE 7.1.1 Installation Cookbook - Linux (v2) PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Tivoli Storage Manager for Virtual Environments

IBM Tivoli Software | © 2013 IBM Corporation

This is a summary of the steps which will be accomplished in this document

TSM for VE ports

Standard TSM ports

In a non-GUI Linux environment, the ports can be manually added to the

After updating the iptables files, restart the iptables service.

Supported Linux versions for the mount proxy:

64-Bit RHEL 6.1 or higher

Supported Windows versions for the mount proxy:

64-Bit Windows Server 2008 R2

Ensure that the Linux iSCSI utilities (iscsiadm) are installed.

The IP of the network adapter configured on the Linux mount proxy

The Linux mount proxy server can be a physical machine or a VM guest

Click to accept the terms of the

The Deployment Engine will be

Three options are available for GUI access.

Choose the desired option(s) and click Next.

Enter your vCenter Server address and

Click on Tivoli Data Protection for

Click on Tivoli Data Protection for

Enter the required information to connect to your TSM server

Enter the DNS name or IP address

Modify the TSM Server port

Enter a TSM server Admin ID and

Check the box to save the ID and

Enter a prefix for the TSM

Note: The wizard will

Verify the Policy domain to be

Create the vCenter Node in TSM.

This field will be pre-filled with a

Check the ‘Register Node’ box

Create the VMCLI Node.

This field will be pre-filled with a

Check the ‘Register Node’ box

Select the VMware Datacenters to be managed.

In this example Datacenter-1 was

TSM node names for the datacenter and Data

Each of these may be modified by highlighting

Do not click Next yet.

Note that the passwords for each

To set the password for a node, either

(see next page)

Enter a password for the

Repeat the Set Password process

Do not click Next yet.

By clicking on the generated Primary Node name, you

Any changes to the Primary Node will automatically be

Do not click Next yet.

vCenter Node Name

VMCLI Node Name

Datacenter Node Name

Data Mover Node Name

Mount Proxy Node Name

Mount Proxy Node Name

Change directory to /opt/tivoli/tsm/client/ba/bin. Copy the dsm.opt.smp file to a new file

Copy the dsm.sys.smp file to dsm.sys.

SErvername VE711L_DATACENTER-1_DM <use the datamover node name>

VMMAXParallel 4 <Maximum Concurrent Guest Backups>

<Include the datamover name in the log files>

ln –s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad.<datamover node name>

1) Change directory back to /opt/tivoli/tsm/client/ba/bin.

Set the password for the vCenter Server.