Thanks, likewise our linux guests and VM itself is down.

I was more curious around the cp allocations for page, spool tdisk were
they preserved.

Brian

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Macioce, Larry
Sent: Tuesday, February 19, 2008 1:49 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Backing up and restoring zVM 5.2 using IBM's DSS backup
utility under zOS 1.7/1.9

We have used the method you show to restore a Linux guest and we were
able to logon and use it with no problem we were using z/OS 1.6.
But when we back up Linux and/or VM they are down so the backups are
stable.

Mace 

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Walter
Sent: Tuesday, February 19, 2008 1:30 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Backing up and restoring zVM 5.2 using IBM's DSS backup
utility under zOS 1.7/1.9

Brian,

Do you understand that if you backup any system from any other system, 
using tools which are not aware of file updates in cache, and files or 
databases which are spread across physically disparate DASD, then the 
backup is unreliable unless the system being backed up has been
gracefully 
shutdown before the back begins, and is not brought up until the backup
is 
complete?

I.e. if you are backing up z/VM from z/OS, z/OS just backs up tracks of 
data.  If those tracks are changing, the odds of reliably restoring the 
system are not too reliable (pun intended).

That's not z/VM's fault.  If you backup z/OS DASD from z/VM while z/OS
it 
is running, the restore will probably not be reliable.  If you back up a

Linux guest running on z/VM from z/OS, z/OS is unaware of files cached
on 
the Linux guest.

Solution: backup a system using its own products which are aware of
these 
limitations, or use backup tools at rely on a client running on the
system 
being backed up to get a stable, reliable, and _restorable_ backup.

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Hamilton, Brian" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
02/19/2008 11:19 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Backing up and restoring zVM 5.2 using IBM's DSS backup utility under
zOS 
1.7/1.9






Is anyone using DSS to backup their VM system under zOS and have you
been 
successful in restoring and IPL?ing ? 
 
Sample of the DSS backup statements were using,
 
DUMP TRACKS(0,0,3338,14) INDDNAME(DASD) OUTDDNAME(TAPE) ADMIN - 
 CPVOLUME CANCELERROR 
 
Thanks
 
Brian


 
The information contained in this e-mail and any accompanying documents
may contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if
this message has been addressed to you in error, please immediately
alert the sender by reply e-mail and then delete this message, including
any attachments. Any dissemination, distribution or other use of the
contents of this message by anyone other than the intended recipient is
strictly prohibited. All messages sent to and from this e-mail address
may be monitored as permitted by applicable law and regulations to
ensure compliance with our internal policies and to protect our
business. Emails are not secure and cannot be guaranteed to be error
free as they can be intercepted, amended, lost or destroyed, or contain
viruses. You are deemed to have accepted these risks if you communicate
with us by email. 

-----------------------------------------
********************************************************************
The information transmitted is intended solely for the individual
or entity to which it is addressed and may contain confidential
and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is
prohibited. If you have received this email in error please contact
the sender and delete the
material from any computer.
********************************************************************

Reply via email to