Skip to main content

Coming soon

Pillar for Commvault.

What we’re building: everything Commvault 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 Commvault.

Read-only, over the Commvault REST API.

  • Clients and virtual machines

    Every client and VM, with its backup sets and subclients.

  • Plans

    Each plan, the RPO it carries, and the storage it writes to.

  • Jobs

    Every run: result, duration, and what failed.

  • Storage policies and libraries

    Each policy, its copies and their size, and every library.

  • SLA status

    Which servers met their SLA, missed it, or await investigation.

  • Schedules, events and alerts

    Every schedule, including disaster recovery groups, and every event by severity.

Verification

Verifying with Commvault.

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

  • Failover Groups

    A Failover Group recovers the machines behind a service together, in priority order.

    • Pillar proposes the group’s membership and priorities from discovered dependencies, for a person to accept in Commvault.
    • Commvault runs the Test Failover in the recovery target’s virtual lab; Pillar reads the job’s outcome as an attribute of the service.
    • A service whose group has not been exercised inside its objective shows as the gap it is.
  • Application Validation and Testboot

    Commvault boots a backup from storage and checks that the application answers.

    • Pillar records each validation and its result as dated evidence for the service it serves.
    • A service with no recent validation, or a failed one, is flagged against its commitment.
    • The boot is Commvault’s; Pillar never runs it.
  • Recovery Readiness

    Commvault reports each client’s RPO against what was achieved, and RTO against what is estimated.

    • Pillar reads it by service, so a missed objective reads as “Payroll”, not a client name.
    • 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 Commvault’s own SLA, Backup Job Summary, Recovery Readiness and Audit Trail reports.

Stay tuned

Commvault, understood by service.