This is what we do......simply because we have not found a better way with the tools we have. We have been primarily an MVS shop and have not been doing z/VM for quite a year yet. It has been a real learning curve getting z/VM 5.2 in place and then doing RedHat Linux guests (15 so far). Backup/restores and a DR plan has been one of our concerns.
The steps I take when I do backups are: 1) Schedule shutdown of all Linux guests and z/VM.....usually on a Sunday afternoon. 2) Run a series of batch jobs to backup all z/VM and Linux DASD using DFDSS to do physical dumps to STK 9840 tape. This is so we can easily transport or vault offsite. 3) Startup z/VM and guests. The dumps usually take a few hours with the number of disk we have. We use Tivoli to do file backups of the guests nightly (automated). The logic is to use the Tivoli backups to do restores of files or individual servers if something bad happens. If it is a DR event then I would use the DFDSS snapshop to restore the entire zVM/guest environment and then use the Tivoli to bring the servers up to the most current backup. We have done some testing of this and it seems to work fine so far. Not pretty........basic......but it works. Jon Brock <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 03/29/2007 09:54 AM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: Backup & Restore Since you are running MVS on your box, you can always (assuming you are sharing DASD) take your volume-level backups on the MVS side, which is what we do so far. To add to the fun, if your DASD has snapshot capability, you can get minimal guest downtime by: 1) Shut down a guest. 2) Snap its DASD on z/OS. 3) Start up the guest. 4) Back up the snapshot copy to tape. This is the procedure I use here for DR backups. File level backups are a whole different animal, though. Jon <snip> Primarily I need a DR solution; mainly to be able to bring the system back from a disaster in under a week. There are already DR processes in place for other systems on the mainframe(s), such as MVS, CICS, etc. I am behind on z/VM in that regard. </snip> ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
