Caution: We don't run z/Linux here. I just a "lurker". I assume you want to use z/OS to do your backups and restores. What might be acceptable (or might not) would be to have your "system" filesystems on non-EAV disks. You know that these can be successfully dumped and restored using DFSMSdss. These would be the volumes required to IPL your Linux system, as well as other volumes for one product which I will reference.
I would strongly suggest downloading and installing the free Co:Z product set from Dovetailed Technologies. This software is "free as in beer", but you can purchase a support contract. Much like Linux is free (such as CentOS), but you can purchase a support contract (such as RHEL or SUSE). Ref: http://dovetail.com/solutions.html Now, you can use Co:Z hybrid batch so that a z/OS job step can run z/Linux programs and scripts. The job contains the series of z/Linux commands to execute. They are sent to z/Linux over an SSH connection, which is running a shell on z/Linux with the z/OS batch job feeding the shell with input and accepting the output back. You should also install the Co:Z Data Set Pipes on z/Linux for full functionality. So, to do a backup using this method, some example z/OS JCL running Co:Z Hybrid Batch might be: //PROCLIB JCLLIB ORDER=(hlq.COZ.SAMPJCL) //BACKUP EXEC PROC=COZPROC,ARGS='user@zlinux' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEDUMP DD SYSOUT=* //SYSOUT DD SYSOUT=* //* SPEED THINGS UP BY NOT USING THE SSH //* BACK CHANNEL //COZCFG DD * ssh-tunnel=false //STDIN DD * set -x #because I like to see the commands tar --one-file-system -cvj /some/EAV/mount-point |\ todsn -b '//DD:TAROUT01' tar --one-file-system cvj /another/EAV/mount-point |\ todsn -b '//DD:TAROUT2' /* //TAROUT1 DD DSN=hlq.EAV1.TAR.BZ2,DISP=(NEW,CATLG), // UNIT=TAPE,LABEL=EXPDT=99000, // RECFM=U,LRECL=27998,BLKSIZE=27998 //* I USE 27998 BECAUSE IT IS FULL TRACK BLOCKING //* ON A 3390. I DO THIS JUST IN CASE I WANT THE //* DSN ON A 3390 FOR SOME WEIRD REASON. //TAROUT2 DD DSN=hlq.EAV2.TAR.BZ2,DISP=(NEW,CATLG), // UNIT=TAPE,LABEL=EXPDT=99000, // RECFM=U,LRECL=27998,BLKSIZE=27998 This may be an acceptable way to do a backup. To do a restore, you use DFSMSdss to restore the non-EAV volumes. You then IPL z/Linux and create/mount the EAV filesystems. You then use Co:Z Hybrid Batch on z/OS to do a tar x. This could be something like: //PROCLIB JCLLIB ORDER=(hlq.COZ.SAMPJCL) //BACKUP EXEC PROC=COZPROC,ARGS='user@zlinux' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEDUMP DD SYSOUT=* //SYSOUT DD SYSOUT=* //* SPEED THINGS UP BY NOT USING THE SSH //* BACK CHANNEL //COZCFG DD * ssh-tunnel=false //STDIN DD * set -x cd /some/EAV/mount-point fromdsn -b '//DD:TARIN1' |\ tar xvj //TARIN1 DD DISP=OLD,DSN=hlq.EAV1.TAR.BZ2 I have done things like this in order to back up my Linux/Intel desktop ${HOME} subdirectory on a z/OS virtual tape data set. Now, the only problem with this might be the speed of the IP link. If you are on a single CEC, then you should be using Hipersockets (IMO) and so the IP traffic would be fairly fast (I was told that it is basically a memory to memory move done by PR/SM firmware) and not impact your LAN traffic. If you use Hipersockets, then there is no need to use the SSH encryption, which decrease the CPU requirement, because the IP traffic cannot be sniffed on the LAN at all. This is just an off-the-wall thought from a weird z/OS sysprog. === The Co:Z product set contains a lot of neat stuff (IMO). The "todsn" that I referenced above can also write to a DSN as well as a DDNAME. There is also a corresponding "fromdsn". The "-b" switch I used says to do a binary transfer. If you don't use a "-b", todsn and fromdsn will convert to/from IBM-1047 (EBCDIC code page) and ISO8859-1 (ASCII code page). But there is a "-s" switch to specify the "source" code page and a "-t" switch to specify the "target" code page. The "fromdsn" command can also read job output from the JES SPOOL on z/OS to "stdout" which can be redirected to a file or piped into a command on Linux. On Fri, Jan 11, 2013 at 8:04 AM, Rob van der Heij <[email protected]> wrote: > Anyone doing his Linux backups (and restore) with DFSMSDSS maybe? > > A friend wanted to start using EAV and defined some 170G disks, > through DEVNO managed on z/VM. And while it seems the backup may have > worked, the restore certainly doesn't and complains with ADR024E and > some strange cylinder range. I'm told the big disks go in cylinder > managed space rather than track managed, but my source did not have > APAR or further detail. > > The customer is reluctant to put his crown jewels on a disk with no > backup. Anyone got the recipe for backup & restore? > > Thanks, Rob > > ---------------------------------------------------------------------- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- Maranatha! <>< John McKown ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
