On May 8, 2006, at 2:19 PM, James Melin wrote:
What I've never been able to figure out is how to tell z/VM that
the backup process on z/OS is done and to either change runlevels
or IPL the guest or
what have you.
Again daily system shutdowns are not suitable for a 24/7 production
environment. So how to balance the need vs the reality is the real
trick.
"By doing file-level backups of the Linux guests" is the answer. I'm
not recommending daily system shutdowns by any means. I'm also
pointing out that DDR or its moral equivalent isn't the right answer
EITHER. If you do it that way, sooner or later you will end up with
data corruption.
Here's one way you can do it with no additional licensing fees and no
new software from the z/OS or z/VM perspective.
Install a Bacula instance. Have your Bacula SD use a big LVM disk
pool as its storage device. Arrange the scheduling so that the
Bacula job mounts the disk pool, runs its backup, and then unmounts
the disk pool when it's done, and further so that the Bacula backups
are done before your nightly volume dump happens.
Then dump the disk pool volumes, but NOT the other volumes on your
Linux guests. Since they will be unmounted when the volume backup
runs you know that they are clean. To restore, restore THOSE volumes
and a basic Linux system with Bacula (which could be a separate DDR
image, if you like). Mount the LVM and then restore your remaining
guests from that pool.
Didn't cost you an additional dime in software licensing fees.
Adam
----------------------------------------------------------------------
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
