'''Note: ''' If you do not have these latest patches and hotfixes, then open in a new tab or window. http://tools.cisco.com/support/downloads/go/Model.x?mdfid=282340975&mdfLevel=Software%20Version/Option&treeName=Voice%20and%20Unified%20Communications&modelName=Cisco%20Unified%20MeetingPlace%207.0&treeMdfId=278875240. Select '''Unified MeetingPlace Application Server > 7.0(3)''', then download '''70MR2_Prerequisite.zip'''. Extract the files on your local system.

'''Note: ''' You must be at Cisco Unified MeetingPlace 6.0 MR5, or the migration tool will fail.

'''Note: ''' You must be at Cisco Unified MeetingPlace 6.0 MR5, or the migration tool will fail.

About Migration

Because of the different system architectures between Cisco Unified MeetingPlace Release 7.0 and previous releases of Cisco Unified MeetingPlace, you cannot upgrade to this release of Cisco Unified MeetingPlace from a previous 5.4 or 6.0 release. However, you can migrate to this release from a previous release. Migration preserves some of the existing customer and system data while installing a new system.

Migration Process

We currently only support migrations from Cisco Unified MeetingPlace Release 6.0 maintenance release 5 (MR5) to Release 7.0.3 (MR2). If you are using an earlier version of Cisco Unified MeetingPlace and want to migrate to Release 7.0.3, then you must first upgrade to Cisco Unified MeetingPlace Release 6.0 MR5.

The following table presents an overview of the major steps required to migrate a Cisco Unified MeetingPlace Release 6.0 MR5 system to Cisco Unified MeetingPlace Release 7.0.3 (MR2).

Note: This table is written in the order in which you should proceed with your migration. We recommend you familarize yourself with the overall process, as written in the table, before actually proceeding with the migration. You may also want to print a copy of this migration procedure, as a reference.

Procedure

Step #

Step Description

Related Topics

Step 1.

If your system is earlier than Cisco Unified MeetingPlace6.0 MR5, then first upgrade your system to this version.

If your Cisco Unified MeetingPlace system includes a Microsoft Outlook plug-in integration and users schedule meetings through Cisco Unified MeetingPlace (back-end integration), then export the ICalendarMeetings table from the Web Conferencing Server Database to a text file.

Migration Path Matrix

The following table lists supported migrations for Cisco Unified MeetingPlace Release 5.4 and 6.0, and the corresponding maintenance releases (MR).

Note: You must be at Cisco Unified MeetingPlace Release 6.0 MR5 to migrate to Cisco Unified MeetingPlace Release 7.0.3 (MR2). Obtain the latest software patches and hotfixes for the Audio Server (6.0.5.17 or later), Web Server 6.0.639.99, and MeetingTime (version 6.0.5.9 or later) before starting the migration. These patches and hotfixes are in the Cisco Unified MeetingPlace Release 7.0.3 Prerequisite Package. See the following table, for information on how to obtain this package.

Note: If you have various Cisco Unified MeetingPlace system components at different versions, then bring all components to the same Cisco Unified MeetingPlace version, before starting the migration.

Caution! If the migration fails, then remain at Cisco Unified MeetingPlace 6.0 MR5 and contact Cisco TAC for further assistance. Once you have started the migration, you will not be able to revert back to a Cisco Unified MeetingPlace 5.4 system.

Caution! If the migration fails, then keep your system at Cisco Unified MeetingPlace 6.0 MR5 and contact Cisco TAC for further assistance. Once you have started the migration, you will not be able to revert back to a Cisco Unified MeetingPlace 6.0 system.

Caution! If the migration fails, then keep your system at Cisco Unified MeetingPlace 6.0 MR5 and contact Cisco TAC for further assistance. Once you have started the migration, you will not be able to revert back to a Cisco Unified MeetingPlace 6.0 MR1 system.

Caution! If the migration fails, then keep your system at Cisco Unified MeetingPlace 6.0 MR5 and contact Cisco TAC for further assistance. Once you have started the migration, you will not be able to revert back to a Cisco Unified MeetingPlace 6.0 MR2 system.

Caution! If the migration fails, then keep your system at Cisco Unified MeetingPlace 6.0 MR5 and contact Cisco TAC for further assistance. Once you have started the migration, you will not be able to revert back to a Cisco Unified MeetingPlace 6.0 MR3 system.

Caution! If the migration fails, then keep your system at Cisco Unified MeetingPlace 6.0 MR5 and contact Cisco TAC for further assistance. Once you have started the migration, you will not be able to revert back to a Cisco Unified MeetingPlace 6.0 MR4 system.

About Migration Paths

We currently only support migrations from Cisco Unified MeetingPlace Release 6.0 maintenance release 5 (MR5) to Release 7.0.3 (MR2). If you are using an earlier version of Cisco Unified MeetingPlace and want to migrate to Release 7.0.3, then you must first upgrade to Cisco Unified MeetingPlace Release 6.0 MR5. If you want to migrate to Release 7.0.1 or 7.0.2, then see How to Migrate to Cisco Unified MeetingPlace Release 7.0.1 or 7.0.2.

Web Servers

Before the Web Server migration, back up your Web Server data.

You can either reuse an existing Cisco MCS for the Web Server or you can install a newer Cisco MCS. Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 7.0.3 Web Server has the same hostname as the Cisco Unified MeetingPlace Release 6.0 Web Server.

If you are installing the Cisco Unified MeetingPlace Release 7.0.3 Web Server on a new machine, then restore your existing Web Server data on the new machine.

If you are retaining the same hardware for Cisco Unified MeetingPlace Release 7.0.3 Web Server, then temporarily use another machine to back up your existing Web Server data.

Caution! If you choose to continue using the same hardware for your Web Server, then make sure that it meets the minimum requirements for the Cisco Unified MeetingPlace 7.0.3 Web Server.

Audio and Application Servers

Cisco Unified MeetingPlace Release 6.0 uses an Audio Server 8100 series. Cisco Unified MeetingPlace Release 7.0 no longer uses an Audio Server but instead uses an Application Server. The Application Server is installed on a Cisco MCS. This component must be installed new and cannot be upgraded from Cisco Unified MeetingPlace Release 6.0. You can migrate data from the Audio Server to the Application Server.

Video Systems

If you currently use a Cisco Unified MeetingPlace 3545 Media Server for Cisco Unified MeetingPlace Release 6.0, you can reuse the chassis and the Video Blade. However, you must upgrade the software for the video blade.

Because of the different configurations, you cannot reuse any part of the Cisco Unified MeetingPlace 3515 Media Server nor can you reuse the Audio Blade of the Cisco Unified MeetingPlace 3545 Media Server.

Familiarize yourself with the configuration of the Cisco Unified MeetingPlace Release 7.0 system. See the previous sections in this Installation Guide, as well as the Configuration Guide for Cisco Unified MeetingPlace Release 7.0.

Do not run backups during the migration process. If you have scheduled automatic backups, ensure that you suspend them.

If you have not run the vfptrfix command within the last 2-3 months, we highly recommend running it to fix voice pointer errors, before exporting data from the Cisco Unified MeetingPlace 6.0 Audio Server (Step 5 of the Migration Process.) (Although this command may take several hours to complete, it helps prevent the MigrateData Capture tool from failing, due to too many voice pointer errors.)

Using telnet, sign in to the CLI in Cisco Unified MeetingPlace as the admin user. Then, sign in as the CSC user (su), and enter the password of the day (contact Cisco TAC to obtain the password). Run the vfptrfix -f -v command.

If you are using the Cisco Unified MeetingPlace Microsoft Outlook plug-in, then make sure that you export the ICalendarMeetings table before migrating your Web Server to Release 7.0. Complete this export as Step 11 of the Migration Process.

History of past meetings and meeting participants (preceding 38 days or the number of days until the meeting statistics are purged)

Continuous meetings that are still active (ongoing)

Recorded user names

Recorded meetings (for both voice and web) and attachments (these can only be accessed from the web) for completed meetings (preceding 38 days or the number of days until the meeting statistics are purged)

Related Topics

Retaining Recordings For More Than 38 Days

The migration process documented in this module retains historical meeting data for up to 38 days. If you want to retain data for a longer period, you may chose one of the following options.

You can keep the legacy Cisco Unified MeetingPlace system for historical data.

We recommend you restrict users from starting new meetings on the legacy system. You can rename the legacy Cisco Unified MeetingPlace system with a new name, and retain the existing name on the new Cisco Unified MeetingPlace 7.0.3 system for an easier transition.

Retain the existing Cisco Unified MeetingPlace system for a specified period, and ask meeting hosts and participants to download historical meetings and attachments on to their own machine.

After the specified time, you can bring down the legacy system.

Setting Up a Trial System

If you are unsure if you want to migrate to Cisco Unified MeetingPlace Release 7.0.3, you can first set up a Cisco Unified MeetingPlace Release 7.0.3 trial system.

To set up a trial system, you will need new hardware. You can either temporarily install a Cisco Unified MeetingPlace Web Server or you can permanently install a new Cisco Unified MeetingPlace Web Server to replace your older Cisco Unified MeetingPlace Web Server.

With the trial system, you can import groups and profiles. However, you cannot import meetings, due to the risk of sending out conflicting or invalid notifications.

If you decide to convert your trial system to a Cisco Unified MeetingPlace Release 7.0.3 production system, you must first clear out the trial data and then import the actual data from the older system.

Note: All recordings made between when you import the data to the trial system, to when you import the data again before converting the trial system to production, are lost.

What To Do Next

If you have not done so already, complete Step 3 of the Migration Process by applying the latest hotfixes and patches to your 6.0 Audio Server and MeetingTime. Ensure that the Audio Server is version 6.0.5.17 or later and that MeetingTime is version 6.0.5.9 or later.

How to Prepare for a Migration

This is Step 4 of the Migration Process. Be sure you have completed Step 3 (applying the latest hotfixes and patches to your 6.0 Audio Server and MeetingTime) before starting this step.

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

Migration Considerations

Caution! 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 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 your existing Cisco Unified MeetingPlace 6.0 system. It is important to have a backup of your data should the migration fail, or you need to cancel the migration.

Ensure that you have Cisco Unified MeetingPlace Release 7.0 licenses. 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.3 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.3 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

Language settings for users are preserved. However, you will need to configure the language systems on the Cisco Unified MeetingPlace 7.0.3 Application Server.

Keep a record of your existing system configuration parameters so that you can use these to configure your Cisco Unified MeetingPlace 7.0.3 system.

Ensure that the Cisco Unified MeetingPlace Release 7.0.3 system has enough ports for the largest meeting scheduled on the Cisco Unified MeetingPlace Release 6.0 system.

During the migration, you will need to transfer files between servers. Be sure to have a file transfer application, such as WinSCP, available to transfer these files.

General Migration Errors and Troubleshooting

If there are errors (for example, with a user or meeting record) the migration does not stop, but skips those records.

If you see the following error, it is because a password is required for the meeting in Cisco Unified MeetingPlace Release 7.0.3 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:

To prevent file corruption, edit the migration files with a text editor. Turn off the word wrap option to improve readability. When finished, save the file with a .csv extension.

Experienced users can use Microsoft Excel to edit the migration files. If you use Microsoft Excel, then reopen the saved file with a text editor and remove all the commas in the first line. When finished, save the file with a .csv extension.

Note: 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. We recommend only experienced users use Microsoft Excel.

Because of the hardware differences, you must migrate from a Cisco Unified MeetingPlace Release 6.0 Audio Server to a Cisco Unified MeetingPlace Release 7.0.3 Application Server. You cannot use a Cisco Unified MeetingPlace Release 6.0 Audio Server with a Cisco Unified MeetingPlace Release 7.0.3 system and you cannot upgrade from a Cisco Unified MeetingPlace Release 6.0 Audio Server to a Cisco Unified MeetingPlace Release 7.0.3 Application Server.

Note: We recommend that you keep the legacy Cisco Unified MeetingPlace 6.0 Audio Server until you confirm that the migration to Cisco Unified MeetingPlace 7.0.3 is successful.

Note: Plan accordingly, as the Audio Server data migration may take 24 to 48 hours to complete. The time depends on multiple factors including the database, the number of recordings, the number of meetings, number of users, number of notifications, and so on.

To migrate data from an Audio Server to an Application Server, perform the following tasks in this order:

Ensuring There is Sufficient Disk Space

Make sure that you have sufficient free disk space on the Cisco Unified MeetingPlace Release 6 Audio Server for certain file systems.

Procedure

Sign in to the Cisco Unified MeetingPlace Audio Server command-line interface as the CSC user (contact Cisco TAC to obtain the password of the day).

Enter the df command to check the space utilization on the root, db, and tmp file systems.

The root file system should have less than 65 percent utilization.

mtgplace# df /

Filesystem BlkSize Blocks Used Free %

/dev/sdncr.1a 16384 31999 19569 12430 61%

If the root file system utilization is higher than 65 percent, then check /usr/users/csc for old case log files and remove them. If you still cannot find enough free space, then contact Cisco TAC for further assistance.

The DB filesystem should have less than 60 percent utilization:

mtgplace# df /lat/db

Filesystem BlkSize Blocks Used Free %

/dev/sdncr.0c 16384 320000 138058 181942 43%

If the db file system utilization is higher than 60 percent, then contact Cisco TAC for further assistance.

The tmp file system should have less than 80 percent utilization.

mtgplace# df /tmp

Filesystem BlkSize Blocks Used Free %

/dev/sdncr.1b 16384 51200 24633 26567 48%

If the tmp file system utilization is higher than 80 percent, then check /tmp/update for old update files and remove them.

Note: You must be at Cisco Unified MeetingPlace 6.0 MR5, or the migration tool will fail.

Restriction

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

Procedure

Stop the Gateway SIM and Web Conferencing services. See "How to Use the Cisco Unified MeetingPlace Web Conferencing Service" in the Configuration Guide for Cisco Unified MeetingPlace Release 7.0 or the online help in the administrator interface.

Use MeetingTime and sign in, as a system administrator, to the Cisco Unified MeetingPlace 6.0 MR5 Audio Server.

Go to Options > Edit Settings.

Use the arrows to set the Minutes to wait for report results to 300.

Setting this value to the maximum value of 300, effectively results in no timeout limit.

Complete this command immediately before capturing the migration data.

Use MeetingTime to sign in, as a system administrator, to the Cisco Unified MeetingPlace 6.0 MR5 Audio Server.

Go to Administration > Report.

Click MigrateData Capture from the left panel.

Select the time period for retaining the history of completed meetings and meeting participants. Click 38 from the right panel and use the arrows, if you want to select a shorter time period. Then click OK.

The maximum time period is 38 days.

Click migratedata.zip from the right panel. Click OK to save the file to the default location, or click Browse to navigate to the directory where you want to save this file. Click Save.

Click Generate Report.

The system displays a message stating that this report can generate a high data transfer load on the Audio Server and is intended only as a migration tool to Cisco Unified MeetingPlace Release 7.0. Do not run this report during periods of active utilization.

Click Yes to acknowledge the message, then click Yes again, when the system asks if you want to continue.

When complete, the system returns you to the Report tab.

The migratedata.zip file contains the following:

mpweb_purge_mtgs.sql

MtgCat.xml

mtversion.txt

RawGroup.txt

RawMeetings.txt

RawMtgCat.txt

RawPartAtt.txt

RawProfile.txt

RecordedNames.zip

The MigrateData Capture report exports all the .wav files (for recorded names) to the Reports folder in the directory in which Cisco Unified MeetingPlace MeetingTime is installed.

Note: The system does not remove these files after creating the RecordedNames.zip file. Therefore, if you want to capture migration data from another Cisco Unified MeetingPlace Release 6.0 Audio Server, or redo the migration data capture by using the current Audio Server, then remove all of the .wav files from the Reports folder.

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

For failover purposes, please make sure that you have fully built, configured, and completed migration on your primary server (Node1) before you configure a standby server (Node2) and enable replication.

Procedure

Sign in to the Application Server command-line interface as the root user. (For more information, see CLI User Level Options.)

Navigate to the /tmp directory and use the touch command to create a file, .migrate (an empty file).

[root@<server_name> tmp]# touch .migrate

Verify that an empty .migrate file has been created.

find . -empty -exec ls {} \;

This command returns a list of all empty files. For example:

[root@<server_name> tmp]# find . -empty -exec ls {} \;

./dbtasklocks/TRIGGER_WATCH

./.migrate

./brassd.log

Sign in to the Application Server command-line interface by entering su – Informix.

Navigate to the appropriate directory by entering cd /opt/cisco/meetingplace/database/db-maintenance/.

Enter ./update_statistics.sh, then wait until the command completes (in approximately 5 minutes).

Sign in to the Administration Center on the Application Server.

Choose Maintenance > Migration Import Tool.

Click Browse to navigate to the data file that contains the import data.

Click Execute.

After the import is completed, the system displays a new tab stating that the import has finished.

Troubleshooting the Application Server Data Migration

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:

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.3 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.

Sign in as root on the Cisco Unified MeetingPlace 7.0 Application Server command-line interface, and enter mpx_sys restart to cancel the migration.

If more than 5000 errors occur during a migration, then the migration terminates with an error message:

Error Message: Maximum errors reached. Aborting action.

Contact Cisco TAC for further assistance.

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

If you see the preceding error message when importing migratedata.zip from the Administration Center on the Application Server, then check the following:

Make sure the correct version of MeetingTime and the Audio Server are being used to export the database as per Migration_Requirements.

Make sure there is no existing data in the Application Server by running the dbsize command as the root user. If there is any data, then run the cleardb command to clean up the data.

Check the migration logs located at migrate*.log in the /tmp folder and at migrate*.html.info in the /mpx-record/migrate folder.

Check the mpx-record/migrate folder and see if all the contents of migratedata.zip are unzipped.

If the contents of migratedata.zip are not completely unzipped or are missing, then manually unzip migratedata.zip by running unzip migratedata.zip from the mpx-record/migrate folder through the command-line interface.

Fixing Migration Data Errors

Problem: If there are errors during a migration (for example, with a user or meeting record), then the migration skips those records. Depending on the number of errors, there are two solutions.

Solution: If there aren't too many errors for users or meetings, then we recommend you recreate the user profiles and meetings.

Solution: If the number of errors is higher, then complete the following steps.

Note: With this process, no recorded name gets migrated. If a failed meeting record includes recurrence, then the recurrence is broken at that meeting instance. Manually cancel, then reschedule the meeting with recurrence.

The Cisco Unified MeetingPlace Release 6.0 database contains two types of users: local and non-local. Local users were manually created using Cisco Unified MeetingPlace and non-local users were imported into Cisco Unified MeetingPlace from an external directory by Cisco Unified MeetingPlace Directory Services.

The migration process imports all users as local users. Cisco Unified MeetingPlace Release 7.0.3 cannot modify the user profiles for user who had non-local status before but that now have local status.

The following process restores the local or non-local status for users to the original value.

Procedure

Sign in as the administrator to the Cisco Unified MeetingPlace Release 6.0 Web Server and as a superuser to the Cisco Unified MeetingPlace Release 7.0.3 Application Server.

On the Cisco Unified MeetingPlace Release 7.0.3 Application Server, navigate to the following directory: /opt/cisco/meetingplace/migrationtools/current/directoryservice/etc. This directory contains two files: SunOne_ldaptools.zip and MP6.0_MPDSMigrationHelper.bat.

Copy those two files to a local directory on the Cisco Unified MeetingPlace Release 6.0 Web Server where Cisco Unified MeetingPlace Directory Services is running.

Navigate to the directory to which you just copied the files.

Unzip the SunOne_ldaptools.zip file to a new directory.

Copy the MP6.0_MPDSMigrationHelper.bat file to the same new directory.

The reason is that the Cisco Unified MeetingPlace Release 7.0.3 version of Directory Service tries to create the same users on Cisco Unified MeetingPlace Release 7.0.3 and cannot get user updates from Active Directory or Cisco Unified Communications Manager.

To trigger a full synchronization from Active Directory or Cisco Unified Communications Manager and to update the users, follow the steps in this procedure.

You can check if you have this hotfix installed by completing the following.

Sign in to a Microsoft Windows machine running either SQL Server Enterprise Manager and run the following command:

SELECT TOP 1 * FROM [MPWEB].[dbo].[Version] ORDER BY SchemaVersion DESC;

The return value must be 92.

Note: Follow the instructions in the included README to install the hotfix.

Caution! If the Web Server migration fails, and you need to revert back to Cisco Unified MeetingPlace 6.0 MR5 Web Conferencing Server, then make sure to remove this hotfix before reusing your existing system. The README contains the information to remove this hotfix.

Note: Only complete this procedure if your Cisco Unified MeetingPlace system has a Microsoft Outlook plug-in with a back-end integration (users schedule meetings through Cisco Unified MeetingPlace). If you do not utilize the Microsoft Outlook plug-in, or you have a front-end integration (users schedule Outlook meetings through Microsoft Outlook), then do not complete this procedure.

The Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard generates an executable that migrates configuration settings and meeting information from one Web Server to another. If you have a load-balancing cluster of Web Servers, complete the following procedures on each server in the cluster.

Note: The restore file generated by the Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard cannot be used to revert to Release 6.0 if the migration fails. You will need to have a manual backup created if you need to revert to the original release. For more information, open, in a new tab or browser window, How to Back Up and Restore MPWEB SQL Database.

Note: If you are planning to install the Cisco Unified MeetingPlace Release 7.0.3 Web Conferencing Server on the same hardware as the legacy Cisco Unified MeetingPlace Release 6.0 Web Conferencing Server, then back up your Web conferencing data on a different server.

The Web Conferencing backup utility uses the Microsoft Windows backup tool as its underlying backup engine. Since the Windows backup tool does not perform any compression, the total size of your projected backup equals the total data size of the files and folders that you want to back up. You may use the Properties function in Windows Explorer to get the size of each folder and add them together to get the total size of back up data.

By default, the backup utility backs up data from the following folders:

C:\Program Files\Microsoft SQL Server\MSSQL\Data

C:\Program Files\Cisco Systems\MPWeb\Meetings

C:\Program Files\Cisco Systems\MPWeb\WebConf\content\7

The \MPWeb\WebConf\content\7 folder contains an extremely large number of folders and files.

These folders are based on the default set up of the local SQL Server database on the Cisco MCS server and on the lack of a shared storage location.

Note: The Web Conferencing backup utility cannot back up data from a shared storage location. To back up such data, manually navigate to the location of your shared storage location, copy the contents of the entire folder, then paste them into another location.

The utility then stores the backed up data in the following folder by default:

Specifying a Different Backup Destination Folder

Complete this procedure if you want to set up your own destination backup folder, where your backed up data will be stored. If you do not do this procedure, the Web Conferencing backup utility will store its backed up data in C:\Program Files\Cisco Systems\MPWeb\MPBackup by default.

Procedure

Navigate to the folder where the backup utility is located. Example: C:\Temp\mpweb_software>

Enter the location of your backup destination folder by reviewing the following examples:

Example 1:

If you enter ciscounifiedmeetingplacewebconferencingbackup.exe f:

the backup utility will create a folder called f:\MPBackup and use it as the destination folder for your backed up data.

Example 2:

If you enter ciscounifiedmeetingplacewebconferencingbackup.exe f:\backup

the backup utility will create a folder called f:\backup\MPBackup and use it as the destination folder for your backed up data.

Note: If you specify f:\ instead of f:, or f:\backup\ instead of f:\backup, the backup utility will fail and abort. In other words, do not include the \ as the last character in your path specification.

Backing Up Data from the Source Web Server

As a precaution, complete this procedure even if you will be using the same hardware for the Cisco Unified MeetingPlace 7.0 Web Server.

Before You Begin

Manually estimate the total data size of your backup operation to ensure that your destination has enough disk space to hold the backed up data files.

Manually stop the MSSQLSERVER service and disable the service until the backup is done.

Note: This backup takes 15-30 minutes, depending on the number of users, meetings, attachments, and recordings. For example, the backup takes about 10 minutes for a system with about 300,000 profile users and 400,000 meetings, with a small number of attachments and recordings.

Procedure

On the original Cisco Unified MeetingPlace 6.0 MR5 Web Conferencing Server, exit any open applications.

This section describes how to migrate data, such as meeting recordings, attachments, custom strings, and MPWEB database information from the Cisco Unified MeetingPlace 6.0 Web Server to the Cisco Unified MeetingPlace 7.0 Web Server on new hardware.

Restrictions

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

You cannot migrate the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The 7.0.3 Application Server must be running before you can migrate the Web Server.

To ensure that the Application Server is running, sign in to the CLI as mpxadmin and enter swstatus. For more information about using the CLI, see the Configuration Guide for Cisco Unified MeetingPlace Release 7.0 or the online help in the administrator interface.

Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 7.0.3 Web Conferencing Server has the same hostname as the Cisco Unified MeetingPlace Release 6.0 Web Conferencing Server.

Before You Begin

Look up the value of the "Hostname [Home Page]" parameter for the Cisco Unified MeetingPlace Release 6.0 Web Server and resolve it to obtain the IP address of the NIC that is used during the installation of the Cisco Unified MeetingPlace 7.0.3 Web Conferencing Server. Enter this value when prompted for the local IP address during the Web Server installation.

Note: The correct IP address (hostname) is not necessarily that of NIC 1; therefore, we recommend that you look at the administrator interface for the value of the "Hostname [Home Page]" parameter.

If your Cisco Unified MeetingPlace Release 6.0 system was enabled for video, use the Add/Remove Programs function to remove the video program from the Web Server. The video program that worked in Cisco Unified MeetingPlace Release 6.0 does not work in Cisco Unified MeetingPlace Release 7.0.3.

Verify that the Cisco Unified MeetingPlace Release 6.0 Web Server has network connectivity to the Cisco Unified MeetingPlace Release 7.0.3 Application Server by running the nslookuphostname and then pinging the hostname.

Procedure

On the original Cisco Unified MeetingPlace 6.0 MR5 Web Server, exit any open applications.

Although it is not mandatory, we recommend you clean up old files and applications on your existing hardware, before installing the Cisco Unified MeetingPlace 7.0.3 Web Conferencing Server. After cleaning up your system, it should be a clean Cisco MCS.

Restrictions

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

You cannot migrate the Cisco Unified MeetingPlace Web Conferencing Server when the Application Server is being rebooted. The 7.0.3 Application Server must be running before you can upgrade the Web Conferencing Server.

To ensure that the Application Server is running, sign in to the CLI as mpxadmin and enter swstatus. For more information about using the CLI, see the Configuration Guide for Cisco Unified MeetingPlace Release 7.0 or the online help in the administrator interface.

Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 7.0.3 Web Conferencing Server has the same hostname as the Cisco Unified MeetingPlace Release 6.0 Web Conferencing Server.

When you migrated your Cisco Unified MeetingPlace Audio Server data, you selected the historical time period for retaining the history of completed meetings and the meeting participants. Run the mpweb_purge_mtgs.sql script to delete all meetings data (including CTA links) from the Web Server database older than the time period you specified when creating migratedata.zip. See Exporting Data from the Cisco Unified MeetingPlace Release 6.0 Audio Server.

Note: Although synchronization between the Application Server and the Web Server happens automatically, we recommend that you execute this script before starting the Web Server.

Note: The script execution takes 15 to 30 minutes, depending on the number of users, meetings, attachments, and recordings. For example, it takes about 5 minutes for a system with about 300,000 profile users and 400,000 meetings with minimal attachments and recordings.

Procedure

Sign in to the Cisco Unified MeetingPlace Application Server command-line interface as the mpxadmin user.

Navigate to the /mpx-record/migrate directory.

Run the mpweb_purge_mtgs.sql script. Complete one of the following:

Copy mpweb_purge_mtgs.sql to a Microsoft Windows machine running either SQL Server Enterprise Manager or SQL Query Analyzer. Using one of these tools, open and execute mpweb_purge_mtgs.sql against the newly restored Web Conferencing Server 7.0.3 database.

When the migration is complete, the system will automatically replace all future meeting requests that contain the URL of the Cisco Unified MeetingPlace Release 6.0 system with the URL of the Cisco Unified MeetingPlace Release 7.0.3 system.

Ensure that all end users have installed the most recent version of the Microsoft Outlook for Cisco Unified MeetingPlace integration. See the Integration Note for Installing and Configuring Microsoft Outlook with Cisco Unified MeetingPlace Release 7.0 or the online help in the administrator interface for more information.

Migrating the Microsoft Outlook Users Who Schedule Meetings From Outlook

Complete this procedure if your Cisco Unified MeetingPlace system has a front-end integration with the Microsoft Outlook plug-in

Note: Ensure that you have already upgraded your Cisco Unified MeetingPlace Application Server and Web Conferencing Server to version 7.0.3.

Executing the migrateFromMP6MR5.sh Script

Caution! Only execute the migrateFromMP6MR5.sh script as part of the Microsoft Outlook plug-in migration from Cisco Unified MeetingPlace 6.0 MR5 to Cisco Unified MeetingPlace 7.0.3 (MR2). Do not execute this script on a live Cisco Unified MeetingPlace 7.0.3 system, or you will overwrite Outlook meetings data.

Note: Ensure that you have created the ICalendarMeetings.txt file and copied it to the Cisco Unified MeetingPlace 7.0.3 Application Server.

The time to complete this procedure depends on the size of your ICalendarMeetings table. For example, an ICalendarMeetings table with 12,500 records and a file size of approximately 1.5 MB takes approximately 10 minutes.

Procedure

Change to the root user by entering su - and enter the root password.

Navigate to the /opt/cisco/meetingplace/migrationtools/current/notifications directory.

The migrateFromMP6MR5.sh script and the ICalendarMeetings.txt file should be in this directory.

Execute the migrateFromMP6MR5.sh script.

>./ migrateFromMP6MR5.sh ICalendarMeetings

After execution, the script reports the total number of inserted, updated, and skipped NotifItemInfo records. The script also creates the migrateFromMP6MR5.log file in the same folder.

What To Do Next

Testing the Outlook Migration

Note: Ensure that you have already migrated your Cisco Unified MeetingPlace Web Server to Release 7.0.3, before completing this procedure.

Procedure

On your Microsoft Outlook calendar, find a future meeting that was scheduled from the Release 6.0 system.

Open the appointment.

Go to the MeetingPlace tab.

If prompted, sign in to the Cisco Unified MeetingPlace Release 7.0.3 system.

Note: If this is the first time that you are logging in to the Cisco Unified MeetingPlace Release 7.0.3 system, the system opens a new appointment. If this happens, close the new appointment and reopen the appointment that you opened in Step 2.

Verify that the meeting details are the same as they were on the Cisco Unified MeetingPlace Release 6.0 system.

Test if notifications are working properly by making an update to this meeting. The meeting host and all the meeting participants should receive notifications and their Outlook calendars should be correctly updated.