Hya
Hum, importing would be soooo long it should not be considered as a DR plan, but as the last chance process.
You can bprecover the catalog of SERVER 1 onto SERVER2, but all the catalogs would point to SERVER1.
What you could do if you really don't want to rename SERVER1 to SERVER 2 is manualy (means by script) modify the images catalog files.
An image generate 2 files in /usr/openv/netbackuo/db/images/xxxx000000 directory : 1 is metadata, ascii file. the other is files_file binary list.
Edit ALL the metadata files Ascii file to have them point onto SERVER2 instead of SERVER1.
Of course, the recover of a volDB from SERVER1 to SERVER2 is a problem too !
Forget it : if your under a DR PLAN, all the tapes must be inventoried in SERVER2 who would consider them as new unassigned tapes.
- put them in a pool
- manually protect them with assignation :
vmquery -assignbyid
|
(chose 1234567890 for assigntime, 0 for status)
Thanks to the mediaDB, and to your modifications in the images DB, you can make any restore you want !!!
BUT, THIS IS A DR PLAN not supposed to be used that way if you want SERVER2 to definitively work in replacement of SERVER1 !!!!
To be proper and clean, I would still suggest to rename SERVER2 to SERVER1 ... it's the only supported way by VERITAS. And even if you consider this as a temporary replacement. When SERVER1 is back ... make a bpbackupdb of old SERVER2 (now known as SERVER1) and restore back to your SERVER1.
This modification of your image catalog is just something to go much faster than the importatio!n.
Kerk the noob