Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4
Appendix A: Cisco Unified MeetingPlace Web Conferencing and SQL Server
Downloads: This chapterpdf (PDF - 297.0KB) The complete bookPDF (PDF - 4.38MB) | Feedback

Cisco Unified MeetingPlace Web Conferencing and SQL Server

Table Of Contents

Cisco Unified MeetingPlace Web Conferencing and SQL Server

About Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

How to Restore the Cisco Unified MeetingPlace Web Server After Boot Failure

Restoring the Cisco Unified MeetingPlace Web Server if the Audio Server Has Not Changed

How to Change the SQL Password and Apply the New Password to Cisco Unified MeetingPlace Web Conferencing

Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing

How to Modify the SQL Database Properties to Manage MPWEB Database Size

How to Back Up and Restore MPWEB SQL Database

How to Detach and Attach the MPWEB SQL Database

How to Replace a Cisco Unified MeetingPlace Web Server and Retain the SQL Database

How to Migrate from a Local SQL Server Database to a Remote SQL Server Database

How to Access Cisco Unified MeetingPlace Web Conferencing When Locked-Out Due to Incorrect User Authentication Setup


Cisco Unified MeetingPlace Web Conferencing and SQL Server


This chapter includes procedures for managing and maintaining the SQL Server database.


Note The SQL commands and operations described in this chapter are provided only for your convenience and should not be treated as definitive reference. For additional details about these commands and operations, search the Microsoft Knowledgebase or download the free Microsoft SQL Server 2000 Online Help package from Microsoft.


See the following sections:

About Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

How to Restore the Cisco Unified MeetingPlace Web Server After Boot Failure

How to Change the SQL Password and Apply the New Password to Cisco Unified MeetingPlace Web Conferencing

How to Modify the SQL Database Properties to Manage MPWEB Database Size

How to Back Up and Restore MPWEB SQL Database

How to Detach and Attach the MPWEB SQL Database

How to Replace a Cisco Unified MeetingPlace Web Server and Retain the SQL Database

How to Migrate from a Local SQL Server Database to a Remote SQL Server Database

How to Access Cisco Unified MeetingPlace Web Conferencing When Locked-Out Due to Incorrect User Authentication Setup


Note In this chapter, SQL Server refers to either full SQL Server or Microsoft SQL Desktop Engine (MSDE).


About Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

The Cisco Unified MeetingPlace Web Conferencing SQL database is created from information that is replicated from the Cisco Unified MeetingPlace Audio Server. The Cisco Unified MeetingPlace Replication Service continues to update this SQL database in real-time as changes occur in the Audio Server database.

The Cisco Unified MeetingPlace Gateway SIM is a common component of the Cisco Unified MeetingPlace gateway products. Gateway SIM functions as the channel through which gateways communicate with the Audio Server. The Gateway SIM allows you to add and delete units from the Audio Server.

Once a unit (gateway server) is attached to a Audio Server, you should only detach it for the following reasons:

You are replacing an old gateway server with a new server.

In this case, detach the old gateway server from the Audio Server to decommission it.

You are replacing the Audio Server with a brand new machine.

The new Audio Server uses the same database from the old server.

The new Audio Server uses a brand new database.

You are testing the gateway server in a lab against a lab Audio Server.

When the gateway is ready to be put into production, detach it from the lab Audio Server and re-attach it to a production Audio Server.

Because the Web Conferencing SQL database is based on the Audio Server database, a serious database corruption can occur if you switch the Audio Server and continue to use the old SQL database on the Cisco Unified MeetingPlace web server.

Web Conferencing stores the hostname of the Audio Server in its SQL database. This hostname is the value you entered when you installed Web Conferencing. To prevent SQL database corruption, when the web server boots up, it compares this hostname with the hostname of the Audio Server that is configured in the Gateway SIM. If they do not match, Web Conferencing considers the Audio Server to have changed and fails to boot up.

To restore the Cisco Unified MeetingPlace web server after boot failure, see the "How to Restore the Cisco Unified MeetingPlace Web Server After Boot Failure" section.

How to Restore the Cisco Unified MeetingPlace Web Server After Boot Failure

This section describes how to restore Cisco Unified MeetingPlace Web Conferencing functions after a boot failure due to mismatched Audio Server hostnames.

See the following procedures:

To Restore the Cisco Unified MeetingPlace Web Server if the Audio Server Has Changed

To Restore the Cisco Unified MeetingPlace Web Server by Using SQL Enterprise Manager

To Restore the Cisco Unified MeetingPlace Web Server by Using osql Commands

To Restore the Cisco Unified MeetingPlace Web Server if the Audio Server Has Changed

You must drop (delete) the SQL database that Cisco Unified MeetingPlace Web Conferencing is currently using and create a new SQL database from the database on the new Cisco Unified MeetingPlace Audio Server.


Step 1 Delete the current MPWEB database by completing the instructions in the "To Detach the Database" section. You do not need to delete the MPWEB-Slave-#### database.

Step 2 Confirm that the physical files associated with the MPWEB database (mpweb.mdf and mpweb.ldf) are deleted from your hard disk.

Step 3 Restart the Cisco MeetingPlace Web Conferencing service or reboot the server.

When Cisco MeetingPlace Web Conferencing services start up, a new MPWEB database is created.


Restoring the Cisco Unified MeetingPlace Web Server if the Audio Server Has Not Changed

If the Cisco Unified MeetingPlace web server cannot be started because you have changed the value of the hostname in the Gateway SIM administrator user interface, modify the value of the hostname in the SQL database to match the new hostname value in the Gateway SIM.

Do one of the following two procedures:

To Restore the Cisco Unified MeetingPlace Web Server by Using SQL Enterprise Manager

To Restore the Cisco Unified MeetingPlace Web Server by Using osql Commands

Restrictions

This procedure is strictly limited to the situation where the database on the Cisco Unified MeetingPlace Audio Server system is the same as the database on the Cisco Unified MeetingPlace web server.


Caution Misuse of this procedure in any other situations will cause database corruption and subsequent Cisco Unified MeetingPlace Web Conferencing functional failures.

To Restore the Cisco Unified MeetingPlace Web Server by Using SQL Enterprise Manager


Step 1 Stop the Cisco MeetingPlace Web Conferencing service.

For instructions, see the "Stopping All Cisco Unified MeetingPlace Web Conferencing Services" section on page 2-2.

Step 2 Verify that all Web Conferencing services are shutdown, including the IIS Admin Service and WWW Publishing Service.

Step 3 Open Enterprise Manager and navigate to the \Databases folder.

Step 4 Choose and expand the MPWEB database.

Step 5 From the left pane, choose Tables.

Step 6 In the right pane right-click System, then from the pop-up menu, choose Open Table > Return All Rows.

Step 7 Change the value in the HostName column to the desired value.

Step 8 Start the Cisco MeetingPlace Web Conferencing service or reboot the server.


To Restore the Cisco Unified MeetingPlace Web Server by Using osql Commands


Step 1 Open a DOS command window.

Step 2 Log in to the SQL Server by entering C:\osql -U userid -P password, replacing userid and password with the appropriate value.

Step 3 To specify that you want to access the MPWEB database, enter use mpweb, then enter go.

Step 4 To specify the new hostname value, enter update system set hostname = `hostname', where hostname is the Audio Server configured in the Gateway SIM administrator's user interface, then enter go.

Step 5 To verify the new value in the SQL database, enter select hostname, then enter go.


Example

In this example, the following server information is used:

Cisco Unified MeetingPlace Audio Server hostname stored in the SQL database is an IP address of 172.16.8.40.

Cisco Unified MeetingPlace Audio Server specified in the Gateway SIM administrator's user interface is 'SanJoseMP.cisco.com'.

172.16.8.40 is the IP address of SanJoseMP.cisco.com, and the server has not changed.

C:\>osql -U sa -P password
1> use mpweb
2> go
1> update system set hostname = 'SanJoseMP.cisco.com'
2> go
(1 row affected)
1> select hostname from system
2> go
 hostname
 ----------------------------------------------------------------
 SanJoseMP.cisco.com
(1 row affected)
1>exit

How to Change the SQL Password and Apply the New Password to Cisco Unified MeetingPlace Web Conferencing

To change the SQL password and apply the new password to Cisco Unified MeetingPlace Web Conferencing, complete the following tasks in the order shown:

Do one of the following, as applicable:

To Change the SQL Password by Using Enterprise Manager

To Change the SQL Password by Using osql

To Apply the New SQL Password to Cisco Unified MeetingPlace Web Conferencing

To Change the SQL Password by Using Enterprise Manager

The most convenient method for changing the SQL Server account password is to use Enterprise Manager, which is the administrative tool provided by Microsoft SQL Server.

To use this procedure, you must know the old SQL password. If you do not know the old SQL password, see the "To Change the SQL Password by Using osql" section.


Caution Changing the SQL Server account password while the Cisco Unified MeetingPlace Web Conferencing service is running will result in an immediate outage. Stop the service before beginning this procedure.

Step 1 Open Enterprise Manager, expand the Security folder, and choose Logins.

A list of accounts displays on the right.

Step 2 Double-click the SQL account that you want to change.

Step 3 Change the password in the configuration window.

Step 4 Proceed to the "Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing" section.


To Change the SQL Password by Using osql

You can use this procedure whether you know the old SQL password or not.


Step 1 Open a DOS command window.

Step 2 If you know the old SQL password, log in to SQL Server by entering C:\osql -U userid -P password, replacing userid and password with the appropriate value, then proceed to Step 3.

or

If you do not know the old SQL password, log in to SQL Server by entering C:\osql -E nt_acct, where nt_acct is NT account that has access right to the server, then proceed to Step 4.

Step 3 To change the password, enter sp_password sa_pwd, new_pwd, sa, where sa_pwd is the old sql password and new_pwd is the new sql password.

Step 4 To change the password, enter sp_password null, new_pwd, sa, where null represents the password that you do not know and new_pwd is the new sql password.

Step 5 Enter go.

Step 6 Proceed to the "Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing" section.


Examples: Changing the SQL Password by Using osql

In the following examples, the output is displayed for each command that is used in the "To Change the SQL Password by Using osql" section.

Sample Output for Changing the SQL Password if You Know the Old Password

C:>\osql -U sa -P sa_pwd
>sp_password sa_pwd, new_pwd, sa
>go
Password changed
1> exit

Sample Output for Changing the SQL Password if You Do Not Know the Old Password

This example shows the osql commands executed to log in to osql by using the NT account mpadmin and to change the SQL account SA password from some unknown value to new_pwd.

C:\>osql -E mpadmin
1>	sp_password null, new_pwd, sa
2>  go
Password changed
1> exit

Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing

Before You Begin

Ensure that the username and password information that you will provide exists on the SQL Server and that the proper database access rights are assigned. For more information, see the "Creating a Least Privileged SQL Account" section in Chapter 2 of the applicable Installation Planning Guide for Cisco Unified MeetingPlace Web Conferencing, at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

Stop the Cisco Unified MeetingPlace Web Conferencing service.

Verify that all Web Conferencing services are stopped, including IIS Admin and WWW Publishing services.


Caution You cannot create or change the username or password on the SQL Server in the Web Conferencing tab. This tab supplies Web Conferencing with only the proper SQL database login information.

To Apply the New SQL Password to Cisco Unified MeetingPlace Web Conferencing


Step 1 Open the Cisco Unified MeetingPlace Gateway Configurations utility.

a. Right-click the Cisco Unified MeetingPlace (orange door) icon in the system tray.

b. Click Properties.

Step 2 Click the Web Conferencing tab.

Step 3 Change the old SQL password to the new SQL password that you configured in the "To Change the SQL Password by Using Enterprise Manager" procedure.

Step 4 Click Apply, then click OK.

Step 5 Restart the Cisco MeetingPlace Web Conferencing service.


How to Modify the SQL Database Properties to Manage MPWEB Database Size

The MPWEB database that Cisco Unified MeetingPlace Web Conferencing creates is comprised of two files: MPWEB.mdf and MPWEB.ldf. The .mdf file contains the actual data, while the .ldf contains changes (both the content and timing) made to that data.

On a SQL server that has been actively and properly managed through regular database backup, this .ldf file (also called Transaction Log) remains a reasonable size. However, if the SQL database has not been backed up in a while, this transaction log may become very large.

To help prevent the file from growing too large, configure the following three important properties for the MPWEB database:

Recovery = Simple

Torn Page Detection = On

Auto Shrink = On

To Modify the SQL Database Properties to Manage Database Size


Caution This procedure applies only to the MPWEB database. Do not apply this procedure to the MPWEB-Slave database.

Step 1 Open a DOS command window.

Step 2 To log in to SQL Server, enter C:\osql -U userid -P password, replacing userid and password with the appropriate value.

Step 3 To see the current properties of the database, enter sp_helpdb MPWEB, then enter go.

Step 4 To modify properties, enter alter database mpweb set auto_shrink on, recovery simple, torn_page_detection on, then enter go.

Step 5 If you are low on disk space because the database file is already large, force an immediate database shrink and remove empty space in the database files by entering dbcc shrinkdatabase ('mpweb', percent). where percent is the amount of free space that you want to allow.


Examples: Modifying the SQL Database Properties to Manage Database Size

In the following examples, the output is displayed for each command that is used in the "To Modify the SQL Database Properties to Manage Database Size" procedure.

Sample Output for Viewing Current Database Properties

In this example, Recovery Mode is set to FULL and Torn Page Detection and Auto Shrink are not configured on this database.

1> sp_helpdb MPWEB
2> go
name         db_size       owner        dbid    created         status 
compatibility_level
MPWEB    1254.00 MB    sa           5       Oct 16 2003
Status=ONLINE, Updateability=READ_WRITE, UserAccess=MULTI_USER, Recovery=FULL,
Version=539, Collation=SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52,
IsAutoCreateStatistics, IsAutoUpdateStatistics

Sample Output for Modifying Database Properties

1> alter database mpweb set auto_shrink on, recovery simple, torn_page_detection on
2> go
1> sp_helpdb MPWEB
2> go
name         db_size       owner        dbid    created         status 
compatibility_level
MPWEB   1254.00 MB    sa            5       Oct 16 2003
Status=ONLINE, Updateability=READ_WRITE, UserAccess=MULTI_USER, Recovery=SIMPLE,
Version=539, Collation=SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52, IsAutoShrink,
IsTornPageDetectionEnabled, IsAutoCreateStatistics, IsAutoUpdateStatistics

Sample Output for Decreasing File Size

In this example, the size of the files are decreased in the MPWEB database to allow 10 percent free space in the files of MPWEB.

1> dbcc shrinkdatabase ('mpweb', 10)
2> go
DbId   FileId CurrentSize MinimumSize UsedPages   EstimatedPages
 ------ ------ ----------- ----------- ----------- --------------
      5      2        2912        1280        2912           1280
(1 row affected)
DBCC execution completed. If DBCC printed error messages, contact your system
administrator.

How to Back Up and Restore MPWEB SQL Database

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

To Create a Backup File by Exporting the MPWEB Database

To Restore the Database

To Create a Backup File by Exporting the MPWEB Database

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


Step 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), proceed to 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.

Step 2 If the SQL Server that is hosting the MPWEB database runs on the Cisco Unified MeetingPlace web server, proceed to 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.


Step 3 To access the command prompt, choose Start > Run and enter cmd.

Step 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.

Step 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.


Step 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.

Step 7 To confirm that the operation is successful, review the informational messages.

Step 8 If the Web Conferencing server is running 5.4(156) or a later 5.4 release, skip to Step 11. The MPWEB-Slave database is no longer used in these releases.

Step 9 To determine the slave database name on your SQL Server, enter select name from sysdatabases where name like 'MPWEB%', then enter go.

Step 10 To back up the slave database, enter backup database [MPWEB-Slave-XXXXXXX] to disk = 'C:\temp\mpweb-slave-XXXXXXXX.dat', where XX are the digits of your MPWEB-Slave database and brackets enclose the database name because of the dash in the filename, then enter go.

Step 11 To exit osql, enter exit.

Step 12 Save the mpweb.dat and MPWEB-Slave-XXXXXXXX (if applicable) 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" section.

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-Slave-37102728.

1> select name from sysdatabases where name like 'MPWEB%'
2> go
---------------------------------------------------
name                
[char              ]
--------------------
MPWEB               
MPWEB-Slave-37102728

Sample Output for Backing Up the Slave Database

1> backup database [MPWEB-Slave-37102728] to disk = 'C:\temp\mpweb-slave-37102728.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-slave-#######.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.


Step 1 If the SQL Server that hosts the MPWEB database runs on the Cisco Unified MeetingPlace web server, proceed to 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.


Step 2 Access the command prompt.

Choose Start > Run and enter cmd.

Step 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.

Step 4 Check if a database called MPWEB exists on this server.

Enter select name from sysdatabases where name like 'MPWEB%', then enter go.

Step 5 If a MPWEB database exists, verify that no Cisco Unified MeetingPlace Web Conferencing server is currently using this database.

Step 6 (Optional) If one or multiple Cisco Unified MeetingPlace web servers are using the database, do the following:

a. Log on as an administrator on each server.

b. Stop the Cisco MeetingPlace Web Conferencing service.

c. Wait for all the Cisco MeetingPlace Web Conferencing services, the IIS Admin service, and the World Wide Web publishing service to stop.

d. To drop the database, enter drop database MPWEB, then enter go.

Step 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.

Step 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.


Step 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.


Step 10 Ensure that the operation was successful by reviewing the informational messages.

Step 11 To restore the MPWEB-Slave-#### database file (if applicable), repeat Step 9 and Step 10.

Step 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" section.

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> 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-Slave-####] from disk = 'C:\temp\mpweb-slave-####.dat' with
move 'MPWEB-Slave-####Data' to 'D:\MSSQLServer\Data\MPWEB-Slave-####.MDF', move
'MPWEB-Slave-####Log' to 'D:\MSSQLServer\Data\MPWEB-Slave-####.LDF'
2> go

Sample Output for Exiting osql

1> exit
C:>

How to Detach and Attach the MPWEB SQL Database

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

To Detach the Database

To Attach the Database

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.


Step 1 On the Cisco Unified MeetingPlace web server, log on as administrator.

Step 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.

Step 3 If the SQL Server hosting the MPWEB database runs on the Cisco Unified MeetingPlace web server, proceed to 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.


Step 4 Access the command prompt.

Choose Start < Run, then enter cmd.

Step 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.

Step 6 Access the MPWEB database.

Enter use mpweb, then enter go.

Step 7 Display a list of the database files.

Enter sp_helpfile, then enter go.

Step 8 Access the SQL Server master database.

Enter use master, then enter go.

Step 9 Detach the MPWEB database.

Enter sp_detach_db 'MPWEB, then enter go.

Step 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.

Step 11 Determine the slave database name on your SQL Server.

Enter select name from sysdatabases where name like 'MPWEB%, then enter go.

Step 12 (Optional) If there is a second database named MPWEB-Slave-####, repeat Step 6 through Step 10 to detach that database, replacing the database name MPWEB with MPWEB-Slave-####.


Note The two databases are logically linked; therefore, if you want to archive the detached MPWEB database, you must do the same for the MPWEB-Slave-#### database. If you want to reattach the MPWEB database to another SQL Server, you must reattach the MPWEB-Slave-#### database, too.


Step 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" procedure.

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-Slave-37102728.

1> select name from sysdatabases where name like 'MPWEB%'
2> go
---------------------------------------------------
name                
[char              ]
--------------------            
MPWEB-Slave-37102728

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.


Step 1 If the SQL Server to which you want to attach your MPWEB database runs on the Cisco Unified MeetingPlace web server, proceed to 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.

Step 2 Access the command prompt.

Choose Start > Run, then enter cmd.

Step 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.


Step 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.


Step 5 Determine if a database named MPWEB already exists on this server.

Enter select name from sysdatabases where name = 'MPWEB', then enter go.

Step 6 If no MPWEB database exists, proceed to 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" procedure.


Step 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.


Step 8 Copy the MPWEB.mdf and MPWEB.ldf files under the data folder that you identified in Step 7.

Step 9 Attach the MPWEB database.

Enter sp_attach_db 'MPWEB','data path\MPWEB.mdf','data path\MPWEB.ldf', then enter go.

Step 10 (Optional) 1If you have a valid set of files for the MPWEB-Slave-#### database, repeat Step 5 through Step 10, replacing MPWEB with MPWEB-Slave-#### to attach that database.

Step 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" section.

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:>

How to Replace a Cisco Unified MeetingPlace Web Server and Retain the SQL Database

During installation, a MPWEB database is tied to a specific Cisco Unified MeetingPlace web server through a unique GUIDWebID that is generated by the Cisco Unified MeetingPlace Web Conferencing installer and stored in the registry and SQL database. Therefore, if you want to transfer the MPWEB SQL database and all attachments from the old server to a new server, the new server must use the same GUIDWebID as the old server. This requires preparing the following three components from the old server to the new server:

The whole \MPWEB\Meetings folder (including all sub-folders) in zipped or unzipped format.

The GUIDS.reg file with modifications to add the GUIDWebID and the mpweb-slave database filename information. The GUIDS.reg file, as well as the GUIDWebID and DBName registry values, come from the old server.

A backup of the MPWEB database from the old server.


Note You do not need to back up the mpweb-slave database (MPWEB-Slave-#######) because it can be regenerated on the new machine.


To replace an existing Cisco Unified MeetingPlace web server with a new server and retain the attachments of past meetings so that they are accessible from the new server, do the following procedures in the order shown:

To Prepare the Current Cisco Unified MeetingPlace Web Server

To Install the Replacement Cisco Unified MeetingPlace Web Server

To Build the Replacement Cisco Unified MeetingPlace Web Server

To Prepare the Current Cisco Unified MeetingPlace Web Server


Step 1 Stop all Cisco Unified MeetingPlace Web Conferencing services, including the Gateway SIM service.

For instructions, see the "Stopping All Cisco Unified MeetingPlace Web Conferencing Services" section on page 2-2.

Step 2 Detach this Cisco Unified MeetingPlace web server from the Cisco Unified MeetingPlace Audio Server.

a. Open the Gateway SIM Agent.

For instructions, see the "Opening the MeetingPlace Gateway Configurations Utility" section on page 2-6.

b. From the Gateway SIM tab, write down the hostname or IP address of the Cisco Unified MeetingPlace Audio Server for future reference.


Note You must use the same server reference when you install the new Cisco Unified MeetingPlace web server. If the Audio Server is specified as a hostname, you will enter that same hostname; if it is specified as an IP address, you will use an IP address later.


c. Detach this Cisco Unified MeetingPlace web server from the Audio Server by clicking Delete Unit.

Step 3 Make a copy of the entire \MPWEB\Meetings folder and its contents.

Step 4 Make a copy of the GUIDS.reg file.

You can find this file where Cisco Unified MeetingPlace Web Conferencing application files are stored.

Step 5 Open regedit and obtain the registry values for GUIDWebID and DBName.


Caution Ensure that the registry values are correct. Compare the values that you obtained in Step 5 against what you enter in Step 6.

Step 6 Open GUIDS.reg in a text editor and add the GUIDWebID and DBName registry paths and key values.

Step 7 Save the file with these changes.

Step 8 Make a backup of the MPWEB database.

For instructions, see the "How to Back Up and Restore MPWEB SQL Database" section.

Step 9 Copy the attachments, GUIDS.reg and the MPWEB backup to the new server.

Step 10 Proceed to the "To Install the Replacement Cisco Unified MeetingPlace Web Server" procedure.


To Install the Replacement Cisco Unified MeetingPlace Web Server

You must install the same release of Cisco Unified MeetingPlace Web Conferencing or later on the new server as is running on the old server. For example, if you are running Release 5.4 on the old server, you must install Release 5.4 or a later release on the new server.

Before you install Web Conferencing on the new server, you must run GUIDS.reg on the new server to add the following four keys in to the registry: GUID IDs for Site, System, Web, and mpweb-slave db filename (if applicable for your release). To run GUIDS.reg, right-click GUIDS.reg, then choose merge.


Step 1 Install Cisco Unified MeetingPlace Web Conferencing.

For instructions, see Chapter 2 in the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing, at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

Step 2 When you are prompted at the end of the installation, reboot the server.

After the initial reboot, the installation program continues and may reboot a few more times to complete the installation.

Step 3 When you are prompted for the Cisco Unified MeetingPlace Audio Server information, enter the value that you wrote down in Step 2 of the "To Prepare the Current Cisco Unified MeetingPlace Web Server" procedure.

Step 4 After the installation completes, verify that Cisco Unified MeetingPlace Web Conferencing is functional.

Step 5 Proceed to the "To Build the Replacement Cisco Unified MeetingPlace Web Server" procedure.


To Build the Replacement Cisco Unified MeetingPlace Web Server

Verify that the release of Cisco Unified MeetingPlace Web Conferencing that is installed on the new server is either the same or later than the release installed on the old server. For example, if you are running Release 5.4 on the old server, you must be running Release 5.4 or a later release on the new server.


Step 1 Stop all Cisco Unified MeetingPlace Web Conferencing services.

Step 2 Delete the MPWEB SQL database that is created automatically during the Cisco Unified MeetingPlace Web Conferencing installation by using either Enterprise Manager or the osql drop database command.

For more information about this osql command, see the "To Restore the Database" procedure.

Step 3 Restore the old MPWEB database on to the new server by using either Enterprise Manager or the osql restore database command.

For more information about this osql command, see the "To Restore the Database" procedure.

Step 4 Delete all contents in the \MPWeb\Meetings\ folder.

Step 5 Restore all the files and attachments from the old server in to \MPWeb\Meetings folder.

Step 6 Reboot the server.

or

Restart the Cisco Unified MeetingPlace Web Conferencing service.

Step 7 Access the home page and log in with a System Manager profile to make the appropriate changes in the Web Server administrative pages, such as the web server Hostname.


How to Migrate from a Local SQL Server Database to a Remote SQL Server Database

If you installed the Cisco Unified MeetingPlace Web Conferencing by using a local MSDE (Microsoft SQL Server Desktop Engine) or SQL Server database, do the following tasks in the order shown to migrate the MPWEB database to a remote server.


Note In this section, "SQL Server" refers to any supported version of Microsoft SQL Server or MSDE, except where otherwise noted.



Caution Follow the tasks and procedures in this section carefully. Failure to do so may result in needing to recreate the database and loss of access to archived meeting attachments on the Cisco Unified MeetingPlace Web Conferencing server.

1. Verify that the remote SQL Server installation meets Cisco Unified MeetingPlace Web Conferencing requirements. Refer to the System Requirements for Cisco Unified MeetingPlace Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

2. If you have not already done so, upgrade the Cisco Unified MeetingPlace Web Conferencing server to release 5.4(156) or a later 5.4(x) release. For instructions, refer to the release notes for the release and to the "Upgrading to Web Conferencing Release 5.4" chapter of the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

3. Stop the Cisco MeetingPlace Web Conferencing service and back up your existing MPWEB database. See the "To Create a Backup File by Exporting the MPWEB Database" procedure. (Note that the MPWEB-Slave database is no longer used in Web Conferencing release 5.4(156) and later 5.4(x) releases.)

4. Restore the MPWEB database on the remote SQL Server. See the "To Restore the Database" procedure.

5. Reconfigure the ODBC settings on your Cisco Unified MeetingPlace Web Conferencing server to point to the new SQL Server. Do the "To Reconfigure ODBC Settings on the Cisco Unified MeetingPlace Web Conferencing Server" procedure.

6. Update the registry on the Cisco Unified MeetingPlace Web Conferencing server. Do the "To Update the Registry on the Cisco Unified MeetingPlace Web Conferencing Server" procedure.

7. Decommission the local SQL server installation. (It is important to decommission the local SQL server installation to ensure that the old MPWEB SQL database cannot be used by the Cisco Unified MeetingPlace Web Conferencing services in the event that an ODBC or network configuration problem occurs.) To decommission the installation, make sure the Cisco MeetingPlace Web Conferencing service is still stopped and either do the "To Detach the Database" procedure or stop and disable the SQL Server service or stop the SQL Server service and uninstall Microsoft SQL Server or MSDE.

8. Restart the Cisco MeetingPlace Web Conferencing service.

To Reconfigure ODBC Settings on the Cisco Unified MeetingPlace Web Conferencing Server


Step 1 On the Cisco Unified MeetingPlace web server, log on as administrator.

Step 2 On the Windows Start menu, click Program Files > Administrative Tools > Data Source (ODBC).

Step 3 Click the System DSN tab.

Step 4 Select MPWEB and click Configure. The Microsoft SQL Server DSN Configuration window opens.

Step 5 In the Server field, select the name of the server you want to use for the MPWEB database.

Step 6 Click Next.

Step 7 For the method of verifying login ID authenticity, click With SQL Server Authentication Using a Login ID and Password Entered by the User.

Step 8 Verify that the Connect to SQL Server to Obtain Default Settings for the Additional Configuration Options check box is checked, and enter the SQL account login ID and password.

Step 9 Click Next.

Step 10 In the Change the Default Database to field, verify that the correct database is selected, and click Next to accept other defaults.

Step 11 Click Test Data Source. If the data source is accessible, you should see a message indicating that the tests were completed successfully.


To Update the Registry on the Cisco Unified MeetingPlace Web Conferencing Server


Step 1 From the Windows start menu, click Run, type Regedit, and press Enter.

Step 2 Browse to HKEY_LOCAL_MACHINE\Software\Latitude\MeetingPlace Webpublisher\ODBC.

Step 3 Double-click DatabaseServerName, and enter the name of the remote SQL server.

Step 4 Delete the DBReset registry key.

Step 5 Set the value for DBUserID and DBPassword in clear text so the system knows which user ID and password to use when connecting to the SQL Server.


Note Do not change the value of the DBName key (MPWEB). When you restart the MeetingPlace Web Conferencing service, the system will encrypt the values held by the DBUserID and DBPassword keys for security reasons and recreate the DBReset key to keep track of the fact that the values are now encrypted.



How to Access Cisco Unified MeetingPlace Web Conferencing When Locked-Out Due to Incorrect User Authentication Setup

If you configure Cisco Unified MeetingPlace Web Conferencing to use anything other than the MeetingPlace native login form for user authentication, you may not be able to log in to Cisco Unified MeetingPlace through the web due to incomplete user authentication configuration. For example, you configured LDAP, then MeetingPlace user authentication, but failed to enter a valid LDAP hostname or to ensure that the LDAP user IDs existed in MeetingPlace. In such circumstances, you are unable to log into Web Conferencing to correct your configuration errors.

To restore access to Web Conferencing, you can do one of the following:

Create or correct the MeetingPlace profile to allow you to log in by using MeetingTime. For more information about MeetingTime, see the applicable Administration Guide for Cisco Unified MeetingPlace Audio Server, at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_maintenance_guides_list.html.

Edit the SQL database and reset the mode to MeetingPlace native login form. Do the following procedure.

To Update the Cisco Unified MeetingPlace Web Conferencing User Authentication Mode in SQL Server


Step 1 Open a DOS command window.

Step 2 Log in to the SQL server by entering C:\osql -U userid -P password, replacing userid and password with the appropriate value.

Step 3 To specify that you want to access the MPWEB database, enter use mpweb, then enter go.

Step 4 Enter Update web set AuthMode = 1.

Step 5 Enter Update web set AuthLoginMode = 1, then enter go.

Table A-1 and Table A-2 provide mode definitions as a reference.

Table A-1 AUTHMODE Commands

AUTHMODE Command
Value

#define SQLCONFIG_AUTHMODE_NONE

0

#define SQLCONFIG_AUTHMODE_MP

1

#define SQLCONFIG_AUTHMODE_LDAP

2

#define SQLCONFIG_AUTHMODE_LDAPMP

3

#define SQLCONFIG_AUTHMODE_TRUSTEXT

4

#define SQLCONFIG_AUTHMODE_BASIC_DOMAIN

5

#define SQLCONFIG_AUTHMODE_WIA

6


:

Table A-2 AUTHLOGINMODE Commands

AUTHMODE Command
Value

#define SQLCONFIG_AUTHLOGINMODE_NONE

0

#define SQLCONFIG_AUTHLOGINMODE_WEB

1

#define SQLCONFIG_AUTHLOGINMODE_HTTP

2