Cisco Cisco MeetingTime Quick Setup Guide

From the menu, select New Terminal. 

This brings up a terminal session. 

Restore the data by entering the following: 

sudo $MP_DATABASE/db-maintenance/restore.sh 

At the system prompt, press S to stop the Cisco Unified MeetingPlace application.

Choose the type of restore you want. Press A for archive or L for the local disk.

If you pressed L, then press Enter three times.

If you pressed A, then complete these steps:

Copy all files from the opt/cisco/meetingplace/licenses folder of your latest archive location to the 
/opt/cisco/meetingplace/licenses folder. 

Press Enter.

Copy all files from the opt/cisco/meetingplace/afs/custom folder of your latest archive location to 
the /opt/cisco/meetingplace/afs/custom folder. 

Press Enter.

Copy all files from the mpx-record folder of your latest archive location to the /mpx-record folder.

Press Enter.

Choose an entry from the displayed list of backups,

Enter the number associated with the backup entry.

When prompted, press R to perform the restore.

When the system finishes the archive, it displays the message: “You restored database successfully.”

If you are restoring an Application Server that is configured in a failover deployment, reboot the server 
after the restore is completed.

If the server needs to be in active mode after it reboots, switch it to active mode.

On the desktop, select RedHat > Network Services. 

Select Log out. 

If you restore archived data after you reinstall Cisco  Unified  MeetingPlace Web  Conferencing or the 
entire Cisco Unified MeetingPlace system, the system may not find meetings because the 
Application Server cannot reach the Web Server. If this occurs, then you need to manually edit the 
Web Server connection to use the new 

 which changed during the reinstallation 

process. For details, see 

 in the 

 module.

If the Web Server page in the Administration Center appears to have duplicate entries after 
completing the restore, make the old entries inactive, then log in to the Application Server CLI as 
root user and use the gwstatus command to verify that the inactive entries have been removed.