I think you were right on track with your suggestion.
Yesterday afternoon the network people did some reconfiguration, and one
of the changes was to set a certain parameter to "auto" (I'm assuming it
was the "auto-negotiate" you were talking about).
Last night the backups went down to about 2:43 (that's 2 min 43 sec)
instead of nearly 3 hours. As I said, even if this error message DOESN'T
come out, we can't PROVE that it fixed the problem (at least, not for a
few months) because it was so sporadic. But if I had to bet on it, I'd be
willing to put a few bucks on it.
Thanks for your response
From:
"Clark, Margaret" <MClark AT SDDPC DOT ORG>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
09/24/2010 02:00 PM
Subject:
Re: [ADSM-L] MSG ANR4724E
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
No idea about ANR4724E, but has the client's network connection been set
to auto-negotiate? That would account for the extended execution time.
- Margaret Clark
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nick Andrelli
Sent: Thursday, September 23, 2010 9:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] MSG ANR4724E
I have an issue while backing up a Windows client.
I occasionally (about once every 3 weeks) receive the following message:
ANR4724E During the backup of node JDCDCA (10) filespace
JDCDCA\SystemState\NULL\System State\SystemState (1) a deletion activity
occurred. (SESSION: 66148)
We have two glaring configuration issues that we are working to correct,
but I wanted to see if anyone else had noticed something along these
lines. Our problems are:
1. Some recent network reconfiguration caused the backups on this
client to extend from less than 10 minutes to almost 4 hours (since
backups run through the midnight hours, they still completed within the
allotted window and no one paid attention to the extended duration). This
happened once before recently, but has been resolved (and we never
received ANR4724E on that system).
With a 4-hour backup window, it is entirely conceivable that something has
been deleted during that timespan, BUT?
However, we have 2 other Windows clients also caught up in the
re-configuration issue that run about the same 4-hour duration and have
never generated error message ANR4724E.
2. The system times on the server and client differ by 10 minutes 32
seconds. I don?t have access authority that would let me check the time
discrepancies between the server and the other clients.
As an old mainframe sysprog, 10 SECONDS difference between machines could
be disastrous, never mind 10 MINUTES. Am I over-reacting to this
discrepancy? Is it really a conceivable trouble point, or can TSM handle
it?
Since the problem is only sporadic, resolving both of these configuration
issues is no proof that either was the cause of the problem. Even without
fixing them, we could go for another 3-4 weeks without seeing a problem.
But I?d appreciate finding out if anyone else has hit this type of
situation before.
|
