The way I configured my device pools was something like:<br>
<br>
pub at main site.<br>
<br>
sub A, sub B at main site<br>
Sub C, sub D at secondary site<br>
<br>
I split campus up into two areas, phones in one area go to the main site and in the other go to the secondary.<br>
CCM Groups: ABC, BAD, CDA, DCB<br>
<br>
then based on the primary line of a phone:<br>
ABC = even numbered DN's in main area<br>
BAD = odd numbered DN's in main area<br>
CDA = even numbered DN's in second area<br>
DCB = odd numbered DN's in second area<br>
<br>
this way either site can cover if the other goes offline, and the loads
are relatively well balanced on each server. have a seperate TFTP
Server at the main site that could turn into a subscriber if needed,
and a spare server at the secondary site that could be pub or sub if
needed. Has worked out well so far, havent had to rebuild any servers
yet though (jinx!)<br><br><div><span class="gmail_quote">On 6/26/06, <b class="gmail_sendername">Carter, Bill</b> <<a href="mailto:bcarter@sentinel.com">bcarter@sentinel.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Actually it isn't a bad idea to have drives available for cold standby.<br>IPCC Express cold standby servers will be located at the DR site. The<br>subnet will be extended to the DR site via metro fiber. When the rotate
<br>drives for IPCC they can have standby drives for the DR site.<br><br>I need to think about server placement and groups. I was thinking of<br>the Publisher being a "Glass House" server. CM groups would be<br>
configured with primary and secondary as HQCM02 and DRCM04, or HQCM03<br>and DRCM05.<br><br>Maybe I could do this:<br>Group A - HQCM02, DRCM04, HQCM01<br>Group B - HQCM03, DRCM05, HQCM01<br><br>In this scenario, during a prolonged outage, I could put HQCM01 drives
<br>into the DRCM05 server. Then devices would register to either DRCM04 or<br>HQCM01 server.<br><br>
</blockquote></div><br>-- <br>Ed Leatherman<br>IP Telephony Coordinator<br>West Virginia University<br>Telecommunications and Network Operations