Exchange Server Forums

SCR Information Store

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> High Availability >> SCR Information Store

Page: [1]

Message

<< Older Topic Newer Topic >>

SCR Information Store - 1.Nov.2011 4:03:13 PM

doohder

Posts: 30
Joined: 31.Jan.2007
Status: offline

This may be a dumb question but I can't seem to find this cleanly documented anywhere. I have implemented SCR to our backup datacenter test-replicationhealth shows that replication is working flawlessly. One thing I noticed after restarting the server at the backup datacenter is that the "Microsoft Exchange Information Store" will not start. I assume that this is a expected result since the Store Groups arne't actually presented to these servers to mount. I would assume after doing a failover and Store Groups get presented that the service would start find.

Is this expected behavior for this service to not be running on the SCR targets?

Thanks,

Post #: 1

Featured Links*

RE: SCR Information Store - 1.Nov.2011 4:30:34 PM

doohder

Posts: 30
Joined: 31.Jan.2007
Status: offline

Also keep in mind that I removed the default Storage Groups that get installed during setup. This mean ESM show no store groups.

(in reply to doohder)

Post #: 2

RE: SCR Information Store - 2.Nov.2011 10:38:59 AM

troy12n

Posts: 166
Joined: 1.Oct.2007
Status: offline

That is NOT the expected behavior.

Let me ask one question though. Are you replicating the "first storage group" from your SCR source? If so, that is not a recommended config.

You should create additional storage groups and 1 database per storage group and SCR them to the SCR target.

On my SCR Targets (many to few), the "First Storage Group" is the only database mounted, the rest stay dismounted until (hopefully never) needed. But the info store service should be running. The reason for this is the system attendant runs from the first store.

Check your event logs for info into why your store service is not starting or crashing.

(in reply to doohder)

Post #: 3