In a server hosting environment, user spool files may not be necessary at you backup site. The remaining System Data Files (SDF) are not written ou t very often and you can probably do a COLD start at the backup site which will throw away all of the spool files but not the SDF files. For extra safety you might backup your SDF files to a CMS minidisk (DCSSBKUP/DCSSRS AV commands). Then at the backup site, if you do have problems with some SDF , you can restore it and continue. If you do need spool files to be restore d, then use SPXTAPE to dump all of your spool separately from your DASD back ups (sorry, z/OS can't do this yet), do a CLEAN start at your backup site and
restore all of your spool and SDF files from the backup tape. /Tom Kern On Thu, 10 Jan 2008 13:32:34 -0500, Jim Bohnsack <[EMAIL PROTECTED]> wro te: >Karl--About the biggest problem you are likely to face if you take >backups of 530RES and SPL is that you might or I should say, would, lose >open VM spool files. An ipl from the restored volumes would have to be >done using "FORCE" rather than "WARM" because there would have been no >WARM START DATA saved. For better or worse, our normal backups are >taken against up and running VM systems. > >Since you're running z/OS and doing backups from there, I would >recommend doing regularly scheduled backups. The wasted effort or >redundant or duplicate backups are a small price to pay for the security >of knowing that a change was made and you or someone forgot to take a >backup. Tapes sometimes go bad. If you have a previous backup to go >back to, that's another safety net. > >Jim >
