DR Compliance

Generate audit-ready RPO/RTO compliance reports, DR test audit trails, and failover history from nxtDR for regulatory and internal governance requirements.

Overview

nxtDR generates audit-ready reports documenting replication status, achieved RPO/RTO values from DR tests, and complete failover history. These reports satisfy common regulatory requirements (ISO 22301, SOC 2 Type II, HIPAA, PCI-DSS) that mandate documented DR testing and measurable recovery objectives.

Prerequisites

• Protection plans with at least one completed DR test
• Administrator access to Disaster Recovery → Reports
• Compliance reporting period defined (typically monthly, quarterly, or annual)

---

Report Types

Report Type	Contents	Typical Use
RPO/RTO Compliance	Achieved vs configured RPO and RTO per plan per period	Regulatory submission, internal governance
DR Test History	All DR test events — date, plan, measured RTO, pass/fail	Audit evidence of testing cadence
Failover Audit Log	Complete record of all failover and failback events	Incident investigation, change management
Replication Status	Daily snapshot of replication lag and data currency	Ongoing compliance monitoring
Recovery Point Inventory	Available recovery points per plan at report time	Data retention compliance

---

Generating Reports

Dashboard

Navigate to Disaster Recovery → Reports and select the report type:

1. Select report type

   Select from the report type list. Each report type has configurable parameters for the plan name, date range, and output format.

2. Set parameters

   Parameter	Description
   Plan	Specific plan or “All Plans”
   From / To	Reporting period start and end dates
   Format	PDF (for submission) or CSV (for further analysis)
   Include raw data	Append raw metric data as appendix (PDF only)

3. Generate and download

   Click Generate Report. The report is created and available for download within seconds for short periods, or minutes for long reporting periods.

   Report downloaded and shows plan name, period, achieved RPO/RTO values, and compliance status.

CLI

nxtDR disaster recovery operations are managed exclusively through the nxtDR Dashboard. CLI access is not available for DR operations. Use the Dashboard tab above to generate and download compliance reports.

---

DR Test Cadence Requirements

Most regulatory frameworks mandate regular DR testing. nxtDR tracks test history automatically. Use nxtRadar to alert when testing cadence slips:

Regulation	Typical DR Testing Requirement
ISO 22301	Annual minimum; test must cover critical systems
SOC 2 Type II	At least annual; evidence of testing required for audit
HIPAA	No explicit cadence; must be “tested and revised” periodically
PCI-DSS	Annual test of incident response / DR procedures

Configure a nxtRadar alert for nxtDR_last_test_age_days > 90 to ensure quarterly testing. This exceeds all common regulatory minimums and provides early warning to schedule tests before the annual window closes. See Monitoring for alert rule configuration.

---

RPO/RTO Compliance Report Contents

The RPO/RTO Compliance report includes the following sections:

Executive summary

One-page summary showing:

• Protection plans covered
• Reporting period
• Overall compliance status (compliant / non-compliant)
• Number of DR tests performed
• Number of actual failover events

Per-plan RPO compliance

For each plan:

• Configured RPO target
• Average, p95, and maximum replication lag during the period
• Percentage of time replication lag was within RPO target
• Number of RPO breach events and total breach duration

Per-plan RTO compliance

From DR test results:

• Configured RTO target
• Measured RTO for each DR test performed in the period
• Pass/fail against configured target
• Trend (improving, stable, degrading)

Appendix: raw event data

Optional detailed data:

• Replication lag time series
• All recovery point timestamps
• Script execution logs from DR tests
• Failover event timelines

---

Automated Report Delivery

Schedule compliance reports for automatic generation and delivery. Navigate to Disaster Recovery → Reports → Scheduled Reports and click Create Schedule:

Setting	Description
Report Type	RPO/RTO Compliance, DR Test History, or Failover Audit Log
Plans	Specific plan or all plans
Frequency	Monthly, quarterly, or annual
Format	PDF (for submission) or CSV (for analysis)
Recipients	Email addresses for automatic delivery

Manage existing schedules from the Scheduled Reports list.

---

Evidence Preservation

Compliance audits may require evidence that DR testing and monitoring occurred throughout the audit period. nxtDR retains:

Data Type	Retention Period	Location
DR test reports	Indefinite (until manual deletion)	nxtDR controller database
Replication lag metrics	90 days raw; 1 year downsampled	nxtRadar metric store
Failover event logs	Indefinite	nxtDR controller audit log
Runbook script output	90 days	nxtDR controller log archive

If your regulatory framework requires longer retention, export reports to an external system immediately after generation. nxtDR does not enforce retention beyond the defaults listed above.

---

Next Steps

Monitoring

Configure alerts to maintain compliance proactively

nxtDR User Guide — DR Testing

Run DR tests to generate the evidence captured in compliance reports

Security

Access control and audit trail for nxtDR administrative operations

Troubleshooting

Diagnose replication lag that threatens RPO compliance