Setting up the Dell DR Series System with IBM Tivoli Storage Manager Dell Engineering May 2016 A Dell Technical White Paper
Revisions Date Description January 2014 Initial release August 2014 Added screenshots where new functionality is introduced in 2014 April 2015 Updated for v3.2 release June 2015 Updated the cleaner recommendations May 2016 Updated with ISCSI VTL support and instructions THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. © 2016 Dell Inc.
Table of contents 1 2 3 Installing and configuring the DR Series system ....................................................................................................................... 5 1.1 Creating a container (NFS/CIFS) ......................................................................................................................................... 8 1.2 Creating a VTL container with an iSCSI connection ..................................................................................
Executive summary This document provides information about how to set up the Dell DR Series system as a backup to disk target for IBM Tivoli Storage Manager (TSM). For additional information, see the DR Series system documentation and other data management application best practices whitepapers for your specific DR Series system at: http://www.dell.
1 Installing and configuring the DR Series system 1. Rack and cable the DR Series system, and power it on. In the Dell DR Series System Administrator Guide, refer to the sections “iDRAC Connection”, “Logging in and Initializing the DR Series System”, and “Accessing IDRAC6/Idrac7 Using RACADM” for information about using the iDRAC connection and initializing the appliance. 2. Log on to iDRAC using the default address 192.168.0.
5. View the summary of preferences and confirm that it is correct. 6. Log on to the DR Series system administrator console using the IP address you just provided for the DR Series system with the username: administrator and password: St0r@ge! (The “0” in the password is the numeral zero.). Note: if you do not want to add the DR Series system to Active Directory, see the DR Series System Owner’s Manual for guest logon instructions. 7. Join the DR Series system into the Active Directory domain. a.
b. Enter your Active Directory credentials.
1.1 Creating a container (NFS/CIFS) 1. Create and mount the container by selecting Containers in the left navigation area and then clicking Create at the top of the page. 2. Enter a Container Name, and click Next. 3. Select the storage access protocol as NAS, and then click Next.
4. Select to Enable Access Protocols (NFS or CIFS) as appropriate and select the Marker type as Auto. Click Next. 5. Configure access by doing one of the following: • For NFS, select the preferred client access credentials, and click Next. • 9 For CIFS, select the preferred client access credentials, and click Next.
6. Check the configuration summary, and click Create a New Container. 1.2 Creating a VTL container with an iSCSI connection 1. Create and mount the container by selecting Containers in the left navigation area and then clicking Create at the top of the page. 2. Enter a container name, select the VTL option, and then click Next.
3. Select the required tape size, the access protocol as iSCSI, and the marker type. Also, enter the initiator details as appropriate. Click Next. 4. Click Create a New Container.
5. Confirm that the container is successfully added on the Containers page.
2 Configuring IBM Tivoli Storage Manager for CIFS & NFS target containers 2.1 Configuring the device class for CIFS & NFS protocols The following instructions describe a basic configuration for connecting a DR Series system to the Windows version of IBM Tivoli Storage Manager (TSM) version 7.1.4. 1. Open the IBM Tivoli Storage Manger Administration Center. 2. Click Storage Devices > View Storage Classes. 3. Click Create a Device Class.
4. Select the FILE device type, and click Next. (This device type is optimized for writing to disk-based storage.) 5. Under General Information, enter the following information, and click Next. • Name – Enter a descriptive name for the device class. • Path – Add the UNC path to the DR container for CIFS and the mount point of DR Series system export for NFS. • Mount Limit – Set the mount limit. The DR Series system supports up to 32 concurrent CIFS connections. The optimal number of connections is five.
An example for the NFS container path follows. 6. Click Finish.
2.2 Configuring the storage pool for CIFS & NFS protocols 1. Click Storage Devices > View Storage Pools. 2. Click Create Storage Pools.
3. Click Next. 4. Enter the following information for General Storage Pool Settings and then click Next. • Storage Pool Name: Enter a descriptive name for the DR Series system pool. • Storage Pool Description: Enter a description for the DR Series system pool. • Storage Pool Type: Select Sequential Access as the DR Series system is integrated as a FILE type device.
5. Enter the required information for the device class, and click Next. • Device Class Name: Select the name of the DR Series system device class (created previously). • Maximum Number of Scratch Volumes: Set the number of scratch volumes in the system. (Setting the value between 100 to 200 scratch volumes is recommended.) 6. For Identifying Duplicates, accept the defaults selections, and click Next.
7. 2.3 Creating a policy domain for the backup job 1. 19 Review the settings and click Finish. Click Policy Domains > View Policy Domains.
2. Click Create a Policy Domain. 3. Click Next. 4. Enter the following required information, and then click Next. • Name: Enter a descriptive name for the DR Series system policy domain. • Description: Enter a description for the DR Series policy domain.
5. Enter the required information for data and storage pool settings, and then click Next. • Specify default management class: Select the DR Series system pool that was set up previously. • Number of file versions to Keep: Specify how many versions of a file to keep. • Number of days to keep inactive versions: Specify how many days to retain data after it falls out of policy. Note: File versions and inactive versions are set based on company policies. 6.
7. Select View all client nodes to display the set of clients to move to the DR Series system, and click Next. Note: You can choose to limit if you have a lot of client computers. 8. Select the check boxes next to the clients you want to back up to the DR Series system, and click Next.
9. Click Finish. 2.4 Creating client node and backup sets 1. 23 Open the client nodes and backup sets from TSM to register the client machine.
2. Provide the client name, policy name, and password to connect. 3. Confirm that the client node is successfully registered.
3 Creating and configuring iSCSI target container(s) for TSM 3.1 Configuring the iSCSI initiator 3.1.1 Configuring ISCSI initiator for Windows 1. 25 In the Windows TSM Server, open iSCSI initiator software, and then enter the DR IP/Hostname as target. Click Quick Connect.
Quick connect will discovers the targets. 2. Click Done. 3. Then, select the required targets and click Connect.
4. Click Advanced. 5.
6. Click OK. 7. 28 Verify that the Status shows as “Connected,” and click OK.
3.1.2 Configuring the iSCSI initiator – Linux Before you begin this procedure, ensure that the iSCSI initiator is installed (iscsi-initiator-utils). For example, enter the following command: yum install iscsi-initiator-utils ; /etc/init.d/iscsi start To configure the iSCSI target for Linux, follow these steps. 1. Add the CHAP Authentication details for the DR Series system on the Linux Initiator as follows: a. Edit /etc/iscsi/iscsid.conf and un-comment the following line: node.session.auth.
3.2 Configuring DR Series system VTL for Windows and Linux TSM servers Note: Refer to the following instructions for viewing the tape devices and IDs, which you will need to configure the DR Series system VTL. For Windows: To see the Tape Library device IDs, use the command “tsmdlst.” For example: cd C:\program files\Tivoli\TSM\Server\Tsmdiag .\tsmdlst.exe For Linux: For discovering the tape devices and their IDs, refer to Appendix C later in this document. 3.2.
Check in the library volumes 3.2.1.6 # checkin libvolume TSM-iscsi search=yes checklabel=barcode status=scratch 3.2.2 Configuring the DR Series system VTL for Linux 3.2.2.1 Define library # define library TSM-iscsi libtype=scsi shared=yes autolabel=yes Define library path 3.2.2.2 # define path RHEL-TSM-SERVER TSM-iscsi srct=server autodetect=yes destt=library device=/dev/tsmscsi/lb0 Define drive 3.2.2.
3.3 Configuring the device class for iSCSI VTL Follow Steps 1, 2, and 3 earlier in the Device Class creation section 2.1. 1. Select the Device Type as LTO for iSCSI VTL. 2. Under General Information, provide the name and select the library configured. Under Drive-level data encryption, select the Do not allow drives to encrypt data option, and under Logical block protection, click None.
3. Click Next and then click Finish. 3.4 Configuring the storage pool for iSCSI VTL 1. Follow Steps 8,9 and 10 from the previous Storage Pool creation section 2.2 2. Under General storage pool settings, provide the pool name and type, and then click Next.
4. Provide the necessary Device name and maximum number of Scratch volumes and click Next. 5. Click Finish.
3.4.1 Adding volumes to a library 1. After creating a storage pool, click Storage Devices in the Left Pane, and then select the library that was configured earlier. 2. Select the column (which was default earlier) and disable the target reset option when the server is restarted.
3. In the Volumes section, click Add Volumes. 4. Select the option, All of the volumes are labeled. Just check them in. Click Next.
6. Select the option, Search for all eligible volumes in the library’s regular slots. Click Next. 7. 37 On the Check in Volumes page, do the following: a. Select the option, Read bar codes and check in all eligible volumes. b. Select Scratch as the pool to check in volumes to the scratch pool. c. Click Next.
8. For Advanced Options, select the option, Do not prompt me to insert the tape volumes into the library. Click Next. 9. Click Finish.
10. Check that all the volumes are created. 3.4.2 Adding volumes to a storage pool 1. 39 Go to the Storage Pool section (which was created earlier for the iSCSI target), and click Volumes.
2. In the Volumes section, click Add Volumes. 3. Provide the details of the volumes one by one in the volumes name column. Note: Provide exactly the same volume name as present in the LIBRARY for volume name for the storage pool.
4. Check that all the storage pool volumes are configured 3.5 Creating the policy domain for iSCSI VTL Follow the steps described in the earlier section related to Policy Domain creation, Section 2.3. 3.6 Creating the client node for iSCSI VTL Follow the steps described earlier in the section for creating a client node, Section 2.4.
4 Using the Backup & Archive GUI On a client machine, open the Backup-Archive GUI. Provide the user ID and password details that were described previously. When you have logged on, the Backup button will be enabled. The Backup and Restore Manager is ready to perform. When you have successfully completed the steps above, you have configured the DR Series system for TSM. The next time the client is scheduled to back up it will back up to the DR Series system(s).
5 Setting up the DR Series system cleaner Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from system containers in which files were deleted as a result of deduplication. The system cleaner runs during idle time. If your workflow does not have a sufficient amount of idle time on a daily basis, then you should consider scheduling the cleaner to force it to run during a scheduled time.
6 Monitoring deduplication, compression, and performance After backup jobs have run, the DR Series system tracks capacity, storage savings, and throughput on the DR Series system dashboard. This information is valuable in understanding the benefits of the DR Series system. Note: Deduplication ratios increase over time. It is not uncommon to see a 2-4x reduction (25-50% total savings) on the initial backup. As additional full backup jobs are completed, the ratios will increase.
A Configuring CIFS authentication This appendix describes the steps for sync-ing CIFS authentication between the TSM service account and the DR Series system. There are two methods for allowing the TSM service account to authenticate to a DR Series system. • • Integrate the Tivoli Storage Manager Media Server and DR Series system with Active Directory (AD). o Ensure the AD user has appropriate ACLs to the DR4X00 Container. o Set the TSM Server service to run with .
Note: If you are using local sync’ed accounts instead of an Active Directory account, make sure that there is a “.\”in front of the user name. 3. Click OK. 4. Right-click the TSM Service process, and click Stop/Start to restart the process.
B Best practices/considerations B.1 Deduplication The DR Series system has inline deduplication built-in and does not require any additional deduplication to be done ahead of data being written to the DR Series system. The system will remove any redundancies in the data before the data is stored on disk. Enabling deduplication before the data stream is sent to the DR Series system will cause the data to be obfuscated, not allowing the system to achieve optimal dedupe savings.
C Configuring the tape library devices on Linux After installing the required device drivers for medium changer and drive, we need to configure tape Library with TSM Server. There is need to figure out the device IDs for respective devices so that Library can be defind in TSM. In Windows server, there is a command utility “tsmdlst,” which lists all the devices with their IDs. The same can be done in Linux TSM server with “Autoconf” utility located at ‘/opt/tivoli/tsm/devices/bin’.
6. Change the permissions of the devices to avoid IO error during Library configuration – chmod 777 /dev/tsmscsi/* chown tsminst1:tsmsrvrs /dev/tsmscsi/* chmod 777 /dev/IBM* chown tsminst1:tsmsrvrs /dev/IBM* Note: tsminst1 and tsmsrvrs are the user and group created for TSM installation.
