> 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.
That's what automation on z/OS is for (and in fact, one of the reasons we wrote SYSVINIT -- to get defined run levels that could be triggered by NJE messages from another node). Have Netview or OPC on z/OS trigger on the end of the backup job, and send a message from z/OS to AUTOLOG1 on your VM system to do "RUNLEVEL DEFAULT" (if you're running SYSVINIT). "RUNLEVEL BACKUP" switches you to "backup configuration" gracefully. You define what gets run in each. > 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. The combination of backups from inside the Linux guests and periodic snapshots is the solution. There are good products for doing the backups from inside the guests that do not require tape on Linux. If you want clean snapshots, Adam's right -- periodically you *have* to shut the guests down to get a clean snap -- once a month is not a bad period for most people (YMMV, before anyone decides to be a PITA). Combine that with daily file-level backups (which don't require the shutdown), and you're pretty much set. Wrt to availability, you probably will have to design for HA and failover to allow you to take servers out for backups. Fortunately, you can also define groups of servers in SYSVINIT...8-). ---------------------------------------------------------------------- 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
