[cisco-voip] Consolidate two separate UCCX cluster and migrate to 9.x

[Ashwani R]

Kevin, Mike,

Thanks for your input.  I think I would go with second route and build the
new cluster manually and leave other servers up for couple more months
after the cut-over for historical data.

Thanks,
Ashwani

On Thu, Dec 18, 2014 at 10:17 AM, Kevin Przybylowski <kevinp at advancedtsg.com
> wrote:
>
>  Ashwani,
>
>
>
> Since you’re taking 2 separate CCX servers, and migrating to 1 there is no
> way to bring over Historical data from the older version as part of the
> upgrade.  As this is Historical data, I would advise the supervisors to
> generate all the reports they’ll need the week before the cutover and then
> do a clean cut on the new version.
>
>
>
> How big is the call center as far as applications/skills/scripts/etc?  If
> small enough, you will save yourself lots of heartache and time if you
> treat the new cluster as new and manually migrate the 2 call centers over.
> This task is fairly easy if old and new are both online.
>
>
>
> I would also agree with Mike and suggest you bring it up to 10.5, just
> note that HRC is no longer used and the Reporting users will have to be
> trained on CUIC if you do that.
>
>
>
> Kevin P.
>
>
>
>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Mike King
> *Sent:* Thursday, December 18, 2014 9:40 AM
> *To:* Cisco VoIPoE List
> *Subject:* Re: [cisco-voip] Consolidate two separate UCCX cluster and
> migrate to 9.x
>
>
>
> Ashwani,
>
>
>
> At this point, I question why you don't upgrade to 10.5.   Coming off 7.1,
> you're in for a major jump/upgrade path, you might as well go the last two
> versions and be current.
>
>
>
> Also, you didn't make clear if you're going to 9.0, or 9.1.  They will
> have different EOS dates.
>
>
>
> Cisco has not made public any EOS/EOL statements about CUCM9.x, but based
> off this chart:
>
> http://www.voicecerts.com/2011/05/cisco-unified-communications-manager.html
>
> (Not on the chart, 8.6, which was EOS January 2014)
>
>
>
> I wouldn't be surprised to see an EOL statement in the next calendar year
> for 9.0.   I personally think we'll see it in January.  If you have a Cisco
> Account Manager, and have signed an NDA, you might be able to get the EOS
> date from him.
>
>
>
> I wouldn't guess what 9.1 EOS date would be.
>
>
>
> As for Merging two clusters together, I don't think with that big a jump,
> you'll be able to keep the historical data.  I believe UCCX 7 still ran on
> Windows, and UCCX 9 is on Linux, I don't think this data is carried over.
> Perhaps someone with more experience with these types of upgrades will
> comment.
>
>
>
> I recommend practicing your upgrade several times. With this big of a jump
> practicing several times (Looking at you Leilo and your Saga) will expose
> upgrade issues in the lab, not in production.
>
>
>
> Mike
>
>
>
> On Thu, Dec 18, 2014 at 8:36 AM, Ashwani R <ashwani at ranpise.com> wrote:
>
>   Team,
>
> I have a customer who has two separate UCCX HA cluster with their
> respective CUCM cluster (merging two companies).  They would like to merge
> both CUCM and UCCX cluster to one cluster and upgrade them to 9.x.  They
> are running CUCM version *7.1.3.10000-11* and UCCX cluster running *
> 7.0(2) Build254*.  What is the best way to do this? Can they keep both
> historical data from UCCX and move them to 9.x ?  I know this is not
> possible but just want to see if anyone has done it before.  We have
> already built new 9.x CUCM and UCCX cluster with new set of IP addresses
> with blank configurations. Any help will be appreciated.
>
> Thanks,
>
> Ashwani
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/e7f87402/attachment.html>