A Full Backup saves the entire system. It creates a snapshot of a moment in time, and allows you to restore the system back to that state.
A typical edgeCore deployment will consist of many different layers of configuration.
Exporting a Full Backup will capture all the configuration listed above. It does not capture some external support artifacts such as:
The above artifacts are beyond the scope of the product itself, but they should be considered from an overall deployment perspective.
Refer to information provided on Backup and Restore.
To restore a backup, select an item in the list, and activate the Restore Wizard by either clicking the “Restore” button in the bottom toolbar, or double-clicking the item in the list. The wizard’s steps are described below.
This dialog provides several options that affect how the backup will be applied.
Determines how to handle custom (filesystem) content on the current system.
Determines how to handle provisioning information on the current system.
Determines how to handle License information on the current system.
Determines whether to show a preview of contents prior to restoring.
The restore summary shows a preview of content that will be restored on the active server. This gives an administrator the chance to preview changes to the system prior to restoring a full backup.
As a safety measure, the system will automatically perform a full backup prior to a restore. These recovery backups can be used to revert the system’s configuration state to that prior to performing the restore. They are available through the “Recovery” tab in the “Backup & Restore” UI. See Backup and Restore for more information.
edgeCore also allows server administrators to create and restore backups via the operating system command line interface.
To create a full backup via command line using the new Edge CLI, the server must be running. The command is as follows:
bin/es-cli.sh backup [-l] [-c] [-f FILENAME] --user username [--pass password]
See Edge CLI for more information, including instructions for running the new Edge CLI on Windows.
The backup command in the legacy Edge CLI (edge.sh) will be deprecated in edgeSuite 4.0. For now, however, it is still available and can be run as follows:
bin/edge.sh backup [-l] -f FILENAME
Note that the resultant backup image will be found in [INSTALL_HOME]/exports/FILENAME. An extension of .zip is automatically added to the name if not specified. Similar to the new Edge CLI, the -l option can be added to include the log files in the backup file.
For systems running on Windows, use edge.bat instead.
To restore a full backup via command line using the new Edge CLI, the server must be running. The command is as follows:
bin/es-cli.sh restore [--list archives] [-r] [-l OPTION] [-t TYPE] [-c] -f FILENAME --user username [--pass password]
FILENAME is required unless running the restore command with –list archives.
The restore command in the legacy Edge CLI (edge.sh) will be deprecated in edgeSuite 4.0. For now, however, it is still available and can be run as follows:
bin/edge.sh restore [-r] [-l] [-t TYPE] -f FILENAME
Note that, for restore purposes, the backup image may exist in any folder on the system.
For systems running on Windows use edge.bat instead.