That's exactly what we are doing now, using PIPEDDR to create a CMS file image of the DASD, and FTP'ing that CMS file to a Linux server (there's no 'unbursting' or storing the images on 3390 disk drives, these are just CMS files that contain 3390 DASD images created using PIPEDDR). The problem is that it takes a LOT of disk space and a LOT of time to create the CMS file image in the first place, I'm looking to write the PIPEDDR output DIRECTLY to a TCPIP socket and have "something" on the intel Linux server receive this stream and write it out to a file. That eliminates the need to FIRST create a CMS file to be FTP'd.
So on the VM/CMS side: PIPE TRACKREAD | TRACKSQUISH | (output to TCPIP socket) And on the Linux side something that receives the output from above and writes it to a file. -MC -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ann (ISD, IT) Sent: Friday, June 20, 2008 10:08 AM To: [email protected] Subject: Re: DDR'ing 3390 DASD To Remote Location -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Tuesday, June 17, 2008 8:51 PM To: [email protected] Subject: Re: DDR'ing 3390 DASD To Remote Location Thought about what you're after and would suggest this instead: - Use PIPEDDR to write to a file and FTP this file to your Linux server (or use use TSM and make your remote Linux server a TSM server and backup - perhaps using cmsfs on a local Linux guest to read the minidisk(s) where you store your 3390 images) - Create a 'one pack' z/VM system which you can IPL and has PIPEDDR on it -- ftp 3390 images from Linux server and PIPEDDR restore the DASD. I guess I don't see the value in having Linux 'unburst' the PIPEDDR packed file via a datastream and write to 3390 DASD (is that what you wanted??). Better to store physical images and use them by other data transports (like ftp or nfs) which already exist and just use image files created by PIPEDDR/DDR2CMS/whatever. For a DR solution for z/VM - you'll need some method to restore tape/disk/PIPEDDR/whatever-method you choose -- so what did you imagine that being? My experience with z/VM DR is to bring up a minimal z/VM system and restore from there.. either that or DDR tapes. So wondering what's on the DR side to make all this work? Scott On Tue, Jun 17, 2008 at 3:13 PM, Bruce Furber <[EMAIL PROTECTED]> wrote: > With the right disk controller you can PPRC (Peer to Peer Remote Copy) > > > ----- Original Message ----- > From: "Michael Coffin" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, June 17, 2008 11:42 AM > Subject: DDR'ing 3390 DASD To Remote Location > > > (Cross-posted on VMESA-L and LINUX-390) > > Hi Folks, > > I want to eliminate use of tapes in my weekly DR process. Currently > we DDR numerous 3390 spindles to 3590 tape cartridges. > > I > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.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://www.marist.edu/htbin/wlvindex?LINUX-390 ************************************************************************ * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************************ * ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.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://www.marist.edu/htbin/wlvindex?LINUX-390
