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?
