Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Upgrade path 2.4.6 to 3.1.x

Have a customer who wishes to upgrade 2.4.6 to 3.1.x. The wrinkle is that customer is migrating his Exchange 5.5 Windows Domain environment to Exchange2000 cluster / Active Directory. Is there any reading covering migration process for Unity?<br><br>


Re: Upgrade path 2.4.6 to 3.1.x

This is a "forklift" upgrade so if they're changing their backend it should be doable as long as they don't decide to also change everyone's alias (mail nickname) in the process.

You do an export of your Unity 2.x data using the FullDBExport utility (ships with Unity 3.x CD in the Migration Tools directory or you can get it off AnswerMonkey or CCO utilities page). this builds a seperate database you can copy to a tape/cd/network location/wherever. You then uninstall Unity 2.x and install a new copy of 3.x in the configuration they want. In this case into their new Exchange 2000 environment. Once you have that you run the FullDBImport utility (also ships on the CD or you can get it on AnswerMonkey or CCO) which will rebuild your user database, call handlers etc... there's a list in the help file for the FullDbImport/Export utilities for which data is not preserved (i.e. subscriber phone passwords, routing rules etc...). Most items are saved.

The import tool looks for existing users in the directory first by Directory ID, then by relative distingusihed name then by alias. If they're changing their backed system to Ex2K, the alias will the the only one of these preserved. If they change the aliases in this process, the import tool will create new mail users on the fly... which is probably not what you want.

Check out the help files for the import/export tools (available on AnswerMonkey and CCO if you don't have your 3.x CDs yet) and it'll shed some light on this process for you. The Install guide for 3.x also includes some info here.

Jeff Lindborg
Unity Technical Lead/Answer Monkey
Cisco Systems (new page for Unity support tools and scripts)