Yo Yo.
Well, I'm not so sure it's a lookup problem. This is only happening on our
level 9 backups. When we run full backups, everything gets backed up ok. I've
even verified this same strange behavior with another user on this mailing list.
Also, I would think that SYSTEM STATE, SYSTEM DB and SYSTEM FILES would all
fail, but on some hosts only the SYSTEM STATE fails and on another host, only
SYSTEM DB fails.
As for the client versions, were running 6.0.1 to 6.1.1! Maybe it's time for
an upgrade! I'll try a re-install first. If that doesn't work I'll try an
upgrade and let ya'll know the status.
Thanks,
-Matt
On Wed, 15 Oct 2003 08:35:42 +0200
Riaan Louwrens <riaanl AT SOURCECONSULTING.CO DOT ZA> wrote:
> Yo,
>
> Ive seen some similar erros before and it has always either been some
> permission / hostname resolution problem (i.e. make sure the account the
> services run under has full access (which it probably does) and that all
> name resolution (both forward and reverse) works from both clients.
>
> Secondly, it sometime, for reasons that I cannot explain needed a re-install
> on the client side (this is fortunately only a 2 minute job).
>
> I'm assuming that you are running 613 ? (Ive had some "unexplicable" errors
> lately which was solved as well by going to latest level) ...
>
> Just a thought.
>
> Riaan
>
> -----Original Message-----
> From: Matt Hemingway [mailto:matt.hemingway AT PCNALERT DOT COM]
> Sent: Tuesday, October 14, 2003 5:46 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] Windows SYSTEM STATE Failure
>
>
> Yo.
>
> I've got a couple Windows clients whose SYSTEM STATE backups fail. Backing
> of all drives on these clients work fine, but when it comes to backing up
> the SYSTEM STATE, I get the following error message:
>
> * client.domain.com:SYSTEM STATE:\ 1 retry attempted
> * client.domain.com:SYSTEM STATE:\ 10/14/03 01:40:38 nsrexec: Attempting a
> kill on remote save
> * client.domain.com:SYSTEM STATE:\ aborted due to inactivity
>
> I've got another Windows client whose SYSTEM DB doesn't get backed up. It's
> the same error message as the above one (just swap STATE with DB).
>
> Ideas?
>
> -Matt
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
