• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TSM DB restore fails with DB2 sqlcode 1005

joshmo

ADSM.ORG Member
#1
Hi All,

So I have attemted to restore my TSM db to a new server.
Im going from Windows 2008R2 to Windows 2012R2, same TSM version. (7.1)

After a bit of fiddling with the devconfig to get the tape to mount, im failing with the following:

ANR8328I 001: LTO volume BLAHL5 mounted in drive TAPE0 (mt3.0.0.1).
ANR1363I Input volume BLAHL5 opened (sequence number 1).
ANR4609I Restore database process found FULL database backup timestamp
20180409093419 from database backup media.
ANR1364I Input volume BLAHL5 closed.
ANR3008I Database backup was written using client API: 6.3.0.0.
ANR4638I Restore of backup series 1794 operation 0 in progress.
ANR4897I Database restore of operation 0 will use device class LIB_LTO5 and
attempt to use 1 streams.
ANR2971E Database backup/restore/rollforward terminated - DB2 sqlcode -1005
error.

Any suggestions greatly recieved.

Thanks!
 

Trident

TSM noob with 10 years expirience
ADSM.ORG Moderator
#2
Hi,

Have a look in db2diag.log (may be called db2diag.X.log). Or even better, tail it while restore is running.

-= Trident =-
 

Spree

ADSM.ORG Member
#3
Google points me to here. I am having the same problem.

I have an upcoming project that I need to upgrade a TSM 6.2 + RHEL 5 server to a TSM version under IBM support (7.1/8.1), but 7.1/8.1 no longer supports RHEL 5 that I needed to upgrade RHEL version as well. I was told that in-place upgrade an RHEL server version would be a great hassle and was suggested to do a new OS installation instead.

So I first set-up a TSM 6.2 server on RHEL 5, upgrading it to TSM 6.3 server, then back-up the TSM database and move the backup file to a new server with RHEL 6 + TSM 6.3 installed, wanting to restore the database on it to continue the upgrade test.

But problem occured during the TSM database restore. Log shows "ANR2971E Database backup/restore/rollforward terminated - DB2 sqlcode -1005 error".

db2diag.log shows the following:

=====

2018-06-14-11.25.46.042118+480 I98643E305 LEVEL: Event
PID : 10065 TID : 139763463538464PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 : <preformatted>
Single node instance [0] is starting

2018-06-14-11.25.46.049504+480 I98949E1637 LEVEL: Event
PID : 10065 TID : 139763463538464PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/tsminst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFEEE0477F0 : 2F68 6F6D 652F 7473 6D69 6E73 7431 2F73 /home/tsminst1/s
0x00007FFEEE047800 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFEEE047810 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFEEE047820 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047830 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047840 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047850 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047860 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047870 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047880 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE047890 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE0478A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE0478B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE0478C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE0478D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFEEE0478E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2018-06-14-11.25.46.186692+480 E100587E329 LEVEL: Error (OS)
PID : 10067 TID : 140334058833696PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.25.46.196765+480 E100917E329 LEVEL: Error (OS)
PID : 10067 TID : 140334058833696PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.26.54.058706+480 I101247E305 LEVEL: Event
PID : 10082 TID : 139961893652256PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 : <preformatted>
Single node instance [0] is starting

2018-06-14-11.26.54.059111+480 I101553E1637 LEVEL: Event
PID : 10082 TID : 139961893652256PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/tsminst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFE419DB5A0 : 2F68 6F6D 652F 7473 6D69 6E73 7431 2F73 /home/tsminst1/s
0x00007FFE419DB5B0 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFE419DB5C0 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFE419DB5D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB5E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB5F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB600 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB610 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB620 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB630 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB640 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB650 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB660 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB670 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB680 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE419DB690 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2018-06-14-11.26.54.126233+480 E103191E329 LEVEL: Error (OS)
PID : 10084 TID : 139697641150240PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.26.54.134573+480 E103521E329 LEVEL: Error (OS)
PID : 10084 TID : 139697641150240PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.18.124279+480 I103851E305 LEVEL: Event
PID : 10098 TID : 139662073145120PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 : <preformatted>
Single node instance [0] is starting

2018-06-14-11.27.18.124673+480 I104157E1637 LEVEL: Event
PID : 10098 TID : 139662073145120PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/tsminst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFE1C486570 : 2F68 6F6D 652F 7473 6D69 6E73 7431 2F73 /home/tsminst1/s
0x00007FFE1C486580 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFE1C486590 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFE1C4865A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C4865B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C4865C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C4865D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C4865E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C4865F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486600 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486610 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486620 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486630 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486640 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486650 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFE1C486660 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2018-06-14-11.27.18.186619+480 E105795E329 LEVEL: Error (OS)
PID : 10100 TID : 139847167964960PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.18.194950+480 E106125E329 LEVEL: Error (OS)
PID : 10100 TID : 139847167964960PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.25.859197+480 I106455E305 LEVEL: Event
PID : 10113 TID : 140594014967584PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 : <preformatted>
Single node instance [0] is starting

2018-06-14-11.27.25.859535+480 I106761E1637 LEVEL: Event
PID : 10113 TID : 140594014967584PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/tsminst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFC77CEA4C0 : 2F68 6F6D 652F 7473 6D69 6E73 7431 2F73 /home/tsminst1/s
0x00007FFC77CEA4D0 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFC77CEA4E0 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFC77CEA4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA500 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA520 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA530 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA540 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA550 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA560 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA570 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA580 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA590 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA5A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFC77CEA5B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2018-06-14-11.27.25.936644+480 E108399E329 LEVEL: Error (OS)
PID : 10115 TID : 139653369218848PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.25.944709+480 E108729E329 LEVEL: Error (OS)
PID : 10115 TID : 139653369218848PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.56.182768+480 I109059E305 LEVEL: Event
PID : 10121 TID : 139876987180832PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
DATA #1 : <preformatted>
Single node instance [0] is starting

2018-06-14-11.27.56.183453+480 I109365E1637 LEVEL: Event
PID : 10121 TID : 139876987180832PROC : db2start
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 34 bytes
/home/tsminst1/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x00007FFFE9CF25A0 : 2F68 6F6D 652F 7473 6D69 6E73 7431 2F73 /home/tsminst1/s
0x00007FFFE9CF25B0 : 716C 6C69 622F 6164 6D2F 6462 3273 7461 qllib/adm/db2sta
0x00007FFFE9CF25C0 : 7232 004E 4F4D 5347 0000 0000 0000 0000 r2.NOMSG........
0x00007FFFE9CF25D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF25E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF25F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2600 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2610 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2620 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2630 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2640 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2650 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2660 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2670 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2680 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00007FFFE9CF2690 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2018-06-14-11.27.56.252479+480 E111003E329 LEVEL: Error (OS)
PID : 10123 TID : 140242980992800PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.56.262884+480 E111333E329 LEVEL: Error (OS)
PID : 10123 TID : 140242980992800PROC : db2star2
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment, probe:100
CALLED : OS, -, shmget OSERR: EEXIST (17)

2018-06-14-11.27.56.290849+480 I111663E669 LEVEL: Warning
PID : 10102 TID : 140184106714912PROC : dsmserv
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, Connection Manager, sqleUCgetDirInfo, probe:1012
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1013 sqlerrml: 6
sqlerrmc: TSMDB1
sqlerrp : SQLEUCCM
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2018-06-14-11.27.56.312348+480 I112333E690 LEVEL: Error
PID : 10102 TID : 140184106714912PROC : dsmserv
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluxResolveDBname, probe:1752
MESSAGE : ZRC=0xFFFFFC0B=-1013
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: 0 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL09076
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 00000

2018-06-14-11.27.56.314072+480 E113024E396 LEVEL: Severe
PID : 10102 TID : 140184106714912PROC : dsmserv
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqludProcessInitialCall, probe:2122
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-1005
DATA #2 : Hexdump, 4 bytes
0x00007F7F21BF3BF8 : 13FC FFFF ....

2018-06-14-11.27.56.315189+480 E113421E806 LEVEL: Severe
PID : 10102 TID : 140184106714912PROC : dsmserv
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqludProcessInitialCall, probe:2122
MESSAGE : SQL1005N The database alias "" already exists in either the local
database directory or system database directory.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1005 sqlerrml: 0
sqlerrmc:
sqlerrp : sqludPro
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 00000

=====

Any help would be much appreciated. Thanks.
 

marclant

ADSM.ORG Moderator
#6
"ANR2971E Database backup/restore/rollforward terminated - DB2 sqlcode -1005 error".
The DB2 sqlcode -1005 is the reason for the failure
2018-06-14-11.27.56.315189+480 E113421E806 LEVEL: Severe
PID : 10102 TID : 140184106714912PROC : dsmserv
INSTANCE: tsminst1 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqludProcessInitialCall, probe:2122
MESSAGE : SQL1005N The database alias "" already exists in either the local
database directory or system database directory.
The DB2 SQL codes in the TSM errors always end up in format SQL####N in db2diag.log.
Google points me to here.
Googling SQL1005N brought me here:
http://www-01.ibm.com/support/docview.wss?uid=swg21665868
 

Spree

ADSM.ORG Member
#7
I did notice that by Google search but I normally run a "dsmserv removedb TSMDB1" before running database restore so the db should be non-existent and cataloging a non-exitent db would not work.
 

joshmo

ADSM.ORG Member
#9
Hi the issue for me was that when I moved the library containing the DB backup to the new server the scsi path was different so the tape wasn't mounting. I worked around the issue by creating a new LUN with a sequential disk volume and running the database backup to that. Represented that lun to the new server and the restore worked without a hitch.
 

Spree

ADSM.ORG Member
#10
Tried again, on the new server:
1) If I initialize a new server instance using dsmicfgx, then do a "dsmserv removedb" action, would lead to the 1005 error.
If I initialize a new server instance using dsmicfgx, then do not "remove db" but just place the instance files from old server and do a database restore right away, it would start the database restore but would lead to 2563 error. Even I tried to roll it forward it would fail as well, could not find the needed point? No difference whether I did or did not specify a point-in-time.
 

Spree

ADSM.ORG Member
#12
Eh, that project mentioned above ended up with customer agreeing to accept building the new ISP backup server without migration.

But after a year, I got a similar problem.

This time, the old server is RHEL 6.4 + ISP 7.1.9, new server needs to be RHEL 7.6 + ISP 8.1.8.

Then I found this by Google:
https://www.ibm.com/support/knowled...0/com.ibm.itsm.srv.doc/t_db_move_new_loc.html

I notice the first 2 points here which I was wondering if I am not following them, it could lead to the failure, like:

•The same operating system must be running on both servers.

==> Does this only mean the same product but does not need to be the same version? (like, is RHEL 6.4 to 7.6 OK?) Or it needs to be same product + same version?

•The sequential storage pool that you use to back up the server database must be accessible from both servers. Only manual and SCSI library types are supported for the restore operation.

==> Is this true? That I need to use a sequential device that can be accessed by both servers? So what I was doing is wrong? (set up a FILE device on server A, then move the file as well as other files in the instance directory from server A to server B to do the restore, but that FILE device class is not referring to the same device that can be accessed by both servers)

Any comments or suggestions will be much appreciated.
 

marclant

ADSM.ORG Moderator
#13
==> Does this only mean the same product but does not need to be the same version? (like, is RHEL 6.4 to 7.6 OK?) Or it needs to be same product + same version?
I believe they mean same platform and same endian. For example, you could not restore to AIX or Windows.
Is this true? That I need to use a sequential device that can be accessed by both servers? So what I was doing is wrong? (set up a FILE device on server A, then move the file as well as other files in the instance directory from server A to server B to do the restore, but that FILE device class is not referring to the same device that can be accessed by both servers)
If you use the same directory for the device class on both servers, you should be ok after copying your volhist and devconfig.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 14 17.3%
  • Keep using TSM for Spectrum Protect.

    Votes: 51 63.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 11.1%
  • Other (please comement)

    Votes: 7 8.6%

Forum statistics

Threads
31,380
Messages
133,653
Members
21,492
Latest member
CamoVan
Top