Backing up and Restoring Critical Data

It is important to frequently back up all critical configuration data and files on the compact flash file system to an external server or mass storage device. Ensure the following files are backed up regularly:

Controller Logs

Back Up and Restore Compact Flash in the WebUI

The WebUI provides the easiest way to back up and restore the entire compact flash file system. The following steps describe how to back up and restore the compact flash file system using the WebUI on the Mobility Master:

1. Click on the Configuration tab.

2. Click Pending Configuration and then Deploy Changes. Pending Changes is visible only when there changes to be saved, if this option is not visible skip this step.

3. Navigate to the Diagnostics > Technical Support > Backup Flash page.

4. Click Create Backup to back up the contents of the compact flash file system to the flashbackup.tar.gz file.

5. Click Copy Backup to copy the file to an external server.

You can later copy the backup file from the external server to the compact flash file system using the file utility in the Diagnostics > Technical Support > Copy Files page.

6. To restore the backup file to the compact flash file system, navigate to the Diagnostics > Technical Support > Restore Flash page. Click Restore.

Back Up and Restore Compact Flash in the CLI

The following steps describe the backup and restore procedure for the entire compact flash file system using the controller’s command line:

1. Enter config mode in the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. on the controller, and enter the following command:

(host) [mynode] (config) #write memory

2. Use the backup command to back up the contents of the compact flash file system to the flashbackup.tar.gz file.

(host) [mynode] (config)# backup flash

Please wait while we tar relevant files from flash...

Please wait while we compress the tar file...

Checking for free space on flash...

Copying file to flash...

File flashbackup.tar.gz created successfully on flash.

3. Use the copy command to transfer the backup flash file to an external server or storage device:

(host) [mynode] (config) copy flash: flashbackup.tar.gz ftp: <ftphost> <ftpusername> <ftpuserpassword> <remote directory>

(host) [mynode] (config) copy flash: flashbackup.tar.gz usb: partition <partition-number>

You can later transfer the backup flash file from the external server or storage device to the compact flash file system with the copy command:

(host) [mynode] (config) # copy tftp: <tftphost> <filename> flash: flashbackup.tar.gz

(host) [mynode] (config) # copy usb: partition <partition-number> <filename> flash: flashbackup.tar.gz

4. Use the restore command to untar and extract the flashbackup.tar.gz file to the compact flash file system:

(host) [mynode] (config) # restore flash

Back Up and Restore Configuration in the CLI

The following steps describe the backup and restore procedure for the configuration file system using the controller’s command line:

1. Enter config mode in the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. on the controller, and execute the following command:

(host) [mynode] (config) #write memory

2. Use the backup command to back up the contents of the configuration file system to the configbackup.tar.gz file.

(host) [mynode] (config) # backup config

Please wait while we take the config backup....... File configbackup.tar.gz created successfully on flash. Please copy it out of the controller and delete it when done.

.

3. Use the copy command to transfer the backup configuration file system to an external server or storage device:

(host) [mynode] (config) copy flash: configbackup.tar.gz ftp: <ftphost> <ftpusername> <ftpuserpassword> <remote directory>

(host) [mynode] (config) copy flash: configbackup.tar.gz usb: partition <partition-number>

You can later transfer the backup configuration file from the external server or storage device to the compact flash file system with the copy command:

(host) # copy tftp: <tftphost> <filename> flash: configbackup.tar.gz

(host) # copy usb: partition <partition-number> <filename> flash: configbackup.tar.gz

4. Use the restore command to untar and extract the configbackup.tar.gz file to restore the configuration:

(host) [mynode] (config) # restore config Please wait while we restore the config backup........ Config restored successfully. Please reload (reboot) the controller for the new config to take effect.

Snapshot

A VMware snapshot is a copy of the virtual machine's disk file (VMDK) at a given point in time. Snapshots provide a change log for the virtual disk and are used to restore a VM Virtual Machine. A VM is an emulation of a computer system. VMs are based on computer architectures and provide functionality of a physical computer. to a particular point in time when a failure or system error occurs.

A snapshot preserves the state and data of a VM Virtual Machine. A VM is an emulation of a computer system. VMs are based on computer architectures and provide functionality of a physical computer. at a specific point in time. A VM Virtual Machine. A VM is an emulation of a computer system. VMs are based on computer architectures and provide functionality of a physical computer. provides several operations for creating and managing snapshots and snapshot chains. These operations let you create snapshots, revert to any snapshot in the chain, and remove snapshots. For additional information about snapshots refer to the VMware kb article https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180.