> Maybe I'm misunderstanding the problem, and making it too simple, but
> when I want to have a client skip its nightly backup for just a night
> or two, I just kill the Networker processes on the client. The backup
> fails, and I get notified about it via the standard notification
> mechanism. It will continue to fail (and notify me) until I restart
> the Networker client software or the machine is rebooted.
>
> Like I said, maybe I'm not getting it, but that seems like a simple
> solution to me...
You are lucky enough to have access to all your clients. Sometimes I do
not (backup for other clients, require administrator rights in AD, ...)
Another technique (at least on a unix server) is to create a temporary
entry in the /etc/hosts file with the client name pointing to a bogus
address. The connection will fail in a similar manner, and you don't
have to touch the client.
--
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|