Failover Evidence Coverage

Audit disaster-recovery failover evidence.

Description

Failover evidence records recovery exercises and their outcomes.

Failover evidence records recovery exercises and their outcomes. Evidence-category coverage differs from a successful recovery test.^[1]

Audit disaster-recovery failover evidence.

When to use Failover Evidence Coverage

Use this tool to audit disaster-recovery failover evidence.

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.

How to use Failover Evidence Coverage and understand its results

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
Enter requiredEvidence, capturedEvidence using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
requiredEvidence	Required failover evidence	list of string	Required
capturedEvidence	Captured evidence	list of string	Required

Enter requiredEvidence as the nonempty expected list and capturedEvidence as observations, which may be empty. Trim entries, compare case-insensitively using en-US lowercase and collapse duplicates. Return matched/missing expected labels and unexpected observed labels. Output follows first occurrence order with the last duplicate’s trimmed spelling.

coverage%=100matchedUnique/expectedUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredEvidence": [
      "alpha",
      "beta",
      "gamma",
      "delta"
    ],
    "capturedEvidence": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 50,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma",
      "delta"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No failover, recovery time or recoverable data is tested. Blank entries are errors; requirements are entirely caller-supplied and items have equal weight.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use RTO/RPO Tier Classifier: Classify RTO and RPO against caller-defined application-tier limits. For a complementary task, use Cloud Responsibility Coverage: Audit cloud shared-responsibility assignments.

References

Failover Evidence Coverage — tool.io

Similar or alternative tools

RTO/RPO Tier Classifier
Classify RTO and RPO against caller-defined application-tier limits.
Cloud Responsibility Coverage
Audit cloud shared-responsibility assignments.