Cisco Unified MeetingPlace Release 8.0 -- Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server

From DocWiki

Revision as of 16:54, 2 July 2010 by MeetingPlace Moderator (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 8.0

Back to: Configuration

Back to: Maintenance


Note: This topic does not apply to deployments in which users schedule meetings from the Cisco WebEx site. For information about Cisco WebEx integration deployments, see the Planning Guide for Cisco Unified MeetingPlace at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.


Note: The SQL commands and operations described in this section 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.


Contents

Accessing Information on the SQL Server Database

Use the Database administration page to access information on the SQL Server database.


Before You Begin

If you are using a remote SQL server, make sure that the time on SQL server is synchronized with the Cisco Unified MeetingPlace Application Server and Web Server.


Procedure
  1. Sign in to the Cisco Unified MeetingPlace web user portal.
  2. Select Admin.
  3. Select Database.
  4. Select a database command.
  5. Select Submit.


How to Create and Use a Least-Privileged SQL Account for the Web Server

By default, the Cisco Unified MeetingPlace Web Server software installer suggests using the SQL built-in sa administrator account as the SQL Server user name. Often, a strong password for the sa account is sufficiently secure to protect your system from unauthorized access. However, if you do not want to continue to use a SQL account that has full administration rights after the installation is complete, you can create a SQL account with minimal privileges that is dedicated for use withCisco Unified MeetingPlace, and configure the Web Server to use this account.


Complete the following procedures in the order shown to create and use a least-privileged SQL account:


Creating a Least-Privileged SQL Account for the Web Server

Caution! If you choose to create a SQL account that is dedicated for use with Cisco Unified MeetingPlace, ensure that it meets all the specified database role requirements in this procedure. Failure to do so can cause a database connection failure between the Web Server software and the SQL Server and result in a total outage or broken features.


Note: If Cisco TAC determines that your SQL account does not meet requirements, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Server software database so that a new database can be created once the account problem is remedied.


Procedure
  1. Open the SQL Server Enterprise Manager and create a new login:
    1. On the Start menu, select Programs > SQL Server 2000 > Enterprise Manager.
    2. Select a server group to expand it, then select the name of a server.
    3. Select Security > New Login.
    The SQL Server Login Properties window displays.
  2. Enter a name for the login on the General tab.
  3. Select SQL Server Authentication.
  4. Enter a password for the account.
  5. Select MPWEB from the Database drop-down menu to set the MPWEB database as the default database.
  6. Select the Database Access tab.
  7. Specify the database roles for the MPWEB database:
    1. Check the MPWEB database in the Databases table.
    2. Check the boxes for the following roles in the Database Roles table:
      • db_datareader
      • db_datawriter
      • db_ddladmin
  8. Repeat Step 7 for each additional MPWEB slave database.
    The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.
  9. Select OK to complete the account configuration.

Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

The MeetingPlace Gateway Configurations utility allows you to update the Web Server with the least-privileged SQL login account that you have already created. It does not create a SQL Server login or update the SQL Server for you.


Before You Begin

Change the username and password on SQL Server. See the Creating a Least-Privileged SQL Account for the Web Server for instructions.


Procedure
  1. Stop the Cisco Unified MeetingPlace Web Master Service.
  2. Open the MeetingPlace Gateway Configurations utility.
  3. Select the Web Server tab.
  4. Enter the hostname or IP address of the SQL Server that you want to update in the Server field.
    Enter local for a local server.
  5. Enter the username and password that you applied to the SQL Server.
  6. Select OK.
  7. Start the Cisco Unified MeetingPlace Web Master Service.


Related Topics


Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

Information in the Cisco Unified MeetingPlace Web Server software SQL database is replicated from the Cisco Unified MeetingPlace Application Server. As changes occur in the Application Server database, the SQL database is updated in real-time.


Each time the Web Server boots up, it compares the Application Server hostname that it has stored in the SQL database with that configured in the Gateway SIM. If the hostnames match, any changes that occur in the Application Server database are replicated to the SQL database in real-time.


If the hostnames do not match, the Web Server will consider the Application Server to have changed and fail to boot up.


Note: The hostname in the SQL database is the value you entered when you installed the Web Server software.


Before You Begin

Complete this procedure if you cannot start the Cisco Unified MeetingPlace Web Server because you changed the value of the hostname in the Gateway SIM.


Restrictions

This procedure is strictly limited to the situation where the database on the Cisco Unified MeetingPlace Application Server 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 Server software functional failures.


Procedure
  1. Stop the Cisco Unified MeetingPlace Web Master Service.
  2. Verify that all Cisco Unified MeetingPlace services are shut down on the Web Server, including the IIS Admin Service and WWW Publishing Service.
  3. Open Enterprise Manager and navigate to the \Databases folder.
  4. Select and expand the MPWEB database.
  5. Select Tables from the left pane.
  6. Right-click System in the right pane.
  7. Select Open Table > Return All Rows.
  8. Change the value in the HostName column to the desired value.
  9. Start the Cisco Unified MeetingPlace Web Master Service or reboot the server.


Related Topics


How to Change and Apply a New SQL Password to the Cisco Unified MeetingPlace Web Server Software

Complete the following tasks in the order shown to change the SQL password and apply the new password to the Cisco Unified MeetingPlace Web Server software:


Changing the SQL Password If You Know the Old Password

Before You Begin

If you do not know the old password, proceed to the Changing the SQL Password if You Do Not Know the Old Password.


Procedure
  1. Stop the Cisco Unified MeetingPlace Web Master Service.
    Caution! Changing the SQL Server account password while the Web Master Service is running will result in an immediate outage. Stop the service before continuing with the password change procedure.
  2. Open Enterprise Manager.
  3. Expand the Security folder.
  4. Select Logins.
    A list of accounts displays on the right.
  5. Double-click the SQL account that you want to change.
  6. Change the password in the configuration window.


Related Topics


What to Do Next

Proceed to the Applying the New SQL Password to the Cisco Unified MeetingPlace Web Server Software.

Changing the SQL Password if You Do Not Know the Old Password

Before You Begin

If you do know the old password, complete the Changing the SQL Password If You Know the Old Password instead.


Procedure
  1. Stop the Cisco Unified MeetingPlace Web Master Service.
    Caution! Changing the SQL Server account password while the Web Master Service is running will result in an immediate outage. Stop the service before continuing with the password change procedure.
  2. Open a DOS command window.
  3. Sign in to SQL Server by entering C:\osql -E nt_acct, where nt_acct is NT account that has access right to the server.
  4. Change the password by entering sp_password null, new_pwd, sa, where null represents the password that you do not know and new_pwd is the new sql password.
  5. Enter go.


Example: Changing the SQL Password by Using osql

This example shows the osql commands executed to sign 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


Related Topics


What to Do Next

Proceed to the Applying the New SQL Password to the Cisco Unified MeetingPlace Web Server Software.

Applying the New SQL Password to the Cisco Unified MeetingPlace Web Server Software

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.
See the Creating a Least-Privileged SQL Account for the Web Server for more information.
Procedure
  1. Open the Cisco Unified MeetingPlace Gateway Configurations utility.
  2. Select the Web Server tab.
  3. Change the old SQL password to the new SQL password.
  4. Select Apply.
  5. Select OK.
  6. Restart the Cisco Unified MeetingPlace Web Master Service.


Related Topics

How to Manage the SQL Database Size


Modifying the SQL Database Properties to Manage Database Size

The MPWEB database that the Cisco Unified MeetingPlace Web Server software 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 properties for the MPWEB database:

  • Recovery = Simple
  • Torn Page Detection = On
  • Auto Shrink = On


Caution! This procedure applies only to the MPWEB database. Do not apply this procedure to any MPWEB slave database (these databases have names that begin with "MPWEB_").


Procedure
  1. Open a DOS command window.
  2. Sign in to the SQL Server by entering C:\osql -U userid -P password, replacing userid and password with the applicable value.
  3. See the current properties of the database.
    1. Enter sp_helpdb MPWEB.
    2. Enter go.
  4. Modify properties.
    1. Enter alter database mpweb set auto_shrink on, recovery simple, torn_page_detection on.
    2. Enter go.
  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.


Related Topics


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 How to Manage the SQL Database Size.


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.


Related Topics


How to Back Up and Restore MPWEB SQL Database

Complete the following procedures in the order shown to back up and restore the MPWEB database:


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


Procedure
  1. Export the MPWEB database.
    • To export the MPWEB database to create a backup copy while the Cisco Unified MeetingPlace Web Master Service 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 Unified MeetingPlace Web Master Service and wait for all of the Cisco Unified MeetingPlace services, IIS Admin service, and World Wide Web publishing service to cease.
  2. Access the SQL Server.
    • If the SQL Server that is hosting the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.
    1. Select Start > Run.
    2. Enter cmd.
    or
    • If the SQL Server hosting the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and sign in.
    Note: If you cannot sign in to the applicable Windows server, then sign 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 that you can connect remotely to the SQL Server.
  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. Select 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.
  5. Export the database.
    1. Enter backup database MPWEB to disk = 'fullyqualifiedpath'', where fullyqualifiedpath is the location that you chose in Step 4.
    2. Enter go.
  6. Review the informational messages to confirm that the operation is successful.
  7. If you upgraded from Release 7.0 to Release 8.0:
    1. Determine the slave database name(s) on your SQL Server.
      • Enter select name from sysdatabases where name like 'MPWEB%'.
      • Enter go.
      The results should include either one or two slave databases.
    2. 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.
      • Enter go.
    3. Repeat Step 7.2. for the second slave database, if applicable.
  8. Enter exit to exit osql.
  9. Save the mpweb.dat file in a safe location, for example, on a tape or network drive on another server.
    If you upgraded from Release 7.0 to Release 8.0, then also save your mpweb_XX.dat files in a safe location.


Related Topics


What to Do Next

Proceed to the Restoring the Database.

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


Restoring the Database

Before You Begin
  • You must have a database backup file called mpweb.dat.
If you upgraded from Release 7.0 to Release 8.0, then you may also have one or more database backup files called mpweb_XX.dat.
  • The database backup file(s) must have been exported with the backup database 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. See the Creating a Backup File by Exporting the MPWEB Database for instructions.


Procedure
  1. Access the SQL Server.
    • If the SQL Server that hosts the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.
    1. Select Start > Run.
    2. Enter cmd.
    or
    • If the SQL Server hosting the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and sign in.
    Note: If you cannot sign in to the separate (remote) Windows server, then sign 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 connect remotely to the SQL Server.
  2. 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.
  3. Check if a database called MPWEB exists on this server.
    1. Enter select name from sysdatabases where name like 'MPWEB%'.
    2. Enter go.
  4. If a MPWEB database exists, verify that no Cisco Unified MeetingPlace Web Server is currently using this database.
  5. (Optional) If one or multiple Cisco Unified MeetingPlace Web Servers are using the database, complete the following:
    1. Sign in as an administrator on each server.
    2. Stop the Cisco Unified MeetingPlace Web Master Service.
    3. Wait for all the Cisco Unified MeetingPlace services, the IIS Admin service, and the World Wide Web publishing service to stop.
    4. Enter drop database MPWEB to drop the database.
    5. Enter go.
  6. Before you import your MPWEB database to SQL Server, find out which database physical files are associated with this MPWEB database.
    1. Enter restore filelistonly from disk = 'C:\temp\mpweb.dat'.
    2. Enter go.
  7. 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.
    1. Enter sp_helpfile master.
    2. 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.
  8. Restore your database and relocate the database physical files to the correct location.
    1. 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'.
    2. 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.
  9. Ensure that the operation was successful by reviewing the informational messages.
  10. If you upgraded from Release 7.0 to Release 8.0, then repeat Step 8 and Step 9 for each slave database to restore the MPWEB_XX slave database files.
  11. Enter exit to exit osql.
Related Topics


Examples: Restoring the Database

In the following examples, the output is displayed for each command that is used in the Restoring 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> 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:>


How to Detach and Attach the MPWEB SQL Database

This document forms 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 may choose to relocate the MPWEB SQL database to a standalone instance of Microsoft SQL Server. For SQL server requirements for a remote (off box) SQL installation, see the System Requirements for Cisco Unified MeetingPlace.


Complete the following procedures in the order shown to detach and attach the MPWEB SQL database:


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


Procedure
  1. Sign in to the Cisco Unified MeetingPlace web user portal.
  2. Select Admin.
  3. Stop the Cisco Unified MeetingPlace Web Master Service.
  4. Wait for all Cisco Unified MeetingPlace services, including the IIS Admin service and World Wide Web Publishing service, to stop.
  5. Access the SQL Server.
    • If the SQL Server hosting the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt:
    1. Select Start > Run.
    2. Enter cmd.
    or
    • If the SQL Server hosting the MPWEB database runs on a separate (remote) Windows server, locate that Windows server and sign in.
    Note: If you cannot sign in to the separate (remote) Windows server, then sign 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 that you can remotely connect to the SQL Server.
  6. 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.
  7. Access the MPWEB database.
    1. Enter use mpweb.
    2. Enter go.
  8. Display a list of the database files.
    1. Enter sp_helpfile.
    2. Enter go.
  9. Access the SQL Server master database.
    1. Enter use master.
    2. Enter go.
  10. Detach the MPWEB database.
    1. Enter sp_detach_db 'MPWEB.
    2. Enter go.
  11. Decide what you should do with the physical files that you identified in Step 8.
    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.
  12. Determine the slave database name(s) on your SQL Server.
    1. Enter select name from sysdatabases where name like 'MPWEB%.
    2. Enter go.
  13. (Optional) If you upgraded from Release 7.0 to Release 8.0, then repeat Step 7 through Step 11 to detach each additional database named MPWEB_XX, 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).
  14. Enter exit to exit osql.
Related Topics


Examples: Detaching the Database

In the following examples, the output is displayed for each osql command that is used in the Detaching 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:>


Related Topics


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


Procedure
  1. Access the SQL Server.
    • If the SQL Server to which you want to attach your MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.
    1. Select Start > Run.
    2. Enter cmd.
    or
    • If the SQL Server runs on a separate (remote) Windows server, locate that Windows server and sign in.
    Note: If you cannot sign in to that Windows server, then sign 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 that you can remotely connect to the SQL Server.
  2. 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.
    • If the SQL Server runs locally, you can omit the -S server-name option.
  3. 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.
  4. Determine if a database named MPWEB already exists on this server.
    1. Enter select name from sysdatabases where name = 'MPWEB'.
    2. Enter go.
  5. If no MPWEB database exists, proceed to Step 6.
    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 Detaching the Database.
  6. 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.
    1. Enter sp_helpfile master.
    2. 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.
  7. Copy the MPWEB.mdf and MPWEB.ldf files under the data folder that you identified in Step 6.
  8. Attach the MPWEB database.
    1. Enter sp_attach_db 'MPWEB','data path\MPWEB.mdf','data path\MPWEB.ldf'.
    2. Enter go.
  9. (Optional) If you upgraded from Release 7.0 to Release 8.0, and you have a valid set of files for MPWEB_XX slave database(s), then repeat Step 4 through Step 8 for each slave database, replacing MPWEB with MPWEB_XX to attach that database.
  10. Enter exit to exit osql.


Related Topics

Examples: Attaching the Database

In the following examples, the output is displayed for each osql command that is used in the Attaching 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:>


Related Topics


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 Server software installer. This GUIDWebID is stored in the registry and SQL database. Therefore, if you want to transfer the MPWEB SQL database 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 and mpweb slave database(s) from the old server.


Complete the following procedures in the order shown to replace an existing Cisco Unified MeetingPlace Web Server with a new server and retain the data of past meetings so that they are accessible from the new server:


Preparing the Current Cisco Unified MeetingPlace Web Server

Procedure
  1. Stop the Cisco Unified MeetingPlace Web Master Service and the Gateway SIM service.
  2. Detach this Cisco Unified MeetingPlace Web Server from the Cisco Unified MeetingPlace Application Server.
    1. Open the Gateway SIM Agent.
    2. From the Gateway SIM tab, write down the hostname or IP address of the Cisco Unified MeetingPlace Application Server for future reference.
      Note: You must use the same server reference when you install the new Cisco Unified MeetingPlace Web Server. If the Application 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.
    3. Select Delete Unit to detach this Web Server from the Application Server.
  3. Make a copy of the entire \MPWEB\Meetings folder and its contents.
  4. Make a copy of the GUIDS.reg file.
    You can find this file where the Cisco Unified MeetingPlace Web Server software files are stored.
  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.

  1. Open GUIDS.reg in a text editor and add the GUIDWebID and DBName registry paths and key values.
  2. Save the file with these changes.
  3. Make a backup of the MPWEB database and the mpweb slave database(s).
  4. Copy the GUIDS.reg and the MPWEB backup to the new server.


Related Topics


What to Do Next

Proceed to the Installing the Replacement Cisco Unified MeetingPlace Web Server.

Installing the Replacement Cisco Unified MeetingPlace Web Server

Replacement installations of the Cisco Unified MeetingPlace Web Server software must match the version that was running on the old server.


Before You Begin
  • 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. To run GUIDS.reg, right-click GUIDS.reg, then select merge.
  • Have the Preparing the Current Cisco Unified MeetingPlace Web Server available to assist you with this procedure.


Procedure
  1. Install the Cisco Unified MeetingPlace Web Server software.
  2. Reboot the server when you are prompted at the end of the installation.
    After the initial reboot, the installation program continues and may reboot a few more times to complete the installation.
  3. When prompted for the Cisco Unified MeetingPlace Application Server information, enter the hostname or IP address of the Application Server from which you detached the Web Server.
  4. After the installation completes, verify that the Cisco Unified MeetingPlace Web Server software is functional.


Related Topics


What to Do Next

Proceed to the Building the Replacement Cisco Unified MeetingPlace Web Server.


Building the Replacement Cisco Unified MeetingPlace Web Server

Before you Begin
  • Verify that the release of Cisco Unified MeetingPlace Web Server software that is installed on the new server is either the same or later than the release installed on the old server.
  • Know how to use Enterprise Manager or the osql drop database command.
See the Restoring the Database for more information about the osql command.


Procedure
  1. Stop the Cisco Unified MeetingPlace Web Master Service.
  2. Use Enterprise Manager or the osql drop database command to delete the MPWEB SQL database.
    This database was created automatically during the Cisco Unified MeetingPlace Web Server software installation.
  3. Use either Enterprise Manager or the osql restore database command to restore the old MPWEB database on to the new server.
  4. Delete all contents in the \MPWeb\Meetings\ folder.
  5. Restore all the files from the old server in to \MPWeb\Meetings folder.
  6. Reboot the server or restart the Cisco Unified MeetingPlace Web Master Service.
  7. Update the Cisco Unified MeetingPlace Web Administration page.
    1. Sign in to the Cisco Unified MeetingPlace web user portal with a system administrator profile.
    2. Select Admin.
    3. Select Web Server.
    4. Update appropriate fields, such as the Web Server Hostname.


Related Topics


Updating the Indices on the SQL Database

The SQL database needs regular maintenance. If the SQL database is running slowly, or if the SQL database is running on a remote SQL server, then you should run this procedure on a nightly or weekly basis.


Procedure
  1. Launch SQL Enterprise manager.
  2. Select the Cisco Unified MeetingPlace Web Server software database, which is named something similar to MPWEB_<GUID_ID>_<Location>.
    <Location> can be either 1 or 2, depending on whether this is an internal or an external Web Server.
  3. Select Tools > Wizards from the menu options at the top of the window.
  4. Expand on the Management option.
  5. Select Database Maintenance Plan Wizard.
  6. Select Next on the Welcome to the Database Maintenance Plan Wizard page.
  7. Select the database on the Select Database page.
  8. Select Next.
  9. Check Reorganize data and index pages on the Update Data Optimization Information page.
  10. Select Next.
  11. (Optional) Change the schedule on which this maintenance procedure runs.
  12. Select Next on the Database Integrity Check page.
  13. Uncheck Backup the database on the Specify the database backup plan page.
  14. Select Next.
  15. Select Next on the following pages:
    • Specify backup disk directory page
    • Specify the transaction log backup plan page
    • Reports to generate page
    • Maintenance Pan History page
  16. Select Finish on the Completing the maintenance plan wizard page.


How to Use a Custom TCP Port for the SQL Server Connection


Customizing the SQL Port for the Local SQL Database

Procedure
  1. In the SQL server network utility, perform the following:
    Note: To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.
    1. Select TCP.
    2. Select Properties
    3. Change the default port from 1433 to the desired port.
    4. Select OK.
  2. Stop the SQL server.
  3. Start the SQL server.
  4. Edit the registry:
    1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.
    2. Create a registry key of type DWORD named SlaveDBPort.
    3. Set the created entry to your desired value for the port.
  5. Restart the Cisco Unified MeetingPlace Web Master Service.


Customizing the SQL Port for the Remote SQL Database

Procedure
  1. Install the Cisco Unified MeetingPlace Web Server software as usual, choosing remote database (this will install with the default port, 1433).
  2. Use the SQL server network utility to change the port on the remote database:
    Note: To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.
    1. Select TCP.
    2. Select Properties.
    3. Change the default port from 1433 to the desired port.
    4. Select OK.
  3. Stop the SQL server.
  4. Start the SQL server.
  5. Edit the registry:
    1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.
    2. Create a registry key of type DWORD named SlaveDBPort.
    3. Set the created entry to your desired value for the port.
  6. Select Start > Programs > Administrative Tools > Open Data Sources (ODBC).
  7. Select System DSN.
  8. Select MPWEB.
  9. Select Configure.
  10. Select Next on the Microsoft SQL Server DSN Configuration screen.
  11. Select Client Configuration.
  12. Uncheck Dynamically determine port box.
  13. Enter your custom port number.
  14. Select OK.
  15. Close ODBC.
  16. Restart the Cisco Unified MeetingPlace Web Master Service.


Switching from the Local Database to the Remote Database on the Custom Port

Procedure
  1. Start with the local database on default port 1433.
  2. Stop the Cisco Unified MeetingPlace Web Master Service.
  3. Use the SQL server network utility to change the port on the remote database:
    Note: To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.
    1. Select TCP.
    2. Select Properties
    3. Change the default port from 1433 to the desired port.
    4. Select OK.
  4. Stop the SQL server.
  5. Start the SQL server.
  6. Edit the registry:
    1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.
    2. Create a registry key of type DWORD named SlaveDBPort.
    3. Set the created entry to your desired value for the port.
  7. Select Start > Programs > Administrative Tools > Open Data Sources (ODBC).
  8. Select System DSN.
  9. Select MPWEB.
  10. Select Configure.
  11. Change the "Which SQL server do you want to connect to" field to the remote SQL server name.
  12. Select Next on the Microsoft SQL Server DSN Configuration screen.
  13. Select Client Configuration.
  14. Uncheck Dynamically determine port box.
  15. Enter your custom port number.
  16. Select OK.
  17. Close ODBC.
  18. On the web server, open the MeetingPlace Gateway Configuration utility.
  19. Select Web Server.
  20. Change the database name from (local) to remote database.
  21. Enter the user name and password for the remote database.
  22. Select Apply.
  23. Select OK.
  24. Start the Cisco Unified MeetingPlace Web Master Service.


Relocating the Database

You may want to relocate the database and put the Cisco Unified MeetingPlace Web Server software and databases on separate servers, for example, if your Web Server is running out of disk space, or for performance or backup considerations.


Note: Do not uninstall the local SQL Server if you are using remote SQL Server 2005. If, however, you are using remote SQL Server 2000, then you may choose to uninstall the SQL Server software and delete the MPWEB SQL database files from the Cisco Unified MeetingPlace Web Server.


  1. Detach the MPWEB SQL databases on the existing (for example, local) SQL Server.
  2. Attach the MPWEB SQL databases to the new (for example, remote) SQL Server.
  3. On the Web Server, change the Database Connection settings 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 Server.
    3. Enter the remote SQL server name in the Server field.
    4. Enter the new Username and Password.
    5. Click OK.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools