This document provides steps for backing up the MPWEB Structured Query
Language (SQL) database.
Note: In this document, "SQL Server" refers to any version of Microsoft SQL
Server or Microsoft Desktop Engine (MSDE) mentioned in the Components Used section.
There are no specific requirements for this document.
The information in this document is based on these software and
Cisco MeetingPlace Web versions 4.2.5 and later
MSDE versions 1.0 and 2000
Microsoft SQL Server versions 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.
For more information on document conventions, refer to the
Cisco Technical Tips
Complete these steps:
If you want to export the MPWEB database to create a backup copy
(for example, as part of a daily backup procedure), there is no need to stop
Cisco MeetingPlace Web. You can do a "hot" export of the database while Cisco
MeetingPlace Web is running. In this case, proceed directly to Step 3. If your
goal is to export the MPWEB database so it can be imported on another SQL
Server to continue operations for this Cisco MeetingPlace Web server, proceed
to Step 2.
Log in as administrator on the Cisco MeetingPlace Web server. For
Cisco MeetingPlace Web versions 4.2.5 and 4.2.7, stop all Cisco MeetingPlace
Web services and the WWW Publishing service. For Cisco MeetingPlace Web version
4.3.0.x, stop the MeetingPlace Web Conferencing service and wait for all of the
MeetingPlace Web services and the WWW Publishing service to
If the SQL Server hosting the MPWEB database runs on the Cisco
MeetingPlace Web server, proceed to the next step. If the SQL Server hosting
the MPWEB database runs on a separate (remote) Windows server, locate that
Windows server and log in to it. If you cannot log in to that Windows server,
you need to log in 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 you can remotely connect to the SQL
Go to Start > Run and issue the
cmd command to access the command
Connect to the SQL Server by issuing the
osql command with the sa account and the appropriate
password, as shown here:
C:> osql -U sa -S server_name
Note: If the SQL Server runs locally, you can omit the -S
option. The argument
stands for the Windows server
Note: If you are not allowed to connect to this SQL Server as sa,
connect using an account that has the privileges necessary to back up a
Choose a fully qualified path and filename to export your database
to (in the example, C:\temp\mpweb.dat is used). If you are connected to the SQL
Server by running osql on a remote workstation or
server, remember that this path must be valid on the Windows server that hosts
SQL Server, not on your local workstation. Export the database by issuing these
1> backup database MPWEB to disk = 'C:\temp\mpweb.dat'
Review informational messages to confirm that the operation was successful:
Processed 616 pages for database 'MPWEB', file 'MPWEBData' on file 1.
Processed 3 pages for database 'MPWEB', file 'MPWEBLog' on file 1.
BACKUP DATABASE successfully processed 619 pages in 1.709 seconds (2.962 MB/sec)
If Cisco MeetingPlace Web 4.3.0.x is installed, there is a second
slave MPWEB database that must be backed up. Its name includes a series of
digits that varies from one installation to another. Issue this command to
determine the slave database name on your SQL Server:
1> select name from sysdatabases where name like 'MPWEB%'
In this example, the name of the slave database is
MPWEB-Slave-37102728. Following the instructions of Step 6 above, you must back
it up by issuing this command (replace xxxxxxxx with the
digits used by the database name on your system):
1> backup database [MPWEB-Slave-xxxxxxxx] to disk = 'C:\temp\mpweb-slave-xxxxxxxx.dat'
Issue the exit command to exit
Save the export file mpweb.dat (and
, if necessary) in a
safe location, such as another server or a tape.
Note: This backup file cannot be restored to earlier versions of SQL
Server. For example, if you created this backup file on MSDE 2000, you cannot
import it on a SQL Server 7 or MSDE 1.0 server, but you can restore it on a SQL
Server 2000 or MSDE 2000 server with the equivalent or higher service pack