DB2 Recovery Problems

[stigger]

We are attempting to recover a DB2 instance for DR purposes.

We have a tape containing a full backup from another networker setup.

We have scanned in the tape, but apparently the scanner cannot rebuild the file indexes of DB2 backups so a browse restore from the client cannot be used, We've been advised that we need to perform an saveset restore and then provide that to the Database for recovery.

Again we've tried that and are getting the following error.


[root@maitop2 /]# recover -a -iY -S 2408751053 -d /global/gen/nfs/pcbackup/sap/ -s maitop2
Recovering a subset of 1 files within DB2:\PIX\ into /global/gen/nfs/pcbackup/sap
67848:recover: Failed to recover save set(s): Permission denied by server maitop2: Cross Platform Recovery not supported


The platform is DB2 9.5 DB2 module 4.0 networker 7.5.2 both server and client.

Any ideas???

 

[605]

The "Cross Platform Recovery" refers to the client OS - obviously the one from source and destination are different. NW does not allow that.

 

[stigger]

That's what you'd think but they aren't both as Solaris 10 servers is are the backup server.

Strange Huh

I thought it might be something to do with the fact that it's a DB2 backup and no a filesystem one???

 

[a060463xyz]

saveset recovers from backups done with a networker database module are not possible.
do the folowing :
get the client-id of the original client from your origin Networker datazone.

Create a new client with the same name and clientid in your DR Networker Datazone. Import the Tape with scanner, chanhe the mode of the saveset if its recyclable bacjt to !recyclable. Rebuild the cfi if you have an index saveset of the db2 client or with scanner, and then recover using the db2 Admin gui.m There you can select the networker savesets.

 

[stigger]

How do I rebuild the CFI The scanner didn't do it...

 

[a060463xyz]

if you created the client with the same clientid you can use nsrck -L7 if you have an index saveset of this client.

If not scanner -i should do the job.
If it is not workig try to change the state of the saveset with nsrmm -o and retry the scanner operation:

scanner -i -S ...