Edit, step 6 <i>should</i> read <br>6 - DRS restore of 8x backup to <b>UCS</b> server<br><br clear="all">Matthew Saskin<br><a href="mailto:msaskin@gmail.com" target="_blank">msaskin@gmail.com</a><br>203-253-9571<br><br>
<br><br><div class="gmail_quote">On Thu, Mar 31, 2011 at 3:25 PM, Matthew Saskin <span dir="ltr"><<a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Fastest way to do it (per cluster) in my opinion:<br><br>1 - Acquire spare MCS server<br>2 - Implement change freeze on CUCM cluster in question, start cataloging "emergency changes" that are made<br>3 - Perform DRS backup of Publisher, DRS restore to spare MCS server<br>
4 - Upgrade spare MCS server 7x to 8x<br>5 - DRS backup of spare MCS server<br>6 - DRS restore of 8x backup to MCS server<br>7 - Rebuild subscribers from scratch on UCS<br>8 - Migrate IP phones from 7x cluster to 8x cluster on UCS<br>
9 - remove change freeze, re-implement any emergency changes that were required<br><br>There's some significant effort involved, in particular on the subscriber rebuilds, ensuring any custom TFTP files (wallpapers, etc.) are in place. That said, it's less work overall than doing a double upgrade.<br clear="all">
<font color="#888888">
<br>Matthew Saskin<br><a href="mailto:msaskin@gmail.com" target="_blank">msaskin@gmail.com</a><br><a href="tel:203-253-9571" target="_blank">203-253-9571</a></font><div><div></div><div class="h5"><br><br>
<br><br><div class="gmail_quote">On Thu, Mar 31, 2011 at 2:01 PM, Peter Slow <span dir="ltr"><<a href="mailto:peter.slow@gmail.com" target="_blank">peter.slow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello Everyone,<br>
<br>
I'd like your input on a project I'm working on. I have five clusters,<br>
all of which are currently running 7.1.5.31900-3. My goal is to<br>
upgrade each of them to 8.5 running in/on UCS.<br>
<br>
My _understanding_ is that I need to get a cluster to at least 8.0(2c)<br>
(which is what actual version, btw?), do a DRS backup, install the<br>
same version in UCS and then restore the backup into the VM.<br>
<br>
I was under the impression (until i read all of<br>
<a href="http://tinyurl.com/5nuf25" target="_blank">http://tinyurl.com/5nuf25</a> ) that on most I2 servers a Bridged upgrade<br>
is required and this would present an issue, because of time<br>
constraints - The smallest cluster is 9 servers, the largest is 17 or<br>
so and it can take upwards of 10 hours to upgrade a cluster, and about<br>
that long to actually get everything switched over _after_ upgrading<br>
is complete. (I realize this doesn't need to be a serial process, but<br>
it mostly is at the moment, aside from subs having their versions<br>
switched in pairs.)<br>
<br>
The main goal here is to get to UCS, and the team I'm working with<br>
REALLY doesn't want to upgrade the MCS servers one weekend, then move<br>
to UCS servers a week later. (Thus far, I've been telling them that<br>
this is going to be necessary AND that there is NO way to install<br>
7.1(5) in VMWare and _then_ upgrade to 8.x) Right now my only<br>
alternative _seems_ to be getting a CUCM in the lab running 7.1(5),<br>
doing a DRS export to that form the production cluster, upgrading<br>
that, then doing a DRS backup from _that_ to the UCS cluster in order<br>
to get the pre-staged environment up.<br>
<br>
There's some additional background below.<br>
<br>
Constraints:<br>
The first cluster to be upgraded is composed exclusively of 7845-I2<br>
IBM servers.<br>
In some cases clusters might have 7845-I1's functioning as TFTP or<br>
MoH servers, I am allowed to replace these with I2's prior to the<br>
upgrade if I need to.<br>
76 GB drives and 4 GB RAM in the I2s<br>
The upgrades / reboots etc need to take place during a weekend outage<br>
window that provides me with enough time to roll back if something<br>
awful happens. (I'd like to get everything done in a day, so that I<br>
can spend Sunday troubleshooting if I need to.)<br>
<br>
Questions:<br>
* If a bridged upgrade is required, do _all_ servers in the cluster<br>
need to be upgraded, or can I just upgrade the publisher, export with<br>
DRS and proceed from there?<br>
* Can I run 8.5 on my existing cluster of 7845-I2's w/ 76 gig drives<br>
and 4 gigs of RAM? <a href="http://tinyurl.com/5nuf25" target="_blank">http://tinyurl.com/5nuf25</a> seems to indicate that I<br>
can, but if it's wrong, I get fired.<br>
* Am I correct about an upgrade from 7.1(5) to 8.x within VMWare not<br>
being supported / possible?<br>
<br>
-Pete<br>
<br>
Peter I. Slow<br>
AIM: humboldtbgp<br>
Email: <a href="mailto:peter.slow@gmail.com" target="_blank">peter.slow@gmail.com</a><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br>
</div></div></blockquote></div><br>