Cisco Cisco Unified MeetingPlace Audio Server Quick Setup Guide

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. 

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: 

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.

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 

 field. For example, 

if you enter “pub” in the 

 field, the following directories are 

automatically created when the archiving script runs:

pub/compressed_backup