Title isn't that great, so feel free to change. Basically, I will describe an issue we had this week. I want to get responses from everyone on what you would have done in the scenario. I won't post what we did at first, but will later on. Scenario: If anyone would like more details, let me know. Additional Information:
|
Heres what I did... As soon as the database went down, make sure the replication service was stopped and wouldnt start until I wanted it to. Find the cause of the problem. I was able to get a backup by restarting the database and triggering the event. Once this was finished, I worked on the backup to test, which my first step was running dbvalid against it. I found it was a heavy populated table (in our world, at least). Naturally, as soon as it tried to validate that table, the backup db crashed. Now, I know what table it is, but range of data is it? I followed the Sybase technical document to figure that out (took forever). Once I knew exactly where the problem was, I unloaded every bit of data I could. What I couldn't get from this database, I was able to get from the one site that replicates all data. So. Now I know where the problem is, and I have the data to rebuild. What next? Remove said table from all publications. Create a new table Create new publication with just this table, subscribe all the sites, and simply 'start' them (Not Synchronize). |
Question 1: Are you using SQL Remote or MobiLink to synchronize with your remote sites? Question 2: Do you have a recent backup at the central site?
Its always useful to know the exact version and build number and in the case of assertion(s) the exact assertion number and message. Without this information, it is impossible to make any suggestions.
In addition, are the assertions seen on the consolidated, a single remote, or multiple locations?
And more questions: If your consolidated is corrupt (so you might need a backup), when have your remotes replicated the last time? IMHO, the question who many remotes would be out-of-sync if a backup at the cons must be restored is one of the most important ones...
I think I have answered all the questions so far.
Retag remark: I just think that this is very related to SQL Remote (or replication in general) so I added that tag (and had to remove "backup-and-recovery"). Restoring a not-replicated database is so much easier...
@Calvin: I wanted to change the title, and I wanted to change the tag what-would-you-do-if... but at 100+ views you can't argue with success! Now I think the title and the tag are brilliant!