Failing backup when server is down
1996-11-11 05:23:00
Subject: |
Failing backup when server is down |
From: |
Eric van Loon <evanloon AT KLM DOT NL> |
Date: |
Mon, 11 Nov 1996 11:23:00 +0100 |
Hi ADSM-ers!
I have a ADSM/MVS server with a few OS/2 clients.
Last night we had a network switch and the ADSM server was down during that
switch.
For the nodes that didn't start their backup before the server went down I saw
they were trying to contact the server at schedule execution time, but they
failed (of course, the server is down):
10-11-1996 23:52:28
Executing scheduled command now.
10-11-1996 23:52:29 ANS4942S Session rejected: SNALU6.2 connection failure.
CPIC unable to allocate conversation
The thing I can't explain is that the clients try to re-establish the
connection (every 5 minutes) a couple of time and then the following message
appears:
11-11-1996 01:32:45 ANS4847E Scheduled event 'DAILY_SCHEDULE' failed. Return
code = 1.
11-11-1996 01:32:45 Sending results for scheduled event 'DAILY_SCHEDULE'.
11-11-1996 01:32:45 ANS4942S Session rejected: SNALU6.2 connection failure.
CPIC unable to allocate conversation
At 02:23 the session with the server is re-established but the clients do not
restart their schedule!
I have the backup window started at 21:00, the backup window length is 14 hours
and randomization is set to 50%, so the window is not yet ended.
Does anybody know why the clients do not continue their backup cycles?
Thanks in advance!
Kindest regards,
Eric van Loon
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Failing backup when server is down,
Eric van Loon <=
|
|
|