Cisco Cisco Unified MeetingPlace Web Conferencing Guida Alla Risoluzione Dei Problemi

operations for this Cisco MeetingPlace Web server, proceed to Step 2.
Log in as administrator on the Cisco MeetingPlace Web server. For Cisco MeetingPlace Web
versions 4.2.5 and 4.2.7, stop all Cisco MeetingPlace Web services and the WWW Publishing service.
For Cisco MeetingPlace Web version 4.3.0.x, stop the MeetingPlace Web Conferencing service and
wait for all of the MeetingPlace Web services and the WWW Publishing service to stop.

2. 

If the SQL Server hosting the MPWEB database runs on the Cisco MeetingPlace Web server, proceed
to the next step. If the SQL Server hosting the MPWEB database runs on a separate (remote)
Windows server, locate that Windows server and log in to it. If you cannot log in to that Windows
server, you need to log in to any Windows−based workstation or server on the network that has a
valid installation of SQL Server Client Tools, including the osql command, so you can remotely
connect to the SQL Server.

3. 

Go to Start > Run and issue the cmd command to access the command prompt.

4. 

Connect to the SQL Server by issuing the osql command with the sa account and the appropriate
password, as shown here:

C:> osql −U sa −S server_name

Password: password

1>

Note: If the SQL Server runs locally, you can omit the −S server_name option. The argument
server_name stands for the Windows server name.

Note: If you are not allowed to connect to this SQL Server as sa, connect using an account that has
the privileges necessary to back up a database.

5. 

Choose a fully qualified path and filename to export your database to (in the example,
C:\temp\mpweb.dat is used). If you are connected to the SQL Server by running osql on a remote
workstation or server, remember that this path must be valid on the Windows server that hosts SQL
Server, not on your local workstation. Export the database by issuing these commands:

1> backup database MPWEB to disk = 'C:\temp\mpweb.dat'

2> go

Review informational messages to confirm that the operation was successful:

Processed 616 pages for database 'MPWEB', file 'MPWEBData' on file 1.

Processed 3 pages for database 'MPWEB', file 'MPWEBLog' on file 1.

BACKUP DATABASE successfully processed 619 pages in 1.709 seconds (2.962 MB/sec)

6. 

If Cisco MeetingPlace Web 4.3.0.x is installed, there is a second slave MPWEB database that must be
backed up. Its name includes a series of digits that varies from one installation to another. Issue this
command to determine the slave database name on your SQL Server:

1> select name from sysdatabases where name like 'MPWEB%'

2> go

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

name                

[char              ]

−−−−−−−−−−−−−−−−−−−−

MPWEB               

MPWEB−Slave−37102728

In this example, the name of the slave database is MPWEB−Slave−37102728. Following the
instructions of Step 6 above, you must back it up by issuing this command (replace xxxxxxxx with the
digits used by the database name on your system):

1> backup database [MPWEB−Slave−xxxxxxxx] to disk = 'C:\temp\mpweb−slave−xxxxxxxx.dat'

2> go

7. 

Issue the exit command to exit osql.

8.