Cisco Unified MeetingPlace, Release 6.x -- SQL Server and Slave Databases

From DocWiki

Jump to: navigation, search

Cisco Unified MeetingPlace, Release 6.x > Web Conferencing > Installing and Upgrading > Installing Web Conferencing > Pre-Installation Tasks



Contents

Background

Each Cisco Unified MeetingPlace Web Server uses one MPWEB database and one MPWEB “slave” database (whose name is usually of the form “MPWEB_<GUID>_X”). Two or more MeetingPlace Web servers configured to be in the same MeetingPlace Web cluster must share their MPWEB and MPWEB slave databases, and therefore must use the same SQL Server.

Restriction: One MeetingPlace Web server or cluster on your internal network cannot share its MPWEB and MPWEB slave databases with the one of external (DMZ) MeetingPlace Web server or cluster. Therefore, internal MeetingPlace Web servers and DMZ MeetingPlace Web servers must use separate SQL Servers.


WebConnect

In a WebConnect deployment (multiple sites with automatic rollover from site to site), all the internal MeetingPlace Web servers must share the same central SQL Server for their MPWEB database. This requirement is only for internal MeetingPlace Web servers and only for the MPWEB database.

For Cisco Unified MeetingPlace Web Conferencing Release 6.0 FCS, MR1, MR2 and MR3, this shared central SQL Server is also used for all the MPWEB slave databases of all internal servers from all sites (because each MeetingPlace Web server can only use one SQL Server in these older releases).

For Cisco Unified MeetingPlace Web Conferencing Release 6.0 MR4, you can now choose to use a separate SQL Server for the MPWEB database and the MPWEB slave database.


Dual SQL Server Configuration

Cisco Unified MeetingPlace Web Conferencing Release 6.0 MR4 has the ability to use a separate SQL Server for the storage of the MPWEB database and the MPWEB slave database. In earlier releases, you were prompted by the installer for the location of the (one) SQL Server that you wanted to use (either “Local Server” or “Remote Server”). In release 6.0 MR4, the installer prompts you separately for the location of the SQL Server for both the MPWEB and MPWEB Slave database.


For common installations, you must continue to use the same SQL Server for both databases. Either choose “Local Server” or “Remote Server” for both databases and use the same SQL Server name and credentials. However, if your deployment requires that you share the MPWEB database between multiple sites (such as in a WebConnect deployment) and you have no other option than using a remote SQL Server across a WAN link that has limited bandwidth and will slow down SQL operations in order to comply with this shared MPWEB database requirement, it is then highly recommended to use a different SQL Server for the MPWEB Slave database, one SQL Server that would either be on the local MeetingPlace Web server, or on a remote SQL Server whose location is on the same LAN as your MeetingPlace Web server, therefore guaranteeing a high performance network path between the MeetingPlace Web server and the SQL Server hosting the MPWEB Slave database.



Example

Here is an example of a two-site, WebConnect system. One system is in New York and one is in Hong Kong. Each site has one Cisco Unified MeetingPlace Audio Server and its associated MeetingPlace Web servers: two internal MeetingPlace Web servers in a cluster and two external (DMZ) MeetingPlace Web servers, also in a cluster.


The New York site has the following servers:

  • NY-MPAS: MeetingPlace Audio server
  • NY-WEB1: Internal Web Server #1
  • NY-WEB2: Internal Web Server #2
  • NY-SQL1: Dedicated SQL Server on the internal network
  • NY-WEBDMZ1: External (DMZ) Web Server #1
  • NY-WEBDMZ1: External (DMZ) Web Server #2


The Hong Kong site has the following servers:

  • HK-MPAS: MeetingPlace Audio Server
  • HK-WEB1: Internal Web Server #1
  • HK-WEB2: Internal Web Server #2
  • HK-WEBDMZ1: External (DMZ) Web Server #1
  • HK-WEBDMZ1: External (DMZ) Web Server #2
  • HK-DMZSQL1: Dedicated SQL Server in the DMZ


Because this is a WebConnect system, the system administrator has chosen to use NY-SQL1 to be the central, shared SQL Server that all the internal MeetingPlace Web servers (on both sites) will use for the shared MPWEB database. This dedicated SQL Server will also be used for the New York internal web cluster MPWEB slave database, because it is local on the New York site and the internal New York MeetingPlace Web servers will benefit from a fast network link to that SQL Server. On the DMZ side, the system administrator has chosen to use the first MeetingPlace Web server to host the SQL Server databases for the MeetingPlace Web DMZ servers.


At the Hong Kong site, the system administrator will configure the internal MeetingPlace Web servers to also use the remote NY-SQL1 for the MPWEB database to comply with the central, shared SQL Server requirement, but will choose a different SQL Server to be used for the MPWEB Slave database. The system administrator will use a local SQL Server on the first internal Web server for the MPWEB slave database, to benefit from fast access to a local SQL server. On the DMZ side, the system administrator has chosen to use a remote SQL Server located in the DMZ to host the MPWEB and MPWEB Slave databases used by the two MeetingPlace Web DMZ servers.


Therefore, the system administrator should make the following choices during the MP Web installation:

  • NY-WEB1: Choose remote SQL Server NY-SQL1 for both MPWEB and MPWEB slave
  • NY-WEB2: Choose remote SQL Server NY-SQL1 for both MPWEB and MPWEB slave
  • NY-WEBDMZ1: Choose local SQL Server for both MPWEB and MPWEB slave
  • NY-WEBDMZ2: Choose remote SQL Server NY-WEBDMZ1 for both MPWEB and MPWEB slave
  • HK-WEB1: Choose remote SQL Server NY-SQL1 for MPWEB , and local SQL Server for MPWEB slave
  • HK-WEB2: Choose remote SQL Server NY-SQL1 for MPWEB and remote SQL Server HK-WEB1 for MPWEB slave
  • HK-WEBDMZ1: Choose remote SQL Server HK-DMZSQL1 for both MPWEB and MPWEB slave
  • HK-WEBDMZ2: Choose remote SQL Server HK-DMZSQL1 for both MPWEB and MPWEB Slave


The Cisco Unified MeetingPlace Web Conferencing installer will install SQL Server on these two servers:

  • NY-WEBDMZ1
  • HK-WEB1


The installer will not install a local SQL Server on the other MeetingPlace Web servers, because the system administrator chooses to use a remote SQL Server for both the MP Web and MP Web slave databases for these servers.

The system administrator would also have to provision a SQL Server on NY-SQL1 and HK-DMZSQL1 before installing Cisco Unified MeetingPlace Web Conferencing on the Web servers.


During the installation process on each MeetingPlace Web server, after choosing the SQL Server (local or remote) for the MPWEB and the MPWEB slave databases, the installer will prompt for the SQL credentials to be used on each server.

  • If you have chosen a local SQL Server, the “Server Location” field is set to (local) and grayed out. Only enter the credentials.
  • If you have chosen a remote SQL Server, enter the name of the remote SQL Server and the credentials to be used.
  • If you have chosen to use the same SQL Server (either local or remote) for both databases (MPWEB and MPWEB slave), enter the same credentials twice (once in each section).

Rating: 0.0/5 (0 votes cast)

Personal tools