Cisco Unified MeetingPlace, Release 7.0 -- How to Prepare for a Migration

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Migration Best Practices)
Line 179: Line 179:
* To prevent file corruption, edit the migration files with a text editor. Turn off the word wrap option to improve readability. Experienced users can use Microsoft Excel to edit the migration files. When finished, save the file with a .csv extension and then with a .txt extension.
* To prevent file corruption, edit the migration files with a text editor. Turn off the word wrap option to improve readability. Experienced users can use Microsoft Excel to edit the migration files. When finished, save the file with a .csv extension and then with a .txt extension.
 +
 +
 +
'''Error Message: '''Migration import is not allowed. Check version of meetingtime used for creating migrate.zip.
 +
 +
* If you see above error message when importing migratedata.zip from App Admin page, please follow below.
 +
* Check correct version of MeetingTime and Audio server as per http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_7.0_--_Migration_Requirements.
 +
* Make sure there is no existing data in App server by running “dbsize”. If there is any run “cleardb” to clean themup.
 +
* Check migration logs located at “migrate*.log” in /tmp folder and  ”migrate*.html.info” in /mpx-record/migrate folder.
 +
* Check “mpx-record/migrate” folder if all the contents of migratedata.zip are unzipped.
 +
* If any contents of migratedata.zip is not zipped or missing, unzip migratedata.zip manually by running “unzip migratedata.zip” from mpx-record/migrate folder through CLI.
 +
[[Category: Migrating from Cisco Unified MeetingPlace, Release 6.0 to Release 7.0]]
[[Category: Migrating from Cisco Unified MeetingPlace, Release 6.0 to Release 7.0]]

Revision as of 01:38, 15 September 2010

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one page: Installation


During a migration, many errors can occur. We strongly recommend that you thoroughly review this section before you begin a migration.


Contents

Prerequisites for the Migration

  • Install and configure your Cisco Unified MeetingPlace Release 7.0 system. You should be thoroughly familiar with the configuration of the Cisco Unified MeetingPlace Release 7.0 system.
  • Get new licenses for your Cisco Unified MeetingPlace Release 7.0 system. Licenses for Cisco Unified MeetingPlace Release 6.0 do not work with a Cisco Unified MeetingPlace Release 7.0 system. For example, Cisco Unified MeetingPlace Release 6.0 used a license called Exchange and Cisco Unified MeetingPlace Release 7.0 uses a license called msft_int. See About Licenses for more information about Cisco Unified MeetingPlace Release 7.0 licenses.


Migration Considerations

  • Do not run any other processes or tasks on your Cisco Unified MeetingPlace Release 6.0 system during a migration, especially during the data backup process. This can potentially affect the data that is being transferred from one system to another.
  • The migration script converts Cisco Unified MeetingPlace Release 6.0 users of the type "technician" to users of the type "delegate" in Cisco Unified MeetingPlace Release 7.0.
  • The allowed range for the value for the GROUP_ATTR_PREFERREDUNIT parameter in Cisco Unified MeetingPlace Release 6.0 was 0-32767. In Cisco Unified MeetingPlace Release 7.0, the allowed range for that value is 0-999. If your Cisco Unified MeetingPlace Release 6.0 system has values that are higher than 999, the migration will produce an error.
  • The system migrates Cisco Unified MeetingPlace Release 6.0 meetings with passwords but problems can arise if the Cisco Unified MeetingPlace Release 6.0 password is less than the minimum password length required in Cisco Unified MeetingPlace Release 7.0. Therefore, we suggest that you set the value for the "Minimum meeting password length" parameter in Cisco Unified MeetingPlace Release 7.0 to the same value as or a smaller value than the parameter value in Cisco Unified MeetingPlace Release 6.0.
  • Service codes associated with video meetings are not migrated. When a meeting with video endpoints that was migrated from Cisco Unified MeetingPlace Release 6.0 to Cisco Unified MeetingPlace Release 7.0 starts, the system uses the appropriate Cisco Unified MeetingPlace Release 7.0 service code that matches the Application Server configuration for video rate and audio quality.
  • E-mail formats are mapped as follows:


Table: E-Mail Type Mappings
E-Mail Type (Release 6.0) E-Mail Type and Format (Release 7.0) License Needed (Release 7.0)

none

SMTP (HTML)

--

cc:Mail

SMTP (HTML)

--

Lotus Notes

IBM Lotus Notes (Plain text)

lotusnotes

Microsoft Mail

SMTP (HTML)

--

Microsoft Exchange

Microsoft Exchange (Rich Text Format)

msft_int

Qualcomm Eudora

SMTP (HTML)

--

Netscape Messenger

SMTP (HTML)

--

Other

SMTP (HTML)

--



Migration Best Practices

Caution! Make sure that you back up the data on your existing Cisco Unified MeetingPlace 6.0 system before starting the migration.

Become familiar with the Cisco Unified MeetingPlace Release 7.0 system. To avoid multiple errors when importing data from the Cisco Unified MeetingPlace Release 6.0 system to the Cisco Unified MeetingPlace Release 7.0 system, follow these tips:

  • Ensure that you have installed the Cisco Unified MeetingPlace Release 7.0 licenses on the system. This avoids errors about audio ports that need to be reserved for meetings.
  • Ensure that the values for the system, meeting, and user configuration parameters for the Cisco Unified MeetingPlace Release 7.0 system are as close as possible to those values for the same parameters on the Cisco Unified MeetingPlace Release 6.0 system.
    Note: These are critical initial settings for the Cisco Unified MeetingPlace Release 7.0 system. After the migration is complete, you can change these system parameters with no repercussions.
    Both systems must have the same values for the following fields:
    • Minimum profile password length
    • Minimum user password length
    • Maximum ports per scheduled meeting
    • Maximum ports per reservationless meeting
    • Maximum meeting length (minutes)
    • Meeting ID start guard time (minutes)
    • Meeting ID end guard time (minutes)
    • Minimum meeting password length
    • Maximum advance days to schedule
    • Minimum meeting ID length
  • Ensure that the Cisco Unified MeetingPlace Release 7.0 system has enough ports for the largest meeting scheduled on the Cisco Unified MeetingPlace Release 6.0 system.

Migration Errors and Troubleshooting

  • If there are errors (for example, with a user or meeting record) the migration does not stop, but does skip those records.
  • The system always generates the following error messages during the data migration, due to the differences in system profile designs between Cisco Unified MeetingPlace Release 6.0 and Cisco Unified MeetingPlace Release 7.0. These messages can be ignored:


Error Message: Error importing record 2: Profile number 0001 already exists. Import line: "Sales","Engineer","salesengineer","0001","","gd","System"," Error importing record 3: Profile number 0002 already exists. Import line: "Tech","Engineer","technician","0002","","gd","System","0","

  • If you see the following error, it is because a password is required for the meeting in Cisco Unified MeetingPlace Release 7.0 but there was no password for the meeting in Cisco Unified MeetingPlace Release 6.0. The system has automatically set the meeting password to 12345 and imported the meeting:


Error Message: Error in record 1, meeting id "xxxx": Password is configured to be mandatory, but none was provided.

  • You must install the Cisco Unified MeetingPlace Release 7.0 licenses before the migration. If you did not install the lotusnotes or the msft_int license and you migrate a meeting that uses that license, the system maps the meeting to the generic SMTP (HTML) format (see Table: E-Mail Type Mappings) and displays the following error message:


Error Message: Changing email format to RTF for group xxx. Import line: "",87,"","4353","xxx","Yes","No","Yes","Beep","BeepName

  • If the migration import fails, scan the output file for the failure reasons. Fix any errors manually or by using Cisco Unified MeetingPlace MeetingTime. If you use Cisco Unified MeetingPlace MeetingTime, you must export the migrate file again from the Cisco Unified MeetingPlace Release 6.0 Audio Server.
  • Always scan the results of the migration import on the Cisco Unified MeetingPlace Release 7.0 system. The most common problems occur when importing the first records from user groups and user profiles. If you see problems, cancel the migration and correct the errors. Delete the database on the Cisco Unified MeetingPlace Release 7.0 Application Server and migrate the data again.
  • If you use Microsoft Excel to edit migration files, you might experience the file formats changing or invisible hex characters being added to the header. Only experienced users should use Microsoft Excel.
  • To prevent file corruption, edit the migration files with a text editor. Turn off the word wrap option to improve readability. Experienced users can use Microsoft Excel to edit the migration files. When finished, save the file with a .csv extension and then with a .txt extension.


Error Message: Migration import is not allowed. Check version of meetingtime used for creating migrate.zip.

  • If you see above error message when importing migratedata.zip from App Admin page, please follow below.
  • Check correct version of MeetingTime and Audio server as per http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_7.0_--_Migration_Requirements.
  • Make sure there is no existing data in App server by running “dbsize”. If there is any run “cleardb” to clean themup.
  • Check migration logs located at “migrate*.log” in /tmp folder and ”migrate*.html.info” in /mpx-record/migrate folder.
  • Check “mpx-record/migrate” folder if all the contents of migratedata.zip are unzipped.
  • If any contents of migratedata.zip is not zipped or missing, unzip migratedata.zip manually by running “unzip migratedata.zip” from mpx-record/migrate folder through CLI.

Rating: 1.0/5 (1 vote cast)

Personal tools