> Ultimately I am thinking weekly full volume backups via CDL > (so I get such > things as the cyl-0, the IPL records, etc) and daily incrementals via > either bacula or the NFS option. What is the best way to copy > only changed > files?
Use the Bacula client inside the Linux guests. Right now I don't have VM ownership of those two tape > devices, and > I'm not sure that I can sell that to anyone. Don't really > have a direct > means of having VM tell z/OS in another LPAR that it is time > to give it the > tape drives for a while. That's the best way to use the NFS option. Have Bacula write "disk-tapes" -- emulated tapes on disk space provided by NFS on z/OS -- and otherwise it looks like Bacula with real tape drives. Same operation, same syntax. > The other question is this... if I go the NFS option, which > is the most > likely, will rsync work for me, or will it be a problem. Don't use rsync. Use the Bacula clients and have Bacula collect the data. > Ultimately I'd want to do NFS backup target datasets as a GDG > so I could go > back to previous versions if I had to. If you use Bacula, then you don't have to do all this management yourself; let the bacula catalog worry about it. > Also, there is the > issue that if I > use NFS, and immediately migrate the dataset by management > class, when it > comes time for backup, does it cause the previously migrated > version of the > dataset to be recalled, then backup proceeds and then > re-migration happens? > (presuming non-GDG) You don't use GDGs. Bacula has a concept of a emulated tape -- a sequential disk file that Bacula uses as if it were a tape volume. The Bacula client determines what changes need to be stored, contacts the Bacula server, and transfers only the changed files, which are spooled to disk. The Bacula server then collects the data and writes to a "disk-tape" file on the z/OS NFS partition in one fell swoop. When the disk-tape file is closed, z/OS migrates the disk-tape file. Bacula knows what blocks in that disk-tape file belong to which original client file. The next backup brings the selected disk-tape file back online, appends all the data from that backup run to it, and then allows it to be migrated again. So, only one migration per job that uses that particular disk-tape, and you can have as many disk-tapes as you wish (or have disk space to provide). ---------------------------------------------------------------------- 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
