Configuration and Maintenance Guide for MeetingPlace 7.1
Backing Up, Archiving, and Restoring Data on the Application Server
Downloads: This chapterpdf (PDF - 146.0KB) The complete bookPDF (PDF - 5.46MB) | Feedback

Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server

Table Of Contents

Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server

About Database Backups, Archives, and Restoration

Database Backups

Cleanup Process for Database Backups

About Archiving the Database Backup Files and Other Files

SSH/rsync Archiving Method (Recommended)

FTP Archiving Method

How to Back Up, Archive, and Restore Data

Configuring Backups and Archiving

Backing Up Data Using the CLI

Archiving Data Using the CLI

Restoring Data Using the CLI


Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server


Release 7.1
Revised: April 3, 2011 8:31 pm

The Cisco Unified MeetingPlace backup and restore functions ensure that the system can recover with minimal data loss in case of database failure or corruption.


Caution We recommend that you do not run reports or backups during peak hours of use, such as on the hour. Doing so may cause the system to fail.

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

About Database Backups, Archives, and Restoration

Database Backups

Cleanup Process for Database Backups

About Archiving the Database Backup Files and Other Files

Database Backups

We highly recommend that you back up and archive the Cisco Unified MeetingPlace Application Server for deployments with both a single Application Server and a deployment with Application Servers deployed for failover. You must set up the backup process on each Application Server individually.

The database backups include IP addresses and hostnames; therefore, you can only restore the backup onto the same Application Server where the backup occurred.

There are three types of database backups:

L0 (Level 0) backup. This is the most common database backup. This is a complete physical and logical backup of the database from which data can be restored.

L1 (Level 1) backup. The L1 backup is an incremental backup. It contains a backup of all the data that has been changed since the last L0 backup. It takes much less disk space than an L0 backup; however, it cannot be used for full restoration. If the system fails, you must use both the L0 and L1 backup files to restore data.

L2 (Level 2) backup. The L2 backup is incremental to the L1 backup, so it needs both the L0 and the L1 backups to restore data.

Cisco Unified MeetingPlace uses a combination of L0, L1, and L2 backups and uses an Informix command called ontape for the backup mechanism.

The database backup file is physically located on the system disk of the Application Server. The system disk can contain up to three automatically-created L0 backups: the current L0, plus the previous one or two L0 backups. The L1 and L2 backups are also kept there. All of the older backups are removed from the system disk during the cleanup process.


Caution Use caution if you manually modify the backup files on the local disk or in the archive location. For successful data restoration, the three levels of backup files must be present in the correct order. For example, if the correct L0 and L2 backup files are present while the appropriate L1 backup file is missing, then the data cannot be restored.

You can enable or disable an automatic backup. If the automatic backup is enabled, an L0 backup happens twice a week, every Monday and Thursday at 11:00PM, local server time. The L1 backup is run each day at 1:00AM, local server time, while the L2 backups are done daily at 4:00AM, 8:00AM, 12:00PM, 4:00PM, and 8:00PM, local server time. The schedule is stored in the crontab file.


Note Advanced system administrators can change the frequency of the automatic backups by editing the crontab file. Be careful when modifying the cron schedule, which determines the order of the backups.


The automatic backup process also incorporates archiving (if enabled) and cleanup. This ensures that if there is a database corruption or disk failure, in the worst case, less than five hours of data is lost.

Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Cleanup Process for Database Backups

The cleanup process occurs before every scheduled backup in the crontab file. During the cleanup process, the following files are deleted:

Backup files older than seven days.

Unusable files, such as L1 and L2 backup files that are older than the oldest remaining L0 backup file.


Note If you disable automatic backups, the cleanup process continues to run as scheduled in the crontab file. Therefore, if you want to keep backup files that are older than seven days, you must archive them.


Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

About Archiving the Database Backup Files and Other Files

Archiving makes a remote copy of all the backup files and external files, such as licenses, meeting attachments, and voice recordings that have not yet been deleted by the automatic system cleanup processes. If a newly archived file has the same name as an existing archived file, the new file overwrites the old file. Maintaining the archive and the remote system used for storing the archive is the responsibility of the system administrator.


Note Backup files and archives do not include backup configuration settings, SNMP configuration settings, or SMTP configuration settings.


Automatic archiving can be enabled or disabled. When enabled, it is initiated by and happens after the automatic database backup. There are two options:

SSH/rsync Archiving Method (Recommended)

FTP Archiving Method

SSH/rsync Archiving Method (Recommended)

The remote server to which you archive files must support rsync and SSH connections:

To archive to a UNIX or Linux server, SSH service and rsync must be enabled on that server. Both SSH service and rsync are included in most UNIX and Linux distributions.

To archive to a Windows-based server, both an SSH server and an rsync utility must be installed on that server.

Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

FTP Archiving Method

The following restrictions apply to the FTP archiving method:

The FTP archiving method does not use a secure connection to transfer files to the remote server.

The FTP archiving method enables the Cisco Unified MeetingPlace server to transfer backup files and other critical files to the remote server; FTP clients cannot transfer files to the Cisco Unified MeetingPlace server.

Make sure that the remote host login credentials provide the permissions required to create new directories within in the directory specified in the Pathname location of archive field. For example, if you enter "pub" in the Pathname location of archive field, the following directories are automatically created when the archiving script runs:

pub/compressed_backup

pub/licenses

pub/custom

Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

How to Back Up, Archive, and Restore Data

Configuring Backups and Archiving

Backing Up Data Using the CLI

Archiving Data Using the CLI

Restoring Data Using the CLI

Configuring Backups and Archiving

You can use the Cisco Unified MeetingPlace Administration Center to configure the system to automatically back up data. This section describes how to configure the parameters for the automatic backups that the system performs.

Procedure


Step 1 Log in to the Administration Center.

Step 2 Select Maintenance > Backup and Archive.

(Release  7.0.1 only) Select Maintenance > Configure Backup.

Step 3 Configure the fields on the Backup and Archive Page.

(Release  7.0.1 only) Configure the fields on the Configure Backup Page.

Step 4 Perform one of the following actions:

To save these values without running the backup program, select Save.

To save these values and run the backup process, select Save and Run Backup.

To save these values and run the archive process, select Save and Run Archiving.


Related Topics

Field Reference: Backup and Archive Page

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Backing Up Data Using the CLI

If you choose to disable the automatic back up feature (by selecting No for the Enable automatic backup field on the Backup and Archive Page), you can still manually back up data.

Restriction

Only run one backup (L0, L1, or L2) at a time.

Procedure


Step 1 Log in to the Cisco Unified MeetingPlace operating system as the mpxadmin user.

Step 2 At the password prompt, enter the mpxadmin password.

Step 3 Right-click on the desktop.

Step 4 From the menu, select New Terminal. This brings up a terminal session.

Step 5 Manually back up the data by entering the following:

sudo $MP_DATABASE/db-maintenance/backup.sh <number>

where <number> is the number of the backup you are running. To make sure you run only one backup at a time, specify 0 for an L0 backup, 1 for an L1 backup, or 2 for an L2 backup.

When the system finishes the backup, it displays a "Backup ended" message.

Step 6 On the desktop, select RedHat > Network Services.

Step 7 Select Log out.


Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Archiving Data Using the CLI

The archive.sh script forces archiving, regardless if auto-archiving is on or off, as set in the procedure described in the "Configuring Backups and Archiving" section.

Procedure


Step 1 Log in to the Cisco Unified MeetingPlace operating system as the mpxadmin user.

Step 2 At the password prompt, enter the mpxadmin password.

Step 3 Right-click on the desktop.

Step 4 From the menu, select New Terminal. This brings up a terminal session.

Step 5 Manually archive the data by entering the following:

sudo $MP_DATABASE/db-maintenance/archive.sh


Note The archive.sh script uses remote log-in credentials that are defined in the $MP_DATABASE/db-maintenance/settings.config file. You set these credentials using the procedure described in the "Configuring Backups and Archiving" section.


When the system finishes the archive, it displays "Archive ended" and "Archive external files ended" messages.

Step 6 On the desktop, select RedHat > Network Services.

Step 7 Select Log out.


Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Restoring Data Using the CLI

Restoring the data recreates database server data from backed-up storage spaces and logical log files. You may need to restore your data if you need to replace a failed disk that contains database server data, if there is a logic error in a program that has corrupted the database, if you need to move your database server data to a new computer, or if a user accidentally corrupts or destroys data.

Before You Begin

To restore data up to the time of the failure, you must have at least one L0 backup.

You must have the backup files in the correct order. For example, if you have the correct L0 and L2 backup files, but not the appropriate L1 backup file, you cannot restore the data. This requires extra caution if you manually back up files on a local disk or in the archiving location.

You can only restore the data to a server with the same IP and hostname as was originally configured for your backup.

If you are restoring two Application Servers that are configured in a failover deployment, make sure that the servers are in standby mode before running the restore on them.

If you are restoring two Application Servers that are configured in a failover deployment, make sure that you turn off replication before running the restore.

Restrictions

You can only restore a database that is from the same version of Cisco Unified MeetingPlace. You cannot restore a database from a previous version.

The names of the databases that you are restoring from and restoring to must be the same.

Procedure


Step 1 Log in to the Cisco Unified MeetingPlace operating system as the mpxadmin user.

Step 2 At the password prompt, enter the mpxadmin password.

Step 3 Right-click on the desktop.

Step 4 From the menu, select New Terminal.

This brings up a terminal session.

Step 5 Restore the data by entering the following:

sudo $MP_DATABASE/db-maintenance/restore.sh

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

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

Step 8 If you pressed L, then press Enter three times.

Step 9 If you pressed A, then complete these steps:

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

b. Press Enter.

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

d. Press Enter.

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

f. Press Enter.

Step 10 Choose an entry from the displayed list of backups,

Step 11 Enter the number associated with the backup entry.

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


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


Step 13 On the desktop, select RedHat > Network Services.

Step 14 Select Log out.


Troubleshooting Tips

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 Installation key which changed during the reinstallation process. For details, see "Adding or Editing a Web Server Connection" in the Connecting the Cisco Unified MeetingPlace Application Server to a Web Server 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.

Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Sending E-Mail Blasts from Cisco Unified MeetingPlace module

What To Do Next

When updating (synchronizing) all meetings on the Web Server, the system purges all the data for meetings that do not exist on the Application Server. Therefore, the next time you or the system updates all meetings, the system purges the following from the Web Server:

Recordings and attachments for meetings that occurred between the backup time and the restore time.

Meetings that were scheduled between the backup time and the restore time.

Nevertheless, you or your users may save local copies of recordings before they are purged. You can use an e-mail blast to inform your users of the following:

Time period (between the most recent backup time and the restore time) of affected meetings.

How to save local copies of recordings. See "Listing to a Cisco Unified MeetingPlace Recording" in the User Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_user_guide_list.html.

Deadline for saving local copies of recordings. This is determined by the next update-all-meetings event, which occurs automatically at midnight every Saturday night (local server time), or when you complete the "Updating All Meetings" section in the Configuring the Cisco Unified MeetingPlace Web Server for Optimal Data Storage module.

If you restored two application servers that were configured in a failover deployment, complete the failover setup on Node 1 and Node 2.

Related Topics

About Database Backups, Archives, and Restoration

Configuring the Application Servers in a Failover Deployment

Sending E-Mail Blasts from Cisco Unified MeetingPlace

How to Configure Application Server Failover in the Configuring Application Server Failover for Cisco Unified MeetingPlace module