Don't think that's us as our idletimeout is already set to 3600 and the backup 
always fails after 10-15 minutes.
I suspect it's a Netapp problem.

Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of 
Cameron Hanover
Sent: Thursday, July 29, 2010 1:50 PM
To: [email protected]
Subject: Re: [ADSM-L] SNAPDIFF problems

We were having snapdiff backups show up with Failed 8 under 'q events' until we 
upped idletimeout to 60 minutes.  We didn't test thoroughly, but I believe 
snapdiffs were showing failed when the command session idled out when 
non-snapdiff backups wouldn't show as such.

-
Cameron Hanover
[email protected]

"Our integrity sells for so little, but it is all we really have. It is the 
very last inch of us, but within that inch, we are free."
--Valerie (V for Vendetta)

On Jul 29, 2010, at 4:29 PM, Sheppard, Sam wrote:

> After several stops and starts, I finally managed to get the SNAPDIFF feature 
> to work on our 6.1.3.4 server.  Client is Win 2003 server 64 bit 6.2.0.1. We 
> have been backing up a large Windows file and print store with 5 or 6 servers 
> and having problems with volumes that were too large and with too many files. 
>  These are being migrated to CIFS on Netapp.  The first of these was moved a 
> little over a week ago and was backing up fine using the SNAPDIFF feature 
> until Monday night's backup. This backup failed with:
> 
> ANR0480W Session 503377 for node DPCRCFPUT01 (WinNT) terminated  - connection 
> with client severed. (SESSION: 503377)
> 
> This has been failing ever since; gets the error, restarts then gets the 
> error again after about 10 minutes or so until the window expires.
> 
> This fails consistently with both the scheduled backup and with the command 
> line when the -SNAPDIFF option is specified.  Remove the SNAPDIFF and 
> everything consistently works fine, although it takes a bit longer.
> 
> Any ideas out there?
> 
> Thanks
> Sam Sheppard
> San Diego Data Processing Corp.
> (858)-581-9668
> 
> 

Reply via email to