Skip to main content

Coming soon

Pillar for Rubrik.

What we’re building: everything Rubrik knows about your backups, read by service.

Request early accessSee it working with Veeam

Design partners now. General availability in 2027.

APIs

What Pillar will read from Rubrik.

Read-only, over the Rubrik Security Cloud GraphQL API.

  • SLA Domains

    Snapshot frequency, retention, archival and replication for every workload assigned to one.

  • Snapshots

    Every point, when it expires, and whether it is retention-locked.

  • Workloads

    VMs, databases, filesets and NAS, each with its compliance status and last snapshot.

  • Clusters

    Each cluster’s status and capacity: used, available and held by snapshots.

  • Events and audit

    Every backup, recovery and failover with its result, and who did what.

  • Recovery Plans

    Each plan, its last outcome, and whether a test failover is scheduled.

Verification

Verifying with Rubrik.

Rubrik runs the checks. Pillar supplies the definition and consumes the result.

  • Recovery Plans

    Orchestrated Application Recovery groups the machines behind a service and fails them over together.

    • Pillar proposes the plan’s membership and order from discovered dependencies, for a person to accept in Rubrik.
    • Rubrik runs the test failover; Pillar reads the outcome as an attribute of the service.
    • A service whose plan has not been exercised inside its objective shows as the gap it is.
  • Live Mount

    Rubrik boots a backup beside production, straight from backup storage.

    • Pillar records each mount and its result as dated evidence for the service it serves.
    • A service with no recent mount, or a failed one, is flagged against its commitment.
    • The mount is Rubrik’s; Pillar never runs it.
  • Compliance status

    Rubrik marks every workload compliant or not against its SLA Domain.

    • Pillar reads that status by service, so one lapsed workload reads as “Payroll”, not an object id.
    • Ranked by the recovery commitment the service carries, not by count.
    • Owner and department on every finding, so the right person hears about it.

By service

Proved by service, evidenced on request.

  • Aligned to a service

    Discovery, agentless and credentialed, ties every backed-up machine to the service it serves and the recovery commitment it inherits, checked continuously as an estimated recovery.

  • Evidence on request

    The record for each service, mapped to SOX, GDPR, DORA, HIPAA and ISO 22301 and exported to PDF, CSV or OneTrust, beside the reports Rubrik already builds, exported as CSV.

Stay tuned

Rubrik, understood by service.