Guest

Cisco Unified MeetingPlace

MeetingPlace Web 4.x: MeetingPlace Web SQL Database Relocation from one SQL Server to Another

Hierarchical Navigation

Downloads

Document ID: 50992


Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Relocation Procedure
Related Information

Introduction

This document provides the procedure used to relocate the Cisco MeetingPlace Web MPWEB SQL database from one SQL Server to another.

An example of a database relocation scenario is when the Cisco MeetingPlace Web server has MSDE locally installed and you want to move the MPWEB SQL database to a remote full SQL Server so that the Cisco MeetingPlace Web begins to use the remote SQL Server instead of its local Microsoft Desktop Engine (MSDE).

In this document, "SQL Server" refers to any version of Microsoft SQL Server or MSDE mentioned in the Components Used section of this document.

warning Warning: Failure to execute the steps in this document means that the database has to be recreated. You also lose access to your archived meeting attachments on the Cisco MeetingPlace Web server.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco MeetingPlace Web version 4.x

  • MSDE 1.0 and 2000

  • Microsoft SQL Server 7.0 and 2000

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

The procedure described in this document applies only to Cisco MeetingPlace Web version 4.x. The procedure for the latest versions of Cisco MeetingPlace Web can be accessed as given below:

Cisco Unified MeetingPlace 6.x

Cisco Unified MeetingPlace 7.x

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Relocation Procedure

Complete these steps:

  1. Backup the existing MPWEB SQL database by following the instructions detailed in MeetingPlace Web SQL Database Backup.

    Because you are relocating the MPWEB SQL database, stop all MeetingPlace Web services beforehand as explained in MeetingPlace Web SQL Database Backup.

  2. Restore the MPWEB database on the new SQL Server by following the instructions detailed in MeetingPlace Web SQL Database Restore.

  3. Reconfigure the Open Database Connectivity (ODBC) settings and registry settings of your Cisco MeetingPlace Web server to point to the new SQL Server by following the instructions detailed in MeetingPlace Web MPWEB Database Configuration with a Remote SQL Server.

  4. Now that the SQL database that the Cisco MeetingPlace Web server needs and uses is physically on another remote SQL Server, clean up the local Cisco MeetingPlace Web server.

    • Detach the legacy MPWEB database on the old SQL Server by following the instructions detailed in MeetingPlace Web MPWEB SQL Database Detachment (to make sure it is not accessible). After you detach, either delete the database file(s) (MPWEB and MPWEB-SLAVE-#####) or move it to backup folders so as not to confuse future system administrators.

    • Disable the old SQL Server service that is running on the Cisco MeetingPlace Web server. In the system tray, right-click on the SQL Service Manager and select MSSQLSERVER. Stop if it is still running. After stopping, disable the MSSQLSERVER service.

    Note:  Do not uninstall the SQL Server that is on your MPWEB server. Doing this unregisters SQLDMO.dll which then causes the Cisco MeetingPlace Web functionality to fail.

  5. Restart the Cisco MeetingPlace Web services.

    For Cisco MeetingPlace Web versions 4.2.5 and 4.2.7, restart all MeetingPlace Web services and the World Wide Web publishing service. For Cisco MeetingPlace Web 4.3.0.x, restart the MeetingPlace Web Conferencing service.

Related Information

Updated: Apr 21, 2009 Document ID: 50992