One of our customers will be conducting a Disaster recovery exercise. The client will be restoring their volumes using DFDSS (Logical restore). I am not comfortable with them using a LOGICAL BACKUP/LOGICAL RESTORE. One main concern is that the catalog entries will be out of sync.
A couple of comments:
1 - why do you think you need different RESTORE statements for non-SMS and SMS volumes, with and without the CATALOG parm? CATALOG is the default when restoring SMS datasets, but it can't hurt to specify it as far as I know. So you could have just one set of input
2 - be sure that the backups are really logical dataset dumps. You can't do logical restores from physical dumps.
3 - the DSS manual always confuses me on what you need to specify for a physical restore vs a logical restore. I think you have coded parms that will try to do a physical restore but I am not sure. Definitely you should test this before going to DR. There is nothing more embarrassing than reserving time at DR, hauling a bunch of tapes there, and finding that you can't restore them so you have to pack up and go home and explain to management. I did that once, not fun.
Assuming that the backups and restores are correct, yes, each restored dataset will be cataloged, so it will solve the catalog sync issue.
-- Bruce Black Senior Software Developer Innovation Data Processing ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
