REO Application Notesupport.overlandstorage.com/jive/servlet/KbServlet/... · 2 ! AN-DBP-064a:...

REO SERIES™AN-DBP-064a: Configuring IBM Tivoli

Storage Manager 5.2 and Sun Solaris 9 with Fibre Channel-Connected REO VTL

Overland Storage REO SERIES™

PrefaceThis document assumes that you have already set up and configured your REO. For more information, see the Setup Guide that came with your appliance.

This document describes how to configure a REO virtual tape-library (VTL) via Fibre Channel (FC) that uses an Emulex LP10000 FC host bus adapter (HBA) with Sun Solaris 9 and IBM Tivoli Storage Manager (TSM) 5.2.6.4.

Verifying that the HBA and Solaris Recognize the VTL1 Launch the Emulex Hbanyware utility (/usr/sbin/hbanyware), and verify

that the REO VTL and associated tape devices are present.

2 To ensure that Solaris can create the tape-device files, verify that the proper entries exist in the st.conf file.

Example of st.confname="st" parent="lpfc" target=0 lun=195;name="st" parent="lpfc" target=0 lun=196;name="st" parent="lpfc" target=0 lun=197;

3 To verify that the tape-device drivers were created, type:ls /dev/rmt/?

A message similar to the following appears (in this example the VTL uses two virtual tape drives): /dev/rmt/0 /dev/rmt/1

2 ! AN-DBP-064a: Configuring IBM Tivoli Storage Manager 5.2 and Sun Solaris 9 with Fibre Channel-Connected REO VTL

Application Note

Modifying TSM Configuration Files1 To verify that the TSM software (server and drivers) is installed on the

Solaris system, type:pkginfo | grep TIV

Messages similar to the following should appear:application TIVsmS Tivoli Storage Manager/Sun Serverapplication TIVsmSdev Tivoli Storage Manager/Sun SolarisDevice Drivers

2 To ensure that the TSM drivers are used with the VTL, modify the mt.conf and lb.conf files as described in the following.

a Change directory to /usr/kernel/drv

b Edit mt.conf, and add the correct target and logical unit number (LUN) information for the virtual tape-drives. Use the Emulex Hbanyware utility to determine the correct information. Save the file when you are done.

The following shows an example.# ----------------------------------------------------------# TSM Fibre tape device driver configuration file.# ----------------------------------------------------------## This file should contain one stanza of the following form# for each FC-attached tape drive that the TSM server is to use:## name="mt" class="scsi"

# target=$X$ lun=$Y$ hba="Z" wwpn="W";

name="mt" class="scsi"target=0 lun=196;

name="mt" class="scsi"target=0 lun=197;

c Edit lb.conf, and add the correct target and LUN information for the virtual tape-library. Use the Emulex Hbanyware utility to determine the correct information. Save the file when you are done.

The following shows an example.# ----------------------------------------------------------# TSM Fibre autochanger device driver configuration file.# ----------------------------------------------------------## This file should contain one stanza of the following form# for each FC-attached autochanger that the TSM server is to use:## name="lb" class="scsi"# target=$X$ lun=$Y$ hba="Z" wwpn="W";#

name="lb" class="scsi"target=0 lun=195;

3 Create the device drivers for TSM.

a To create the MT device files for the virtual tape-drives, type:add_drv <insert applicable parameters>

The following shows an example:add_drv -m '* 0666 bin bin' /usr/kernel/drv/mtWarning: Pathname support will be discontinued in future releases of add_drv.Unable to install (mt) from /usr/kernel/drv/mt.Driver will be installed from /usr/kernel/drv/sparcv9/mt.

Modifying TSM Configuration Files " 3


b To create the LB device files for the virtual tape-library, type:add_drv <insert applicable parameters>

The following shows an example:add_drv -m '* 0666 bin bin' /usr/kernel/drv/lbWarning: Pathname support will be discontinued in future releases of add_drv.Unable to install (lb) from /usr/kernel/drv/lb.Driver will be installed from /usr/kernel/drv/sparcv9/lb.

4 Verify that the TSM drivers have been created.

a To verify that the MT devices were created for the virtual tape-drives, type:ls -l /dev/rmt/*mt

Messages similar to the following should appear:lrwxrwxrwx 1 root other 55 Dec 6 09:04 /dev/rmt/2mt -> ../../devices/pci@1f,0/pci@5/fibre-channel@0/mt@0,c4:mtlrwxrwxrwx 1 root other 55 Dec 6 09:04 /dev/rmt/3mt -> ../../devices/pci@1f,0/pci@5/fibre-channel@0/mt@0,c5:mt

b To verify that the LB devices were created for the virtual tape-library, type:ls -l /dev/rmt/*lb

Messages similar to the following should appear:lrwxrwxrwx 1 root other 55 Dec 6 08:08 /dev/rmt/0lb -> ../../devices/pci@1f,0/pci@5/fibre-channel@0/st@0,c4:lblrwxrwxrwx 1 root other 55 Dec 6 08:08 /dev/rmt/1lb -> ../../devices/pci@1f,0/pci@5/fibre-channel@0/st@0,c5:lblrwxrwxrwx 1 root other 55 Dec 6 09:04 /dev/rmt/4lb -> ../../devices/pci@1f,0/pci@5/fibre-channel@0/lb@0,c3:lb

5 Note the MT and LB devices.

You will use this information later when you configure TSM. In the preceding examples, devices 2mt and 3mt are the virtual tape-devices and 4lb is the virtual tape-library.

Configuring the VTL with TSM1 To start the TSM server, type the following from the install path of TSM

Server.dsmserv

A TSM server prompt (for example, TSM:SERVER1>) should appear.

2 To configure the VTL and associated drives, type:./dsmserv

3 To define a library, type:def libr neo libt=scsi

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE LIBR neo libt=scsiANR8400I Library NEO defined.ANR1434W No files have been identified for automatically storing device configuration information.

4 To define the path for the library, type:def path server1 neo srctype=server desttype=library device=/dev/rmt/4lb


Application Note

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE PATH server1 neosrctype=server desttype=library device=/dev/rmt/4lbANR8953I Library NEO with serial number is updated with the newly discovered serial number 125F85B0C3.ANR1434W No files have been identified for automatically storing device configuration information.ANR1720I A path from SERVER1 to NEO has been defined.

5 To define one of the virtual tape-drives (the element address for the first tape drive is 480), type:def drive neo mt0 element=480

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE DRIVE neo mt0element=480ANR8404I Drive MT0 defined in library NEO.ANR1434W No files have been identified for automatically storing device configuration information.

6 Define additional tape drives, incrementing the element address by one.def drive neo mt1 element=481

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE DRIVE neo mt1element=481ANR8404I Drive MT1 defined in library NEO.ANR1434W No files have been identified for automatically storing device configuration information.

7 To define the path for the first drive, type:def path server1 mt0 srctype=server desttyp=drive device=/dev/rmt/2mt library=neo

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE PATH server1 mt0srctype=server desttyp=drive device=/dev/rmt/2mt library=neoANR8955I Drive MT0 in library NEO with serial number is updated with the newly discovered serial number 125F85B0C4.ANR1434W No files have been identified for automatically storing device configuration information.ANR1720I A path from SERVER1 to NEO MT0 has been defined.

8 To define paths for additional virtual tape-drives, type:def path server1 mt1 srctype=server desttype=drive device=/dev/rmt/3mt library=neo

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE PATH server1 mt1srctype=server desttype=drive device=/dev/rmt/3mt library=neoANR8955I Drive MT1 in library NEO with serial number is updated with the newly discovered serial number 125F85B0C5 .ANR1434W No files have been identified for automatically storing device configuration information.ANR1720I A path from SERVER1 to NEO MT1 has been defined.

Configuring the VTL with TSM " 5


9 To define a device class for the VTL, type:def devclass ltoclass devtype=lto library=neo format=drive

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE DEVCLASS ltoclassdevtype=lto library=neo format=driveANR2203I Device class LTOCLASS defined.ANR1434W No files have been identified for automatically storing device configuration information.

10 To define a stage pool for the VTL, type:def stgpool ltopool ltoclass maxscratch=5 dataformat=native

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: DEFINE STGPOOL ltopoolltoclass maxscratch=5 dataformat=nativeANR2200I Storage pool LTOPOOL defined (device class LTOCLASS).

11 To label the virtual tape-devices and check them in to the scratch pool, type:label libv neo search=yes labelsource=barcode overwrite=yes checkin=scratch

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: LABEL libv neo search=yeslabelsource=barcode overwrite=yes checkin=scratchANR0984I Process 2 for LABEL LIBVOLUME started in the BACKGROUND at 02:44:59 PM.ANR8799I LABEL LIBVOLUME: Operation for library NEO started as process 2.TSM:SERVER1>ANR8439I SCSI library NEO is ready for operations.ANR8810I Volume XXX001 has been labeled in library NEO.ANR8810I Volume XXX002 has been labeled in library NEO.ANR8810I Volume XXX003 has been labeled in library NEO.ANR8810I Volume XXX004 has been labeled in library NEO.ANR8810I Volume XXX005 has been labeled in library NEO.ANR8810I Volume XXX006 has been labeled in library NEO.ANR8810I Volume XXX007 has been labeled in library NEO.ANR8810I Volume XXX008 has been labeled in library NEO.ANR8810I Volume XXX009 has been labeled in library NEO.ANR8810I Volume XXX010 has been labeled in library NEO.ANR8810I Volume XXX011 has been labeled in library NEO.ANR8810I Volume XXX012 has been labeled in library NEO.ANR8810I Volume XXX013 has been labeled in library NEO.ANR8810I Volume XXX014 has been labeled in library NEO.ANR8810I Volume XXX015 has been labeled in library NEO.ANR8810I Volume XXX016 has been labeled in library NEO.ANR8810I Volume XXX017 has been labeled in library NEO.ANR8810I Volume XXX018 has been labeled in library NEO.ANR8810I Volume XXX019 has been labeled in library NEO.ANR8810I Volume XXX020 has been labeled in library NEO.ANR1434W No files have been identified for automatically storing device configuration information.ANR8801I LABEL LIBVOLUME process 2 for library NEO completed; 20 volume(s) labelled, 20 volume(s) checked-in.ANR0985I Process 2 for LABEL LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 02:45:01 PM.

12 To audit the virtual devices in the REO VTL, type:audit library neo checklabel=barcode

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: AUDIT LIBRARY neochecklabel=barcodeANR0984I Process 3 for AUDIT LIBRARY started in the BACKGROUND at 02:45:17 PM.


Application Note

ANR8457I AUDIT LIBRARY: Operation for library NEO started as process 3.TSM:SERVER1>ANR1434W No files have been identified for automatically storing device configuration information.ANR8461I AUDIT LIBRARY process for library NEO completed successfully.ANR0985I Process 3 for AUDIT LIBRARY running in the BACKGROUND completed with completion state SUCCESS at 02:45:17 PM.

13 To verify that all virtual devices are in the scratch pool, type:q libv

Messages similar to the following should appear:ANR2017I Administrator SERVER_CONSOLE issued command: QUERY LIBV

Configuring a Backup Job1 From the working directory of TSM Client, execute dsmj by typing:

/opt/tivoli/tsm/client/ba/bin/dsmj &

Library Name Volume Name Status Owner Last Use Home Device Element Type----------- ---------- ----- ----- ------- ---- ------------ ----NEO XXX001 Scratch 32NEO XXX002 Scratch 33NEO XXX003 Scratch 34NEO XXX004 Scratch 35NEO XXX005 Scratch 36NEO XXX006 Scratch 37NEO XXX007 Scratch 38NEO XXX008 Scratch 39NEO XXX009 Scratch 40NEO XXX010 Scratch 41NEO XXX011 Scratch 42NEO XXX012 Scratch 43NEO XXX013 Scratch 44NEO XXX014 Scratch 45NEO XXX015 Scratch 46NEO XXX016 Scratch 47NEO XXX017 Scratch 48NEO XXX018 Scratch 49NEO XXX019 Scratch 50NEO XXX020 Scratch 51

Configuring a Backup Job " 7


2 Log on to the Backup/Archive Client.

3 Click Backup.

4 Select the source that you want to back up, and then click the Backup button.

\


Application Note

A status report appears while the job is active.

5 When the message appears that indicates the backup job completed successfully, click OK.

Configuring a Restore Job1 Log on to TSM as described in the previous section, and click Restore.

Configuring a Restore Job " 9


2 Select a File Level restore, browse for the source to restore, and then click the Restore button.

3 Restore the files to the Original location, or redirect the restore by selecting Following location, and providing a path for the alternate location.

4 Click the Restore button to begin.

5 To view the status of the restore job, click the active job.


REO Application Notesupport.overlandstorage.com/jive/servlet/KbServlet/... · 2 ! AN-DBP-064a:...

Documents

Transcript of REO Application Notesupport.overlandstorage.com/jive/servlet/KbServlet/... · 2 ! AN-DBP-064a:...