You might try backing up each mount point as a separate client. You'll need
several dsm.opt files with the proper include and clientname options.

We do this on some of our large Novell clusters treating each volume as a
distinct client.


Gerald Michalak
630-691-4819
gmichala AT us.ibm DOT com



"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 04/06/2006
09:26:09 AM:

> You're right! Started out at v5.3.0 on Win 2003. Have upgraded to
> v5.3.2.2, v5.3.3, and downgraded back down to 5.3.0 to work through
> various issues (win error 1450, insufficient resources). Journaling may
> not be answer either, though I would love for it to be, because there is
> a high degree of file movement on this client (can you say buffer
> overflow?). And oh yes, it is taking its sweet time in file inspection.
> But there has to be way to handle this...
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Prather, Wanda
> Sent: Thursday, April 06, 2006 9:08 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Loaded client/server question
>
> You don't mention what client this is - but the newly released ones
> (5.3.3) support journaling for AIX as well as Windows.
> That might help with the incremental backup issue.  Could be a lot of
> the time is just in navigating the file tree.
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Bell, Charles (Chip)
> Sent: Wednesday, April 05, 2006 5:26 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Loaded client/server question
>
>
> I've posed the sob story on here before, but I have a client that has 39
> NTFS mounts with millions of files on each. When backing this up on an
> incremental basis, it takes multiple days now. Also, the TSM database
> grows at a rapid rate, and I have PMRs open on both issues.
>
>
>
> Now...my question is should I have a separate TSM server serving this
> client or should I have 2 instances? I can't back up this client to the
> current TSM server because we can't continue to feed the Enterprise DB
> for this one client. I seriously need some suggestions and how-to's
> because I've never experienced client behavior such as this.  :-(
>
>
>
> Feel free to email me directly if you have any ideas...
>
>
>
> God bless you!!!
>
> Chip Bell
> Network Engineer I
> IBM Tivoli Certified Deployment Professional (ITSM 5.2)
> Baptist Health System
> Birmingham, AL
>
>
>
>
>
>
>
>
> -----------------------------------------
> Confidentiality Notice:
> The information contained in this email message is privileged and
> confidential information and intended only for the use of the
> individual or entity named in the address. If you are not the
> intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this information is strictly
> prohibited. If you received this information in error, please
> notify the sender and delete this information from your computer
> and retain no copies of any of this information.