For the guarded failover portion, we have a rexx script and server that keeps track of which system the guest was last booted on. If it is logged in on the same host, the system just starts up. If it is autologged on the other host, it immediately logs off (it¹s 191 disk is R/O, so no damage done.) If it is logged in at a terminal on the other host, there is a prompt telling the user that it was last brought up on <the other other> host, and do you really want to bring it up here?
Answering no causes a logout. Answering yes starts the boot process, which includes logging the new boot into the system and the process is ready to work in the other direction. I have this code available, if you¹d like a copy.... -- .~. Robert P. Nix Mayo Foundation /V\ RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ ----- "In theory, theory and practice are the same, but ³Join the story... Ride Ural.² in practice, theory and practice are different." On 1/10/08 10:33 AM, "Karl Kingston" <[EMAIL PROTECTED]> wrote: > > We just installed z/VM 5.3. We have 2 systems running. VM1 and VM2. > Right now, all of our Linux guests (about 5) are on VM1. They also have a > directory entry on VM2 (but password set to NOLOG). > > 1) What's the best way to do failover if we need to get something over? > Right now, my plan is basically to log into VM2 and change the NOLOG to a > password and then start the guest. Basically I want to avoid having our > Operations staff make mistakes and start 2 instances of the same linux guest > (on 2 VM systems). > > 2) We use FDR/ABR on our z/OS side for backing up for Disaster Recovery. We > would like to keep using FDR. Now I know I can get clean backups if the > systems are shut down. Are there any gotcha's if I take a FDR full dump > against say 530RES or 530SPL while the system is up? \ > > 3) last of all, how often does VM get backed up when it's just used as a Linux > server system?? > > Thanks >
