Rasim, I did an upgrade from Unity 7 to Unity Connection 9.1.2 a couple years back, and I think I know what you mean. For my upgrades, I wanted to build Unity CxN in parallel with my production Unity 7, so that I could do a migration at my chosen pace. For this I went with COBRAS. It’s been a while, but I don’t remember whether or not this jump allowed for a backup and restore type of upgrade. But it sounds like that’s your plan of attack. For COBRAS export from Unity, use breifcase mode. This does not require network path from source and target server. also, does not make any changes to source sever the way "hot mode" does. For what its worth, here’s some information on what COBRAS gets you for this type of upgrade. In case you change your mind…
COBRAS gets most data for the following parameters: Call Handlers Subscribers Interview Handlers Directory Handlers (will be called Name Loop Handlers in UC) Public Distribution Lists Schedules Routing Rules (typically recommending for restores only, not migrations) Custom Key Mapping Coversation Data (UC to UC restores only) COBRAS does NOT get data for the follwoing: Class of Service Restriction tables Locations Contacts ( SMTP/AMIS/Bridge/VPIM subscribers) Holidays Sys Config Data ( LDAP integration, IMAP login, RSA config, Advanced settings, etc.) Subscriber Templates Call Handler Templates Password policy information Securty messages from older UC revs. - J From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Rasim Duric Sent: Tuesday, April 21, 2015 12:56 PM To: voip puck Subject: [cisco-voip] Unity Connection upgrade from 7.1(3) to 9.1(2) Hello everyone, I'm planning to upgrade our two Unity Connection servers 7.1(3)ES11 to 9.1(2)SU3. In the Cisco document at this URL:http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.pdf, page 30, you can read the following: During the migration, only user data and, optionally, voice messages are preserved. System-level configuration data (for example, templates and classes of service) must be manually configured. I'm migrating CUC 7.1(3)ES11 from one physical server to another physical server (compatible with 9.1(2)SU3 specs). The plan is to install 7.1(3) from scratch on the new server and then restore the old server via DRS. After the 7.1(3) is up and running on the new server, perform the 9.1.(3)SU3 upgrade. I think all data should be preserved including the templates, the Class of Services, etc. in my case. When would someone actually experience the above statement from the Cisco document? What else is not preserved? If anyone has done a similar upgrade, I'd like to hear any tips and tricks or issues you ran into. Thanks. Rasim Duric Network analyst, Network Infrastructure Computing and Communications Services (CCS) University of Guelph 519-824-4120 Ext 53146 rdu...@uoguelph.ca<mailto:rdu...@uoguelph.ca> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> Room 037, Animal Science and Nutrition Building Guelph, Ontario, N1G 2W1
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
