There are hundreds of programs that create tape data sets daily. The most used programs that create tape data sets are FDR, ADRDSSU, FDRABR, DFHSM, IDCAMS, SYNCSORT, IEBGENER, SAS, IBM DB2 utilities like DSNUTILB, and programs like OTDBS008 that invoke backup software.
The tape files created have various expiration dates. Backups taken by DSNUTILB typically expire within a few days, while backups taken by FDR or ADRDSSU could expire in a few weeks or be kept for years. It is usually not worthwhile to upload files with short retentions to the Cloud.
CLOUDVTB utilizes a set of Upload Rules, entered on the CLOUDVTB ISPF panels, that allow the user extensive flexibility on what to select or exclude to be copied to Private Cloud (NFS) Server or to the Public Cloud.
To determine which files get copied, CLOUDVTB applies the criteria in the Upload Rule to the information in your tape management system.
For example, if you create one copy of your backups with FDRABR and that copy is kept onsite, you may want to create a second copy for disaster recovery.
You would only need 2 selection criteria in the Upload Rules Panels to do this:
So with these 2 selection criteria all FDRABR backup tapes that were created within the last 7 days will be uploaded. The default is that if the tape file has already been uploaded it will not be uploaded again. You can also limit the selection to tape files with a certain qualifier within the tape data set name and you could also exclude files that are going to expire within nn days.
The default is that the uploaded tape file will have the same expiration date as the tape file that was copied. If you want to change the NFS/Cloud copy to expire 60 days after the onsite copy change the default 0 below to 60:
Once you have established an Upload Rule, you can use your scheduling software to run the Upload Rule when you want.
|return to CLOUDVTB Introduction|