I would explain to them very clearly that every backup is equivalent to a full 
backup, but only the files that have really changed, and not just archive bit 
change, are backed up.  Help them understand how TSM tracks every file 
individually and that 30 days retention is more than doable.

Or, you could do what I've done and just tell them that any day of the week you 
do backups, you can restore the server to just what it looked like at the time 
of the backup for that day for all of the 30 days they require.  Then, setup 
the retention for 30 days and 30 versions and you'll be set.  Both of you will 
have what you want and need.  

Many people say "FULL" because that's all they understand.  However, I've never 
seen a regulation that actually stated anything of the kind.

See Ya'
Howard

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Mario Behring
> Sent: Wednesday, March 12, 2008 6:10 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Full policy
> 
> Hi list,
> 
> I have a TSM Server 5.2.2 running on a Linux box.
> 
> There is this customer that have a business requirement of FULL backup
> every day with a 30 days retension period. There are several customers
> attended by this TSM Server. All of them with usual policies.
> 
> Considering that I have an IBM robot with 3 drives and 18 LTO2 slots
> (200-400GB tapes), what should be the best approach to answer this
> customer requirement?
> 
> I´ll have to create a policy just for this customer, as I usually do,
> but I am concerned with backup windows and tha amount of tape I´ll
> need.
> 
> Any help is appreciated.
> 
> Mario
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com