Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.

Vault Activity

Overview​

The Vault Activity tab is a chronological log of every vault network open and close that a vault agent has executed. Each entry is a real Quantum Trust Protocol (QTP) encrypted message (VAULT_OPEN or VAULT_CLOSE) recorded in the Quantum Trust Protocol audit log — this tab is a focused, filtered view of just those two message types.

Use this view to confirm that airgap windows opened and closed as expected, and to audit the duration of each window.

Event Types​

EventBadgeMeaning
Vault OpenBlue (unlock icon)The vault agent announced opening of the vault network via QTP (VAULT_OPEN). Sent when the first operation needs the vault network (a heartbeat or a group's sync).
Vault CloseYellow (lock icon)The vault agent announced closing of the vault network via QTP (VAULT_CLOSE). Sent when the last operation holding the vault finishes, before the airgap is physically closed.

VAULT_OPEN/VAULT_CLOSE are per open period, not per group or per heartbeat. The vault agent keeps the vault open while any operation needs it — a heartbeat check-in, or a protection group's sync from its start until its jobs finish — and closes it when the last one is done. Example: group A syncs 03:45–05:00, a heartbeat runs at 04:10, group B syncs 04:30–04:50 > one Vault Open at 03:45 and one Vault Close at 05:00 ("4500s window").

If the vault agent restarts while the vault is open, the vault is not closed (so running copy jobs keep their network). That open period then has no Vault Close, and the restarted agent records a new Vault Open.

What Each Event Shows​

Each row displays:

  • Event badge — Vault Open (blue) or Vault Close (yellow)
  • Agent name — the vault agent that generated the event
  • Subject — human-readable detail:
    • Vault Open: Vault open — <AgentName> — ACD: <device IP> — <reason> — the operation that opened the vault: heartbeat, or sync:<group> (scheduled), (retry), (adopt) (following jobs that were already running, e.g. after an agent restart)
    • Vault Close: Vault closed — <AgentName> — <durationSeconds>s window — <reason>
  • QTP Msg ID — the message UUID for cross-reference in the Quantum Trust Protocol Audit Log tab
  • Timestamp — when the event was recorded (UTC, displayed in local time)
  • Error message — only shown if the agent reported a problem (red text)

Reading the Activity Log​

A normal successful airgap cycle is two rows:

  1. Vault Open — network opened, sync cycle starting
  2. Vault Close — network closed after sync work finished; the Ns window value shows how long the airgap was held open

If you see a Vault Open with no matching Vault Close within a reasonable time, the cycle may have stalled — check the agent's Dashboard pill, the Quantum Trust Protocol Audit Log tab for WINDOW_ABANDONED records, or alarm CV-114.

info

Heartbeats are no longer shown here. Heartbeat check-ins appear as HEARTBEAT_CHECKIN records in the Quantum Trust Protocol Audit Log tab.

Data Source​

This tab fetches the last 250 VAULT_OPEN and 250 VAULT_CLOSE QTD records from the server (server-side filtered) and merges them newest-first. Auto-refresh is not enabled — click Refresh to reload.

Empty State​

"No vault open/close events recorded yet." appears when no vault agent has yet issued a VAULT_OPEN/CLOSE — typically before vault mode has been activated for the first time, or before the agent's first sync cycle.