TSM 6.2.2.30 migration redhat x86 to AIX power8

[Houssam]

i'm having issues with migrating tsm server, i'm using backup restore db methode, when i start the restore with dsmserv restore db, i have this error in the trace file:

icPrepareRespVerb : snapshot is 0 and fileclass is DB_DC
This is either tape class but not log volume or file class

in the devconf the class is clearly a file type, i made the files transfert (backupdb, volhist, devconf, dsmserv.opt ... etc)using tools like mobaXtrem or winscp, with my windows machine


devconf
/* Device Configuration */
DEFINE DEVCLASS DB_DC DEVT=FILE MAXCAP=10485760K MOUNTL=20 DIR=/tsm/stgpool/DBBACKUP SHARE=NO
SERVERPASSWORD=216c8e09095399404a7c12219df41929c7*/
SET SERVERNAME TSM_PROD
SET SERVERPASSWORD 21de0530403033885470010d27b6a8c

SERVERBACKUPNODEID 1



volhist

**************************************************
Operation Date/Time: 2016/11/28 07:14:19
Volume Type: BACKUPFULL
* Location for volume /tsm/stgpool/DBBACKUP/80313660.dbv is: ''
Database Backup LLA: FULL_BACKUP.20161128071419.1
Database Backup HLA: /NODE0000/
Volume Name: "/tsm/stgpool/DBBACKUP/80313660.dbv"
Backup Series: 1710
Backup Op: 0
Volume Seq: 1
Device Class Name: DB_DC
Database Backup ID: 0 ,24593664
Database Backup Home Position: 0
Database Backup Total Data Bytes : 1 , 286334987
Database Backup Total Log Bytes: 0 , 117489675
Database Backup Log Block Number: -1 , -1
**************************************************

16:01:46.695 [1][rdbicut.c][1204][SearchString]:token Device Class Name: =DB_DC
16:01:46.695 [1][rdbicut.c][1056][SearchString]atabase Backup ID: =0
16:01:46.695 [1][rdbicut.c][1081][SearchString]atabase Backup ID: =24593664
16:01:46.695 [1][rdbicut.c][1112][SearchString]atabase Backup Home Position:=0
16:01:46.695 [1][rdbicut.c][1056][SearchString]atabase Backup Total Data Bytes : =1
16:01:46.695 [1][rdbicut.c][1081][SearchString]atabase Backup Total Data Bytes : =286334987
16:01:46.695 [1][rdbicut.c][1056][SearchString]atabase Backup Total Log Bytes: =0
16:01:46.696 [1][rdbicut.c][1081][SearchString]atabase Backup Total Log Bytes: =117489675
16:01:46.696 [1][rdbicut.c][1063][SearchString]:Something is wrong. Can not find Database Backup Log Block Number: .
16:01:46.696 [1][rdbicut.c][924][RdbIcGetBackupVolume]:No log block number found. This may be ok.
16:01:46.696 [1][rdbicut.c][1001][SearchString]:Something is wrong. EOF on volhist file.
16:01:46.696 [1][rdbicut.c][941][RdbIcGetBackupVolume]:Total number of FULL backup volume found for RESTORE is 1
16:01:46.696 [1][rdbicrst.c][1090][RdbAdmRestoreDB]:Item found in volume history file is 1.
16:01:46.696 [1][pvropts.c][396][pvrProcessDevconfig]rocessing DevConfig file, searching for devclass DB_DC
16:01:46.696 [1][pvropts.c][1384][ProcessDevClass]rocessing DEFINE DEVCLASS command - searching for device class DB_DC.
16:01:46.696 [1][pvrclass.c][856][pvrParseDefineDevClass]arsing DEFINE DEVCLASS (1).
16:01:46.696 [1][pvr.c][5776][PvrValidateAttribs]:validating attribs for devType=2
16:01:46.697 [1][pvr.c][5798][PvrValidateAttribs]:validateAttribs return 0.
16:01:46.697 [1][pvrclass.c][3244][pvrDefineDevClass]efining device class DB_DC (1).
16:01:46.697 [1][pvrclass.c][3263][pvrDefineDevClass]efining device class devType (2).
16:01:46.697 [1][pvrclass.c][3301][pvrEndDefineDevClass]:End Define for device class 1, committed = 1.
16:01:46.697 [1][pvrclass.c][3338][pvrEndDefineDevClass]evice class 1 is only compatible with itself.
16:01:46.697 [1][psfile.c][1461][psRemoveLogFile]:Attempt to remove .LOG files in directory /tsmarchlogfailover/RstDbLog
16:01:46.697 [1][icrest.c][190][icPrepareRespVerb]:icPrepareRespVerb : snapshot is 0 and fileclass is DB_DC
16:01:46.697 [1][icrest.c][449][icPrepareRespVerb]:This is either tape class but not log volume or file class
16:01:46.698 [1][mmslib.c][6874][MmsTestLibtype]:Testing for existence of library .

 

[marclant]

Different endianness, you will need to migrate instead of restore.

Here is the procedure:
https://www.ibm.com/developerworks/...b3e&file=5d444a6d-651a-482e-b687-2fcd87e7f1ce

 

[Houssam]

Thanks for the answer, how can i migrate then, i already read the procedure.
Can the migration be performed with extract and incert db??

 

[marclant]

Can the migration be performed with extract and incert db??

Yes, that's what Page 2 says. You have to follow that procedure.

 

[Houssam]

Thank you, I'll update tomorrow this thread.

 

[Houssam]

tried to test on aix machine the extract db : nohup /opt/tivoli/tsm/server/bin/dsmserv extractdb, seems that the command is not recognized as it tells in extract.out
Invalid server operating mode specified - EXTRACTDB.
i'm not sure if extractdb is possible in 6.2.2.3, and the upgrade util dsmupgrd is only available for TSM 5.

 

[Houssam]

for more détails this is the command i used :
nohup /opt/tivoli/tsm/server/bin/dsmserv extractdb \hladdress=localipadress lladdress=1500 >extract.out 2>&1 &

 

[marclant]

You are at 6.2.2.3.



Apply the latest 6.2.x fix pack. Or better yet, apply the latest 6.3.x fixpack if your Linux distribution supports it. This way, if you run into problems, you can get support. At 6.2, you are not supported. Once your version meets the requirements for the migration, retry.

 

[Houssam]

thanks a lot, i noticed that this morning, i'm trying to get the customer to upgrade his server, one more question : in the procedure they are talking about migrating from aix to linux x86_64, but i'm doing the other way, it means that i want to migrate from linux x86_64 to aix on power, do i have to upgrade to 6.2.5 or 7.1.5 ? i'm a bit confused.

 

[marclant]

but i'm doing the other way, it means that i want to migrate from linux x86_64 to aix on power

Looks like the procedure is only for the other way around. I don't know if it will work or not. Since you are moving to a new server, there is no harm in trying because the source server is not being modified.

You can play it safe and upgrade the Linux box to 7.1.7 before attempting the procedure, it's always safer to be at a current release in case there were APARs that are now fixed with the extractdb utility.

 

[Houssam]

dear marclant,

thanks for your response, i got this working by bypassing tsm and doing a pure db2 migration, the solution was to :

1- make : db2move tsmdb1 export
2- this will create table files of all the db2 database
3- copy the files in binary mode to the new tsm server using the same paths as source server
4- make : db2move tsmdb1 import

seems that it is realy hard (or not supported) to make it by following the document procedure, as the way i want to do it is not documented.
hope this will help someone else.