Error of startup after successful DB restore

After a successful restore, the server does not come up. Both the
production and DR servers are at the same level, but I get this errors
on
startup:

[tsmserv2] /usr/tivoli/tsm/server/bin # dsmserv
ANR0000W Message repository for language AMENG does not match program
level.
ANR0000I Message repository's compile date: Tue Dec 16 08:49:40 2003
ANR0000I Program's message timestamp:       Tue Jun 10 01:10:49 2003
ANR7800I DSMSERV generated at 10:00:19 on Jun 13 2003.

Tivoli Storage Manager for AIX-RS/6000
Version 5, Release 2, Level 0.0

Licensed Materials - Property of IBM

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

ANR0900I Processing options file dsmserv.opt.
ANR7811I Direct I/O will be used for all eligible disk files.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 1960 megabytes.
ANR0201I Database assigned capacity is 12784 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR0354I Recovery log redo pass in progress.
ANR0355I Recovery log undo pass in progress.
ANR0352I Transaction recovery complete.
ANR1635I The server machine GUID,
d3.a8.5c.1a.63.e7.11.d9.8a.13.08.63.ac.1e.03
.4f, has initialized.
ANR9999D tb.c(799): ThreadId<0> Column count mismatch for table Nodes -
expect
ed 48, found 50
ANR0101E adminit.c(1112): Error 18 opening table "Nodes".
[tsmserv2] /usr/tivoli/tsm/server/bin #

Any suggestions?




>>> mark.stapleton AT BERBEE DOT COM 01/28/2005 10:56:42 AM >>>
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of Lawrence Clark
>We have set up a backup TSM server for DR purposes.
>TSM has been installed to the same level and a database
>created of a size larger than the production TSM database, all
>DB volumes are formatted.
>
>On the production  side, the database is backed up to disk.
>This is then copied over to a 2nd AIX server...now the backup
>TSM server.
>
>Looking in the manual, it appears the database restore assumes
>the files will be on a cartridge.
>
>Questions:
>- should the server be down to restore the database?
>- what is the format of the command in an AIX environment to
>restore the db if the files are under /var/tsmdbbk/morning as so:
>-rw-------   1 root     sys      9663676416 Jan 28 04:08 06902830.dbb
>-rw-------   1 root     sys      2981181842 Jan 28 04:11 06903334.dbb

Yes, the server must be down, and no, the backup(s) don't have to be
on
a cartridge.

Assuming that there are intact and update volume history and device
configuration files, the command is basically

  dsmserv restore db todate=today source=dbbackup

If the volume history file is not present, the commands would be

  dsmserv restore db devc=<file_device_class>
    vol=/var/tsmdbbk/morning/06902830.dbb

followed by

  dsmserv restore db devc=<file_device_class>
    vol=/var/tsmdbbk/morning/06903334.dbb commit=yes

(All commands assume that you have a device configuration file
present,
and in the directory that your dsmserv.opt file points at.) The
<file_device_class> is the same devclass that you use to run the db
backups. Don't forget the commit flag for the last volume. If you
don't
put that in, you'll get to do the entire restore again.

--
Mark Stapleton (stapleton AT berbee DOT com)
Berbee Information Networks
Office 262.521.5627