Configuration Rollback
Page 46 7210 SAS M, T, X, R6 Basic System Configuration Guide
• When a rollback save [no “-”] is executed, the system shifts the file suffix of all the
previous checkpoints by 1 (new id = old id + 1). If there are already as many checkpoint
files as the maximum number supported then the last checkpoint file is deleted.
• The maximum number of rollback checkpoints is configurable and defaults to 10 (“latest”
and 1 through 9, where checkpoint file 9 is deleted during the next rollback-save).
• The location and name of the rollback checkpoint files is configurable to be local (on
compact flash or USB drive) or remote. The file-url must not contain a suffix (just a path/
directory + filename). The suffix for rollback checkpoint files is “.rb” and is automatically
appended to rollback checkpoint files.
config>system>rollback# rollback-location <file-url>
• There is no default rollback-location. If one is not specified (or it is cleared using “no
rollback-location”) and a rollback save is attempted, the rollback save will fail and return
an error message.
• The entire set of rollback checkpoint files can be copied from the active CPM CF to the
inactive CPM CF. This synchronization is done through the following command:
admin>redundancy# rollback-sync
• The operator can enable automatic synchronization of rollback checkpoint files between
the active CPM and inactive CPM. When this automatic synchronization is enabled, a
rollback save will cause the new checkpoint file to be saved to both the active and
standby. The suffixes of the old checkpoint files on both active and standby CPMs are
increased.
Note: The automatic sync only causes the ONE new checkpoint file to be copied to both
CFs (the other 9 checkpoints are not automatically copied from active to standby but that
can be done manually with admin red rollback-sync).
config>redundancy# [no] rollback-sync
• “config red sync {boot-env|config}” and “admin red sync {boot-env|config}” do not
apply to rollback checkpoint files. These commands do not manually or automatically
sync rollback checkpoint files. The dedicated rollback-sync commands must be used to
sync rollback checkpoint files.
• Rollback files can be deleted using a dedicated rollback checkpoint deletion command.
admin>rollback# delete {latest-rb|<checkpoint-id>}
− Deleting a rollback checkpoint causes the suffixes to be adjusted (decremented) for all
checkpoints older that the one that was deleted (to close the “hole” in the list of
checkpoint files and create room to create another checkpoint)
− If “config redundancy rollback-sync” is enabled, a rollback delete will also delete the
equivalent checkpoint on the standby CF and shuffle the suffixes on the standby CF.
− If an operator manually deletes a rollback checkpoint file (using file delete) then the
suffixes of the checkpoint files are NOT shuffled, nor is the equivalent checkpoint file
deleted from the standby CF. This manual deletion creates a “hole” in the checkpoint
file list until enough new checkpoints have been created to roll the “hole” off the end
of the list.
To Next Page
Loading...
