Setting up Linux data mover nodes

You can use the vStorage backup server to set up your Linux data mover nodes.

Before you begin

Gather the information described in the conceptual topic, Manually setting up the data mover nodes in a vSphere environment.

About this task

Procedure

Use the IBM-installed Java version, located at the Linux installation location for Java: export JAVA_HOME=/opt/tivoli/tsm/tdpvmware/common/jre/jre
Set the relevant environment variables.
1. Ensure that the JAVA_HOME environment variable is exported correctly:
```
JAVA_HOME=<jre-or-jdk-install-dir>
```
2. Ensure that the PATH environment variable is exported correctly:
```
export PATH=$PATH:$JAVA_HOME/jre/bin
```
Set up the client acceptor service and data mover scheduler service by completing the following tasks:
- Configure the data mover on Linux®.
  
  For the data mover on Linux, use the appropriate approach to configuration for your Linux OS and version: systemd or SysV. These are described in the following sections.
  
  To configure the data mover on Linux using systemd, complete the following steps:
  In this example procedure, PREFIX_DATACENTER_DM is used as a node name.
  1. Copy the updated file /etc/systemd/system/dsmcad.service to /etc/systemd/system/dsmcad@PREFIX_DATACENTER_DM.service, with file permissions 664.
  2. To ensure the script has 664 permissions, issue the following command:
```
chmod 664 dsmcad@PREFIX_DATACENTER_DM.service
```
  3. In the /etc/systemd/system/dsmcad@PREFIX_DATACENTER_DM.service file, change the command ExecStart=/usr/bin/dsmcad to the following command:
    ExecStart=/usr/bin/dsmcad -servername=%i -optfile=/opt/tivoli/tsm/client/ba/bin/dsm.%i.opt
    The %i is a special variable that will be set when running the systemctl command with "pre-at" as part of the unit file name, the "at" characters, and the wanted value.
  4. Ensure that the PREFIX_DATACENTER_DM stanza is specified in the /opt/tivoli/tsm/client/ba/bin/dsm.sys file and that it contains the ERRORLOGNAME and SCHEDLOGNAME options that are specific to the PREFIX_DATACENTER_DM node.
  5. In the /opt/tivoli/tsm/client/ba/bin/dsm.PREFIX_DATACENTER_DM.opt file, ensure that the SERVERName PREFIX_DATACENTER_DM option is set.
  6. Ensure that no dsmcad process is running that uses the PREFIX_DATACENTER_DM node name.
  7. Run the following commands to configure and enable the service to automatically start on boot:
```
systemctl start dsmcad@PREFIX_DATACENTER_DM
```
```
systemctl status dsmcad@PREFIX_DATACENTER_DM
```
```
systemctl enable dsmcad@PREFIX_DATACENTER_DM
```
  To configure the data mover on Linux using SysV, complete the following steps:
  In this example procedure, PREFIX_DATACENTER_DM is used as a node name.
  1. Copy the provided rc.dsmcad script and update the script so that the SERVERNAME is set to your node name: SERVERNAME=PREFIX_DATACENTER_DM
  2. Save the file as /etc/init.d/dsmcad.PREFIX_DATACENTER_DM
  3. Ensure the file has 775 permissions with chmod 755 dsmcad.PREFIX_DATACENTER_DM
  4. Create a text file called dsm.PREFIX_DATACENTER_DM.opt in /opt/tivoli/tsm/client/ba/bin and add the following setting: servername PREFIX_DATACENTER_DM
  5. Create dsm.sys in /opt/tivoli/tsm/client/ba/bin and add the data mover sample options.
    For a description of the options, see Options reference.
    
    For instant access, instant restore, or mount (file restore) operations, you must add VMISCSISERVERADDRESS to the data mover options file. Specify the iSCSI server IP address of the network card on the vStorage backup server that is used for the iSCSI data transfer during instant operations. The physical network interface card (NIC) that is bound to the iSCSI device on the ESX host must be on the same subnet as the NIC on the vStorage backup Server that is used for the iSCSI transfer.
  6. After creating the configuration files, store the vCenter credentials so that the data mover / mount proxy can access the vCenter inventory. Go to /opt/tivoli/tsm/client/ba/bin and issue the command: ./dsmc set password –type=VM fullyqualifieddomainnameofvcenter vcenteruserid vcenterpassword
    For information on required administrator rights. see technote 7047438
  7. Go to /opt/tivoli/tsm/client/ba/bin and execute the command: ./dsmc set password –type=VM fullyqualifieddomainname vcenteruserid vcenterpassword
  8. Depending on your OS, execute the following commands:
    - Red Hat: chkconfig - - add dsmcad.PREFIX_DATACENTER_DM
    - SUSE: chkconfig - - add dsmcad.PREFIX_DATACENTER_DM
    - Ubuntu: update-rc.d dsmcad.PREFIX_DATACENTER_DM defaults
  9. Run the command: service dsmcad.PREFIX_DATACENTER_DM start
  10. Once you have one data mover configured, you can use the Web Client plug-in GUI to add additional data movers or mount proxies.
  Note: When you run the chkconfig command the dsmcad.PREFIX_DATACENTER_DM will restart on a system reboot
  
  To start the service: service dsmcad.PREFIX_DATACENTER_DM start
  
  To stop the service: service dsmcad.PREFIX_DATACENTER_DM stop
  Note: If you uninstall IBM Storage Protect, you must stop the associated services:
  - Use the above stop command to stop the dsmcad service.
  - Disable the service with the command: systemctl disable dsmcad@PREFIX_DATACENTER_DM.service so that auxiliary files, such as/var/run/dsmcad.PREFIX_DATACENTER_DM.pid, are removed.
  - On RHEL or SLES, use the command: chkconfig --del dsmcad.PREFIX_DATACENTER_DM
  - On Ubuntu, use the command: update-rc.d dsmcad.PREFIX_DATACENTER_DM remove
  - Remove the dsmcad.* files from the /etc/init.d directory.

Results

Start a data mover command-line session with the -asnodename and -optfile command-line parameters: dsmc -asnodename=VC1_DC1 -optfile=dsm_DM1.opt
Make sure that after your initial sign-on, you are not prompted for your password.

Attention: To prevent the IBM Storage Protect scheduler from failing, make sure that the asnodename option is not set in the dsm.opt file (Windows) or dsm.sys file stanza (Linux). The scheduler queries the IBM Storage Protect server for schedules associated with nodename (data mover node), not asnodename (datacenter node). If asnodename is set in dsm.opt or dsm.sys, schedules associated with asnodename (and not nodename) are queried. As a result, scheduling operations fail.

Complete these tasks:

Verify the connection to the IBM Storage Protect server by issuing this command:
```
dsmc query session
```
This command shows information about your session, including the current node name, when the session was established, server information, and server connection information.
Verify you can back up a VM by issuing this command:
```
dsmc backup vm vm1
```
where vm1 is the name of the VM.
Verify that the backup completed successfully by issuing this command:
```
dsmc query vm "*"
```
Verify that the VM can be restored by issuing this command:
```
dsmc restore vm vm1 -vmname=vm1-restore
```
Verify that the client acceptor and agent are set up correctly:
1. In a web browser, enter IBM Storage Protect vSphere Client plug-in address. For example:
```
https://guihost.mycompany.com/vsphere-client/
```
2. Log in with the vCenter user name and password.
3. In the vSphere Web Client, click IBM Storage Protect > Configure > Data Movers.
4. Ensure that Verified is shown in the Status column for the data mover. If Failed is shown, hover over the status to view the failure message.
  Tip: When the IP address changes on the system where the Data Protection for VMware vSphere GUI is installed, you must complete the following:
5. Complete the tasks described in Troubleshooting
6. Set up the client acceptor again so that the Data Protection for VMware vSphere GUI becomes enabled for operations. Otherwise, the Plug-in Manager shows the Data Protection for VMware vSphere GUI status as disabled.