We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Solved
Database copy status failed
Posted on 2013-01-08
Hi everybody, I have an Exchange 2010 with 2 mailbox role servers.
¿Is there a script or something similar to prevent when database copy status = failed? Something that execute an Update-MailboxDatabaseCopy
Thanks in advance
¿Is there a script or something similar to prevent when database copy status = failed? Something that execute an Update-MailboxDatabaseCopy
Thanks in advance
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2
- +1
6 Comments
Hi,
If you don't have SCOM, I would suggest you to use some script to get the status of replication at specific interval.
check it here : http://www.stevieg.org/2011/06/exchange-environment-report/
If it is failed try to resume the db copy before trying to update. You have to find some permanent solution, updating db copy each time would not be good if they are across the site.
If you don't have SCOM, I would suggest you to use some script to get the status of replication at specific interval.
check it here : http://www.stevieg.org/2011/06/exchange-environment-report/
If it is failed try to resume the db copy before trying to update. You have to find some permanent solution, updating db copy each time would not be good if they are across the site.
Active today
Hi,
If to automatically reseed database each time the replica fails was a good idea, Microsoft would have integrated this behavior in Exchange...
The problem is that there are many different causes of a replication failure that will not need a full reseed and more than that, forcing a ressed without understanding why the replica failed would lead you to a data lost.
The good idea is to write a script to monitor and to WARN you when something is wrong. But NEVER automate problem resolution because only an admin can understand the problem and choose the correct action !!
Have a good day.
If to automatically reseed database each time the replica fails was a good idea, Microsoft would have integrated this behavior in Exchange...
The problem is that there are many different causes of a replication failure that will not need a full reseed and more than that, forcing a ressed without understanding why the replica failed would lead you to a data lost.
The good idea is to write a script to monitor and to WARN you when something is wrong. But NEVER automate problem resolution because only an admin can understand the problem and choose the correct action !!
Have a good day.
Yes, I go with PaciB. There is no point of reseeding the database without knowing why it got failed. It should be because of Disk, N/W or some other reasons. Try to find out the cause and fix it before reseeding next time.
Active 1 day ago
Writing a PS script is not a big deal, however fixing it without knowing root cause is not a preferred method. Also sometime, there could be cases it might not fix with a script too. Best option is to setup a monitoring alert and take action accordingly.
I would say best is to get a Script that will update you once the DB goes to Failed status ..... or best is to if possible get another Server in DAG for a failover option
I agress somewhat to Amit but one thing is if i have 2 Servers and one has a db failed and sometime later some issues to ServerA DB on ServerB for that DB wont come online :(
- Rancy
I agress somewhat to Amit but one thing is if i have 2 Servers and one has a db failed and sometime later some issues to ServerA DB on ServerB for that DB wont come online :(
- Rancy
Featured Post
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from:
www.mail-signatures…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month12 days, 14 hours left to enroll
650 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.