>Yes, but I get the impression from Renata's post that the job
>accually succeeds and a key skew would cause the backupsys to fail.
Yes, the job does succeed. In fact, I was not clear enough on this
in my initial plea for help, the funny kvno message is not
consistent. It appears to happen for the majority of backupsys runs
for a few weeks and then it won't happen at all for a few weeks. We
run backupsys with no arguments (other than localauth) from our
system control machine.
>I have seen some cases where the problem is configuration and we
>spend alot of time digging in the code looking for a nonexistant
>bug.
I can certainly appreciate that. Unfortunately I believe our
configuration does check out. Our encryption keys are identical on
each server and each keyfile has the same date of the last key
change, some months ago. There appear to be no 'extra' keys. We
also checked out the other items in your list and they all appear to
be correct and consistent. The suggestion about time is one we will
have to monitor. I received a response from another Transarc person
who is familiar with the existence of this problem at another site,
has a TR item going on it, but has not been able to come up with any
solutions. He has not been able to reproduce the problem.
>Then also try a few more tests to see if this only happens on the
>one machine and if it only happens with the one command.
What do you mean by 'one command'? We have not seen any problems
with any other commands, if that is what you are asking.
I thank all of you who are responding for your help.
