Link to home
Start Free TrialLog in
Avatar of jmatarranz
jmatarranzFlag for Spain

asked on

Database copy status failed

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 for become healthy again.

Thanks in advance
Avatar of Amit
Amit
Flag of India image

Do you have any monitoring for Exchange.
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.
ASKER CERTIFIED SOLUTION
Avatar of Bruno PACI
Bruno PACI
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.
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