[cisco-voip] Unity 4.x to 7.x with failover upgrade

[Voice Noob]

No I am going to upgrade the primary server only. Once this is upgraded do a
clean install of the secondary then run the failover config. I don't want to
upgrade both servers.



-----Original Message-----
From: Pat Hayes [mailto:pat-cv at wcyv.com] 
Sent: Friday, January 02, 2009 12:25 PM
To: Voice Noob
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Unity 4.x to 7.x with failover upgrade

If I follow correctly, you're asking if, after rebuilding your primary
server to 7.x and doing a DiRT restore on it, if you should/can:

1. Run the 7.x upgrade on the failover server, then re-run failover
config to tie the cluster back together

or

2. Rebuild the failover to clean 7.x, and then run failover config to
create the cluster

I think option 1 is risky. You have to assume that an upgrade of a
secondary server will work with SQL replication down and the cluster
in a funky state (both servers know they are in a cluster, but one has
been rebuilt, SQL replication is down, different versions, etc). You
could test it, and it might work, but I wouldn't count on getting TAC
support for that upgrade plan.

Option 2 seems a lot safer.You are basically running through the
procedure to replace/restore a Unity cluster. There is a section on
this in the Reconfiguration and Upgrade guide. It is a tested process
and, if you follow the doc and things still go south, TAC will be able
to help you out.

On Fri, Jan 2, 2009 at 9:08 AM, Voice Noob <voicenoob at gmail.com> wrote:
> I do not plan to go to 4.1.2 for Unity first. All of my upgrades have been
> from 4.0(5) directly to 5.0. I am not going to use COBRAS for this
upgrade,
> It does not get everything and I am very comfortable with the upgrade
> process for Unity. I just have not done a unity failover upgrade.
>
>
>
> From: Jason Aarons (US) [mailto:jason.aarons at us.didata.com]
> Sent: Thursday, January 01, 2009 10:44 PM
> To: Voice Noob
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Unity 4.x to 7.x with failover upgrade
>
>
>
> I'll be researching this myself next week and be doing some lab work to
> test.  I have similar scenario in end of January.
>
>
>
> I plan to upgrade from Unity Unified Messaging (with Exchange) 4.0.5 to
> 4.1.2  then;
>
>
>
> a)      New hardware install 4.1.2 and DIRT restore from old hardware,
then
> upgrade to 5.0.1 (they plan to use Exchange 2007 cluster)  I have done
this
> before but without failover
>
>
>
> or
>
>
>
> b)      New Hardware install 5.0.1 (they plan to use Exchange 2007
cluster)
> and use COBRAS to move subscribers/call handlers from old 4.1.2 box (this
is
> new I haven't tried this yet)
>
>
>
> I understand there are issues with DiRT and 4.0.5X thus the 4.1.2 upgrade.
>
>
>
> My customer is not using Viewmail for Outlook so I don't have to worry
about
> pushing that out.
>
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voice Noob
> Sent: Thursday, January 01, 2009 10:45 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Unity 4.x to 7.x with failover upgrade
>
>
>
> I am getting ready to do an upgrade from Unity 4.x to 7.x with failover in
a
> UM setup. I have not done a failover upgrade but I have done several Unity
> upgrades in both VM and UM. I will usually  take a DIRT backup of the
> customer Unity server, upgrade it in VMware to the version I want to go
to.
> Do a new DIRT and then restore it to the new server hardware. I have done
> this before in a UM setup and it can be done but there are a few exchange
> issues you have to deal with. I am not concerned with those and I can work
> through them. My question is do I need to upgrade the failover server? Can
I
> just upgrade the primary and once it is up and working with version 7 do a
> fresh install of the secondary server? Do the changes from the primary
Unity
> server replicate over to the secondary like call manager PUB and SUB?
Thanks
> for any help.
>
>
>
>
>
> ________________________________
>
> Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and
deleting
> it from your computer. Thank you.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>