Cisco Unified MeetingPlace, Release 6.x -- How to Relocate, Detach, and Attach the MPWEB SQL Database

From DocWiki

Revision as of 18:28, 20 July 2009 by Dunn (Talk | contribs)
Jump to: navigation, search

Cisco Unified MeetingPlace, Release 6.x > Web Conferencing > Configuring > Web Conferencing and SQL Server


This section describes part of the process for relocating the Cisco Unified MeetingPlace Web Server (MPWEB) database to a dedicated Microsoft SQL Server instance.

For performance and management reasons, you can choose to relocate the Cisco Unified MeetingPlace Web Conferencing SQL database (MPWEB) to your own standalone instance of Microsoft SQL Server 2000 or 2005 (in backward compatibility mode). For requirements for the customer-provided Microsoft SQL Server, see SQL Server Requirements—Remote (Off Box) in SQL Server Requirements.



To detach and attach the MPWEB SQL database, or relocate the database, do the following procedures in the order shown:


Contents

To Detach the Database

You must detach the MPWEB database with the sp_detach_db command from a SQL Server release that is earlier or equal to the release of the SQL Server to which you want to import the database.


  1. On the Cisco Unified MeetingPlace web server, log on as administrator.
  2. Stop the Cisco MeetingPlace Web Conferencing service and wait for the Cisco MeetingPlace Web Conferencing services, IIS Admin service, and World Wide Web Publishing service to stop.
  3. If the SQL Server hosting the MPWEB database runs on the Cisco Unified MeetingPlace web server, continue with Step 4.
    or
    If the SQL Server hosting the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and log on.
    Note: If you cannot log on to the separate (remote) Windows server, log on to any Windows based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can remotely connect to the SQL Server.
  4. Access the command prompt. Choose Start > Run , then enter cmd .
  5. Connect to SQL Server by using osql with the SA account and the appropriate password.
    • If the SQL Server runs locally, you can omit the -S servername option.
    • If you are not allowed to connect to this SQL Server as SA, connect by using an account that has enough privileges to backup a database.
  6. Access the MPWEB database. Enter use mpweb , then enter go .
  7. Display a list of the database files. Enter sp_helpfile , then enter go .
  8. Access the SQL Server master database. Enter use master , then enter go .
  9. Detach the MPWEB database. Enter sp_detach_db 'MPWEB , then enter go .
  10. Decide what you should do with the physical files that you identified in Step 7.
    These files constitute your detached database. For example, you can archive these files or use them to attach the associated MPWEB database to another SQL Server.
  11. Determine the slave database name(s) on your SQL Server. Enter select name from sysdatabases where name like 'MPWEB% , then enter go .
  12. (Optional) For each additional database named MPWEB_XX, repeat Step 6 through Step 10 to detach that database, replacing the database name MPWEB with MPWEB_XX.
    Note: The databases are logically linked; therefore, if you want to archive the detached MPWEB database, you must do the same for each MPWEB_XX database. If you want to reattach the MPWEB database to another SQL Server, you must also reattach the MPWEB_XX database(s).
  13. To exit osql, enter exit .
Examples: Detaching the Database

In the following examples, the output is displayed for each osql command that is used in the To Detach the Database.

Sample Output for Connecting to SQL Server
C:> osql -U sa -S SERVERNAME
Password: password
1>
Sample Output for Accessing the MPWEB Database
1> use mpweb
2> go
Sample Output for Displaying a List of Database Files

In this example, the database MPWEB relies on two physical files: C:\MSSQL2K\Data\MPWEB.mdf and C:\MSSQL2K\Data\MPWEB.ldf.

1> sp_helpfile
2> go
name fileid filename filegroup size maxsize growth usage
---- ------ -------- --------- ---- ------- ------- -----
MPWEBData 1 C:\MSSQL2K\Data\MPWEB.mdf PRIMARY 2432 KB Unlimited 1024 KB data only
MPWEBLog 2 C:\MSSQL2K\Data\MPWEB.ldf NULL 1280 KB Unlimited 10% log only


Sample Output for Accessing the SQL Server Master Database
1> use master
2> go
Sample Output for Detaching the MPWEB Database
1> sp_detach_db 'MPWEB'
2> go
Sample Output for Determining the Slave Database Name

In this example, the name of the slave database is MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.

1> select name from sysdatabases where name like 'MPWEB%'
2> go
---------------------------------------------------
name
[char ]
--------------------------------------------
MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1
Sample Output for Exiting osql
1> exit
C:>


To Attach the Database

Ensure that you have a valid detached MPWEB database, usually, two files named MPWEB.mdf (data file) and MPWEB.ldf (log file), though file names may vary.


  1. If the SQL Server to which you want to attach your MPWEB database runs on the Cisco Unified MeetingPlace web server, continue with Step 2.
    or
    If the SQL Server runs on a separate (remote) Windows server, locate that Windows server and log on. If you cannot log on to that Windows server, log on to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can remotely connect to the SQL Server.
  2. Access the command prompt. Choose Start > Run , then enter cmd .
  3. Connect to SQL Server by using osql. Enter osql -U sa -S server-name , where server-name is the Windows SQL Server to which you want to attach the MPWEB database.
    Note: If the SQL Server runs locally, you can omit the -S server-name option.
  4. Enter your password for the appropriate SA account.
    Note: If you are not allowed to connect to this SQL Server as SA, connect by using an account that has enough privileges to attach a database.
  5. Determine if a database named MPWEB already exists on this server. Enter select name from sysdatabases where name = 'MPWEB' , then enter go .
  6. If no MPWEB database exists, continue with Step 7.
    or
    If a MPWEB database exists, ensure that it is not being used by an existing Cisco Unified MeetingPlace web server.
    Note: You cannot attach a MPWEB database to this SQL Server if an active MPWEB database exists already. Before you proceed, you must detach the existing MPWEB database by completing the To Detach the Database.
  7. To verify the installation folder of the SQL Server to which you want to restore this database, check the physical location of the SQL Server master database.
    Enter sp_helpfile master , then enter go .
    Note: Unless you have a reason to restore your MPWEB database to another disk location, such as for performance and tuning or data recovery reasons, we recommend that you restore the database to the default data folder of this SQL Server installation.
  8. Copy the MPWEB.mdf and MPWEB.ldf files under the data folder that you identified in Step 7.
  9. Attach the MPWEB database. Enter sp_attach_db 'MPWEB',' data path \MPWEB.mdf',' data path \MPWEB.ldf' , then enter go .
  10. (Optional) If you have a valid set of files for the MPWEB_XX slave database(s), repeat Step 5 through Step 10 for each slave database, replacing MPWEB with MPWEB_XX to attach that database.
  11. To exit osql, enter exit .
Examples: Attaching the Database

In the following examples, the output is displayed for each osql command that is used in the To Attach the Database.


The following examples use the files MPWEB.mdf and MPWEB.ldf:

Sample Output for Connecting to SQL Server
C:> osql -U sa -S SERVERNAME
Password: password
1>
Sample Output for Checking if the MPWEB Database Exists
1> select name from sysdatabases where name = 'MPWEB'
2> go
name
-----------------------------------------------------
(0 row affected)
1>
Sample Output for Checking the Physical Location of the SQL Server Master Database

In this example, SQL Server Version 2000 is installed in C:\MSSQL2K, and the default data folder is C:\MSSQL2K\data.

1> sp_helpfile master
2> go
name filename filegroup size maxsize growth usage
----------------------------------------------------------------------
master C:\MSSQL2K\data\master.mdf PRIMARY 15744 KB Unlimited 10% data only
1>
Sample Output for Attaching the MPWEB Database
1> sp_attach_db 'MPWEB','data path\MPWEB.mdf','data path\MPWEB.ldf'
2> go
Sample Output for Exiting osql
1> exit
C:>


To Relocate the Database

You may want to relocate the database, putting the Cisco Unified MeetingPlace application and database onto different servers, for example if the server you are using is running out of disk space, or for performance or backup considerations.


  1. Detach the MPWEB SQL databases on the existing (for example, local) SQL Server:
    Follow the instructions in To Detach the Database.
  2. Attach the MPWEB SQL databases to the new (for example, remote) SQL Server:
    Follow the instructions in To Attach the Database.
  3. Change the Database Connection settings on your Cisco Unified MeetingPlace Web Conferencing server to point to the new (in this example, remote) SQL Server:
    1. Double-click the orange door icon in the System Tray.
    2. Click Web Conferencing.
    3. Enter the remote SQL server name in the Server field.
    4. Enter the new Username and Password.
    5. Click OK.

Rating: 1.0/5 (1 vote cast)

Personal tools