Cisco Unified MeetingPlace Release 6.1 -- How to Back Up and Restore MPWEB SQL Database

From DocWiki

Jump to: navigation, search

Cisco Unified MeetingPlace Release 6.1 > Web Conferencing > Configuring > Web Conferencing and SQL Server




To back up and restore MPWEB database, do the following procedures in the order shown:

Contents

To Create a Backup File by Exporting the MPWEB Database

This backup file can be restored only on a SQL Server 2000 with equivalent or later service pack installed.


  1. To export the MPWEB database to create a backup copy while Cisco Unified MeetingPlace Web Conferencing is running (as part of a daily backup procedure, for example), continue with Step 2.
    or
    To export the MPWEB database so that it can be imported on another SQL Server that can continue operations for this Cisco Unified MeetingPlace web server, stop the Cisco MeetingPlace Web Conferencing service and wait for all of the Web Conferencing services, IIS Admin service, and World Wide Web publishing service to cease.
  2. If the SQL Server that is hosting the MPWEB database runs on the Cisco Unified MeetingPlace web server, continue with Step 3.
    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 applicable 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 connect remotely to the SQL Server.
  3. To access the command prompt, choose Start > Run and enter cmd .
  4. To connect to SQL Server by using osql with the SA account and the appropriate password, enter osql -U sa -S servername , where servername is the Windows server name.
    • If the SQL Server runs locally, you can omit the option -S servername .
    • If you are not allowed to connect to this SQL Server as sa, connect by using an account with enough privileges to back up a database.
  5. Choose a fully qualified path and filename for your database export.
    Note: If you are connected to the SQL Server by running osql on a remote workstation or server, this path must be valid on the Windows server that hosts SQL Server, not on your local workstation.
  6. To export the database, enter backup database MPWEB to disk = ' fullyqualifiedpath ' ' , where fullyqualifiedpath is the location that you chose in Step 5, then enter go .
  7. To confirm that the operation is successful, review the informational messages.
  8. To determine the slave database name(s) on your SQL Server, enter select name from sysdatabases where name like 'MPWEB%' , then enter go . The results should include either one or two slave databases.
  9. To back up the slave database(s), enter backup database [ MPWEB_ XX ] to disk = 'C:\temp\mpweb_ XX .dat' , where XX are the digits of the first slave database and brackets enclose the database name, then enter go .
  10. Repeat Step 9 for the second slave database, if applicable.
  11. To exit osql, enter exit .
  12. Save the mpweb.dat and each mpweb_ XX .dat file in a safe location, on a tape or network drive on another server, for example.
Examples: Exporting the MPWEB Database to Create a Backup File

In the following examples, the output is displayed for each command that is used in the To Create a Backup File by Exporting the MPWEB Database.

Sample Output for Connecting to the SQL Server
C:> osql -U sa -S SERVERNAME
Password: password
1>
Sample Output for Exporting to the Database
1> backup database MPWEB to disk = 'C:\temp\mpweb.dat'
2> go
Sample Output for Viewing Informational Messages
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)
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
MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1
Sample Output for Backing Up the Slave Database
1> backup database [MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1] to disk =
'C:\temp\mpweb_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.dat'
2> go
Sample Output for Exiting osql
1> exit
C:>
To Restore the Database

To complete this procedure, you must have a file called mpweb.dat or mpweb_XX.dat that was exported with the backup database command from a SQL Server with a version that is earlier or the same as the SQL Server to which you want to import the database.


  1. If the SQL Server that hosts the MPWEB database runs on the Cisco Unified MeetingPlace web server, continue with Step 2.
    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 you can connect remotely to the SQL Server.
  2. Access the command prompt. Choose Start > Run and enter cmd .
  3. Connect to SQL Server by using osql with the SA account and the appropriate password.
    Enter osql -U sa -S servername , where servername is the Windows server name.
    • If the SQL Server runs locally, you can omit the option -S servername .
    • If you are not allowed to connect to this SQL Server as SA, connect by using an account with enough privileges to back up a database.
  4. Check if a database called MPWEB exists on this server.
    Enter select name from sysdatabases where name like 'MPWEB%' , then enter go .
  5. If a MPWEB database exists, verify that no Cisco Unified MeetingPlace Web Conferencing server is currently using this database.
  6. (Optional) If one or multiple Cisco Unified MeetingPlace web servers are using the database, do the following:
    1. Log on as an administrator on each server.
    2. Stop the Cisco MeetingPlace Web Conferencing service.
    3. Wait for all the Cisco MeetingPlace Web Conferencing services, the IIS Admin service, and the World Wide Web publishing service to stop.
    4. To drop the database, enter drop database MPWEB , then enter go .
  7. Before you import your MPWEB database to SQL Server, find out which database physical files are associated with this MPWEB database.
    Enter restore filelistonly from disk = 'C:\temp\mpweb.dat' , then enter go .
  8. Verify the installation folder of the SQL Server where you want to restore this database and check the physical location of the SQL Server master database.
    Enter sp_helpfile master , then enter go .
    Note: Unless you have a specific reason to restore your MPWEB database to another disk location, such as for performance and tuning or data recovery, we recommend that you restore the MPWEB database to the default Data folder of this SQL Server installation.
  9. Restore your database and relocate the database physical files to the correct location.
    Enter restore database MPWEB from disk = 'C:\temp\mpweb.dat' with move 'MPWEBData' to 'D:\MSSQLServer\Data\MPWEB.MDF', move 'MPWEBLog' to 'D:\MSSQLServer\Data\MPWEB.LDF' , then enter go .
    Note: You must use the with move clause to successfully restore the database because the database backup file contains physical file locations that are not valid for this SQL Server installation.
  10. Ensure that the operation was successful by reviewing the informational messages.
  11. To restore the MPWEB_XX slave database files, repeat Step 9 and Step 10 for each slave database.
  12. To exit osql, enter exit .
Examples: Restoring the Database

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

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
-----------------------------------------------------
MPWEB
1>
Sample Output for Dropping the Database
1> drop database MPWEB
2> go
Deleting database file 'D:\MSSQLServer\Data\MPWEB.LDF'.
Deleting database file 'D:\MSSQLServer\Data\MPWEB.MDF'.
1>
Sample Output for Checking Associated Files

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

  1. 1> restore filelistonly from disk = 'C:\temp\mpweb.dat'
    2> go
    ---------------------------------------------------
    LogicalName PhysicalName Type FileGroupName Size MaxSize
    ----------- ------------------------ ------ ------------- --------------
    ---------------------
    MPWEBData D:\MSSQLServer\Data\MPWEB.mdf D PRIMARY
    2490368.000000 35184372080640.000000
    MPWEBLog D:\MSSQLServer\Data\MPWEB.ldf L NULL
    1310720.000000 35184372080640.000000
Sample Output for Verifying Folder Installation and Location of SQL Database

In this example, SQL Server (version 2000) was installed in D:\MSSQLServer, and the default 'Data' folder is D:\MSSQLServer\data.

1> sp_helpfile master
2> go
name filename filegroup size maxsize growth
usage
----------------------------------------------------------------------
master
D:\MSSQLServer\data\master.mdf
PRIMARY
15744 KB Unlimited 10% data only
1>
Sample Output for Restoring the MPWEB Database by Using the Move Clause

In this example, additional running upgrade step messages are displayed because the database backup file was created by an earlier version of SQL Server.

1> restore database MPWEB from disk = 'C:\temp\mpweb.dat' with move 'MPWEBData' to
'D:\MSSQLServer\Data\MPWEB.MDF', move 'MPWEBLog' to 'D:\MSSQLServer\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>

===== Sample Output for Restoring the MPWEB Slave Database =====

1> restore database [MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1] from disk =
'C:\temp\mpweb_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.dat' with move
'MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1Data' to
'D:\MSSQLServer\Data\MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.MDF', move
'MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1Log' to
'D:\MSSQLServer\Data\MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.LDF'
2> go
Sample Output for Exiting osql
1> exit
C:>

Rating: 0.0/5 (0 votes cast)

Personal tools