Unable to restore TSM Db to new server - ANR4596E

Status
Not open for further replies.

fredric

ADSM.ORG Member
Joined
Aug 23, 2007
Messages
52
Reaction score
1
Points
0
I want to restore the tsm db to another aix server.
Server A: backup db type=full devc=FILE_NAS
Server B: dsmserv restore db (after definning FILE_NAS and setting "set dbrecovery FILE_NAS)

See output below:

ANR0152I Database manager successfully started.
ANR4636I Starting roll-forward database restore.
ANR4591I Selected backup series 501 from 01/29/13 and 09:11:29 as best
candidate available for restore database processing.
ANR4592I Restore database backup series 501 includes eligible operation 0 with
volume /inst/tsm/db/59447091.DBV having sequence 1 and using device class
FILE_NAS.
ANR4592I Restore database backup series 501 includes eligible operation 0 with
volume /inst/tsm/db/59448400.DBV having sequence 2 and using device class
FILE_NAS.
ANR4596E Restore database is unable to validate the selected database backup
for series 501 and operation 0 against the actual data from the database backup
stream.
ANR4602E No volumes found for TODATE 01/29/13 10:34:08.

I have searched after help, but haven't find any that can help me solve the problem.

Server A: TSM server version 6.2.1.0 (aix 5.3)
Server B: TSM server version 6.3.3 (aix 7.1)

I was told that I can perform a restore to the new version directly, but it's mayby false.

Thanks!

//Fredric
 
Hi
If you are trying to restore TSM DB in most current state so you need 3 components: volume history, device configuration files and recovery logs.
Because you're restore TSM DB to the other server, use point-in-time method by adding parameter TODATE (see volhistory file for identify correct date and use MM/DD/YYYY syntax).
Efim
 
I tried to restore with TODATE but get the same error.

root@tsmtstsrv01# dsmserv restore db todate=01/30/2013
ANR7800I DSMSERV generated at 15:56:46 on Oct 19 2012.
Tivoli Storage Manager for AIX
Version 6, Release 3, Level 3.000

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2011.
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 9961648.
ANR0900I Processing options file /tsm/tsminst1/dsmserv.opt.
ANR7811I Using instance directory /tsm/tsminst1.
ANR4726I The ICC support module has been loaded.

ANR1636W The server machine GUID changed: old value (), new value (7f.4c.4a.ae-
.66.3c.11.e2.8b.49.4e.11.80.38.c9.02).
ANR8200I TCP/IP Version 4 driver ready for connection with clients on port
1500.
ANR4634I Starting point-in-time database restore to date 01/30/13 23:59:59.
ANR4591I Selected backup series 505 from 01/30/13 and 10:21:59 as best
candidate available for restore database processing.
ANR4592I Restore database backup series 505 includes eligible operation 0 with
volume /inst/tsm/db/59537721.DBV having sequence 1 and using device class
FILE_NAS.
ANR4592I Restore database backup series 505 includes eligible operation 0 with
volume /inst/tsm/db/59538933.DBV having sequence 2 and using device class
FILE_NAS.
ANR4596E Restore database is unable to validate the selected database backup
for series 505 and operation 0 against the actual data from the database backup
stream.
ANR4602E No volumes found for TODATE 01/30/13 23:59:59.
root@tsmtstsrv01#
root@tsmtstsrv01#
 
Hi
Try restore again using instance user account (not root)
Double check permission to the folders and files.
Efim
 
Hi,
thanks for the reply, but I'm getting exactly the same result with the tsminst1 user (owner of the instance and full access to the backup files).

//Fredric
 
Check dsmserv.opt. You must have only one volhistory file during restore.
Please show dsmserv.opt and volhistory files.
Efim
 
Hi,
below is the dsmserv.opt (removed all outcomment lines) and volhist.out. There are some parameters that are heritage from the old tsm server.

root@tsmtstsrv01# grep -v "*" /tsm/tsminst1/dsmserv.opt
COMMmethod TCPIP
SELFTUNEBUFpoolsize yes
COMMTIMEOUT 7800
IDLETIMEOUT 300
EXPInterval 1
VOLUMEHISTORY /tsm/volhist.out
DEVCONFIG /tsm/devconfig.out
MOVEBATCHSIZE 512
EXPINTERVAL 0
MAXSESSIONS 200
TXNGROUPMAX 65000
BUFPOOLSIZE 768000
ACTIVELOGSIZE 32768
ACTIVELOGSize 8192
ACTIVELOGDirectory /tsmlog01
ARCHLOGDirectory /tsmarchlog
root@tsmtstsrv01#



root@tsmtstsrv01# cat /tsm/volhist.out
*********************************************************************************************************
*
* Sequential Volume Usage History
* Updated 01/30/13 10:48:35
*
*********************************************************************************************************
Operation Date/Time: 2013/01/30 10:21:59
Volume Type: BACKUPFULL
* Location for volume /inst/tsm/db/59537721.DBV is: ''
Database Backup LLA: FULL_BACKUP.20130130102159.1
Database Backup HLA: /NODE0000/
Volume Name: "/inst/tsm/db/59537721.DBV"
Backup Series: 505
Backup Op: 0
Volume Seq: 1
Device Class Name: FILE_NAS
Database Backup ID: 0 ,804890798
Database Backup Home Position: 0
Database Backup Total Data Bytes : 21 ,1045684235
Database Backup Total Log Bytes: 0 ,1443213323
Database Backup Log Block Number: -1 , -1
**************************************************
Operation Date/Time: 2013/01/30 10:21:59
Volume Type: BACKUPFULL
* Location for volume /inst/tsm/db/59538933.DBV is: ''
Database Backup LLA: FULL_BACKUP.20130130102159.2
Database Backup HLA: /NODE0000/
Volume Name: "/inst/tsm/db/59538933.DBV"
Backup Series: 505
Backup Op: 0
Volume Seq: 2
Device Class Name: FILE_NAS
Database Backup ID: 0 ,804890874
Database Backup Home Position: 0
Database Backup Total Data Bytes : 21 ,1045684235
Database Backup Total Log Bytes: 0 ,1443213323
Database Backup Log Block Number: -1 , -1
**************************************************
root@tsmtstsrv01#
 
Fredric rightly said that the volhistory file format changed from v.6.3.
I missed that the recovery is running on different versions of TSM.
This is unsupported. See character "Moving the Tivoli Storage Manager server to another system" in Administration Guide. - The restore operation must be done by a TSM server at a code level that is the same a that on the server that was backed up.
Efim
 
Hi,

thanks for your replies. I will try to restore to another version. But I will run the new TSM server on a AIX 7.1 and it only supported from 6.2.2. My source system runs 6.2.1. But I think it would work to restore to 6.2.2.
I will let you know.
 
I uninstalled v6.3.3 and installed 6.2.2 instead (6.2.1 not supported by AIX 7.1). I worked well, I was able to restore the backup from the 6.2.1 system. After that, it was a easy to upgrade to 6.3.3 :)

Thanks!

//Fredric
 
Status
Not open for further replies.
Back
Top