Continuity

Continuity and backup: what to protect, and why your inventory remains the reference

The platform runs on your premises: its backup fits into your tools. Here is what to back up, what happens if it is unavailable, and how to prepare a restore.

Contents
  1. Your inventory remains the reference
  2. What to back up
  3. With your tools, according to your policy
  4. Prepare and test the restore
  5. How long to keep backups
  6. Before an update

Because the platform is installed on your servers, its continuity depends on your operating practices, just like your other applications. This page helps you fit the platform into your backup and recovery plan: what to protect, what does not depend on it, and what to test.

Your inventory remains the reference

One principle greatly simplifies the question: the platform does not replace your inventory. It lives in your own tool. The platform does not connect to it and writes nothing to it: it compares its results with an export that the user provides, and you decide what you then carry over into your inventory.

Direct consequence: if the platform is unavailable, your inventory remains intact and usable. Your teams continue to view and update it as before. What is suspended is the ability to analyze new rack photos and to reopen past analyses, until service is restored. Reports and exports already downloaded remain available wherever you stored them.

What to back up

The platform’s own data falls into four sets:

SetContent
DatabaseProjects, analyses and their results, accounts, settings.
PhotosThe rack photos sent for analysis and the images produced, in which the devices are boxed.
ConfigurationPlatform installation settings.
LicenseThe license file, without which nothing starts.

Photos and the database go together: an analysis without its photo loses its value as evidence, and a photo without an analysis is no longer attached to a project. We recommend backing them up at the same time.

The configuration contains secrets specific to your installation: its backup must be protected like any other secret in your information system.

With your tools, according to your policy

The platform does not impose a backup tool on you. Since the data is stored on your servers, it is backed up with the solutions you already use, and follows your policy: frequency, number of copies, location, retention period, media encryption. An optional encrypted backup script is also provided with the kit: database, data volumes, configuration and license, encrypted with a public key that you hold.

The exact data locations, the recommended method to obtain a consistent copy and the restore procedure are to be specified as part of the project and handed over with the installation documentation.

Prepare and test the restore

A backup is only worth something if it can be restored. We recommend planning a restore test at go-live, then at regular intervals:

  1. Restore to a separate environment

    Reinstall the same signed release, then restore the database, photos, configuration and license.

  2. Check startup

    The license must be recognized by each component; the System page must show the expected services.

  3. Check the data

    Reopen a few analyses from the History: the photo, the identified devices and the rack diagram must be present.

  4. Record the result

    Note the date, the release and any discrepancies found in your continuity register.

How long to keep backups

The retention period for backups follows your policy, but it must stay consistent with that of the data itself. An analysis deleted from the platform, or erased because its retention period has expired, should not survive indefinitely in backups. We advise aligning the two and describing them together in your register; the page Retention and deletion gives the points to decide.

Before an update

An update is a natural time to back up: take a full copy just before installing a new release. If anything goes wrong, you can return to the previous state. The update process is described on the page Signed updates and license.

Stay in touch

New releases, newly recognized equipment, articles: one email when there is something new, nothing else.