Hi Holter, Lets name the things... Let's call DEAD the linux image with damaged system, and RECOVERY our recovery system.
You just have to logout DEAD to avoid data corruption, and logon RECOVERY. On your 3270 console, issue this command: LINK DEAD 100 200 MR CP will ask you the MR password (check USER DIRECT to get the password), and give RECOVERY full control over disk 100 of DEAD, now mapped as disk 200 on RECOVERY. Do it for any other disk from DEAD. Log on RECOVERY via ssh. Use *chccwdev -e 200* to activate the disk 200, and *lsdasd* to see what is 200's device name (eg. /dev/dasdk).\ Create a mount point for this dasd, like /mnt/dead Mount the dasd: *mount /dev/dasdk /mnt/dead* Enjoy! Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Tue, Apr 27, 2010 at 4:43 AM, Kenneth Holter <[email protected]>wrote: > Hi. > > > I just came across this old post. We're about to create a disaster > recovery plan using FDR/UpStream, and the setup described in your post > below seems very interesting. Would you mind sharing info on how you > set up your recovery system with regards to seeing both disks etc? > > > Regards, > Kenneth Holter > > > > On Tue, Jun 23, 2009 at 4:54 PM, Stewart Thomas J > <[email protected]> wrote: > > We "rolled our own" recovery Linux system (aka "virtual live cd"). We > simply created a guest with a minimal Linux install and no LVM. Then via the > beauty of shared disk, if a system fails we just shut down the failed guest > and link our recovery system's disk to the guest as well. We IPL from the > recovery system's disk, but it is configured to see both it's normal disk > and also mount up the LVM directories from the failed system. We use mdisk's > in the 1xx range for the normal system and in the 2xx range for the recovery > system - both are configured for the recovery system so he automatically > brings them both online. > > > > Once up the recovery system can edit individual files on the failed > system's LVM structure, or even perform a network restore. The cool part is > you can even leave your recovery system up during normal operation so it can > be backed up itself, get updates, etc. Then take it down and "swing" it onto > another system when it needs to swoop in for a rescue. > > > > __________________________________ > > Tom Stewart > > Infrastructure Analyst > > John Deere - z/OS Support Services > > em: [email protected] > > __________________________________ > > > > > > > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Kenneth Holter > > Sent: Tuesday, June 23, 2009 12:35 AM > > To: [email protected] > > Subject: Linux live CD for z/Linux? > > > > Hi all. > > > > > > Does there exist any linux live CD's for z/Linux? I've found our CentOS > live CD very useful on our x86 servers, and would like to have the same > option available on z/Linux. > > > > Regards, > > Kenneth Holter > > > > ---------------------------------------------------------------------- > > 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 > > > > ---------------------------------------------------------------------- > 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
