|
Home > Archive > Voice over IP Cisco > September 2005 > Upgrade from CM 3.2 > 3.3 > 4.1
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Upgrade from CM 3.2 > 3.3 > 4.1
|
|
| Andrew Dignan 2005-09-26, 2:45 am |
| Anyone sure if the following is supported:
1. Existing CM cluster running 3.2.3
2. Migrating to new hardware
3. Install BARS 4.0(x) on existing publisher and run backup
4. Install CM 3.3 on new MCS server
5. Import using BARS the backup from step 3
I tried this at home and it does work, I am just not sure if its
supported. The reason I have to do this is because upgrading the
production cluster isn't an option at this point. I have new MCS servers
and I cannot install OS 2.4 on these servers for obvious reasons so I
think going this route is my only option besides upgrading the production
servers to CM 3.3.
I have all new hardware and the goal was to build everything off on its
own island without effecting the production environment. There has to be
a way..supported or not..to get this done.
TIA
| |
| Lelio Fulgenzi 2005-09-26, 2:45 am |
| In my opinion, upgrades typically go well. Nothing out of the ordinary. The
one thing you have to be careful of is the behaviour of your system after
the upgrades. New (and deprecated) system and enterprise parameters as well
as configuration options make upgrading a bit of a task - especially since
the documentation has been lacking in the past. If you have made use of any
special configuration options, ensure that they are still available. For
example, I believe in 3.2 there was a 'voicemail box' option in the
directory number configuration screen - this was removed in 3.3. Your
upgrade path will more than likely include upgrading the phone images as
well - that's something you will also have to test.
Consider running a beta (or alpha as some people call it) cluster with your
new hardware and get some real live testing going on. An intercluster trunk
will allow for communications between the clusters although you will lose
some functionality, e.g. CallBack, PickGroup, etc.
----- Original Message -----
From: "Andrew Dignan" <andy@dignans.com>
To: <cisco-voip@puck.nether.net>
Sent: Sunday, September 25, 2005 11:46 PM
Subject: [cisco-voip] Upgrade from CM 3.2 > 3.3 > 4.1
> Anyone sure if the following is supported:
>
> 1. Existing CM cluster running 3.2.3
> 2. Migrating to new hardware
> 3. Install BARS 4.0(x) on existing publisher and run backup
> 4. Install CM 3.3 on new MCS server
> 5. Import using BARS the backup from step 3
>
> I tried this at home and it does work, I am just not sure if its
> supported. The reason I have to do this is because upgrading the
> production cluster isn't an option at this point. I have new MCS servers
> and I cannot install OS 2.4 on these servers for obvious reasons so I
> think going this route is my only option besides upgrading the production
> servers to CM 3.3.
>
> I have all new hardware and the goal was to build everything off on its
> own island without effecting the production environment. There has to be
> a way..supported or not..to get this done.
>
> TIA
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Andrew Dignan 2005-09-26, 2:45 am |
| Yeah. Thats the plan, to run the new environment and complete a very
detailed test plan on it. I was just concerned about getting CM 3.2 to
the new MCS hardware. It looks like I can do a new install of 3.2 on OS
2.7. I could swear there was an issue with installing 3.2 on an OS that
had Windows SP4 way back when.
digger
> In my opinion, upgrades typically go well. Nothing out of the ordinary.
> The
> one thing you have to be careful of is the behaviour of your system after
> the upgrades. New (and deprecated) system and enterprise parameters as
> well
> as configuration options make upgrading a bit of a task - especially since
> the documentation has been lacking in the past. If you have made use of
> any
> special configuration options, ensure that they are still available. For
> example, I believe in 3.2 there was a 'voicemail box' option in the
> directory number configuration screen - this was removed in 3.3. Your
> upgrade path will more than likely include upgrading the phone images as
> well - that's something you will also have to test.
>
> Consider running a beta (or alpha as some people call it) cluster with
> your
> new hardware and get some real live testing going on. An intercluster
> trunk
> will allow for communications between the clusters although you will lose
> some functionality, e.g. CallBack, PickGroup, etc.
>
> ----- Original Message -----
> From: "Andrew Dignan" <andy@dignans.com>
> To: <cisco-voip@puck.nether.net>
> Sent: Sunday, September 25, 2005 11:46 PM
> Subject: [cisco-voip] Upgrade from CM 3.2 > 3.3 > 4.1
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
|
| Digger,
You will need to be aware that during the upgrade process from 3.2 - 3.3 a
rebuild of the server will be required, as 3.2 uses SQL 7 and 3.3 uses SQL
2000. Therefore I would not be too worried about installing 3.2 on 2000.2.7.
Is the production cluster at the latest SR release for 3.2? e.g. 3.2.3 SR 2?
If so I would install the upgrade assistant on the existing servers and
confirm that there are no issues with upgrading the server, perform a backup
using the latest MCS backup.
Then build your new cluster using the 3.3 CDs and then restore the backup
from the old cluster, before upgrading to 4.1.
Hope this helps.
Glen
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Andrew Dignan
Sent: 26 September 2005 05:39
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Upgrade from CM 3.2 > 3.3 > 4.1
Yeah. Thats the plan, to run the new environment and complete a very
detailed test plan on it. I was just concerned about getting CM 3.2 to
the new MCS hardware. It looks like I can do a new install of 3.2 on OS
2.7. I could swear there was an issue with installing 3.2 on an OS that
had Windows SP4 way back when.
digger
> In my opinion, upgrades typically go well. Nothing out of the ordinary.
> The
> one thing you have to be careful of is the behaviour of your system after
> the upgrades. New (and deprecated) system and enterprise parameters as
> well
> as configuration options make upgrading a bit of a task - especially since
> the documentation has been lacking in the past. If you have made use of
> any
> special configuration options, ensure that they are still available. For
> example, I believe in 3.2 there was a 'voicemail box' option in the
> directory number configuration screen - this was removed in 3.3. Your
> upgrade path will more than likely include upgrading the phone images as
> well - that's something you will also have to test.
>
> Consider running a beta (or alpha as some people call it) cluster with
> your
> new hardware and get some real live testing going on. An intercluster
> trunk
> will allow for communications between the clusters although you will lose
> some functionality, e.g. CallBack, PickGroup, etc.
>
> ----- Original Message -----
> From: "Andrew Dignan" <andy@dignans.com>
> To: <cisco-voip@puck.nether.net>
> Sent: Sunday, September 25, 2005 11:46 PM
> Subject: [cisco-voip] Upgrade from CM 3.2 > 3.3 > 4.1
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.6/111 - Release Date: 23/09/2005
|
|
|
|
|