If you have the space, YES, copy them also to file images. Good idea. This is the beauty of FBA. There's nothing out of band, just the bytes. No track and record structure to maintain.
On Tue, Apr 5, 2022, 17:46 Martha McConaghy <[email protected]> wrote: > That's also a good idea. Thanks, Dave, Alan and Rick! I think, while I'm > at it, I could DDR them to file images so I have a back up too. > > Martha > > > Martha McConaghy > > Marist: System Architect/Technical Lead > > SHARE Association: Secretary > > Marist College IT > > Poughkeepsie, NY 12601 > > ________________________________ > From: Linux on 390 Port <[email protected]> on behalf of David > Kreuter <[email protected]> > Sent: Tuesday, April 5, 2022 5:41 PM > To: [email protected] <[email protected]> > Subject: Re: Moving LUNs using z/VM > > Hi Martha > I did this successfully some years back. Make the input a “full pack “ > mini on edev link it read only to reduce stress. > Good luck > Dave > ________________________________ > From: Linux on 390 Port <[email protected]> on behalf of Martha > McConaghy <[email protected]> > Sent: Tuesday, April 5, 2022 5:34:22 PM > To: [email protected] <[email protected]> > Subject: Re: Moving LUNs using z/VM > > OK, I want to make sure I am understanding it clearly. Its an interesting > idea, but I really can't afford to blow away the original disks, so want to > be really sure. > > The existing disks are used by the virtual machine by having LOADDEV > statements in the directory for the vm and then IPLing the raddr of the > NPIV port on the FC channel, i.e.: > > LOADDEV PORT 500507630628D700 > LOADDEV LUN 4001400900000000 > IPL 2000 > > Now, the idea is to define an EDEV to VM that points to the same LUN, as > well as one that points to the new LUN on the DS8910. Attach both edev > devices to my machine and then use DDR to copy from the old one to the new > one. Very interesting idea. As long as I don't try to write to the > original LUN, define a minidisk on it, etc, it should be OK, in theory. > Has anyone ever tried this? > > Martha > > > Martha McConaghy > > Marist: System Architect/Technical Lead > > SHARE Association: Secretary > > Marist College IT > > Poughkeepsie, NY 12601 > > ________________________________ > From: Linux on 390 Port <[email protected]> on behalf of Rick Troth > <[email protected]> > Sent: Tuesday, April 5, 2022 5:27 PM > To: [email protected] <[email protected]> > Subject: Re: Moving LUNs using z/VM > > What I mean is: > define them even temporarily as EDEVs for the DDR and go for it. > > > > On Tue, Apr 5, 2022, 17:25 Rick Troth <[email protected]> wrote: > > > If they're defined as EDEVs then you can use DDR. > > > > FBA (EDEV or 3370, etc al) being fixed block, copying the whole disk will > > include the boot partition. (Partition tables are not really needed on > > fixed block disks, even laptop SSDs, but don't get me started.) Any > > "partition table", and all partitions, would be included in the DDR copy. > > > > > > > > On Tue, Apr 5, 2022, 17:19 Martha McConaghy <[email protected] > > > > wrote: > > > >> I have a few RHEL servers that run on z/VM but boot off of a direct > >> attached SAN LUN (not an EDEV or ECKD). They reside on an old DS8870 > and I > >> need to move them to a new DS8910. (No PPRC, GDPS, etc.) Is there a > way > >> that I could use VM to copy these LUNs to the new storage? I was > looking > >> at DDR, but wasn't sure if the FB-512 type would work for these. They > >> aren't CMS format disks, obviously, so that isn't an option. I'm > trying to > >> avoid having to attach them to a Linux server to do the work, but will > if > >> that is the only option. Since these are boot volumes, I have to copy > the > >> boot partition and boot record, not just the filesystems. So, a > physical > >> copy would be the best. > >> > >> Any ideas? > >> > >> Martha > >> > >> > >> Martha McConaghy > >> > >> Marist: System Architect/Technical Lead > >> > >> SHARE Association: Secretary > >> > >> Marist College IT > >> > >> Poughkeepsie, NY 12601 > >> > >> > >> ---------------------------------------------------------------------- > >> For LINUX-390 subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO LINUX-390 > or > >> visit > >> http://www2.marist.edu/htbin/wlvindex?LINUX-390 > >> > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
