TSM 7.1 Recovery

BDMcGrew

ADSM.ORG Member
Joined
Mar 9, 2015
Messages
74
Reaction score
1
Points
0
PREDATAR Control23

Good morning,

I'm running TSM 7.1 on CentOS 6 I had a total brain fart and corrupted the / partition and have to reinstall. But, /opt where TSM is installed, /export/home/tsmadmin where the user lives and /tsm where all my databases, log and volumes live are safe. I've found lots of howto's on recovering from a full off-site backup, etc., but I don't think I need to go that far.

I _think I should just have to reinstall enough TSM to replace any kernel modules or /usr files but I'm not sure sure? Can anyone offer any advice here? My primary stg is disk and tape and then off-site DR is tape. Since all the local disk media is still safe I'm hoping for some kind of in-place recovery and not have to go pull all the DR volumes out of the vault.

thanks,

-b
 
PREDATAR Control23

I have been in this situation and the only way to get TSM back up 'clean' is to reinstall TSM and restore from your last good backup.

Sorry, shortcuts may not give you back a clean environment.
 
PREDATAR Control23

Right, so I just reinstalled from scratch and will be installing TSM shortly. I do have volhist and devconf thankfully.

The disk volume (/tsm) where the database and bfs files live is still in tact. My database backups are off-site. Will I need to get them back or will what's on disk get me a recovery? I do not have a .dbv backup on disk.

Can someone point me to the howto on recovering the server from scratch? I've found lots of howtos' on restoring the database but that assumes a functional TSM install.

thanks,
 
PREDATAR Control23

The basic rundown:

1. reinstall the same version of TSM
2. create the same instance and owner as the previous corrupted version - same DB and LOG volumes should be created

At this point you have a functional TSM BUT with no data

3. restore the DB from the backup - see this
4. login to the restored TSM and recreate the old environment from what you already have
 
PREDATAR Control23

I'm well on my way but oh boy have I found something weird and not really finding any help in the Google either.

TSM is finding the DBB volume but then mounting the tape from the day before.

Vol: PEY423L4 - 12/03/2015
Vol: PEY420L4 - 12/02/2015
Vol: PEY405L4 - 12/01/2015

So it found and knew PEY423L4 was required but mounted PEY420L4.
I tried todate=-1, it found and knew PEY420L4 was required but mounted PEY405L4.
I then tried todate=-2, it found and knew PEY405L4 was required but tried to mount a missing PEY410L4.

Like it's finding the requested volume but mounting the wrong volume from the previous full dbb.

Code:
root@tsm32 drm]# dsmserv -u admin -i /export/home/tsm32/admin/tsminst1 restore db
ANR7800I DSMSERV generated at 10:21:12 on May 29 2015.

Tivoli Storage Manager for Linux/x86_64

Version 7, Release 1, Level 1.300


Licensed Materials - Property of IBM


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


ANR7801I Subsystem process ID is 8236.
ANR0900I Processing options file /export/home/tsm32/admin/tsminst1/dsmserv.opt.ANR7814I Using instance directory /export/home/tsm32/admin/tsminst1.
ANR4726I The ICC support module has been loaded.
ANR1636W The server machine GUID changed: old value (), new value (c4.42.14.32-
.cc.9a.e5.11.bc.8f.00.30.48.f4.11.a8).
ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
1500.
ANR0478W Session request refused. Server is running in standalone mode.
ANR4636I Starting roll-forward database restore.
ANR4591I Selected backup series 14 from 12/03/15 and 05:49:15 as best candidate
available for restore database processing.
ANR8955I Drive DRIVE1 in library TL4000 with serial number  is updated with the
newly discovered serial number 1310018374.
ANR8955I Drive DRIVE2 in library TL4000 with serial number  is updated with the
newly discovered serial number 1310015998.
ANR4592I Restore database backup series 14 includes eligible operation 0 with
volume PEY420L4 having sequence 100001 and using device class LTOTAPE.
ANR4598I Validating database backup information for selected backup series 14
and operation 0 using volume PEY420L4.
ANR8356E Incorrect volume PEY405L4 was mounted instead of volume PEY420L4 in
library TL4000.
 
PREDATAR Control23

So, my weekend recap! I'm really hoping someone out here Monday will have some insights!

Who'd have guessed the comments in the devconf for the tapes were actually used. Not me! After getting all the right tapes in all the right slots the restore was underway. But now it's hanging up in another way.

I have 5 DBB tapes from the last week. Of course they get incrementally larger as the week moves on but I've tried all of them and it seems like the restore gets to the end of the volume (~32GB) and hangs up with a read error. Almost like it's choking on an EOF marker or something (yes, old school Unix). This happens on all 5 DBB volumes. Sadly, I do not have any DBV volumes backed up on disk (that will change).

I feel reasonably confident it's not a hardware problem, but... here’s what I’ve done so far in troubleshooting:

1) Ran hardware diagnostics on the server and all have passed.
2) Ran memory test on the server and all has passed.
3) Ran diagnostics on the library and passed.
4) Ran an old school Unix tar write/read operation of 100GB file to brand new tape using /dev/IBMtape0 and IBMtape1 and was successful.
5) Set vm.dirty_background_radtio = 5 and vm.dirty_ratio = 10 in /etc/sysctl.conf (as was a recommendation in a DB2 forum).
6) I'm using the exact same version of Linux, TSM, lin_tape, lin_taped and the QLogic drivers.

It doesn't matter which drive is being used either, the failure is the exact same on either DRIVE1 or DRIVE2.

My controller is a QLogic HPAE312A (qua2xxx) ISP2432 PCI-e 4gb Dual Port controller connected directly to both ports of the library.
TSM is 7.1.1.300 Linux x86_64
Linux is CentOS 6.7 - 2.6.32-573.8.1.el6_x86_64
System drive is a 128GB SSD
TSM Drive is a 4TB Seagate
Library is a Dell TL4000 with 2xIBM LTO3 drives (all have latest firmware)

Again, thanks for any and all help! I'm at a complete loss and going on the 3rd day of bieng down.

-brian

and, a whole bunch of debug in case it helps anyone (volhist and devconf at the bottom)

Code:
[root@tsm32 drm]# cat /export/home/tsm32/admin/tsminst1/dsmserv.opt
* --------------------------------------------------------------- *
* This file was created by the TSM Instance Configuration Utility *
* --------------------------------------------------------------- *

COMMMethod     TCPIP
TCPPort       1500

DEVCONFIG     /tsm/drm/devconf.out
VOLUMEHISTORY     /tsm/drm/volhist.out
TCPADMINPort 1500

ACTIVELOGDirectory   /tsm/actlog
ARCHLOGDirectory   /tsm/archlog

NOMIGRRECL
DISABLESCHED YES
EXPINT 0

[root@tsm32 tsm]# dsmserv -u admin -i /export/home/tsm32/admin/tsminst1 restore db
ANR7800I DSMSERV generated at 10:21:12 on May 29 2015.

Tivoli Storage Manager for Linux/x86_64

Version 7, Release 1, Level 1.300


Licensed Materials - Property of IBM


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


ANR7801I Subsystem process ID is 3814.
ANR0900I Processing options file /export/home/tsm32/admin/tsminst1/dsmserv.opt.ANR7814I Using instance directory /export/home/tsm32/admin/tsminst1.
ANR4726I The ICC support module has been loaded.
ANR1636W The server machine GUID changed: old value (), new value (c4.42.14.32-
.cc.9a.e5.11.bc.8f.00.30.48.f4.11.a8).
ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
1500.
ANR0152I Database manager successfully started.
ANR4636I Starting roll-forward database restore.
ANR4591I Selected backup series 13 from 12/02/15 and 14:34:06 as best candidate
available for restore database processing.
ANR8955I Drive DRIVE1 in library TL4000 with serial number  is updated with the
newly discovered serial number 1310018374.
ANR8955I Drive DRIVE2 in library TL4000 with serial number  is updated with the
newly discovered serial number 1310015998.
ANR4592I Restore database backup series 13 includes eligible operation 0 with
volume PEY416L4 having sequence 100001 and using device class LTOTAPE.
ANR4598I Validating database backup information for selected backup series 13
and operation 0 using volume PEY416L4.
ANR8337I LTO volume PEY416L4 mounted in drive DRIVE1 (/dev/IBMtape0).
ANR1363I Input volume PEY416L4 opened (sequence number 1).
ANR4609I Restore database process found FULL database backup timestamp
20151202143406 from database backup media.
ANR1364I Input volume PEY416L4 closed.
ANR3008I Database backup was written using client API: 6.4.0.0.
ANR4638I Restore of backup series 13 operation 0 in progress.
ANR4897I Database restore of operation 0 will use device class LTOTAPE and
attempt to use 1 streams.
ANR0406I Session 8 started for node $$_TSMDBMGR_$$ (DB2/LINUXX8664) (Tcp/Ip
localhost(34403)).
ANR8468I LTO volume PEY416L4 dismounted from drive DRIVE1 (/dev/IBMtape0) in
library TL4000.
ANR8337I LTO volume PEY416L4 mounted in drive DRIVE2 (/dev/IBMtape1).
ANR0510I Session 8 opened input volume PEY416L4.
ANR1363I Input volume PEY416L4 opened (sequence number 1).
ANR4912I Database  Restore DB in progress and total bytes transferred
67,108,864.
===[ Clip: no errors during 32GB of Restore ]===
ANR4912I Database  Restore DB in progress and total bytes transferred
32,480,690,176.
===[ After an hour of waiting while the drive said "seeking" ]===
ANR8311E An I/O error occurred while accessing drive DRIVE2 (/dev/IBMtape1) for
READ operation, errno = 5, rc = 2863.
ANR0541W Retrieve or restore failed for session 8 for node $$_TSMDBMGR_$$
(DB2/LINUXX8664) - error on input storage device.
ANR0403I Session 8 ended for node $$_TSMDBMGR_$$ (DB2/LINUXX8664).
ANR2971E Database backup/restore/rollforward terminated - DB2 sqlcode -2025
error.

[root@tsm32 log]# cat /var/log/lin_tape.errorlog
===[ Nothing here until the failure occurs ]===
---------------------------------------------------------------------
IBMtape1-----15998  Sun Dec  6 13:12:17 2015
   Scsi Path   :  07 00 00 00
   CDB Command :  08 02 04 00 00 00
   Status Code :  06 00 00 00
   Description :

[root@tsm32 log]# more drmserv.syslog.txt
Dec  6 12:42:38 tsm32 kernel: INFO: task dsmserv:4132 blocked for more than 120 seconds.
Dec  6 12:42:38 tsm32 kernel:  Tainted: G  -- ------------  T 2.6.32-573.8.1.el6.x86_64 #1
Dec  6 12:42:38 tsm32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec  6 12:42:38 tsm32 kernel: dsmserv  D ffff88023a0a79d8  0  4132  3569 0x10000080
Dec  6 12:42:38 tsm32 kernel: ffff88023a0a78f8 0000000000000082 0000000000000554 ffff880513dfac00
Dec  6 12:42:38 tsm32 kernel: ffff88053ac4d000 0000000000000246 ffff88023a0a78f8 ffffffffa008240d
Dec  6 12:42:38 tsm32 kernel: ffff8805367119c0 ffff880513dfac00 ffff880239ab7068 ffff88023a0a7fd8
Dec  6 12:42:38 tsm32 kernel: Call Trace:
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa008240d>] ? qla24xx_start_scsi+0x5ad/0x6a0 [qla2xxx]
Dec  6 12:42:38 tsm32 kernel: [<ffffffff81539455>] schedule_timeout+0x215/0x2e0
Dec  6 12:42:38 tsm32 kernel: [<ffffffff81291fb7>] ? kobject_put+0x27/0x60
Dec  6 12:42:38 tsm32 kernel: [<ffffffff815390d3>] wait_for_common+0x123/0x180
Dec  6 12:42:38 tsm32 kernel: [<ffffffff810672b0>] ? default_wake_function+0x0/0x20
Dec  6 12:42:38 tsm32 kernel: [<ffffffff815391ed>] wait_for_completion+0x1d/0x20
Dec  6 12:42:38 tsm32 kernel: [<ffffffff8127b6dc>] blk_execute_rq+0x8c/0xf0
Dec  6 12:42:38 tsm32 kernel: [<ffffffff8127b420>] ? blk_rq_map_user+0x1a0/0x280
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa0349d18>] lin_tape_blk_rq+0x138/0x570 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa034a19a>] tape_execute_scsi_command+0x4a/0xc0 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa0349112>] ? tape_log_cdb+0x32/0x110 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa034f5bf>] tape_send_scsi_io+0x1ff/0x4a0 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffff8114e012>] ? follow_page+0x412/0x500
Dec  6 12:42:38 tsm32 kernel: [<ffffffff811533c0>] ? __get_user_pages+0x110/0x430
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa034f8db>] tape_send_scsi_cmd+0x7b/0x2d0 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa03384c7>] lin_tape_perform_read+0xf7/0x200 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa033881d>] lin_tape_drive_read+0x24d/0x440 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffffa032df4c>] lin_tape_read+0x1dc/0x300 [lin_tape]
Dec  6 12:42:38 tsm32 kernel: [<ffffffff811921f5>] vfs_read+0xb5/0x1a0
Dec  6 12:42:38 tsm32 kernel: [<ffffffff81192fa6>] ? fget_light_pos+0x16/0x50
Dec  6 12:42:38 tsm32 kernel: [<ffffffff81192541>] sys_read+0x51/0xb0
Dec  6 12:42:38 tsm32 kernel: [<ffffffff8100b2e8>] tracesys+0xd9/0xde

[root@tsm32 drm]# cat volhist.out
*********************************************************************************************************
*
*  Sequential Volume Usage History
*  Updated 12/03/2015 10:35:07 AM
*
*********************************************************************************************************
Operation Date/Time:  2015/11/28 20:58:30
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000BF.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/11/30 15:21:04
Volume Type:  BACKUPFULL
* Location for volume PEY402L4 is: 'VAULT'
Volume Name:  "PEY402L4"
Backup Series:  11
Backup Op:  0
Volume Seq:  100001
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/11/30 21:11:33
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000CE.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/01 01:08:57
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000CF.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/01 04:23:19
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000D0.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/01 12:57:27
Volume Type:  STGDELETE
Volume Name:  "/tsm/vol1/000000D0.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/01 13:02:51
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000D1.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/01 14:20:16
Volume Type:  BACKUPFULL
* Location for volume PEY406L4 is: 'VAULT'
Volume Name:  "PEY406L4"
Backup Series:  12
Backup Op:  0
Volume Seq:  100001
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/01 17:01:51
Volume Type:  STGNEW
Volume Name:  "PEY420L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/01 17:54:23
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000D5.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/02 09:06:02
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000D6.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/02 14:07:44
Volume Type:  STGDELETE
Volume Name:  "PEY405L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/02 14:07:44
Volume Type:  STGDELETE
Volume Name:  "PEY416L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/02 14:10:25
Volume Type:  STGNEW
Volume Name:  "PEY405L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/02 14:34:06
Volume Type:  BACKUPFULL
* Location for volume PEY416L4 is: 'VAULT'
Volume Name:  "PEY416L4"
Backup Series:  13
Backup Op:  0
Volume Seq:  100001
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/02 16:38:20
Volume Type:  STGNEW
Volume Name:  "PEY421L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/02 17:41:15
Volume Type:  STGDELETE
Volume Name:  "PEY420L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/02 20:50:04
Volume Type:  STGNEW
Volume Name:  "/tsm/vol1/000000DB.BFS"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  FILEDEV
**************************************************
Operation Date/Time:  2015/12/03 05:49:15
Volume Type:  BACKUPFULL
* Location for volume PEY420L4 is: ''
Volume Name:  "PEY420L4"
Backup Series:  14
Backup Op:  0
Volume Seq:  100001
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/03 09:39:22
Volume Type:  STGNEW
Volume Name:  "PEY422L4"
Backup Series:  0
Backup Op:  0
Volume Seq:  0
  Device Class Name:  LTOTAPE
**************************************************
Operation Date/Time:  2015/12/03 10:24:01
Volume Type:  BACKUPFULL
Volume Name:  "PEY423L4"
Backup Series:  15
Backup Op:  0
Volume Seq:  100001
  Device Class Name:  LTOTAPE
**************************************************

[root@tsm32 drm]# cat devconf.out
/* Device Configuration */
DEFINE DEVCLASS FILEDEV DEVT=FILE FORMAT=DRIVE MAXCAP=67108864K MOUNTL=32 DIR=/tsm/vol1 SHARE=NO
DEFINE DEVCLASS LTOTAPE DEVT=LTO FORMAT=DRIVE MOUNTL=DRIVES MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=TL4000 WORM=NO DRIVEENCRYPTION=ALLOW LBPROTECT=NO
DEFINE SERVER TSM14 COMMMETHOD=TCPIP HLADDRESS=192.168.0.14 LLADDRESS=1860  NODENAME=TSM32 PASSWORD=21fb76792cc8b3f025ab46468dc8a73b9f  SERVERPASSWORD=21fb76792cc8b3f025ab46468dc8a73b9f
SET SERVERNAME TSM32
SET SERVERPASSWORD 216eba07da71bcadac0ff905e6f7139d14
DEFINE LIBRARY TL4000 LIBTYPE=SCSI SERIAL="00X4U78C4795_LL0" SHARED=NO AUTOLABEL=NO RESETDRIVE=NO
DEFINE DRIVE TL4000 DRIVE1 ELEMENT=257 ONLINE=Yes WWN="2007000E1110D9FF" SERIAL="1310018374"
DEFINE DRIVE TL4000 DRIVE2 ELEMENT=256 ONLINE=Yes WWN="2001000E1110D9FF" SERIAL="1310015998"
/* LIBRARYINVENTORY SCSI TL4000 PEY400L4 4116 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY401L4 4124 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY402L4 4128 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY403L4 4106 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY404L4 4103 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY405L4 4098 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY406L4 4129 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY407L4 4112 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY408L4 4137 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY409L4 4110 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY410L4 4096 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY411L4 4097 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY412L4 4105 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY413L4 4099 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY414L4 4109 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY415L4 4113 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY416L4 4104 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY417L4 4108 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY418L4 4102 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY419L4 4120 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY420L4 4107 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY421L4 4100 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY422L4 4101 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY423L4 4111 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY424L4 4136 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY425L4 4133 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY426L4 4119 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY427L4 4123 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY428L4 4127 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY429L4 4131 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY430L4 4121 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY431L4 4117 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY432L4 4138 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY433L4 4134 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY434L4 4130 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY435L4 4126 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY436L4 4122 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY437L4 4118 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY438L4 4139 101*/
/* LIBRARYINVENTORY SCSI TL4000 PEY439L4 4135 101*/
DEFINE PATH TSM32 TL4000 SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/IBMchanger0 ONLINE=YES
DEFINE PATH TSM32 DRIVE1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=TL4000 DEVICE=/dev/IBMtape0 ONLINE=YES
DEFINE PATH TSM32 DRIVE2 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=TL4000 DEVICE=/dev/IBMtape1 ONLINE=YES
SERVERBACKUPNODEID 1
 
PREDATAR Control23

Success! It's fixed, back online!

Turns out I have 1 drive that is questionable. Unix tar was perfectly happy writing and reading that drive but TSM is not for whatever reason. And, I had not created udev rules so there was added confusion since the element numbers didn't match the drive I thought it was pointing to.

I'd resigned myself to starting over so I pulled all my drives and media out and loaded up fresh hard drives and tapes. As a precaution after running the instance configuration I did a full DBB to disk and to tape and ensured I could restore both. Of course disk restore fine but tape in "DRIVE2" failed. A friend who's a TSM Engineer suggested removing the drive the kept failing from deconf and tryin again and sure enough, it worked.

Put my old drives and tapes back in, eliminate the bad drive, write the udev rules so device names and element numbers match up and quickly restored the previous database with no problems and after all that, I'm back up running and receiving data again.

A major relief!

-brian
 
Top