[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

342.0. "Problems with "Skip" schedule" by TRN02::FRASSINO () Wed Jan 22 1997 13:41

T.RTitleUserPersonal
Name
DateLines
342.1DECWET::RANDALLThu Feb 06 1997 11:0210
Pierpa,

It would be helpful to know version information, but in my tests with
Networker V4.2B the client was not contacted on days where skip was in
the schedule.

We would need exact error messages, and version information to go any
further on this.

-- Rich Randall
342.2V3.2 +patches is used.TRN02::FRASSINOThu Feb 13 1997 10:1810
342.3Please respect 80 column limitsDECWET::KOWALSKITime's not for savingThu Feb 13 1997 10:2020
              <<< DECWET::DOCD$:[NOTES$LIBRARY]NETWORKER.NOTE;1 >>>
                                 -< NetWorker >-
================================================================================
Note 342.2                Problems with "Skip" schedule                   2 of 2
TRN02::FRASSINO                                      10 lines  13-FEB-1997 10:18
                          -< V3.2 +patches is used. >-
--------------------------------------------------------------------------------
Rich,

actually my customer is using a v3.2 + patches ( so v3.2A ). The customer has
noticed this behaviour seeing the savegroup completion mail message. If a
machine with skip schedule is not available on the network, the mail says
connection timed out. From this the customer derives that the server contact
the client even if it is not necessary, due to the skip schedule. I`ve not
error message, apart this "connection timed out" on the mail. Thanks in advance
for any clarification.

			Ciao,
				Pierpa
    
342.4DECWET::RANDALLFri Feb 14 1997 13:258
Pierpa,

It appears that there is a difference between 3.2A and 4.2A-B.  When I ran 
the same test using 3.2A I got error messages saying that the client was
not available even though the client was supposed to be skipped.  So if 
this is a problem then I suggest upgrading to V4.2B.

-- Rich Randall