Restoring from an Infinite Scale backup can be a task bringing the instance back to production after a major incident occurs.

Though no restore strategies are covered, reading this document can add valuable information when creating a backup and restore strategy.

General Considerations

Same as described in the backup documentation, Infinite Scale can run in two different setups when it comes to storing data:

  • All data, meaning configuration, blobs and metadata, is stored on POSIX-compliant filesystems.

  • Blobs are stored on an S3-compliant storage while configuration and metadata are stored on POSIX.

See the linked backup documentation for more details.

When it comes to restoring data, keep in mind that you always have to restore all three data sets consistently:

  • config data

  • metadata 1

  • blobs 1

(1) …​ For POSIX-only environments, the location for blobs and metadata is currently the same. When using S3, the location differs.

Valid for all restore procedures:

  • first check the basic configuration of Infinite Scale on the backup to prepare the necessary volumes, mount points and directories if they are not present on your Infinite Scale instance,

  • Infinite Scale must be in stopped state.

As a rule of thumb, consider also to restore the Infinite Scale binary or the backed-up container. This avoids difficulties after restoring the instance and possibly using an updated Infinite Scale version compared to the version used when backing up. Restoring and updating should always be different tasks.

Pure POSIX Setup

From the backup, restore:

  • config data

  • blobs and metadata

to their prepared locations. When done, you can start your Infinite Scale instance as usual.

Distributed Setup

From the backup, restore:

  • the configuration and metadata to the POSIX locations

  • blobs to the S3 bucket according to the rules, possibilities and methods of the S3 provider.

When done, you can start your Infinite Scale instance as usual.