1) Steps after restoring TSM Database to earlier point in time

After restoring any Tivoli Storage Manager (TSM) server to earlier point in time DB backup by using
DSMSERV RESTORE DB command, there are some more additional steps required before
resuming normal operations of the TSM Server.

Restore of the TSM server database to an earlier point in time can cause TSM to encounter data on
disk and tapes for which it has no record, resulting in ANR1330E and ANR1331E errors.

It is important to save a copy of the volume history file (volhist.out, captured by running the BACKUP
VOLHIST command) on a regular basis. The information in this file can be used to reduce the
amount of volume auditing that is necessary after TSM DB restoration process.

After a TSM Server restore to a previous point in time, it is necessary to ensure that the storage pool
volumes are consistent with the TSM database which has been restored The following steps should
be performed prior to returning the TSM server to normal use

TSM Server Database Restoration after steps

Immediately after the TSM server database is restored, place the following options into
the dsmserv.opt file

NOMIGRRECL
(Prevents migration and reclamation from kicking off when the server is started)

DISABLESCHED YES
(prevents any schedules from starting when the server is started)

EXPINT 0
(prevents expiration from running when the server is started)

If set to something other than 0, change the setting to 0 and record the original setting. After few
steps we will remove or reset this option back to the original setting.

Start the server in the foreground (./DSMSERV)

When the TSM server prompt comes up, enter the command DISABLE SESSIONS so that
clients will be unable to connect to the TSM Server.

Review the saved volhist file, and locate sequential tape or FILE volumes marked as
"STGDELETE" and "STGREUSE" in the list. You will need to audit only these types of
volumes created after the date of the database backup that has been restored. If the volhist
file is lost or unrecoverable, then all sequential volumes must be audited. The audit
command is performed as follows

AUDIT VOLUME <volume_name> FIX=YES

Note that this command will verify the data on the volume against the entries in the TSM Server
database. Any items that are not found will be removed from the TSM Server.

It is also necessary to audit all of the disk pool volumes with the same command above.

Once the audits complete, the data on the volumes will be synchronized with the TSM
Database at the point in time of the last full database backup.

Halt the server and remove the options added in step one, nomigrrecl, disablescheds yes,
and set the expinterval back to its original setting.

Restart the server as normal. Issue the command ENABLE SESSIONS so that the clients
can connect to the server.

2) Tape Library and Tape Drives troubleshooting tips on Windows

Common Issues with TSM Server in Windows connecting to tape libraries and/or drives can be
resolved by checking some basics. The first things to do when addressing hardware issues are
given in the steps below.

1) Verify RSM service is Disabled

From Windows Services, verify that the Removable Storage service is Disabled. If it's not
Disabled and you don't intend to use it, set it to Disabled, and reboot Windows.

2) Verify that Windows Device Manager lists the library (Medium Changer) and/or Tape Drives
3) Verify that Windows Device Manager has the correct device driver for the library and/or
tape drives

Check device driver version from Windows Device Manager, by right-clicking on the device,
select Properties, Device Driver tab.
IBM tape drives and libraries typically use IBMtape (currently 6.2.1.6) or ibmatl (for IBM 3494
tape libraries, currently 6.8.3.0), though there are a few exceptions that use tsmscsi. Non-
IBM tape drives and libraries typically use the tsmscsi device driver (at exactly the same
version as the TSM Server version, to 4 digits) that comes packaged with TSM Server and
Storage Agent, though there are a few exceptions that use other device drivers. A non-IBM
library that uses IBM tape drives will typically use tsmscsi for the library and IBMtape for the
drives.
Check the TSM supported device list for which device driver is needed for supported tape
libraries and drives
IBMtape and ibmatl (for IBM 3494 libraries) are available for download at FixCentral here:
Product Group: Storage Systems
Product Family: Tape Systems
Product Type: Tape device drivers and software
 Product: Tape device drivers
Installed Version: 1.0 (default)
Platform Windows

Hit Continue

Browse for fixes (the default)

Hit Continue

Download: IBMtape

Also download:
* IBM Tape Device Drivers Installation and User's Guide
Available under the fixpack

Then go back to FixCentral, and download

* Product: Tape Diagnostic Tool (ITDT)

itdt replaces former ntutil

For IBMtape, run install-exclusive.exe to install IBMtape and assign IBMtape as the
device driver for supported IBM tape libraries and drives.

For tsmscsi, verify that it was installed by checking Windows Add/Remove Programs. To set
the tape devices to use tsmscsi in Windows 2003, from Windows Device Manager, right-click
on the device, select Update Driver -> Install from a list or specific location (Advanced) ->
Don't search. I will select the driver to install -> Select the IBM Tivoli Storage Manager device
driver -> Continue Anyway.
For details, see the TSM Server 5.5 for Windows Administrator's Guide, Ch. 5: "Attaching
Devices to the Server System", Section: "Controlling Devices with the Tivoli Storage
Manager Device Driver on Windows Server 2003"
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmcw.doc/anrwgd55115
.htm#contxpnet

For 6.1 see TSM 6.1 InfoCenter: Configuring -> Configuring and managing server storage ->
Using devices with the server system (Windows) -> Selecting a device driver -> Controlling
devices with the Tivoli Storage Manager device driver
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.doc/t_devices_con
trolling_with_tsm_device_driver_win.html

4) Run tsmdlst to check device names

From a DOS command prompt window, cd C:\Program Files\tivoli\tsm\console, and run:
tsmdlst
You should see output something like the following list current lb and mt #s for the library and
tape devices.
Tivoli Storage Manager -- Device List Utility

Licensed Materials - Property of IBM

5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

Computer Name: ODINTSMA1

OS Version: 5.2
OS Build #: 3790
TSM Device Driver: TSMScsi - Running

One HBA was detected.

Manufacturer Model Driver Version Firmware Description

----------------------------------------------------------------------
LSI Corporation LSI7102XP-LC lsi_fc 1.27.01.00 01.02.27.00LSI 2GB FC 7002
series, Dual or Quad port (w/929X)

TSM Name ID LUN Bus Port SSN WWN TSM Type Device Identifier
----------------------------------------------------------------------
lb0.0.0.2 0 0 0 2 0010c5101f0008002724 21000090A50013A6 LIBRARY
SPECTRA GATOR 0129
mt0.1.0.2 0 1 0 2 0001050056 21000090A50013A6 GENERICTAPESONY SDX-
900V 0103
mt0.2.0.2 0 2 0 2 0001050538 21000090A50013A6 GENERICTAPESONY SDX-
900V 0103

Completed in: 0 days, 0 hours, 0 minutes, 0 seconds.

5) Check TSM Server drives are online:

From a TSM server command line run

 q drive
If drive(s) are not online, update them with:
update drive <libr> <drive> online=yes

6) Check the TSM Server paths are online and using the correct lb or mt #

From a TSM server command line run

q path f=d

If path(s) are not online or are using the wrong device lb or mt #, update them with the
following (if device names are correct, you don't need to include the device parm):
Library:
update path <server> <library> srct=server destt=libr device=<lb#.#.#.#>
online=yes
Tape drive:
update path <server> <drive> srct=server destt=drive libr=<libname>
device=<mt#.#.#.#> online=yes

7) Check for hardware issues from DOS

From a DOS command prompt window, use ntutil (for devices using IBMtape) or lbtest or
mttest (for devices using tsmscis) to test the library or drives.

7a) lbtest, for libraries using tsmscsi

From DOS, run:

lbtest

Go into manual test and open the library

1: Manual test

1: set device special file

Enter device special file name: lb#.#.#.# [enter]
6: open

Get library inventory

8: ioctl return element count
10: ioctl return library inventory

Move a tape from a tape slot to a drive

11: ioctl move medium
transport element address: XX
source address moving from: YY
destination address moving to: ZZ
 Move the tape back to where it came from
11: ioctl move medium
transport element address: XX
source address moving from: ZZ
destination address moving to: XX

Close the device and exit lbtest

7: close
99: return to main menu
9: exit lbtest

Reference: Technote # 1326205: LBTEST - Practical Examples to Test Functionality

7b) mttest, for tape drives using tsmscsi

From DOS, run:
mttest

Go into manual test and open the drive

1: Manual test

1: set device special file

Enter device special file name: mt#.#.#.# [enter]
20: open

Check basic functionality:

22. read
60. write block to "block.out"

Note: You will get an error stating that only 80 bytes could be read out of 1024. This
is normal and can be ignored
Close the device and exit lbtest
21: close
99: return to main menu
9: exit mttest

7c) itdt (or ntutil), for libraries and tape drives using IBMtape

itdt (which replaced ntutil) operates basically the same as lbtest and mttest, except
that you access both the library and the drives from ntutil. When you start, it operates
in Base Mode by default for access to tape drives. Hit 8 to switch to Library Mode.
 List tape device names you can open from either mode with:
88: List registered devices

A good basic test for tape drives in Base Mode is

39: test unit ready

8) Delete and redefine paths, drive, and library, and checkin scratch tapes, then
private

Sometimes deleting and redefining everything works to reconnect TSM Server to the devices
correctly. The following technote gives these steps in detail.

3) TSM Tape Library troubleshooting tips on AIX

Issues with Tivoli Storage Manager Server in AIX connecting to tape libraries and/or
drives can be resolved by doing some basic tasks. The first things to do when
addressing hardware issues are given in the steps below.
1) Does AIX have the correct device driver for the library and/or tape drives?

2) Does AIX list the library and/or tape drives as Available?

If 6.1, does the db2 instance owner account have read/write access?

3) Does TSM list the drives as online?

4) Does TSM list the paths as online and using the correct device name?

5) Can you test the library and/or drives from device utilities in AIX?

6) Does reconfiguring the library and/or drives in AIX and TSM resolve the issue?

1) Verify that AIX has the correct device driver for the library and/or tape drives

IBM tape drives and libraries typically use Atape (currently 11.7.7.0) or atldd (for IBM 3494 tape
libraries, currently 6.8.4.0), though there are a few exceptions that use tsmscsi. Non-IBM tape drives
and libraries typically use the tsmscsi device driver (at exactly the same version as the TSM Server
version, to 4 digits) that comes packaged with TSM Server and Storage Agent, though there are a
few exceptions that use other device drivers. A non-IBM library that uses IBM tape drives will
typically use tsmscsi for the library and IBMtape for the drives.

Check the TSM supported device list for which device driver is needed for supported tape libraries
and drives
Check current versions installed with:

lslpp -l Atape.*
lslpp -l atldd.* (for IBM 3494 libraries)

lslpp -l tivoli.tsm.devices.* (for non-IBM libraries)

Atape and atldd (for IBM 3494 libraries) are available for download at the following ftp site

To install and commit the Atape driver, uninstall the older version:

installp -u Atape.driver

Then install the new vesrion. For example, if you downloaded the file to
/tmp/Atape.11.7.7.0.engr.bin:

installp -acXd /tmp/Atape.11.7.7.0.engr.bin all

Configure the tape device:

cfgmgr -v

(-v is not required but will show where it hangs if it does)

Verify the new devices are Available:

lsdev -Cc tape

For details, see Technote # 1174910: Upgrading Atape device driver in AIX

For details on configuring non-IBM library and/or tape drives to use tsmscsi in AIX, see TSM Server
5.5 for AIX Administrator's Guide, Ch. 5: "Attaching Devices to the Server System", Section:
"Installing and Configuring Device Drivers", Subsections: "Configuring Tivoli Storage Manager
Device Drivers for Autochangers" and "Configuring Tivoli Storage Manager Device Drivers for Tape
or Optical Drives"

2) Verify that AIX lists the library and/or tape drives

From AIX, run:

* For tape devices using Atape or atldd

# lsdev -Cc tape

* For tape devices using tsmscsi

# lsdev -Cc adsm

Tape devices should be listed as Available.

AIX device names:

* Tape drives that use tsmsci*

/dev/mtx (for example: /dev/mt0)

* Tape libraries that use tsmsci*

/dev/lbx (for example: /dev/lb0)

* IBM 3575, 3581, 3583, 3584 libraries

/dev/smcx (for example: /dev/smc0)

* IBM 349X libraries

/dev/lmcpx (for example: dev/lmcp0)

* tsmsci: Tivoli Storage Manager device driver, packaged with TSM Server

Reference: TSM Server 5.5 Administrator's Guide, Ch 5. "Attaching Devices to the Server System",
Section: "Installing and Configuring Device Drivers", Subsection: "Determining Device Special File
Names"
For TSM Server 6.1, does the db2 instance owner account have read/write access?

# ls -l /dev

For example:

# ls -l rmt[0-9]

crw-rw-rwT 1 root system 40,192 Mar 08 14:02 rmt1

crw-rw-rwT 1 root system 40,256 Mar 08 14:02 rmt2

3) Check TSM Server drives are online:

From a TSM server command line run

q drive

If drive(s) are not online, update them with:

update drive online=yes

4) Check the TSM Server paths are online and using the correct device name

From a TSM server command line run

q path f=d

If path(s) are not online or are using the wrong device device name (for example /dev/smc0 or
/dev/rmt0), update them with the following (if device names are correct, you don't need to include the
device parm):

Library (for example, using smc0):

update path srct=server destt=libr device=/dev/smc0 online=yes

Tape drive (for example, using rmt0):

 update path srct=server destt=drive libr= device=/dev/rmt0 online=yes

5) Check for hardware issues from AIX

From an AIX command prompt window, use tapeutil (for devices using IBMtape)
or lbtest or mttest (located in /usr/tivoli/tsm/devices/bin, for devices using tsmsci) to test the library or
drives.

5a) lbtest, for libraries using tsmscsi

From AIX, run:

lbtest

Go into manual test and open the library

1: Manual test

1: set device special file

Enter device special file name:

For example: /dev/smc0 [enter]

6: open

Get library inventory

8: ioctl return element count

10: ioctl return library inventory

Move a tape from a tape slot to a drive

11: ioctl move medium

transport element address: XX

source address moving from: YY

destination address moving to: ZZ

Move the tape back to where it came from

11: ioctl move medium

transport element address: XX

source address moving from: ZZ

destination address moving to: XX

Close the device and exit lbtest

7: close

99: return to main menu

9: exit lbtest

Reference: Technote # 1326205: LBTEST - Practical Examples to Test Functionality

http://www-01.ibm.com/support/docview.wss?uid=swg21326205

5b) mttest, for tape drives using tsmscsi

From AIX, run:

mttest

Go into manual test and open the drive

1: Manual test

1: set device special file

Enter device special file name:

For example: /dev/rmt0 [enter]

20: open

Check basic functionality:

22. read

60. write block to "block.out"

Note: You will get an error stating that only 80 bytes could be read out of 1024. This is normal and
can be ignored

Close the device and exit mttest

21: close

99: return to main menu

9: exit mttest

5c) tapeutil, for libraries and tape drives using IBMtape

tapeutil operates basically the same as lbtest and mttest, except that you access both the library and
the drives from tapeutil.

A good basic test for tape drives in Base Mode is

6: test unit ready

6) Delete and redefine paths, drive, and library, and checkin scratch tapes, then private

Sometimes deleting and redefining everything works to reconnect TSM Server to the devices
correctly. The following technote gives these steps in detail.