I would start by asking the requestor what is the goal???.
What are they (really) trying to accomplish???.

Then look at the features in TSM and try to match the goal/
requirement with the feature.
  (archive, backupset, copypool,mirror'd DB, roll-forward log
   offsite db backups, etc, etc)

Seems really silly, in this day and age, to backup a file
(ie send it over the network, store it in the same onsite pool
and make another copy of it for the offsite pool) if you already
have it.

 Think of all the wasted expire inventory and tape reclamation time it
will take too!

              ... joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley
Private mail on any topic should be directed to :
         joef AT socrates.berkeley DOT edu
 (510)642-7638 (w)  (209)483-JOEF (M)
                             5633
100 1/2 days until retirement!!!!!!


On Tue, 27 Nov 2001, John Naylor wrote:

> Hi all,
> I may be required to implement a weekly full backup for certain of our key
> netware data servers.
> I have used all the arguments against this pointing out that you do not need 
> it
> with the incremental forever philosophy of TSM.
> I have also pointed out that if you do need it, backupsets are the preferred
> alternative.
> However assuming I am forced to go that route I have a few of queries.
>
> Am I correct that you need to set the backup copygroup mode to absolute for
> every management class mentioned in the dsm.opts plus the default,
> before the "full backups", and reverse it back to modified afterwards.
>
> Will the TSM host server still need to produce and send its list of active 
> files
> to the client for comparison purposes, even if only to mark deleted files
> inactive.
>
> Will the absence of file attribute checking on the client make any noticeable
> difference to how long the backup takes.
>
> Thanks
>
>
>
>
>
>
> **********************************************************************
> The information in this E-Mail is confidential and may be legally
> privileged. It may not represent the views of Scottish and Southern
> Energy plc.
> It is intended solely for the addressees. Access to this E-Mail by
> anyone else is unauthorised. If you are not the intended recipient,
> any disclosure, copying, distribution or any action taken or omitted
> to be taken in reliance on it, is prohibited and may be unlawful.
> Any unauthorised recipient should advise the sender immediately of
> the error in transmission.
>
> Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
> are trading names of the Scottish and Southern Energy Group.
> **********************************************************************
>