Re: TCP/IP connection failure
1996-09-10 15:37:24
Subject: |
Re: TCP/IP connection failure |
From: |
Lowell Shulman <lowell AT NY.UBS DOT COM> |
Date: |
Tue, 10 Sep 1996 15:37:24 -0400 |
>
> > Has anybody experienced this on a schedule from a sunos client? And why
> > does it take 5 hours to retry?
>
> I haven't.. have you tried an interactive (dsmc incr) backup and
> watched its progress?
>
Interactive and all other scheduled backups worked fine until this one, so
there may have been a network glitch. My concern is why didn't it retry
before the window expired. Five hours seems like a long time before trying
again.
> > 09/10/1996 03:09:49 Session established with server ADSM: AIX-RS/6000
> > 09/10/1996 03:09:49 Server Version 2, Release 1, Level 5.9
> > 09/10/1996 03:09:49 Server date/time: 09/10/1996 03:10:51 Last access:
> > 09/09/1996 17:59:30
> >
> > 09/10/1996 03:09:49 Incremental backup of file system: '/'
> > 09/10/1996 08:09:22 ANS4102I ***** Processed 500 files *****
> ^^^^^^^^
> How large are the files this inspection sees, and how is your
> system set to handle changing-file backups (copy control)? It may be
> that you're trying to backup large files in shared-dynamic mode while
> they're constantly changing.. Are you saturating your # of simultaneous
> clients? Do you have enough licenses (though failure of license is
> probably not a TCP/IP failure)? Is this a regular occurence or a
> one-time (possible equipment or networking) failure?
I checked these items and did not exceed maxsessions or max licences. These
are small files being incrementally backed up at 3AM, so they should not be
changing. Any other thoughts?
>
> > 09/10/1996 08:29:23 ANS4834E Unable to start scheduled event 'DAILY'
> > 09/10/1996 08:29:23 ANS4835E Either the window has elapsed or the schedule
> > has been deleted
>
> This depends on the window your backup schedule has listed.
> Mine's usually 6 hours.
The default - 1 hour.
Thanks, Lowell
lowell AT tkg DOT com The Kernel Group, Inc.
|
|
|