This documentation corresponds to an older version of the product, is no longer updated, and may contain outdated information.
Please access the latest versions from https://cisco-tailf.gitbook.io/nso-docs and update your bookmarks. OK
NSO support creating rollback files during the commit of a transaction that allows for rolling back the introduced changes. Rollbacks does not come without a cost and should be disabled if the functionality is not going to be used. Enabling rollbacks impact both the time it takes to commit a change and requires sufficient storage on disk.
Rollback files contain a set of headers and the data required to restore the changes that were made when the rollback was created. One of the header fields includes a unique rollback id that can be used to address the rollback file independent of the rollback numbering format.
Use of rollbacks from the supported APIs and the CLI is documented in the documentation for the given API.
NSO is configured through a configuration file - ncs.conf. In that file we have the
following items related to rollbacks:
/ncs-config/rollback/enabledIf 'true', then a rollback file will be created whenever the running configuration is modified.
/ncs-config/rollback/directoryLocation where rollback files will be created.
/ncs-config/rollback/history-sizeNumber of old rollback files to save.