On Wed, 11 Sep 2013 07:24:23 -0700, Lizette Koehler wrote: > >z/OS V1R11.0 UNIX System Services Planning z/OS V1R11.0 GA22-7800-17 > >Unlike other non-VSAM data sets that can be opened and closed repeatedly >throughout the day, some file systems are often mounted for several days or >weeks at a time, with the individual file members inside opened as needed. >Normally, DFSMShsm's automatic backup (AUTOBACKUP) processes file systems at >most once per mount, so a file system mounted for a week would only have one >backup taken for that week. For some applications, that might not be >frequent enough. Fortunately, DFSMShsmT provides some alternatives to ensure >that backups are taken more frequently. > One must beware of the terminology. "mount" to UNIX means "OPEN" to z/OS, I believe. Read carefully.
But if one syncs the UNIX filesystem (does OMVS support sync?), takes a flash copy of the container, and backs up from that, is integrity guaranteed at least for UNIX files that were not open during the process? UNIX users who plan to keep files open and writeable long-term might well be counseled to take their own backups to .tar.Z files (Even to Classic data sets) at times not conflicting with DASD backups. Should simlar considerations apply to PDSEs which are chronically OPEN (although more rarely updated than zFS). -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
