Why not use the Archive function instead of the backup function?

Then you can schedule a move into a single archive which is the same as
creating a gzip file, and then let your tape drives compress the data.
Granted it may not be as good as gzip, but it's much easier to use.
Then you can set retention for the whole archive, TSM will manage the
package as one object, and as I said before you can move the files into
the archive, and life is good.

See Ya'
Howard


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Conway, Timothy
> Sent: Wednesday, October 01, 2008 3:10 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] stdio and baclient?
> 
> I've searched carefully, but maybe I've failed to come up with good
> search strings, so in case anybody knows of some non-intuitive
options,
> or maybe even a small third-party interface through the API...
> 
> I've got data sets that I need to retain for 53 weeks as complete
> copies.  They're copies of informix databases - about 1GB per copy.
> gzip significantly beats TSM compression, and I could cut the number
of
> objects to keep in the database by 389%, but I can't count on having
> room for a tempfile
> I'd like do something like this:
> 
> tar -cf - carma.dbs |gzip -9|dsmc ar $PLANT.`date +%Y%m%d$H`.db.tar.gz
> -filehandle=0 -archmc=plant_53week
> 
> Instead of this:
> 
> tar -cf - carma.dbs |gzip -9>$PLANT.`date +%Y%m%d$H`.db.tar.gz;dsmc ar
> $PLANT.`date +%Y%m%d$H`.db.tar.gz -archmc=plant_53week -filesonly
> -deletefiles
> 
> I figure I'm just smoking crack, but might as well ask.
> 
> 73,
> 
> Tim Conway
> sysadmin, TSM admin
> Swift & Company
> 9705067998