MeetingPlace Web MPWEB SQL Database Restore [Cisco Unified MeetingPlace]

Document ID: 50984

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Database Restore Procedure
Related Information

Introduction

This document provides steps for restoring the MPWEB SQL database.

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

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 Versions 4.2.5 and later
MSDE 1.0 and 2000
Micrsofot 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.

Conventions

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

Database Restore Procedure

Complete these steps:

Make sure you have a valid backup file for the database.

Refer to MeetingPlace Web SQL Database Backup for instructions on how to backup your MPWEB SQL database.

In these sections, it is assumed that you have a file called mpweb.dat that has been exported with the backup database command from a SQL Server whose version is lower or equal to one of the SQL Servers you want to import the database to.
If the SQL Server that hosts the MPWEB database runs on the Cisco MeetingPlace Web server, proceed to step 3.

If the SQL Server that hosts the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and logon to it. If you cannot logon to that Windows server, you need to logon to any Windows-based workstation/server on the network that has a valid installation of SQL Server Client tools that includes the osql command. This allows you to remotely connect to the SQL Server.
Access the command prompt by selecting Start > Run and typing cmd.
Connect to the SQL Server using osql with the sa account and the appropriate password, as shown here:
```
C:> osql -U sa -S <SERVER_NAME>
Password: <type_password>
1>
```
Note: If the SQL Server runs locally, you can omit the option -S SERVER_NAME. <SERVER_NAME> is the Windows server name.

Note: If you are not allowed to connect to this SQL Server as 'sa', connect using an account that has privileges to backup a database.

Check if a database called MPWEB already exists on this server.

1> select name from sysdatabases where name = 'MPWEB'
2> go
name
-----------------------------------------------------
MPWEB
(1 row affected)
1>

If a MPWEB database already exists, you need to make sure that no Cisco MeetingPlace Web server currently uses it.

If one or multiple Cisco MeetingPlace Web server(s) use(s) the database, log on as an administrator on each server. For Cisco MeetingPlace Web versions 4.2.5 and 4.2.7, stop all MeetingPlace Web services and the World Wide Web publishing service.

For Cisco MeetingPlace Web 4.3.0.x, stop the MeetingPlace Web Conferencing service and wait for all the MeetingPlace Web services and World Wide Web publishing service to stop. Next, drop the database by using the command:
```
1> drop database MPWEB
2> go
Deleting database file 'C:\MSSQL2K\Data\MPWEB.LDF'.
Deleting database file 'C:\MSSQL2K\Data\MPWEB.MDF'.
1>
```

Before you import the MPWEB database to the SQL Server, check what database physical files are associated to it:

1> restore filelistonly from disk = 'C:\temp\mpweb.dat'
2> go
---------------------------------------------------
LogicalName PhysicalName            Type  FileGroupName Size          MaxSize              
----------- ------------------------ ------ ------------- ---------- -----
MPWEBData  C:\MSSQL7\Data\MPWEB.mdf D     PRIMARY
    2490368.000000 35184372080640.000000
MPWEBLog   C:\MSSQL7\Data\MPWEB.ldf L     NULL
    1310720.000000 35184372080640.000000
(2 rows affected)

In the example above, the MPWEB database was exported from an MSDE 1.0 server. The default 'Data' folder for this server is C:\MSSQL7\Data and the MPWEB database was created with one data file (logical name = 'MPWEBData', physical name = C:\MSSQL7\Data\MPWEB.mdf) and one log file (logical name = 'MPWEBLog', physical name = C:\MSSQL7\Data\MPWEB.ldf).

Verify the installation folder of the SQL Server you want to restore this database to by checking the physical location of the SQL Server master database:
```
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>
```
In this example, SQL Server (version 2000) has been installed in C:\MSSQL2K and the default 'Data' folder is C:\MSSQL2K\data. Unless you have a specific reason to restore your MPWEB database to another disk location (for performance and tuning or data recovery reasons), you should restore it into the default 'Data' folder of this SQL Server installation. Because the database backup file contains physical file locations that are not valid for this SQL Server, you need to use the WITH MOVE clause to successfully restore the database (see step 9).

Restore your database. Use the WITH MOVE clause to relocate the database physical files to the correct location, if necessary (see the description in step 8):

1> restore database MPWEB from disk = 'C:\temp\mpweb.dat' 
with move 'MPWEBData' to 'C:\MSSQL2K\Data\MPWEB.MDF', move 'MPWEBLog' to 
'C:\MSSQL2K\Data\MPWEB.LDF'
2> go
Processed 216 pages for database 'MPWEB', file 'MPWEBData' on file 1.
Processed 1 pages for database 'MPWEB', file 'MPWEBLog' on file 1.
Converting database 'MPWEB' from version 515 to the current version 539.
Database 'MPWEB' running the upgrade step from version 515 to version 524.
Database 'MPWEB' running the upgrade step from version 524 to version 525.
Database 'MPWEB' running the upgrade step from version 525 to version 526.
Database 'MPWEB' running the upgrade step from version 526 to version 527.
Database 'MPWEB' running the upgrade step from version 527 to version 528.
Database 'MPWEB' running the upgrade step from version 528 to version 529.
Database 'MPWEB' running the upgrade step from version 529 to version 530.
Database 'MPWEB' running the upgrade step from version 530 to version 531.
Database 'MPWEB' running the upgrade step from version 531 to version 532.
Database 'MPWEB' running the upgrade step from version 532 to version 533.
Database 'MPWEB' running the upgrade step from version 533 to version 534.
Database 'MPWEB' running the upgrade step from version 534 to version 535.
Database 'MPWEB' running the upgrade step from version 535 to version 536.
Database 'MPWEB' running the upgrade step from version 536 to version 537.
Database 'MPWEB' running the upgrade step from version 537 to version 538.
Database 'MPWEB' running the upgrade step from version 538 to version 539.
To achieve optimal performance, update all statistics on the 'MPWEB' database 
by running sp_updatestats.
RESTORE DATABASE successfully processed 217 pages in 0.428 seconds (4.136 MB/sec).
1>

Review the informational messages to ensure the operation was successful. In this example, additional messages (running upgrade step) are displayed because the database backup file has been created on an earlier version of the SQL Server.

For Cisco MeetingPlace Web 4.3.0.x and later, the MPWEB database consists of two separate database files: mpweb and mpweb-slave-#####. In this case, you need to also restore the slave database. Apply the same procedure above to restore the mpweb-slave-#### database file.
Exit OSQL by typing:
```
1> exit
C:>
```
If the database needs to be used by one or several Cisco MeetingPlace Web server(s), log on as an administrator on each server.

For Cisco MeetingPlace Web versions 4.2.5 and 4.2.7, start all MeetingPlace Web services and the World Wide Web publishing service.

For Cisco MeetingPlace Web 4.3.0.x, start the MeetingPlace Web Conferencing service.

Related Information

Voice Technology Support
Voice and Unified Communications Product Support
Recommended Reading: Troubleshooting Cisco IP Telephony
Technical Support - Cisco Systems

Updated: Jan 31, 2006

Document ID: 50984

Hierarchical Navigation

Cisco Unified MeetingPlace