<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV id=idOWAReplyText20255 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Are all the CM's 7835's or
better?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I would be temped to pull at drive out of
all CM's (subs and pubs at all locations) leave everything running then once the
drive got to the new location (New server at new location) have everyone put in
the pulled drives. That way the call managers would all be on the same
page with out loosing EM, Forwarding, etc. you would just loose the
changes that day because you would overnight the drive of course.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Scott</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net on
behalf of Lelio Fulgenzi<BR><B>Sent:</B> Sat 1/14/2006 10:57 AM<BR><B>To:</B>
Bob A. Bowie<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] CM4.1.3-move publisher<BR></FONT><BR></DIV>
<DIV>
<DIV><FONT face=Arial size=2>I think people have demonstrated with success the
ability to change an IP address, which may or may not be required in your case.
So you should be OK there. The two things I would worry about are the length of
time your publisher will be down and the features that are unavailable for that
time, i.e. forwarding/unforwarding of phones, extension mobility, IPCC agent
logings, etc. Database replication is another issue, the subscribers can get
into some state of disarray if the publisher is not available for an extended
period of time. I think a restart of the cluster and/or using the DBLhelper tool
may help you here.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The most important thing is the latency between the
sites. A distributed cluster requires a specific maximum roundtrip delay between
cluster members so as long as that is OK, you should be good to go.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT><BR>On 1/14/06, Bob A. Bowie <<A
href="mailto:bababooey@cox.net">bababooey@cox.net</A>> wrote:<BR>> Here is
a summary of what we're doing, if I move the publisher server, the<BR>>
locations are in different areas of the US,<BR>> so the publisher would be
offline a couple of days to physically transport<BR>> which I don't believe
is desirable.<BR>><BR>> To clarify my situation, my company has three core
sites and multple wan<BR>> sites.<BR>> The three core sites contain the
call managers, and one core site the<BR>> publisher.<BR>> We have aquired
new office space with state of the art data center facilites<BR>> and will
become a<BR>> core site. This new site is the optimum site for the
publisher server and I<BR>> will install a call manager suite there.<BR>>
The current publisher though exists at a core site that is not desirable,
so<BR>> I want to move the<BR>> publisher server to the new
location.<BR>> What do you think my best option is in this
case.<BR>><BR>><BR>><BR>> ----- Original Message -----<BR>> From:
"Wes Sisk" <<A href="mailto:wsisk@cisco.com">wsisk@cisco.com</A>><BR>>
To: "Bob A. Bowie" <<A
href="mailto:bababooey@cox.net">bababooey@cox.net</A>><BR>> Cc: <<A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>><BR>>
Sent: Saturday, January 14, 2006 12:08 AM<BR>> Subject: Re: [cisco-voip]
CM4.1.3-move publisher<BR>><BR>><BR>> > please tell us a little more
about what you are trying to do.<BR>> ><BR>> > it is not possible to
'promote' a subscriber to become a publisher.<BR>> ><BR>> > it is
possible to take a BARS backup of your existing publisher,<BR>> >
reinstall the OS and all same version of CM software, install BARS,
then<BR>> > restore your BARS backup. the restore will
re-establish connections and<BR>> > replication between pub and
subs.<BR>> ><BR>> > it is possible to physically move the publisher
CM server.<BR>> > it is possible to change the IP of the publisher to move
it to a<BR>> > different network.<BR>> ><BR>> > what do you
mean by 'move'?<BR>> ><BR>> > /Wes<BR>> ><BR>> ><BR>>
> On Jan 13, 2006, at 12:09 AM, Bob A. Bowie wrote:<BR>> ><BR>> >
Is it possbile to change which server is the publisher in a call manager<BR>>
> cluster?<BR>> > Is it reliable and is there a procedure anywhere on
CCO?<BR>> ><BR>> > Also, do you have to make changes and do
adminsitration from the<BR>> > publisher<BR>> > server only<BR>>
> or do changes made on a subscriber get updated to the publisher?<BR>>
><BR>> > Thanks,<BR>> > Bob<BR>> ><BR>> ><BR>>
> _______________________________________________<BR>> > cisco-voip
mailing list<BR>> > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
><BR>> ><BR>><BR>><BR>>
_______________________________________________<BR>> cisco-voip mailing
list<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
<A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR><BR><BR>--<BR>Ed
Leatherman<BR>IP Telephony Coordinator<BR>West Virginia
University<BR>Telecommunications and Network
Operations<BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></DIV></DIV></BODY></HTML>