Cisco Unified MeetingPlace, Release 7.0 -- How to Migrate a Web Conferencing Server from a Cisco Unified MeetingPlace Release 6.0 System to a Cisco Unified MeetingPlace Release 7.0 System

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one page: Installation



For the Web Servers, the hardware is the same for the Cisco Unified MeetingPlace Release 6.0 and Cisco Unified MeetingPlace Release 7.0. You have two choices when migrating the web conferencing data: either migrate on the same hardware or migrate from an old server to a new server.


Perform this procedure: Backing Up and Restoring the Web Database Before a Migration and then perform only one of the following procedures, based on the type of hardware to which you are migrating:


Contents

Before You Begin

Read How to Prepare for a Migration.




Backing Up and Restoring the Web Database Before a Migration

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 plan to perform this procedure as part of a Release 6.0 to Release 7.0 migration, you will have to complete it even if you already did a manual backup. 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.


Cisco Unified MeetingPlace Web Conferencing Backup Utility

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.

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

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.


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

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

If you run the backup utility in command line mode, you can specify a different location.


Note: The Web Conferencing backup utility cannot backup data from a shared storage location. To backup 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.


Specifying a Different Backup Destination Folder

Complete this procedure to set up your own destination backup folder. This is the 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
  1. Open a DOS command window.
    1. Select Start > Run.
    2. Enter cmd.
  2. Navigate to the folder where the backup utility is located. Example: C:\Temp\mpweb_software>
  3. 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.


Example 3:

Specify your destination backup folder by using a UNC path:

Enter ciscounifiedmeetingplacewebconferencingbackup.exe \\hostname\temp



Determining the Size of Microsoft Windows Explorer Folders

Use Windows Explorer to get the size of each folder and add them to get the total back up data size.


Procedure
  1. Open Windows Explorer.
  2. Right-click on a folder.
  3. Select Properties.
    Windows returns the total number of folders, files and byte size.
    Note: The \MPWeb\WebConf\content\7 folder contains an extremely large number of folders and files. As a result, Windows Explorer may take a long time, possibly up to 40 minutes, to return the properties result.



Backing Up Web Conferencing Data from the Source Web Server

Before You Begin
  • Manually stop the MSSQLSERVER service and disable the service until the backup is done.


Procedure
  1. On the original Web Server, exit any open applications.
  2. Insert the Cisco Unified MeetingPlace Web Conferencing DVD into the DVD-ROM drive and double-click CiscoUnifiedMeetingPlaceWebConferencingBackup.exe.
    Note: To store the backup data in a different location, run the following from the command prompt: CiscoUnifiedMeetingPlaceWebConferencingBackup <location>
  3. Click Next in the first dialog box of the Backup or Restore Wizard and follow the prompts.
    The Backup or Restore Wizard creates a restore file called CiscoUnifiedMeetingPlaceWebConferencingRestore.exe that you can use on a separate Web Server.
  4. Set the MSSQLSERVER service back to its original settings.



Restoring Web Conferencing Data on a Different Web Server

This procedure describes how to migrate data, such as meeting recordings, attachments, custom strings, and MPWEB database information from a source Web Server to a new Web Server.


Before You Begin
  • Copy the backup directory from the source computer to the destination computer where you want to restore the data. This backup directory includes MeetingPlacebackup.bkf and CiscoUnifiedMeetingPlaceWebConferencingRestore.exe.
  • If you are creating this restore binary as part of a Cisco Unified MeetingPlace Release 6.0 to Release 7.0 migration, make sure that the new Application Server that this Web Server will be pointing to has already been migrated using server migration scripts.


Procedure
  1. Double-click CiscoUnifiedMeetingPlaceWebConferencingRestore.exe on the destination computer.
    The Backup or Restore Wizard window displays.
  2. Click Next.
  3. Select Restore files and settings.
  4. Click Next.
  5. Click Browse and navigate to your MeetingPlacebackup.bkf file.
  6. Click Next.
  7. Double-click an item in the left pane to see its contents.
  8. Check the items you want to restore.
  9. Click Next.
  10. Click Finish to close the Wizard.
    The restore operation proceeds.
  11. Click Close to close the Cisco Unified MeetingPlace Restore window.


What to Do Next
  • Verify that all future meetings, attachments, recordings, and web custom strings that were created in the source Web Server are present in the new Web Server.



Migrating Data from a Cisco Unified MeetingPlace Release 6.0 Web Server to a Cisco Unified MeetingPlace Release 7.0 Web Server Using New Hardware

You only need to perform this procedure if you are using new hardware. If you are using the same hardware for both the Cisco Unified MeetingPlace Release 6.0 and Cisco Unified MeetingPlace Release 7.0 Web Servers, follow the instructions in Migrating Data from a Cisco Unified MeetingPlace Release 6.0 Web Server to a Cisco Unified MeetingPlace Release 7.0 Web Server Using the Same Hardware instead.


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 upgrade the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The Application Server must be up before you can upgrade the Web Server. To ensure that the Application Server is up, log 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 Web Server has the same hostname as the Cisco Unified MeetingPlace Release 6.0 Web Server.


Before You Begin

Complete all the steps in Backing Up and Restoring the Web Database Before a Migration.


Procedure
  1. On the Cisco Unified MeetingPlace Release 6.0 Web Server, back up the data.
    For information on backing up the Web Server, see Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server.
    Note: The backup program does not back up the database if you are remote to the Web Server, nor does it back up attachments or recordings that do not reside in the default location.
    The system generates a restore program called CiscoUnifiedWebConferencingRestore.exe.
  2. On the Cisco Unified MeetingPlace Release 7.0 Web Server, run the restore program.
    For information on restoring data from a backup, see Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server.
    Note: You must do this before you install the Cisco Unified MeetingPlace Release 7.0 Web Conferencing server software.
  3. Install the Cisco Unified MeetingPlace Release 7.0 Web Conferencing software on a new Cisco MCS by following the instructions in Installing the Cisco Unified MeetingPlace Web Conferencing Server.



Migrating Data from a Cisco Unified MeetingPlace Release 6.0 Web Server to a Cisco Unified MeetingPlace Release 7.0 Web Server Using the Same Hardware

You only need to perform this procedure if you are using the same hardware for both the Cisco Unified MeetingPlace Release 6.0 and Cisco Unified MeetingPlace Release 7.0 Web Servers. If you are using new hardware, follow the instructions in Migrating Data from a Cisco Unified MeetingPlace Release 6.0 Web Server to a Cisco Unified MeetingPlace Release 7.0 Web Server Using New Hardware instead.


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 upgrade the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The Application Server must be up before you can upgrade the Web Server. To ensure that the Application Server is up, log in to the CLI as mpxadmin and enter swstatus. For information about using the CLI, see Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace.
  • Click-to-attend (CTA) links can only be migrated if the Cisco Unified MeetingPlace Release 7.0 Web Server has the same hostname as the Cisco Unified MeetingPlace Release 6.0 Web Server.


Before You Begin
  • Migrate data from a Cisco Unified MeetingPlace Release 6.0 Audio Server to a Cisco Unified MeetingPlace Release 7.0 Application Server.
  • 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 upgrade. Enter this value when prompted for the local IP address.
    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.
  • Verify that the Cisco Unified MeetingPlace Release 6.0 Web Server has network connectivity to the Cisco Unified MeetingPlace Release 7.0 Application Server by running the nslookup hostname and then pinging the hostname.
  • Detach the Cisco Unified MeetingPlace Release 6.0 Web Server from the Cisco Unified MeetingPlace Release 6.0 Audio Server.


Procedure
  1. Install the Cisco Unified MeetingPlace Release 7.0 Web Conferencing software, including Gateway SIM.
  2. Enter the hostname of the Cisco Unified MeetingPlace Release 7.0 Application Server when the system prompts you for the hostname of the Primary Server.
  3. Enter the IP address associated with the "Hostname [Home Page]" value when the system prompts you for the local IP address.
    The system continues the installation.
  4. Follow the screen prompts to reboot the Web Server.
    The system reboots and continues the installation.

Rating: 0.0/5 (0 votes cast)

Personal tools