My SCR target server ran out of space and SCR failed and I didn't catch it for a couple days... I freed up space but replication still will not start. The first errors were: Event ID 454 ESE Unexpected Error -1014
Proceeded to: Event ID 2097 MSExchangeRepl Out of page buffers...
And finally: Event ID 2074 MSExchangeRepl
I freed up the space and the only error I get now is the 2074 error... It looks like the log shares are there and available but my target server is still complaining. I guess my question is; Is my situation recoverable or do I have to scrap and restart?
Another question though... I just attempted to disable and I got an message stating that SCR isn't enabled on the storage group... If I do a status on the server I get the following.
Get-StorageGroupCopyStatus : Microsoft Exchange Replication service RPC failed : Microsoft.Exchange.Rpc.RpcException: Error e0434f4d from cli_GetCopyStatusEx at Microsoft.Exchange.Rpc.Cluster.ReplayRpcClient.GetCopyStatusEx(Guid[] sgG uids, RpcStorageGroupCopyStatus[]& sgStatuses) at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.InternalGetCopyS tatus(String serverName, Guid[] sgGuids, RpcStorageGroupCopyStatus[]& sgStatuse s, Int32 serverVersion) At line:1 char:27 + get-storagegroupcopystatus <<<< -standbymachine XXXXX
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
If you can't remove it naturally I'd just go through the processes on the web to kill it. SCR has always stunk and tearing it out after it's gone south has never been pretty.
If you can't remove it naturally I'd just go through the processes on the web to kill it. SCR has always stunk and tearing it out after it's gone south has never been pretty.
I dont necessarily agree with that.
All you have to do is disable-storagegroupcopy, then re-set it up using the -DeleteExistingFiles switch.
The interface may not be pretty and failing over / back is a very manual process, but SCR was a quantum leap from what was there before (nothing). And it works 100% of the time. I have only had it fail replication on a couple storage groups in the almost 5 years I have had 2007 up in my org. The symptoms of SCR having issues are pretty obvious if you are looking (backups fail for that store is the first symptom) and if you run get-storagegroupcopystatus regularly (like you should), you are clued into issues if they exist quickly so you can fix. Re-seeding a storage group copy is a trivial thing to do, and even if your DB is HUGE it is not that long to do, assuming you have a somewhat decent pipe.
Are DAG's better? Probably... actually most likely, definetly. But not everyone is on an EA and can afford to rip and replace every time M$ comes up with a new version. There really arent that many compelling reasons for 2007 customers to make the leap to 2010, that's why we are holding out for the 2013/14 version of Exchange.
< Message edited by troy12n -- 20.Mar.2012 9:54:59 AM >
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> High Availability >> SCR Target ran out of space 
SCR Target ran out of space - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
