CCM3.3 Publisher Server Dead (Oh Poo !) 1

[IanHeadley]

CCM v3.3 cluster of two servers, publisher and subscriber, returned from holidays to find the main publisher server had also gone on <permanent> holidays.

Got everything working on the subscriber now BUT the database that is held on the subscriber is a read only version of the phone settings etc. and cannot be amended.

Question is : Can a subscriber server be promoted to a publisher server and if so, how ?!!?!? Doing this will enable me to drop in another subscriber server as the other is completely dead, but only after promotion of the original subscriber.

Thanks, in advance.

 

[pndscm]

I don't think the Subscriber is 'promotable'. Rebuild the Publisher and restore from the backup, then rebuild SQL replication. There is very good documentation for doing SQL fix from Microsoft.com. I had a similar situation when a customers Publisher hard drive went progressivly worse until it died. Unfortunately, it was backing up bad data so my backups were corrupt also. I had to build a new Pub then re-program it offline while looking at the Subscriber. After it was re-built, I then put it online and re-built the SQL replications. Not a fun 20 hours, but the customer was never OOS for any length of time.