Re: [Networker] legato + exchange module failing remotely
2006-06-29 12:15:42
On Jun 29, 2006, at 12:03 PM — 6/29/06, bob flynn wrote:
Hi,
I have the following configuration
* Exchange 2003 server
* Legato 7.2.1 Server
* Current Legato client and Exchange module installed on exchange
server.
I can backup the exchange server manually from the command line on the
exchange server.
When I attempt to run a scheduled backup, it fails.
I have verified that the backup of non exchange components works,
so it
seems to be either not parsing the exchange request correctly or its
incorrectly formed on my side.
An example output;
NetWorker savegroup: (alert) Default completed, total 1 client(s), 0
Hostname(s) Unresolved, 1 Failed, 0 Succeeded. (exduba Failed)
Start time: Wed May 31 15:28:34 2006
End time: Wed May 31 15:28:41 2006
--- Unsuccessful Save Sets ---
* exduba:MSEXCH:IS 1 retry attempted
* exduba:MSEXCH:IS save: Diagnostic: This client is not licensed
for VSS.
* exduba:MSEXCH:IS save: MSEXCH:IS: No such file or directory
I think you have to turn off the VSS option. To do this, go into the
exduba client resource and add "vss:*=off" to the save operations field.
You should also check to be sure the account you are using on the
exchange server to run the networker remote service is authorized to
do so. Look at page 107 of the Exchange module administrator's guide
and make sure the account you are using for this purpose has all the
attributes that are listed on page 107.
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|