Exchange Server Forums

Clusters, Backups etc

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Information Stores >> Clusters, Backups etc

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Clusters, Backups etc - 1.Aug.2008 12:00:04 PM

jamesramesys

Posts: 2
Joined: 28.Jul.2008
Status: offline

Hi All

I have been having an issue with backups of an IS where the VSS writers fail. The errors are as per the article below

http://support.microsoft.com/kb/933779

If i run the command on a cluster will it work? If not do I run it on the cluster or on the nodes?

All help greatly appreciated

James

Post #: 1

Featured Links*

RE: Clusters, Backups etc - 3.Aug.2008 6:08:43 PM

jveldh

Posts: 640
Joined: 12.Apr.2008
From: The Netherlands
Status: offline

James,

It depends on what kind of cluster you have, if you have an active-passive cluster you will need to run it on the active node if you have an active-active cluster you will need to run it on both nodes if the error is on both nodes.

_____________________________

Best regards,

Johan Veldhuis

Visit my website

(in reply to jamesramesys)

Post #: 2

RE: Clusters, Backups etc - 5.Aug.2008 3:47:35 PM

consultOz

Posts: 901
Joined: 11.Mar.2005
From: Virginia, USA
Status: offline

Your active node will have the resorces, most likey you will work on the active node) You run it against the database not to the node itself

You need to schedule downtime to do this and will run the eseutil /mh against the databases ( most likely sitting on SAN - LUN) on the SAN.
If the state is dirty shutdown , you will have to repair the databases.
eseutil /p against the databases priv1.edb and pub1.edb
eseutil /d a defrag on the stores.
isinteg (isinteg -s servername -fix -test alltests)
Mounted the stores at the end. If you search you will see bunch of posts in regards to dirty shutdown and hopefully you will get clean shutdown on all the databases.
--oz

_____________________________

Good luck and Best Regards
Oz Ozugurlu
MVP (Exchange)
MCITP (EMA),MCITP (EA), MCITP (SA),
MCSE 2003 M+ S+, MCDST
Security+, Project+ ,Server+
http://smtp25.blogspot.com (Blog)

(in reply to jveldh)

Post #: 3