DFSMS is enhanced to provide z/OS version to release for support for individual Unix File Backup and Recovery. Just keep in mind that DFSMSdss and DFSMShsm, only process zFS datasets. In general, admins want to use the same tools and applications to backup and restore individual z/OS Unix files residing in zFS data sets, as with other z/OS data sets. That support is integrated into existing DFSMShsm backup and recover, and DFSMSdss Dump and Restore capability. Allowing for centralized data management across the z/OS Platform. In the shell, there are three native Unix utilities you can use to backup and restore files and directories, cpio, tar, and pax. These utilities are used to create an archive file that records the contents of the files and directories in a special format. This is useful for those who want to stick with the native interfaces and possibly exchange or transport the archives with other platforms. Cpio reads and writes either a compact binary header or an ascii format header. There's no limit on length of file name. Tar, reads and writes headers in either a tar format from Unix systems or the USDA format defined by POSIX. With tar format, the path name can be 100 characters. With USDA, it can be 255 characters long. During backup or restore, tar preserves link information. Pax combines the power of cpio and tar. Pax or P-A-X can read and write files in cpio ascii format, cpio binary format, tar format, or USDA format. It can read files that were written by cpio, tar or pax itself. Pax can do code page conversion. To write these archived files to a TAPE, use or get to copy them to a z/OS sequential data set, and then use z/OS utilities to copy the data set to the TAPE. Now, we'll run through this very briefly, but the point here is in z/OS V2 Release 4, storage admins are able to manage the backup and recovery of Unix files within zFS file systems with DFSMSdss and DFSMShsm utilities, which are normally used for standards z/OS data sets. Here we see the use of BACKDS where we specify things like the HSM backup TARGET location, either DASD or TAPE, and how to traverse the directory structure with RECURSE. Here we have the TSO command HBACKDS and the Unix shell command hbackup. Again with multiple options as to how the backup should be performed. We have support for recursion and wildcards. We can say things like backup, everything in /u/dir1 and it's subdirectories, but don't span over into different file systems. Or we can say backup any files that start with ab.txt, with a directory structure and a single fast system. You can also define exclusions, things like don't backup log files. Here's how to issue a recover command with the option for the file to recover and options for replacement and recursion. Here we see a TSO commands to recover file 2, specifying options for REPLACE WAIT. A Unix shell command example is also shown here. Here's batch JCL to use the DFSMSdss Dump and Restore command to request a backup of z/OS Unix file using absolute path names. To use DFSMSdss to dump Unix files we show an example here it's specifying a path to the file to be backed up. A WorkingDirectory, specifying the directory to be backed up and OUTDD name describing the output data set that holds the backup contents. To perform a DFSMSdss restore, we specify the path of the files to be restored, the working directory of where dss should restore and in DD name specifying the INPUT DUMP dataset. That's a whistle-stop tour of backup and recovery. Next, we'll see how hierarchical files on z/OS can be accessed from a workstation by using NFS.
