Storage and recovery

RouteSpear accounts are separate tenants. Access to measurements and configuration is scoped to the tenant, while the service uses shared database and storage infrastructure. Tenant separation does not mean that each account has its own persistent disk or database server.

Organizations can have default recovery requirements, and individual accounts can have overrides. Operators manage these under Storage & recovery in the admin console, including when creating an account. Requirements cover the acceptable data-loss window, recovery time, backup retention and cross-region recovery.

These settings describe recovery objectives. They do not themselves provision backups or establish a recovery SLA. Operators inspect backup coverage and record restore-drill evidence on each account. Missing or stale evidence and incomplete coverage remain visible until addressed.

Recovering one tenant from shared backups requires restoring into an isolated environment, extracting the affected tenant’s data, and validating its configuration, measurements, artifacts, permissions and billing records before cutover. Availability-zone redundancy helps with infrastructure failures; backup restoration is a separate process for data loss or regional recovery.

Ingestion pricing remains separate from agent uptime. Recovery commitments and retention should be confirmed during your service evaluation.