BCDR compliance: turn backup records into usable evidence
15 October 2026
Build stronger BCDR compliance evidence with backup records, retention checks and recovery tests, while separating legal duties from contract terms.
Datto published an article on 9 January 2026 examining how business continuity and disaster recovery supports organisations in regulated industries. For Australian businesses handling sensitive records or delivering critical services, the practical BCDR compliance question is not simply whether backups exist. It is whether you can demonstrate what is protected, how long it is retained and whether it can be recovered.
Datto’s discussion of BCDR and compliance provides the starting point. Its international examples should not be treated as a statement of local obligations. Backup supports compliance evidence; it does not establish compliance by itself.
Start BCDR compliance with an obligations register
Before changing backup settings, identify the requirements that actually apply to your organisation. Separate them into three categories:
- Legal and regulatory obligations: applicable legislation, regulatory standards and recordkeeping duties.
- Contractual commitments: customer agreements, supplier terms, insurance conditions and service-level commitments.
- Internal policies: retention schedules, recovery targets and security standards approved by your business.
These categories can overlap, but they are not interchangeable. A customer contract requiring a particular recovery time is not automatically a statutory requirement. An internal policy may be stricter than the legal minimum, but that does not make it legislation.
Applicability matters too. Privacy Act obligations depend on coverage, including relevant exceptions to the small business exemption. Health record requirements can differ by jurisdiction. APRA prudential standards apply to regulated entities within their scope; a supplier may instead receive related obligations through its contract.
Create a register with the requirement, its source, the affected records or services, an accountable owner and the evidence needed. Ask a suitably qualified legal or compliance adviser to resolve uncertain interpretations. Do not select a retention period simply because a backup product offers it as a preset.
Map requirements to systems and records
A requirement to preserve a business record does not tell you automatically which systems must be protected. Records may be spread across email, accounting software, shared drives, laptops and specialist applications.
For each important record category, document:
- The authoritative system and its business owner.
- Supporting files, attachments and application dependencies.
- The approved retention rule and what starts the retention period.
- The permitted data loss and service interruption.
- Access, storage location and disposal requirements.
Distinguish a backup from an archive. Backups generally support recovery after loss or disruption. An archive or records-management system may be needed for long-term retrieval, controlled disposal or preservation of individual records. A rolling backup schedule may not meet those needs.
Check SaaS platforms explicitly rather than assuming the provider’s availability arrangements cover accidental deletion or your required recovery window. Our guide to protecting data across Microsoft 365, laptops and servers helps frame that coverage review.
Keep backup records that explain coverage and exceptions
Useful BCDR compliance evidence connects approved requirements to actual operations. A dashboard showing successful jobs is helpful, but it may not reveal an excluded folder, an unprotected application or a recently added server.
Keep a practical evidence set containing:
- A protected-system inventory, reconciled against the live environment.
- Backup schedules and configuration exports showing scope and exclusions.
- Job histories identifying successful, failed and missed backups.
- Exception tickets recording investigation, corrective action and closure.
- Change records for retention, access and protection settings.
- Named owners for reviewing alerts and resolving gaps.
Record timestamps and time zones consistently. Where reports are generated automatically, confirm they identify the relevant system and reporting period rather than displaying only an overall status.
A failed job is not necessarily proof of a compliance breach. However, an unexplained failure with no assigned owner weakens your ability to demonstrate control. Preserve both the failure record and the response, rather than presenting a success-only summary.
Verify retention settings against approved rules
Retention settings deserve their own review. Backup frequency determines how often recovery points are created; retention determines how long those points remain available. Neither setting alone proves that a particular record can be retrieved for its required lifetime.
Check the configured policy against the approved schedule, including:
- Whether daily, monthly and annual copies expire differently.
- What happens when an employee leaves or a system is decommissioned.
- Whether storage limits or subscription changes affect available history.
- How legal holds suspend ordinary disposal where required.
- How expired information is removed, including from backup copies.
Keeping everything indefinitely is not a safe default. For entities covered by the Australian Privacy Principles, APP 11 generally requires reasonable steps to destroy or de-identify personal information no longer needed, subject to exceptions. The OAIC’s guidance on APP 11 explains the principle.
Have your adviser confirm how retention, preservation and disposal duties interact. Document how backup expiry and any later restoration will be handled so that restoring old data does not silently undo approved disposal decisions.
Test recovery and retain business acceptance
Recovery tests provide a different kind of BCDR compliance evidence: they show what happened when you tried to use the protected data.
Agree on two measures with business owners. The recovery point objective, or RPO, describes the acceptable amount of lost work measured in time. The recovery time objective, or RTO, describes the target time to restore a service. Targets are not guarantees, and a technical restore is not always the same as a usable business service.
A meaningful test record should capture:
- The scenario, systems and recovery point selected.
- The test environment and safeguards protecting production data.
- Start and finish times, with any excluded activities identified.
- Checks for data integrity, application access and dependencies.
- Business-owner acceptance, failures and assigned corrective actions.
Test more than individual files. An accounting application may need its database, identity services, permissions and integrations before staff can work. Also consider whether recovery remains possible if the normal administrator account is unavailable.
Choose test frequency according to risk and applicable requirements, with additional testing after significant changes. Use downtime costs to prioritise recovery, then retest weaknesses rather than merely recording them.
Protect the evidence and the recovery environment
Backup repositories and audit records need protection themselves. Review administrator access, multifactor authentication, separation from production credentials and alerts for deletion or policy changes. Assess isolated or immutable copies against your threat model, while recognising that their configuration and retention limits still matter.
Keep recovery instructions accessible during an outage, with controlled emergency access. Confirm who can authorise restoration, who coordinates incident response and who decides that normal operations can resume.
Store the obligations register, configuration evidence, exception history and test results in a controlled location. Limit access because logs and recovery reports may contain sensitive details. Retain this evidence according to its own approved schedule.
Together, these records can support an audit or customer assurance review. They do not replace wider controls such as incident reporting, staff training, access governance or supplier oversight.
Review the gaps before the next audit or outage
Start with one critical service. Trace its requirements through backup scope, retention settings and a documented recovery test. Assign owners and deadlines to any gaps, then extend the process to other services.
Tech Engine Australia can help review your cyber security and managed IT arrangements, including backup coverage, recovery readiness and evidence handling. Call 1300 088 324 or email sales@techengine.au to discuss a practical review.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint