Cisco Unity Express VoiceMail and Auto Attendant CLI Administrator Guide

Backing Up from One Platform and Restoring to Another Platform Type

You can back up your Cisco Unity Express configuration from one hardware platform type and restore it on another type. For example, you can back up your configuration from an NME-CUE and restore it on an AIM2-CUE. The following requirements apply:

• The target platform you are restoring to must have the same licenses enabled as the current platform. For example, if you have 200 mailboxes configured, the same number of mailbox licenses must be enabled on the target platform. If using Cisco Unity Express 7.0 or earlier, the target platform must have the same type of license (CUCM or CUCME) installed.
• The target platform you are restoring to must have the same or greater capacity.
• The number of languages installed should not exceed the limits supported by the target platform.
• The target platform must support the same Cisco Unity Express release. If upgrading to a different software release, see the upgrade procedures in the Cisco Unity Express installation and Upgrade Guide.
• The total allocated mail box (mbx) size of the installed platform must be lesser than the maximum capacity of the voice mail of the target platform you are restoring to.

For platform support and capacities, see the Release Notes for Cisco Unity Express. See also the Cisco Unity Express Guide to Hardware Migration and Software Upgrades.

Prerequisites

• Verify that the backup server is configured.
• Verify that an FTP administrator or other user who can log in to the FTP server has full permission on the FTP server, such as read, write, overwrite, create, and delete permissions for files and directories.

Required Data for This Procedure

• Number of revisions to save before the oldest backup is written over
• FTP server URL
• User ID and password of the FTP server login

SUMMARY STEPS

1. config t

2. backup { revisions number | server url ftp-url username ftp-username password ftp-password }

3. exit

4. show backup

DETAILED STEPS

Examples

The following example configures a backup server and displays the show backup output:

SUMMARY STEPS

1. offline

2. backup category { all | configuration | data }

3. continue

4. show backup history

5. show backup server

DETAILED STEPS

	Command or Action	Purpose
Step 1	offline   se-10-0-0-0# offline	Enters offline mode. All active voice-mail calls are terminated.
Step 2	backup category { all | configuration | data }   se-10-0-0-0(offline)# backup category all se-10-0-0-0(offline)# backup category configuration se-10-0-0-0(offline)# backup category data	Specifies the type of data to be backed up and stored.
Step 3	continue   se-10-0-0-0(offline)# continue	Exits offline mode and returns to EXEC mode.
Step 4	show backup history   se-10-0-0-0# show backup history	Displays the backup and restore procedures and the success or failure of those attempts. Note Beginning with Cisco Unity Express 8.0, use the show restore history command to display the restore status.
Step 5	show backup server   se-10-0-0-0# show backup server	Displays the backup files available on the backup server, the date of each backup, and the backup file ID.

Examples

The following is sample output from the show backup history command for versions 7.1 and earlier:

The following is sample output from the show backup history command for versions 8.0 and later:

The following is sample output from the show backup server command:

SUMMARY STEPS

1. show backup server

2. offline

3. restore id backupid category { all | configuration | data }

4. show backup history

5. reload

DETAILED STEPS

Example

The following example displays the backup server:

In Cisco Unity Express versions 7.2 and earlier, the restore history is shown using the show backup history command. In Cisco Unity Express versions 8.0 and later, the restore history is shown using the show restore history command (see example below).

The following example shows the restore history for Cisco Unity Express versions 7.2 and earlier:

The following example shows the restore history for Cisco Unity Express versions 8.0 and later:

Copying from Flash Memory to Another Location

Starting in Cisco Unity Express EXEC mode, use the following command to copy the startup configuration in Flash memory to another location:

This command is interactive and prompts you for the information. You cannot enter the parameters in one line. The following examples illustrate this process.

In this example, the startup configuration is copied to the FTP server, which requires a user ID and password to transfer files. The IP address of the FTP server is 172.16.231.193. The startup configuration file is saved on the FTP server with the filename start.

The following example shows the startup configuration copied to the TFTP server, which does not require a user ID and password. The IP address of the TFTP server is 172.16.231.190. The startup configuration is saved in the TFTP directory configs as filename temp_start.

Copying from the Network FTP Server to Another Location

Starting in Cisco Unity Express EXEC mode, use the following command to copy the network FTP server configuration to another location:

This command is interactive and prompts you for the information. You cannot enter the parameters in one line. The following example illustrates this process.

In this example, the FTP server requires a user ID and password. The IP address of the FTP server is 10.3.61.16. The file start in the FTP server configs directory is copied to the startup configuration.

Copying the Flash Running Configuration to Another Location

Starting in Cisco Unity Express EXEC mode, use the following command to copy the running configuration in Flash memory to another location:

Copying the Network TFTP Configuration to Another Location

Starting in Cisco Unity Express EXEC mode, use the following command to copy the network TFTP configuration to another location:

This command is interactive and prompts you for the information. You cannot enter the parameters in one line. The following example illustrates this process.

In this example, the TFTP server has IP address 10.3.61.16. The file start in directory configs on the TFTP server is copied to the startup configuration.

Overview

Starting in release 3.0, you can transfer files from any Cisco Unity Express application to and from the backup server using Secure File Transfer Protocol (SFTP). SFTP provides data integrity and confidentiality that is not provided by FTP.

Because SFTP is based on Secure Shell tunnel version 2 (SSHv2), only SSHv2 servers are supported for this feature.

To run backup and restore over SFTP, you must configure the URL of the backup server in the form of sftp:// hostname / dir, and also the username and password to login to the server. The backup server must have an SSH daemon running with the SFTP subsystem enabled. The SSH protocol allows various user authentication schemes. In Version 3.2, however, only password authentication is supported.

Configuring Backup and Restore Using SFTP

Prerequisites

Cisco Unity Express 3.0 or a later version

Required Data for This Procedure

There is no data required.

SUMMARY STEPS

1. config t

2. backup { revisions number | server url sftp-url username sftp-username password sftp-password }

3. end

DETAILED STEPS

Overview

Starting in release 3.0, you can authenticate the backup server using the SSH protocol before starting a backup/restore operation. The SSH protocol uses public key cryptography for server authentication.

This feature provides two methods of authenticating a server:

• Establishing a secure connection based only on the URL of a trusted backup server.
• Obtaining the fingerprint of the backup server and using it to establish a secure connection. This fingerprint is also known as the host key or private key.

The first method is easier than the second method, but it is less secure because it does not depend on you knowing the backup server’s private host key. However, if you know the URL of a trusted backup server, it is generally safe. In this case, the backup server securely provides the client with its private host key.

In both cases, when server authentication is enabled, the system validates the SSH server’s private host key by comparing the fingerprint of the key received from the server with a preconfigured string. If the two fingerprints do not match, the SSH handshake fails, and the backup/restore operation does not occur.

You cannot use the GUI to configure this feature; you must use the CLI.

Both methods are explained in the following sections.

Configuring Backup Server Authentication Without Using the SSH Host Key

Prerequisites

Cisco Unity Express 3.0 or a later version

Required Data for This Procedure

To enable SSH authentication of a backup server without knowing the server’s fingerprint (private host key), you must know the URL of a trusted backup server.

SUMMARY STEPS

1. config t

2. backup server url sftp:// url

3. backup server authenticate

4. end

5. show security ssh known-hosts

DETAILED STEPS

Configuring Backup Server Authentication Using the SSH Host Key

Prerequisites

Cisco Unity Express 3.0 or a later version

Required Data for This Procedure

To use a backup server’s fingerprint (private host key) to enable SSH authentication, you must first retrieve the fingerprint “out-of-band” by running the ssh-keygen routine on the backup server. This routine is included in the OpenSSH package. The following example shows the command and its output:

ssh-keygen -l -f /etc/ssh/ssh_host_dsa_key.pub

1024 4d:5c:be:1d:93:7b:7c:da:56:83:e0:02:ba:ee:37:c1 /etc/ssh/ssh_host_dsa_key.pub

SUMMARY STEPS

1. config t

2. security ssh known-hosts host {ssh-rsa | ssh-dsa} fingerprint-string

3. end

4. show security ssh known-hosts

DETAILED STEPS

Overview

Starting in release 3.0, you can protect backed up configuration and data files using signing and encryption before the files are transferred to the backup server.

To enable this feature, you must configure a master key, from which the encryption and signing key (known as the session key) are derived. The backup files are encrypted and signed before they are sent to the backup server. When you restore the files, the master key is used to validate the integrity of the files and decrypt them accordingly. You can also restore the backup files to any other machine running Cisco Unity Express 3.1 or later versions, if you configure the same master key before you begin the restore process. To make it easier to automate a scheduled backup, the master key is stored securely on the hosting device. It is not included in the backup content.

During the restore process, if the system detects that backup content has been tampered with, the restore process aborts. The system also halts and waits for the administrator to take some action, such as restoring using a different revision.

For backward compatibility, you can allow unsigned backup files to be restored if the risk is acceptable.

Configuring the Encryption and Signing of Backup Content on the Server

Prerequisites

Cisco Unity Express 3.0 or a later version

Required Data for This Procedure

There is no data required.

SUMMARY STEPS

1. config t

2. backup security key generate

3. backup security protected

4. backup security enforced

5. end

DETAILED STEPS

Prerequisites

Cisco Unity Express 7.1 or a later version

SUMMARY STEPS

1. backup schedul e [ name ]

2. repeat every { number days at time |number weeks on day | number months on day date | number years on month month } at time

Note Instead of the repeat every command, you can optionally use one of the following commands:

• repeat once at time
• repeat daily at time
• repeat monthly on day date at time
• repeat weekly on day at time
• repeat yearly on month month at time

3. start-date date

4. stop-date date

5. disabled from date to date

6. backup categories [ all ] [ configuration ] [ data ] [ HistoricalData ] [ TimeCardView ]

7. end

8. show backup schedules or show schedules

9. show backup schedule detail job job-name or show schedule detail job job-name

DETAILED STEPS

Examples

The following is sample output from the show backup schedules command:

The following is sample output from the show schedules command:

The following is sample output from the show backup schedule detail job command:

The following is sample output from the show schedule detail job command:

Disabling or Reenabling All Scheduled Backups

Beginning in Cisco Unity Express 8.0, you can disable or reenable all scheduled backups with a single command.

Prerequisites

Cisco Unity Express 8.0 or a later version

SUMMARY STEPS

1. backup schedule disable all from date to date

2. no backup schedule disable all

DETAILED STEPS

Configuring Scheduled Backup Notification

Beginning in Cisco Unity Express 8.0, you can configure the system to notify specific users about the status of a scheduled backup.

Prerequisites

Cisco Unity Express 8.0 or a later version

SUMMARY STEPS

1. backup schedul e [ name name ]

2. backup notification on { success | failure | always } { voicemail user_id | email email_address | epage epage_address }

3. end

4. show backup schedule detail job job-name

DETAILED STEPS