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 [email protected] .

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.

2

IBM Confidential

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

1. 2. 3. 4. 5. 6. 7.

3

Verify Prerequisites Install the TSM for VE software on the Linux vStorage Backup Server. Configuration using the TSM for VE Web Browser GUI. Install and Configure the datamover on the vStorage Backup Server. Configure the Linux (Partner) Mount Proxy. Install and Configure the Windows (Primary) Mount Proxy. Configure and use the vSphere Web Client Extension.

IBM Confidential

Prerequisites

4

IBM Confidential

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.)

5

IBM Confidential

Communication Port Requirements – Firewall Configuration

6

IBM Confidential

Communication Port Requirements – Firewall Configuration In a non-GUI Linux environment, the ports can be manually added to the /etc/sysconfig/iptables file as shown.

7

IBM Confidential

Communication Port Requirements – Firewall Configuration After updating the iptables files, restart the iptables service.

8

IBM Confidential

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.

9

IBM Confidential

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.

10

IBM Confidential

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).

11

IBM Confidential

Tivoli Data Protection for VMware Installation - Linux

12

IBM Confidential

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.

13

IBM Confidential

TSM for VE Installation - Linux Change directory to the DataProtectionForVMware directory in the TSM for VE Media. Run install-Linux.bin.

14

IBM Confidential

TSM for VE Installation - Linux

Click OK.

Click Next.

15

IBM Confidential

TSM for VE Installation - Linux

Click to accept the terms of the license agreement. Click Next.

The Deployment Engine will be installed.

16

IBM Confidential

TSM for VE Installation - Linux

Click Next.

Click Next.

17

IBM Confidential

TSM for VE Installation - Linux 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.

18

IBM Confidential

TSM for VE Installation - Linux 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://www01.ibm.com/support/docview.wss?uid=swg21 659544

19

IBM Confidential

TSM for VE Installation - Linux

Click Next.

20

IBM Confidential

TSM for VE Installation - Linux

Click OK.

21

IBM Confidential

TSM for VE Installation - Linux

Click Install.

22

IBM Confidential

TSM for VE Installation - Linux

Click Next.

Click Done.

23

IBM Confidential

TSM for VE Configuration Run via the TDP for VMware Web Browser GUI

24

IBM Confidential

TSM for VE Configuration Access the GUI via web browser to URL https://hostname:9081/TsmVMwareUI/ . Log in using vCenter Server credentials.

25

IBM Confidential

TSM for VE Configuration 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.

26

IBM Confidential

TSM for VE Configuration 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.

27

IBM Confidential

TSM for VE Configuration Launching the GUI for the first time will automatically launch the Configuration Wizard.

Click Next

28

IBM Confidential

TSM for VE Configuration 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.

29

IBM Confidential

TSM for VE Configuration

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.

30

IBM Confidential

TSM for VE Configuration 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.

31

IBM Confidential

TSM for VE Configuration 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.

32

IBM Confidential

TSM for VE Configuration 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.

33

IBM Confidential

TSM for VE Configuration

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.

34

IBM Confidential

TSM for VE Configuration 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)

35

IBM Confidential

TSM for VE Configuration Set the TSM node passwords for the Datacenter and Data Mover nodes

Enter a password for the selected node and click OK.

36

IBM Confidential

TSM for VE Configuration Set the TSM node passwords for the Datacenter and Data Mover nodes

Repeat the Set Password process for the other node(s) until all nodes show ‘Change’ in the Password column. Click Next.

37

IBM Confidential

TSM for VE Configuration 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.

Do not click Next yet.

38

IBM Confidential

TSM for VE Configuration 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. Do not click Next yet.

39

IBM Confidential

TSM for VE Configuration 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.

40

IBM Confidential

TSM for VE Configuration 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 41

IBM Confidential

TSM for VE Configuration Click Next.

42

IBM Confidential

TSM for VE Configuration 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

43

IBM Confidential

TSM for VE Configuration The Wizard Tasks should all show a state of Successful. Click Close.

44

IBM Confidential

TSM for VE Configuration The Configuration Status screen shows the TSM node names. Notice the yellow warning symbol on the datacenter.

45

IBM Confidential

TSM for VE Configuration 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.

46

IBM Confidential

TSM for VE Configuration TSM Operations Center shows the nodes that were created on the TSM server.

47

IBM Confidential

TSM for VE Configuration The configuration wizard automatically creates the required proxy relationships for the Datacenter and vCenter nodes.

48

IBM Confidential

Installing and Configuring the Datamover

49

IBM Confidential

Installing and Configuring the Datamover 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.

50

IBM Confidential

Installing and Configuring the Datamover 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..opt

51

IBM Confidential

Installing and Configuring the Datamover 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.

52

IBM Confidential

Installing and Configuring the Datamover Copy the dsm.sys.smp file to dsm.sys.

53

IBM Confidential

Installing and Configuring the Datamover Edit the new file to include the parameters shown below. (see next page)

54

IBM Confidential

Installing and Configuring the Datamover More information on these parameters can be found in the BA Client Installation and User’s Guide.

SErvername nodename COMMMethod TCPPort VMCHost TCPServeraddress PASSWORDACCESS HTTPPORT MANAGEDSERVICES SCHEDMODE VMMAXParallel VMCTLMC

ERRORLOGName SCHEDLOGName

55

VE711L_DATACENTER-1_DM VE711L_DATACENTER-1_DM TCPip 1500 vsphere-srv 192.168.2.246 generate 1581 schedule webclient prompted 4 standard



"/opt/tivoli/tsm/client/ba/bin/dsmerror.VE711L_DATACENTER-1_DM.log" "/opt/tivoli/tsm/client/ba/bin/dsmsched.VE711L_DATACENTER-1_DM.log"

IBM Confidential

Installing and Configuring the Datamover Copy the file rc.dsmcad file to a new file by appending the datamover node name, rc.dsmcad.

56

IBM Confidential

Installing and Configuring the Datamover 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..opt

57

IBM Confidential

Installing and Configuring the Datamover 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. /etc/init.d/dsmcad.

58

IBM Confidential

Installing and Configuring the Datamover 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..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.

59

IBM Confidential

Installing and Configuring the Datamover Set the password for the vCenter Server. dsmc set password –type=VM -optfile=dsm..opt -serv= The vCenter admin ID must have the role permissions as specified in this Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21659544

60

IBM Confidential

Installing and Configuring the Datamover Start the DSMCAD service for the datamover: service dsmcad. start Set the DSMCAD service to start automatically after reboot. chkconfig --add dsmcad.

61

IBM Confidential

Installing and Configuring the Datamover 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’.

62

IBM Confidential

Installing and Configuring the Datamover 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.

63

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

64

IBM Confidential

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.

65

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy 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.

66

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy Start the installation of the software from the TSM for VE media.

67

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy 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.

68

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy Complete the software installation.

Click Next Accept the License. Click Next

Click Next

Click Next

Click Install

69

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy Complete the software installation and reboot.

Click Install

Click OK Click Finish

Click OK

Click Yes 70

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy After reboot, click Finish on the Wizard Completion screen.

71

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy 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. 72

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Copy the settings to be used in the dsm..opt file. These are the settings on the ‘Primary Node’ tab.

73

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

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..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.

74

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

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. 75

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy Click on Edit and select Client Preferences.

76

IBM Confidential

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.

77

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy Click on Utilities and select ‘Setup Wizard’.

78

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy Check the box to ‘Help me configure the TSM Web Client’. Click Next.

79

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Click Next.

Select Install a new Web Client agent. Click Next.

80

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Append the Mount Proxy Node name to the Client Acceptor name. Click Next.

Verify the option file name and click Next.

81

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Click Next.

Enter the mount proxy node password. Click Next.

82

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Select ‘Automatically when Windows boots’ as the start option. Click Next.

Append the mount proxy node name to the agent name.

Click Next.

83

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Click Next.

Select ‘Yes’ to start the service. Click Next.

84

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy

Click Apply.

Click Finish. Close the BA Client GUI.

85

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy 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.

86

IBM Confidential

Installing and Configuring the Windows (Primary) Mount Proxy 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.

87

IBM Confidential

Completing the Linux Mount Proxy Installation and Configuration

88

IBM Confidential

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).

89

IBM Confidential

Completing the Linux Mount Proxy Installation and Configuration 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).

90

IBM Confidential

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”.

91

IBM Confidential

Configuring the Linux (Partner) Mount Proxy

On the Configuration Settings page, select “Mount Proxy Node Pairs”.

Click on “View Settings” for the desired node.

92

IBM Confidential

Configuring the Linux (Partner) Mount Proxy Click on the Linux Partner Node tab. Copy the settings.

Copy the settings to be used in the dsm.sys file.

93

IBM Confidential

Completing the Linux Mount Proxy Installation and Configuration 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.

94

IBM Confidential

Configuring the Linux (Partner) Mount Proxy Copy the dsm.opt.smp file to a new file, dsm..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.)

95

IBM Confidential

Configuring the Linux (Partner) Mount Proxy 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.

96

IBM Confidential

Configuring the Linux (Partner) Mount Proxy Copy the ‘rc.dsmcad’ file to a new file by appending the mount proxy node name, cp rc.dsmcad rc.dsmcad.. 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..opt

97

IBM Confidential

Configuring the Linux (Partner) Mount Proxy Create a symbolic link in /etc/init.d for the mount proxy DSMCAD service. ln –s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad. /etc/init.d/dsmcad..

Start the service as specified in the link command: service dsmcad. start Set the service to autostart upon reboot: ‘chkconfig --add dsmcad.

98

IBM Confidential

Configuring the Linux (Partner) Mount Proxy 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’.

99

IBM Confidential

Configuring the Linux (Partner) Mount Proxy 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.

100

IBM Confidential

Configuring the Linux (Partner) Mount Proxy 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.

101

IBM Confidential

Creating Additional Mount Proxy Node Pairs

102

IBM Confidential

Creating Additional Mount Proxy Node Pairs 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.

103

IBM Confidential

Adding a Data Mover

104

IBM Confidential

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.

105

IBM Confidential

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. 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.

106

IBM Confidential

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.

107

IBM Confidential

Schedule a Backup

108

IBM Confidential

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.

109

IBM Confidential

TSM for VE vSphere Web Client Extension

110

IBM Confidential

TSM for VE vSphere Web Client Extension 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.

111

IBM Confidential

TSM for VE vSphere Web Client Extension 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.

112

IBM Confidential

TSM for VE vSphere Web Client Extension 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.

113

IBM Confidential

TSM for VE vSphere Web Client Extension To create a connection from the vSphere Web Client to the vStorage Backup Server, click on ‘IBM Data Protection’.

114

IBM Confidential

TSM for VE vSphere Web Client Extension Click on ‘Set up a connection’ or on the ‘Connections’ tab.

115

IBM Confidential

TSM for VE vSphere Web Client Extension Highlight the vCenter name and click ‘Edit’.

116

IBM Confidential

TSM for VE vSphere Web Client Extension Enter the DNS name or IP Address for the vStorage Backup Server where the TSM for VE GUI is installed. Click Save.

117

IBM Confidential

TSM for VE vSphere Web Client Extension A message should be displayed indicating a successful update. Click Close.

118

IBM Confidential

TSM for VE vSphere Web Client Extension Note that the ‘Connection Status’ column should indicate ‘Verified Connection’.

119

IBM Confidential

TSM for VE vSphere Web Client Extension 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’.

120

IBM Confidential

TSM for VE vSphere Web Client Extension The restore sequence will then begin.

121

IBM Confidential

TSM for VE vSphere Web Client Extension

122

IBM Confidential

TSM for VE vSphere Web Client Extension

123

IBM Confidential

TSM for VE vSphere Web Client Extension 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.

124

IBM Confidential