Comments: What we have down is; 1. MANUAL JOB- SHUTDOWN LINUX 4 z/VM server-AFT 7pm. 2. DDR specific volumes thru an automated exec process. 3. MANUAL JOB- START LINUX 4 z/VM server- AFT 7pm. We are halting to shut down the Linux servers thru the The Linux Web interface. We then perform; DDR of the volumes. This is a 99.9% non violent approach! Down time: approx 1 hour per LINUX server. Start: XAUTOLOG the Linux 4 z/VM server back up; works out just fine. Yes availability, 100% up-time; but this is our trade off. Our experience for backing up the file system from the Network sever side, has had many issues, but our Staff keeps trying!
-----Original Message----- On Behalf Of Alan Altmark But rather than focus on that "edge" condition, we are all, I think, in violent agreement that you cannot take a volume-by-volume physical backup from outside a running Linux system and expect to have a usable backup. Shared dasd on System z has all the same issues that shared LUNs have on distributed systems. The backup *strategies* are identical, even if the mechanisms used to create the backups are not. ---------------------------------------------------------------------- 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
