I am curious why you would have both down at the same time? Every time I have done maintenance on my system I have always left up either the publisher or the subscriber depending on which one I am working on
I guess if you think about what data is being written to the SQL databases it would be the CRD records (unless you are changing things at the moment of power down). CDR records are written via the publisher So you may want the publisher down last. Here is a good question. If I take my publisher down for a reboot what happens to CDR records during this time?
Regarding the CDR records when the Publisher is down. Unless I am mistaken, each Subcriber also holds a CDR database, for just that instance. If the Publisher SQL database cannot be reached, the data is stored in the Subscriber SQL CDR database until the Publisher comes back.
You are correct. Depending on which server the device placing the call is homed to (example: subscriber 1) the server will send the CDR to the publisher on a low priority interval.
This is always the case. The subscribers send their CDR info to the Pub when it is convienient for them to do so. Usually within a minute or so. In the case of the Pub being unavailable, it will wait and try again later.
I believe the CDRs are stored in flat files on the subscriber until the publisher is back online. As far as I can see the subscriber does not have a CDR database. Anyway from CM version 3.2 a subscriber database is read-only.
From a Testing perspective, it depends on what your trying to accomplish. As for the power sequence, shut them all off at the same time, shut them of 1 at a time, try any combination your testplan calls for(of course you have a spare set of mirrored drives of the publisher). I would recommend always bring the pub up first in process of starting a cluster. W2k and SQL well.... you know how that goes.
If you have good backup sti files, and a set of mirrored drives, you could have the cluster back up from a DR test in a matter of minutes!
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.