The guests that the 2nd-level system is running are CMS users and applications. It seems logical to me that if a weekly backup was scheduled when the users are not online and working, the system could be quiesced and backups could be taken. This is what they did when the system was moved to our z10. They logged off all non-system users and did DDR backups. When we restored to our system, it came up without issue.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Alan Altmark Sent: Monday, September 20, 2010 8:18 PM To: [email protected] Subject: Re: DEDICATED DASD - How to backup? On Monday, 09/20/2010 at 04:56 EDT, KEETON Dave * SDC <[email protected]> wrote: > I have a maintenance window of two days a month in which I COULD shutdown the > guest, but it'll meet with resistance I'm sure. The hope was to back > it up > daily. There's a total of 42 3380 volume currently. > > As to the OS, it's VM 3.1 ... yeah, old stuff! We're migrating a customer from > their old mainframe. This is a temporary solution. You really don't want to back up that system while it's running. You need all the data to be consistent, and that only happens when the VM system is down. Even forgetting warm start/checkpoint data, remember that the guests it is running also have data on minidisks that needs to be consistent. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 [email protected] IBM Endicott
