I've talked to them about that too - as recently as SHARE. We're getting to the point where it takes longer than MVS to shutdown and re-ipl :). Especially if they are large virtual machines running big things like WAS and MQ Series.
Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Dave Jones Sent: Wednesday, April 05, 2006 11:28 AM To: [email protected] Subject: Re: [LINUX-390] Freeze Linux Guests momentarily Marcy, I seem to recall that a number of years ago an IBM-er (Romney White, perhaps) suggested a "stun" capability for VM. This would allow you to stun a guest, do something to the system (maybe even move the guest to another, similarly configured system) and have it start back up where it left off. The problem, as I understand it, is that capturing all of the state information about a running guest is non-trivial. DJ Marcy Cortes wrote: > Some sort of suspend would be cool - imagine hibernating all your > guests, doing your VM and/or HW maintenance, and having them just pop > back up! Kind of like hibernate on the PC! > > But, it doesn't really exist. You'll either have to look at some > backup from inside of the guest or if you really need to be 24/7, then > you have to have redundancy in virtual servers - preferably not on the > same HW and perhaps even not in the same data center location. > > > Marcy Cortes > > "This message may contain confidential and/or privileged information. > If you are not the addressee or authorized to receive this for the > addressee, you must not use, copy, disclose, or take any action based > on this message or any information herein. If you have received this > message in error, please advise the sender immediately by reply e-mail > and delete this message. Thank you for your cooperation." > > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Tyler Koyl > Sent: Wednesday, April 05, 2006 10:42 AM > To: [email protected] > Subject: [LINUX-390] Freeze Linux Guests momentarily > > I am quite sure this exists but I need a little help. > > I was wondering if there is a way to place a z/VM 5.1 linux guest into > a froozen state? My thinking is just place the guest into a CP Read State. > Can't seem to find the command to send a guest a request to enter CP > READ. > > I am writing a REXX exec to handle the snapping. The logic I am > looking for is > this: > > /* > Backup guest x > - Place a guest is CP READ state (Or something similar) > - Snap Guest related DASD (SVAA Snapshot) > - Release Guest > > Repeat for each guest to be snapped. > */ > > It has been mandated that the guests will be 24/7 so they cannot be > logged off to do the backup, nor can the portal services etc be turned > off. I am worried about sequential snapping DASD that belong to an LVM > group so this is why I am looking for a work around. > > Any help is appreciated. > > Tyler Koyl > Saskatchewan Wheat Pool > Regina, Saskatchewan, Canada > > > > This e-mail and any attachment(s) are confidential and may be > privileged. > If you are not the intended recipient please notify me immediately by > return e-mail, delete this e-mail and do not copy, use or disclose it. > > ---------------------------------------------------------------------- > 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
