Configuration Guide for Cisco Unified MeetingPlace Release 8.6
Backing Up, Archiving, and Restoring Data on the Application Server
Downloads: This chapterpdf (PDF - 152.0KB) The complete bookPDF (PDF - 7.28MB) | Feedback

Backing Up, Archiving, and Restoring Data on the Application Server

Table Of Contents

Backing Up, Archiving, and Restoring Data on the 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

How to Back Up, Archive, and Restore Data

Configuring Backups and Archiving

Backing Up Data By Using the CLI on the Application Server

Archiving Data By Using the CLI on the Application Server

Restoring Data By Using the CLI on the Application Server


Backing Up, Archiving, and Restoring Data on the Application Server


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.

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

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, 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:15 PM, local server time. The L1 backup runs each day at 1:15 AM, local server time, while the L2 backups run daily at 4:15 AM, 8:15 AM, 12:15 PM, 4:15 PM, and 8:15 PM, local server time.


Note In this release, you cannot use the crontab command to view or edit cron jobs. Instead, advanced system administrator (the root user) can edit the corresponding cron job file under the /etc/cron.d/ directory, the directory under which all cron job files are installed. For database backup and archive, you can change the frequency of automatic backups or archives by editing the /etc/cron.d/cron_root 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. During the cleanup process, these 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, 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.


You can enable or disable automatic archiving. When enabled, it is initiated by and happens after the automatic database backup.

SSH/rsync Archiving

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

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

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


Caution These procedures are intended to provide you with a guideline for setting up a rsync server for Linux, Windows, or Mac operating systems. The exact commands and steps may differ for your particular environment.

Transferring Your Data to a Rsync Server With a Linux or Mac Operating System

Transferring Your Data to a Rsync Server With a Windows Operating System

Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Transferring Your Data to a Rsync Server With a Linux or Mac Operating System

Perform the following tasks, in order, to enable the transfer of data from your Cisco Unified MeetingPlace Application Server to your archive server on a Linux machine or a Mac.


Note This procedure does not include detailed, step-by-step instructions on how to set up, then test, the rsync server on a Linux machine or a Mac. See your operating system documentation for complete details.



Caution This procedure to install a rsync server on a Linux machine uses Red Hat Enterprise Linux 5. The procedure for a Mac uses Mac OS X 10.6.8. Depending on your particular operating system, the specific steps in your procedure may be different.


Step 1 As an administrator, set up your archive machine as a rsync server.

a. Open a command-line interface and confirm that rsync is on your machine by entering rsync --version.

If the prompt returns without a version, then you need to obtain rsync before proceeding further.

b. Enter rsync -- daemon to run rsync in daemon mode.

Step 2 Create an archive folder in a Temp folder or another location of your choice.

Step 3 List the contents of the Temp folder and confirm that the archive folder has been created. Give "read/write" permission to this archive folder (chmod 666 for Linux operating systems).

Step 4 Confirm, and if necessary, enable remote login to your archive server.

Step 5 Sign in as the root user to the command-line interface of the Application Server.

Step 6 Create a test file, for example, Test.txt.

Step 7 Enter rsync -v Test.txt <administrator_user>@<archive_server_IP_address>:<path_to_archive_folder>.

Step 8 As required, enter the password for the administrator_user and answer yes to continue the connection.

Step 9 Once the transfer is complete, the command prompt returns.

Step 10 Go to the archive machine and navigate to the Temp folder. Confirm that Test.txt has been transferred.


Transferring Your Data to a Rsync Server With a Windows Operating System

Perform the following tasks, in order, to set up rsync server and transfer data from your Cisco Unified MeetingPlace Application Server to your archive server on a Windows machine.

The procedure described in this section uses Cygwin to install an rsync server on a Windows machine. You may use Cygwin or another application that provides this functionality. Select an application that best meets your requirements.


Note This procedure does not include detailed, step-by-step instructions on how to set up, then test, the rsync server on a Windows machine. See the Cygwin documentation and Microsoft Windows documentation for complete details on their products.



Caution This procedure to install a rsync server uses Cygwin release 1.7.9-1 on a Windows XP Professional machine. Depending on your Windows operating system and Cygwin release, the specific steps in your procedure may be different.


Note If you are not familiar with it, we recommend you learn more about rsync before installing and configuring a rsync server.


Procedure


Step 1 Sign in as a system administrator.

Step 2 Stop the firewall and any antivirus software.

Step 3 Install the latest version of the Cygwin package from http://www.cygwin.com/ and run setup.exe Accept C:\cygwin as the root directory.

Step 4 At a minimum, select the following packages:

+Editors: Select nano (a simple text editor) or another text editor that you prefer

+Net: rsync, openssh (when openSSH is selected, openSSL is also automatically selected)

+Admin: cygrunsrv (NT/W2K service initiator)

+Shells: bash (if it is not already selected)

+Net: autossh, libssh2-devel (development), libssh2_1 (runtime)

+Devel: librsync-devel

+Libs: librsync-devel, librsync1

Step 5 Add C:\cygwin\bin; to the PATH statement.

This addition is required for applications to work properly, when called outside of Cygwin.

Windows NT:

a. Open the Control Panel.

b. Double-click the System applet.

c. Select the Environment tab.

d. Select the Path variable and add C:\cygwin\bin; to the end of the Path.


Note If the path is not empty and does not end with a semicolon (for example, C:\path), then be sure to add a semicolon (;) when adding C:\cygwin\bin to the end of path (for example, C:\path;C:\cygwin\bin;).


e. Select Set.

f. Select OK and close the Control Panel.

The path is dynamically reloaded (you do not need to reboot the machine).

On Windows 2000/Windows XP:

a. Open the Control Panel.

b. Double-click the System applet.

c. Select the Advanced tab.

d. Select Environment Variables.

e. In the System variables pane, double-click the Path statement and add C:\cygwin\bin; at the end. Select OK.


Note If the path is not empty and does not end with a semicolon (for example, C:\path), then be sure to add a semicolon (;) when adding C:\cygwin\bin to the end of path (for example, C:\path;C:\cygwin\bin;).


f. Select OK and close the Environment Variables window.

g. Select OK to close the System Properties window.

The path is dynamically reloaded (you do not need to reboot the machine).

Step 6 Complete the Cygwin installation.

Step 7 Double-click the Cygwin desktop icon on your desktop or select Start > Cygwin >Cygwin Bash Shell.

The Cygwin bash shell window opens.

Step 8 At the Cygwin prompt, enter ssh-host-config to create the SSH daemon service, set up the SSH host keys, and create the sshd_config file in the /etc directory in the Cygwin tree. Answer the following questions as follows:

*** Query: Should privilege separation be used? (yes/no) yes

*** Query: Do you want to install sshd as a service? (yes/no) yes

*** Query: Enter the value of CYGWIN for the daemon: [] sshd (you can also leave this answer blank.)

By entering sshd or leaving the answer blank, the service is installed as "CYGWIN sshd".

Step 9 Start sshd by completing one of the following.

At the Cygwin prompt, enter net start sshd to start the SSH daemon service.

Select Start > Control Panel > Performance and Maintenance > Administrative Tools, then double-click Services. Select CYGWIN sshd then Start the service.

Step 10 Choose the path for your backup area (for example, /var/rsync_dump in the Cygwin tree).

Step 11 Create the /etc/rsyncd.conf file:

a. Open Windows Explorer. (Right-click Start and select Explore.)

b. Navigate to the C:\cygwin\etc folder and create a new text file rsyncd.txt. (Right-click in the folder and select New > Text Document.)

c. Open the new file, copy the text below and paste it into the file.

d. Save your changes and close the file.

e. Rename this file to rsyncd.conf.

use chroot = false 
strict modes = false
 
   
[modulename]
 
   
	path = /cygdrive/c/cygwin/var/rsync_dump 
	comment = Rsync storage area  
	read only = false 

Note The path, = /cygdrive/c/cygwin/var/rsync_dump, is Cygwin convention for defining Windows paths. /var/rsync_dump is the path you chose in the previous step.


Step 12 (Windows 2003 Server only) Set permissions for an Administrator. If you are using another Windows version, then skip to next step.

a. Open Windows Explorer and navigate to the C: drive.

b. Right-click on the Cygwin directory and select Properties.

c. Select the Security tab. The Administrator user should be the first name in the list. If it is not in the list, then add it to the list.

d. Check the Allow - Full Control check box in the Permissions for Administrator pane.

e. Select Advanced and check Replace permission entries on all child objects with entries shown here that apply to child objects.

f. Select Apply.

g. Select OK and close Advanced Settings.

h. Select OK and close the Cygwin Properties.

Step 13 Open a command prompt window and install rsync as a service.

The text, -u Administrator -w <password>, installs rsync to run as the Administrator user (where <password> is the Administrator account password). Windows 2003 Server requires an Administrator to run rsync, or the service fails to start correctly. For Windows NT, 2000, or XP systems, you can create a "rsync" user with tighter security. Otherwise, the rsync service installs with SYSTEM privileges.

On Windows 2003 (for all versions and service packs, installed as Administrator):

cygrunsrv.exe -I "Rsync" -p /cygdrive/c/cygwin/bin/rsync.exe -a "--config=/cygdrive/c/cygwin/etc/rsyncd.conf --daemon --no-detach" -f "Rsync daemon service" -u Administrator -w <password>

On Windows NT/2000/XP (for all versions and service packs, installed as Administrator):

cygrunsrv.exe -I "Rsync" -p /cygdrive/c/cygwin/bin/rsync.exe -a "--config=/cygdrive/c/cygwin/etc/rsyncd.conf --daemon --no-detach" -f "Rsync daemon service"

Step 14 Start the rsync service by completing one of the following.

In the command prompt window, start the rsync service by entering net start rsync.

Select Start > Control Panel > Performance and Maintenance > Administrative Tools, then double-click Services. Select Rsync then Start the service.

Testing the Archive of the Application Server on the Windows Rsync Server

Procedure


Step 1 Sign in to the Cisco Unified MeetingPlace Administration Center as the admin user.

Step 2 Navigate to Maintenance > Backup and Archive.

Step 3 Set the Archiving method to Remote (SSH/rsync).

Step 4 Set the Pathname location of archive field to /var/rsync_dump (or whatever location you've selected in Step 10 of the previous procedure).

Step 5 Set the Remote archive host field to the hostname or IP address of your Windows rsync server.

Step 6 Set the Remote host user ID and Remote host password fields to your Windows rsync server Administrator account username and password.

Step 7 Select Save and Run Backup to create a backup on the local disk drive of the Application Server.

Step 8 Select Save and Run Archiving to archive the backup files from the Application Server to your Windows rsync server. If the /etc/rsync_dump directory does not exist in the cygwin tree on the Windows rsync server, then it is automatically created for you as a part of archiving process.

Step 9 On your Windows rsync server, navigate to the C:\cygwin\etc\rsync_dump directory and verify that this directory contains backup files from your Application Server.


How to Back Up, Archive, and Restore Data

Configuring Backups and Archiving

Backing Up Data By Using the CLI on the Application Server

Archiving Data By Using the CLI on the Application Server

Restoring Data By Using the CLI on the Application Server

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 Sign in to the Administration Center.

Step 2 Select Maintenance > Backup and Archive.

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

Step 4 Perform one of these 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 By Using the CLI on the Application Server

If you 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 Sign in to the Cisco Unified MeetingPlace operating system as the mpxadmin user.

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

Step 3 Enter su - and the root password.

Step 4 To manually back up your data, enter $MP_DATABASE/db-maintenance/backup.sh number

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.

Step 5 The following message is displayed when the backup is complete:

Program over.
=== Backup ended
Automatic archiving disabled
====== database backup script ended
 
   

Step 6 Log out from the CLI.


Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Archiving Data By Using the CLI on the Application Server

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

Procedure


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

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

Step 3 Enter su - and the root password.

Step 4 Enter the following command to archive your data: $MP_DATABASE/db-maintenance/archive.sh


Note The archive.sh script uses remote sign-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.


Step 5 Wait for the system to finish the archive. The following messages appear: Archive ended and Archive external files ended.

Step 6 Log out from the CLI.


Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Restoring Data By Using the CLI on the Application Server

Restoring the data recreates database server data from backed-up storage spaces and logical log files. You might 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 restore only the data to a server with the same IP and hostname as was originally configured for your backup.

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 Sign in to the Cisco Unified MeetingPlace operating system as the mpxadmin user.

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

Step 3 Enter su - and the root password.

Step 4 Restore the data by entering this command:

$MP_DATABASE/db-maintenance/restore.sh

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

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

Step 7 If you pressed L, press Enter three times.

Step 8 If you pressed A, press Enter at the "Press any key to continue..." prompt.

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

Step 10 Enter the number associated with the backup entry.

Step 11 When prompted, press R to perform the restore.

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

Step 12 Log out from the CLI.


Troubleshooting Tips

If you restore archived data after you reinstall the Cisco Unified MeetingPlace Web Server software or the entire Cisco Unified MeetingPlace system, the system might not find meetings because the Application Server cannot reach the Web Server. If this occurs, 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".

Related Topics

About Database Backups, Archives, and Restoration

How to Back Up, Archive, and Restore Data

Sending Email Blasts on MeetingPlace-Scheduled and Audio-Only Deployments

What To Do Next

When updating (synchronizing) all meetings on the Web Server, the system deletes 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 deletes these items from the Web Server:

Recordings 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 might save local copies of recordings before they are deleted. You can use an email 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 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.