Thanks, I'll check into the virus scan and memory.  As for the snapshots, no we 
are not backing them up.  I think we may look into that in the future but I was 
told we did not purchase the tools required to backup the snapshots.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Matthew Glanville
Sent: Monday, July 09, 2007 3:49 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] netapp backup taking too long


Sounds to me like the TSM Client, a Windows 2003 server needs to have more
memory.
Or it's virus scanning the file share as it's backing it up.

Also look into the 'snapshots' that NetApp may be doing on the file
shares.
Are you also backing up them in addition to the current data?

That could easily quadruple the amount of data backed up with TSM of a
NetApp share.

Having TSM only backup the 'nightly.0' 'snapshot' or some such could work
too, I think, for a nice consistant TSM backup of a NetApp

Matt G.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/09/2007
04:14:50 PM:

> I have a netapp share that is being backed up through a Windows 2003
> server and is taking 23-25 hours to run.  It is on a gigabit
> network, processing approximately 3.9 million items.  Does anyone
> have any suggestions how to accelerate this job?  Max mount
> points=7, resourceutilization=7, memoryefficientbackup=no.  All of
> the netapp shares back up through this one server but this is the
> only one that is this large.  The sys admin setup several batch jobs
> that start separately so that more than one backup can run at one
> time. My TSM server is on AIX 5.3, TSM 5.3 with a 180Gb database,
> 87.2% utilized so I am hesitant to do anything that will further tax
> the server.   Any ideas how I can back this up faster without
> stressing the server?  Thanks.
>
> Debbie Haberstroh
> Server Administration
> Northrop Grumman Information Technology
> Commercial, State & Local (CSL)