Wildgen
asked on
DAG DB Copy will not seed.
All of my replicas in the DAG have failed and are suspended. Trying to reseed but get:
"A source-side operation failed. Error An error occurred while performing the seed operation. Error: A timeout occurred while communicating with server 'EXCH01. Error: "A connection could not be completed within 15 seconds."
Suggested help link goes to unavailable document.
"A source-side operation failed. Error An error occurred while performing the seed operation. Error: A timeout occurred while communicating with server 'EXCH01. Error: "A connection could not be completed within 15 seconds."
Suggested help link goes to unavailable document.
ASKER
Thanks for the articles.
My issue is the Cluster Network failed.
Replication service is running on all servers and on the PAM. We only have two servers at this time.
My issue is the Cluster Network failed.
Replication service is running on all servers and on the PAM. We only have two servers at this time.
Wildgen: Run the below commands and tell me what shows Offline as we have to run a command to bring it Online
cluster group
cluster res
Cluster res "ResourceName" /Online
- Rancy
cluster group
cluster res
Cluster res "ResourceName" /Online
- Rancy
ASKER
The replication issue has been resolved. Seems that the DC that held the schema needed to be cycled. We had recently gone to Win2k8 native mode and the schema master had not been cycled. We were experiencing all sorts of authentication issues so we cycled that box and all of the connections came back.
Now proceedng to reseed the Exchange DB's.
The Cluster Network was reporting as failed because we have configured an additional network for future use in a DR site for replication and it is not ready yet. That was not causing the issue.
I do have a question on the reseed. On some of the DB's, typically the bigger ones around 30gb with large Q length, after the reseed complets it reports as Resynchronizing. Others finish as Healthy. Will the Recynch clear up eventually?
Now proceedng to reseed the Exchange DB's.
The Cluster Network was reporting as failed because we have configured an additional network for future use in a DR site for replication and it is not ready yet. That was not causing the issue.
I do have a question on the reseed. On some of the DB's, typically the bigger ones around 30gb with large Q length, after the reseed complets it reports as Resynchronizing. Others finish as Healthy. Will the Recynch clear up eventually?
Good to know something wasnt know ..... Resolved is always matched with Relief !!
On some of the DB's, typically the bigger ones around 30gb with large Q length, after the reseed complets it reports as Resynchronizing. Others finish as Healthy. Will the Recynch clear up eventually? - Yes it should as maybe they are after reseeding the DB try to copy over the logs as well.
- Rancy
On some of the DB's, typically the bigger ones around 30gb with large Q length, after the reseed complets it reports as Resynchronizing. Others finish as Healthy. Will the Recynch clear up eventually? - Yes it should as maybe they are after reseeding the DB try to copy over the logs as well.
- Rancy
ASKER
Rancy, you are correct. Relief is just a reboot away.... All report Healthy now.
Is there a script that can be run to provide a notification of the replication status. I was thinking about a PS script that could run as a scheduled task and send a daily email alert to an admin.
Thanks.
Paul
Is there a script that can be run to provide a notification of the replication status. I was thinking about a PS script that could run as a scheduled task and send a daily email alert to an admin.
Thanks.
Paul
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the links.
ASKER
Where do I look to fix that?