That is strange, because I've used DFDSS to restore z/VM dasd. That was
where I "discovered" the sentence in the DFDSS manual that says that you
can't use the S/A version. Our D/R backups here are done with Shark
flashcopy and then ADRDSSU to dump from the flashed target to tape. I
have restored dumped tapes to DASD and have been able to IPL the
restored volume.
Jim
McKown, John wrote:
-----Original Message-----
From: The IBM z/VM Operating System=20
[mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard
Sent: Wednesday, January 03, 2007 11:46 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Backup of z/VM and z/VSE
=20
=20
There may be another gotcha. A year ago last June, our shop was in the
middle of a migration to a new datacenter. The concept was simple:
=20
- Copy disks that were to be migrated into a "bunker box" - a SHARK
facility equipped to synchronize data between the two centers.
- Dress rehearsals to discover an fix any problems in the migration
plans. These included synchronizing the data in the two centers ahead
ago time and doing a final incremental sync when ready to try the
migration.
- Final migration.
=20
The DASD Storage Management Group, all z/OS-oriented people, scheduled
time to move VM into the bunker box. In the week leading up=20
to the move,
they discovered that the utility they planned to use (and were assured
by the vendor, who shall remain nameless but whose initials are IBM,
that it could handle the task) would not copy the dasd used=20
by VM. They
had worked frantically with IBM trying to fix the problem. As a
last-ditch effort, they were even sent another utility used internally
by IBM that "definitely would work". It also failed. In near panic, it
was 4:45 PM on Thursday and the move was supposed to take=20
place at 9:00
AM Saturday, they asked me if I had any suggestions that=20
would save the
schedule. The answer was to build a one-pack system on DASD=20
that was not
being migrated and use several virtual machines to DDR the disks. Task
accomplished, and the copying took only half the time that had been
calculated for the z/OS utility.
=20
Unless they have been fixed, the z/OS utilities may fail when working
with VM DASD. I imagine that DFDSS was the first of the utilities that
failed. I do not even know the name of the one cloaked in black.=20
=20
=20
Richard Schuh=20
That is very strange. I have successfully dumped and restored z/VM DASD
using DFDSS on z/OS 1.6. The z/VM system was down at the time. Oh, but
this was via TAPE, not disk-to-disk. That may be the difference.
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.=20
--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]
