Backup Central

I have two Exchange 2003 servers. I run several types of backups - full
information store, all the mailboxes, just executives mailboxes and a
regular backup of the server. Every job barks about the System State,
and fails. I get everything else, but the system state. My other
backups don't' have a problem with the System State. Any ideas?

Thanks,
Kathy Stewart
Security Analyst
Rodale, Inc.
kathy.stewart < at > rodale.com

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Kathy,

what errors are you seeing?

Matthew Keane

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Kathy,

It would appear that the nsrexchsv.exe is being used to backup the SYSTEM
STATE but that would not work. The exchange binary can only interface
with the Exchange API to get access to the DB.

* exch2003:SYSTEM STATE:\ [4720] [I] 04/04/05 21:00:18 nsrxchsv_ese.exe
Version: 4.1.0.148 Supporting Exchange 2000 and Exchange 2003


What is the saveset for the exchange client?

You should have 2 client definitions, one for the Exhcnage backup where
you have the backup command specified as the nsrexchsv.exe as the
command. The second definition would be the either ALL with a skip
directive for the EXCH DB location, or explicitly define the various
filesystems and system DB's that you need backed up. In the second case,
you would not have a backup command which would assume use of the save.exe
binary.

Hope that helps.


Matthew Keane
MTI | Systems Engineer
(303) 524-1156 (d)
(720) 936-2136 (c)
mkeane < at > mti.com

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Thanks Matthew, I made the change and it worked.

Kathy Stewart
Security Analyst
Rodale, Inc.
kathy.stewart < at > rodale.com
610-967-8876




-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU]
On Behalf Of Matthew Keane
Sent: Tuesday, April 05, 2005 3:27 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] Exchange 2003

Kathy,

It would appear that the nsrexchsv.exe is being used to backup the
SYSTEM STATE but that would not work. The exchange binary can only
interface with the Exchange API to get access to the DB.

* exch2003:SYSTEM STATE:\ [4720] [I] 04/04/05 21:00:18 nsrxchsv_ese.exe
Version: 4.1.0.148 Supporting Exchange 2000 and Exchange 2003


What is the saveset for the exchange client?

You should have 2 client definitions, one for the Exhcnage backup where
you have the backup command specified as the nsrexchsv.exe as the
command. The second definition would be the either ALL with a skip
directive for the EXCH DB location, or explicitly define the various
filesystems and system DB's that you need backed up. In the second case,
you would not have a backup command which would assume use of the
save.exe binary.

Hope that helps.


Matthew Keane
MTI | Systems Engineer
(303) 524-1156 (d)
(720) 936-2136 (c)
mkeane < at > mti.com

Note: To sign off this list, send a "signoff networker" command via
email to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can also
view and post messages to the list. Questions regarding this list should
be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu