As my understanding was, these were not VM minidisks, but real dasd, as I
used OS/390 in LPAR mode to restore them. I can ask the DR people what
they ended up with, hell I'll even ship them a tape and if they're willing
to try to do this again, under the table.
The big thing is that we, ourselves, are not a VM shop. I elected to use
the DR vendors VM license because they let us. It theoretically solves
certain problems for us. I have no VM experience at all, personally.
Actually the extent of my VM experience is 'i b217' from a cp read prompt.
I'm just trying to determine what exactly I missed.
Can dd see 'cyl 0' from within linux? That's a good point #1 to start with.
|---------+---------------------------->
| | "Kern, Thomas" |
| | <[EMAIL PROTECTED]|
| | oe.gov> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 07/22/2003 10:03 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: CDL backup via DFSMSdss
|
>------------------------------------------------------------------------------------------------------------------------------|
Are these minidisks defined as FULL volume (cyl 0-end) or do you start the
linux minidisk at cylinder 1?
I have my linux minidisks starting at cylinder 1 (being a longtime VM
person, the label and allocation bitmap are stored on real cylinder zero).
So when I have our OS/390 system use DFDSS to backup/restore the linux
volumes, I actually have them access a FULL volume definition of the same
volume that is owned by a placeholder user (VMDASD). All VM related DASD in
my shop are defined as FULL volumes for this user.
/Thomas Kern
/301-903-2211
> -----Original Message-----
> From: James Melin [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 22, 2003 10:51
> To: [EMAIL PROTECTED]
> Subject: CDL backup via DFSMSdss
>
>
> Apparantly dfdss backup does not copy cylinder 0 when doing a
> volume backup
> of the tracks in a linux volume?
>
> I attempted to backup my quiesced linux dasd and restore it
> at the disaster
> recovery site using VM. The first problem I ran into is that my 'so
> called' 3390-9's are about 1408 tracks too large for a standard mod 9
> volume, so I couldn't restore to the mod 9's provided by the
> DR vendor.
>
> They got creative and put some 27 GB (mod 27?) in an address
> range we were
> not using and I restored to those. We then mapped the real
> disk addresses
> to the expected disk addresses in VM and attempted to IPL.
> That's when the
> DR staff in new jersey determined cyl 0 was empty on the IPL volume.
>
> I am wondering what happened, what got missed, etc. Was it
> the mod-27's the
> killed me? Did it not put the info at the beginning of the volume?
>
