Well, I'd say that you are doing great right now, if you can do a DB backup of 350 G from a Windows box in an hour and 15 minutes!
The biggest problem you are likely to have, as mentioned, is the time it takes to do the conversion to 6.1 (or in the unlikely event you have a problem and need to do a DB audit before you get to 6.1). Here's something that might be useful, depending on your circumstances. If you look at the Occupancy table, it shows not only the amount of storage occupied by your clients, but the number of objects retained for each. Sum the objects for each client, and sort by client in descending order: select node_name, cast(sum(logical_mb/1024) as decimal(10,1)) as "GB" , sum(num_files) as "#Objects" from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='PRIMARY') group by node_name order by 2 desc. At some of my customers, we find that there are just a handful of nodes responsible for 30-40% of the DB objects (imaging apps are usually the biggest offenders). If that is the case for you, that's a logical way to start splitting out your DB, by splitting out a handful of big (in terms of objects) clients. And if it's only a handful of nodes, I suspect it would also be the way that would have the least impact on de-dup. W On Thu, Dec 4, 2008 at 11:18 AM, Conradt, Jeremy < [EMAIL PROTECTED]> wrote: > Expiration takes about 1 hour. DB Backup takes about 1 hour 15 minutes. > > Thanks, > Jeremy > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Wanda Prather > Sent: Wednesday, December 03, 2008 7:01 PM > To: [email protected] > Subject: Re: [ADSM-L] Database size, Split to multiple instances or wait > for version 6.1 > > How long does it take you now to do Expiration and DB backup? > > > > On Wed, Dec 3, 2008 at 4:24 PM, Conradt, Jeremy < > [EMAIL PROTECTED]> wrote: > > > I have a TSM server currently running version 5.3.5 on Windows 2003 > > that we plan to upgrade soon. > > The problem I have is our database has grown to 350 GB. > > The question I have is will version 6.1 of TSM be better capable of > > maintaining a database this size and much larger or should I break it > > apart? > > I would rather keep everything together so we can make better use of > > de-duplication that may be coming out with version 6. > > Thanks, > > Jeremy > > > > > > >
