Device Policy Archive

Overview

When an organization monitors many devices over time, historical policy revisions can use a lot of disk space. Most organizations only need these revisions in SecureTrack when they need to research past network changes.

TOS lets you remove old policy revisions from the SecureTrack database. The revisions are saved in an archive file, which you can load back into the database when needed. Archive files can be restored on any TOS version, even if they were created on an older version. You can load archives in any order, without following a specific revision sequence.

Best practices

  • Schedule archives at regular intervals (for example, every 3 or 6 months) to manage disk space efficiently.

  • Perform archiving during a change window to reduce the impact on users.

  • Use clear and consistent file names that include the date or purpose of the archive.

  • Store archive files in a secure location with regular backups.

  • Test the archive and restore process in a lab environment before using it in production.

FAQ

Yes, archive files can be restored on any TOS version.

No, you can load archives in any order. A continuous revision sequence is not required.

See the TOS CLI Reference for full command details.

Commands

Use these commands to archive, load, or remove policy revisions in SecureTrack:

For detailed command instructions and examples, see the TOS CLI Reference.