In a message dated 8/8/2009 9:23:55 A.M. Central Daylight Time, [email protected] writes:
AFAIK the only sanctioned usage of DFSMSdss or any equivalent utility to backup DB2 data is to put DB2 in "suspend" mode to inhibit all updates, take full-volume dumps of all volumes containing any DB2 datasets, and then "resume" DB2 (requires flashcopy to keep suspend brief). ALL these volumes would have to be restored as a group with DB2 down (as in a full system restore scenario during DR). >> DB/2 is pretty good at this with experienced DBAs. Definitely a team effort. There's manuals, Redbooks and even classes on Recovering DB/2. The big kahuna is catalog consistency. DB/2 enforces it regardless. Hardware, software, or airhead-stuff happens. Doing a dfdss or FDR restore requires putting the tables and indexes back where they were within the range of SYSVOLS and running the DB/2 utilities to get the database ids back in synch. Then have to do a restore to RBA to get updates laid in. Best one I had was full restore and got it motoring only to have the DBA do a restore to RBA to the point where it was dropped in the first place-poof! Least I had the JCL.... ---------------------------------------------------------------------- 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
