We are taking a look @ our policies .  Our Customers  don`t understand the
difference between archive and backups in TSM  . According to them Archive
=full backup   and regular backup is incremental backup    ,but  they
don`t need archive everyday as long as they get what they ask from backups
.
I am trying to convince them that even though regular backups are
incremental , we are  keeping versions of files so that we can restore
your data at any given point . It will take some time  for them to
understand TSM because they are coming from netbackup -  (full /
differential and incremental ) vs TSM policies .

Archives are causing DB to grow -for this week I have changed from Archive
to Incremental - added some more disk space .

Thanks all .




"Shamim, Rizwan (IDS EMEA)" <ShamiRiz AT EXCHANGE.UK.ML DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/19/2003 10:19 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: TSM DB growing @1.5Gb /2 day ??






Your archiving process is causing your DB to grow.  We have a requirement
(7
year retention).

The databases on 3 of our TSM servers are between 185-140GB.  We now run
monthly incrementals - it satisfies our requirements and it works for us.


   ________________________________
    Rizwan Shamim
    Central Backup Service (CBS)
    Merrill Lynch Europe PLC
    Tel: 020 7995 1176
    Mobile:     0787 625 8246
    mailto:rizwan_shamin AT ml DOT com

    Please click on
http://www.ml.com/ukregulatorynotices/uk_regulatory.htm
for important disclosures.

> -----Original Message-----
> From: shekhar Dhotre [SMTP:Shekhar.Dhotre AT LENDLEASEREI DOT COM]
> Sent: Monday, May 19, 2003 3:07 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      TSM DB growing @1.5Gb /2 day ??
>
> Hi all ,
>
> On one of our   TSM  server(Sydney)  database is growing  1.5 GB in 2
> days???  (AS per AP-TSM admin).   What could be the reasons? He is
saying
> that it is happening because  of  archive operations  and  unload
/reload
> will solve problem  . I am going through TSM manuals to find out root
> cuase, meanwhile any thoughts on how to resolve this problem. DB size is
> 160GB (aprox) .
>
> His comments :
> >1) AP(Asia Pacific)  TSM: TSM db @ 99% utilsation - extended database
by
> 1.5Gb (very last space) -This will buy us 1-2 days by which we need to
get
> more disk in place.
>
> Thanks
> SD
> Atlanta ,GA.
>