I thought about archives too but this would be causing bandwith problems (less 
then 1 Mbps) with remote WAN sites. The first incremental 'full' backup will 
take a rather long time, but the bandwith could be increased then as this 
happens only once. And the TDP backups must be included too.
 
Using other TSM nodenames to generate new full backups is a possibility too, 
but the bandwiths at the remote site won't allow it.
 
That is why the option to generate full backups out of the primary storage pool 
seems to be the only valid workaround for the customer's requirement. So is a 
backupset the only possibility to achieve this? And would it be feasible for 
both the file system backups and TDP backups of the clients? 
 
I've always considered backupsets as something that would be created if a large 
restore must be done at a client that has a low bandwith with the TSM server. 
You generate the backupset on the TSM server, copy it to your laptop and go 
yourself then to te remote site to perform the restore from the backupset. But 
I did not think about them yet as a solution to create 'full' backups for 
offsite storage.
 
best regards,
Kurt

________________________________

Van: ADSM: Dist Stor Manager namens Stapleton, Mark
Verzonden: di 13/09/2005 23:35
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: [ADSM-L] generate full backup using backupsets



From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of Kurt Beyers
>Due to SLA agreements a full backup should be taken every
>month that is stored offsite for a year. Of course this does
>not match with the principles 'incremental forever' and the
>versioning defined in the management classes.
>
>I guess that a full backup can be created from the backups
>already residing in the primary storage pool using a backupset.
>
>Would such a setup be feasible for 75 clients (load on the TSM
>server, required time to generate the backupsets, ...)? Can it
>be used for backups from a TDP too? Any howto's for the
>creation of a backupset?

A suggestion:

Run a full archive of 3 clients each day for a month, so that you can
spread out the 75 full backups. Set your archive management class to
keep any given archive for a year. Send those archives to a (small) disk
pool which in turn is migrated to an archive tape pool. Once a month
check those archive tapes out and vault them. After a full 12 months in
the vault, that month's tapes can come to the TSM server as scratch
tapes.

--
Mark Stapleton (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
  Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Office 262.521.5627