HI,
Here I am sharing my experience and troubleshooting on one of the abnormal issue.
Source Of issue :- On Saturday we generally have a application mock testing. and one of the database is set in mirroring between DR & PR Site for any BCP and disaster recovery.
For mock purpose we break the mirroring and use DB as standalone instance. After completion of mock testing we restore previous state backup and reconfigure mirroring between PR and DR.
This time we are unable to set mirroring and giving error, "Unable find destination Path"
DR server is up and running properly. we try to browse shared resources but its gave same error.
We are quite confused because nothing is change on DR DB server.we try to access dr server from other servers and from AD server but no luck.
After investing more than 3 hours I came to know that in DNS server there are 2 hostname with same IP address same as DR server IP.
Actually long time back we had formatted DR DB server and put different hostname. so now issue is clear,
We have deleted old DNS entry and refresh computer account of current DR server (Do not delete both account if do you have to rejoin server in AD)
after replicating changes across all domain. we are able to browse the resources and Mirroring as well.
Conclusion is :- issue start with SQL database mirroring and end with DNS stale record i.e. human error.
Here I am sharing my experience and troubleshooting on one of the abnormal issue.
Source Of issue :- On Saturday we generally have a application mock testing. and one of the database is set in mirroring between DR & PR Site for any BCP and disaster recovery.
For mock purpose we break the mirroring and use DB as standalone instance. After completion of mock testing we restore previous state backup and reconfigure mirroring between PR and DR.
This time we are unable to set mirroring and giving error, "Unable find destination Path"
DR server is up and running properly. we try to browse shared resources but its gave same error.
We are quite confused because nothing is change on DR DB server.we try to access dr server from other servers and from AD server but no luck.
After investing more than 3 hours I came to know that in DNS server there are 2 hostname with same IP address same as DR server IP.
Actually long time back we had formatted DR DB server and put different hostname. so now issue is clear,
We have deleted old DNS entry and refresh computer account of current DR server (Do not delete both account if do you have to rejoin server in AD)
after replicating changes across all domain. we are able to browse the resources and Mirroring as well.
Conclusion is :- issue start with SQL database mirroring and end with DNS stale record i.e. human error.
No comments:
Post a Comment