Hello Anuj,

Shannon's advice is very good; even better, use the GUI, selcting just one
or two usernames.  Get that working before attempting to schedule backups.

In addition:  ensure that the Client on the NetWorker Server is set with the
correct information. In particular, check that the "Backup command" under
the "Remote" tab is correctly set to invoke nsrxchsv.exe.

More complete and informative error messages for Exchange Module are always
found in its private logfile, which is found in nsrxchsv.log in the
...nsr\applogs folder on the Exchange Server.

Make sure that you are doing database backups first -- they are much more
important that mailbox backups.

Thanks,
_Scott

-----Original Message-----
From: Shannon Ward [mailto:sward AT rackspace DOT com]
Sent: Saturday, March 06, 2004 8:21 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Exchange 2003


Haven't worked with the Exchange module yet, but you might try running a
command line manual backup of Exchange from the client (assuming that
there is a command line utility on the client.)  That might produce some
additional troubleshooting messages.

--Shannon Ward


On Sat, 6 Mar 2004 09:57:55 -0000 Anuj Mediratta wrote:

> Hi All,
>
> I am nstalling Exchnage module 4.0, NW 7.1 in a setup using Windows 2003 &
> MS Exchange 2003.
>
> We are able to take the IS group backup but when we try the mailbox backup
> either individual or all mailboxes using the saveste -
> MSEXCH:MB/georger or
> MSEXCH:MB, we get the error -
>
> Feb 28 15:43:19 encorp-bdc: --- Unsuccessful Save Sets ---
> Feb 28 15:43:19 encorp-bdc: * encorpmail.encorpworld.com:MSEXCH:MB/georger
> 1 retry attempted
> Feb 28 15:43:19 encorp-bdc: * encorpmail.encorpworld.com:MSEXCH:MB/georger
> nsrexec: authtype nsrexec
> Feb 28 15:43:19 encorp-bdc: * encorpmail.encorpworld.com:MSEXCH:MB/georger
> savefs: A required privilege is not held by the client.
>
> The networker remote exec services on the exchange server are logged on
> using the Exchange administrator username & password. The remote user
> field
> in the client specification is also using the same administrator
> username &
> password. Removing username & password from remote user field does note
> help. The error remains the same in both cases.
>
> We do not have a dedicated Exchange administrator. The domain
> administrator
> for Windows 2003 controls all Exchange server related activities. Every
> time a new user is created, a new mailbox gets created automatically.
>
> We are unable to locate where to enable any priviledges to this
> administrator & take backups using Legato.
>
> Can some one help me on this?
> regards,
> Anuj
>
> --
> 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=