jschaddock
Programmer
Hello,
I am a SQL DBA and this weekend we had a contingency test to switch the live SQL server from our live server to our contingency server. As part of the test, we stop and disable all replication agent jobs and once the test is finished (and the user have verified that the data is the same) we re-enable the replication agents and start them running. This is not done by myself or my colleagues but is done by our company's contingency department using procedures that we give them.
What happened this weekend was that when my colleague went to re-enable the replication jobs after the test he found that all the publications had been deleted! We have asked contingency whether they did this and they are adamant it was not them and as I know it wasn't us then I am looking for possible reasons for publications to just be deleted for no apparent reason.
From looking at the SQL logs it seems that contingency re-booted the server at least 3 times in a short space of time (I do not know why) so I was wondering if this could be a reason. I have now re-established replication and the agent jobs have all been named with the numbering of jobs starting at 1 as if this is the first time replication has ever been established on the server. The distribution database is also showing as only being created over the weekend when we have had replication running for over 2 years.
Also, looking at the error logs, there are a few alerts saying master database ran out of log space (although when I check the drive with the logs it has plenty).
This all sounds like a hardware issue or issue with the SQL server package but has anyone else had similar problems?
Thanks
J
I am a SQL DBA and this weekend we had a contingency test to switch the live SQL server from our live server to our contingency server. As part of the test, we stop and disable all replication agent jobs and once the test is finished (and the user have verified that the data is the same) we re-enable the replication agents and start them running. This is not done by myself or my colleagues but is done by our company's contingency department using procedures that we give them.
What happened this weekend was that when my colleague went to re-enable the replication jobs after the test he found that all the publications had been deleted! We have asked contingency whether they did this and they are adamant it was not them and as I know it wasn't us then I am looking for possible reasons for publications to just be deleted for no apparent reason.
From looking at the SQL logs it seems that contingency re-booted the server at least 3 times in a short space of time (I do not know why) so I was wondering if this could be a reason. I have now re-established replication and the agent jobs have all been named with the numbering of jobs starting at 1 as if this is the first time replication has ever been established on the server. The distribution database is also showing as only being created over the weekend when we have had replication running for over 2 years.
Also, looking at the error logs, there are a few alerts saying master database ran out of log space (although when I check the drive with the logs it has plenty).
This all sounds like a hardware issue or issue with the SQL server package but has anyone else had similar problems?
Thanks
J