Previous page Next page

restore

Retrieves a specified object from a backup.

Syntax
restore {image | image-config | license } <file-url>
 
Arguments
Prerequisites

Must be in system-operations mode, with privileged-level access.

Description

The restore command restores a license file, or an image from an archival copy that was previously created with the backup command (the archive can contain the entire CNA image or the entire image plus startup configuration).

For example, if your Avaya support user ID were rs_customer and your password were p_wrD, you could use the following command to restore the 2.1.2 image on your CNA device from the image stored on the Avaya FTP server at ftp.avaya.com:

restore image ftp://rs_customer:[email protected]/releases/fcs-2.1.2.img
 

 

If you specify the image keyword when restoring a backup file that contains both operating system image and configurations, only the image will be extracted.

If you specify the image-config keyword (instead of image, in the example) and the URL identifies an image you previously backed up with the backup command and image-config keyword, the configuration that was stored with the image when it was backed up will overwrite your existing startup config.

If you specify image-config when restoring a backup file that contains only an image, the restore will succeed (with no action taken regarding the missing config). See the backup command description for information about saving a config with images during backup.

Use the license keyword to restore a license file (.lic) to the device.

When upgrading to an image downloaded from the Avaya FTP server, be aware that those images do contain a startup config with minimal content. If you upgrade with the image-config keyword, CNA will be restored to an as-new condition.

The archive can be located either locally on CNA, or a remote location accessible by FTP or HTTP. See the copy command for URL syntax.

If you want to halt a restoration in progress, use Control-C (you may have to wait a few minutes and retry if the process is in the midst of a critical step and ignores the halt signal.)

To restore an image from a remote device, you will need free disk space on CNA equal to twice the size of the stored object. Use the ls command to display the repository’s current contents, including both the name of the object and the amount of space it occupies.

To restore an image stored locally on CNA, you need free space equal to the size of the image.

When you attempt to restore a file, the device will calculate the amount of space required and warn you if there is not enough space currently available.

See the note about image size in the description of the backup command.

During the restoration process, progress is indicated by a display of dots that appear at intervals during the process, as shown in the following example:

Checking local disk space           ..                        [OK]
 
Verifying image                     .. ..                     [OK]
 
Upgrading management                .. .. .. ..               [OK]
 
Preparing for peripheral upgrades   .. .. .. .. ..            [OK]
 
Upgrading engine module in slot 2   .. ..                     [OK]
 
Upgrading ustat module in slot 3    .. ..                     [OK]
 
Upgrading ustat module in slot 4    .. ..                     [OK]
 
Upgrading ustat module in slot 7    .. ..                     [OK]
 
Upgrading ustat module in slot 12   .. ..                     [OK]
 
Local image (0616.img) was successfully restored
 

 

Some advisory messages may be displayed between steps but, as along as the line ends with the text OK, the restore will continue. If any other text is displayed inside the brackets, check the log for additional information.

Dot pairs indicate completion of individual steps in the process. You can interrupt the restore process with the Control-C keys, but be aware that the intervals between display of dot pairs is not uniform and can take from a few seconds to several minutes. Also, while the number of dot pairs displayed for any one step is fixed, neither the number of dots nor the steps themselves are guaranteed to remain static from release to release.


Previous page Next page