QuickBooks Backup and Recovery Planning for Accounting Firms

Why the built-in backup feature is not enough on its own

QuickBooks' native backup creates a portable company file copy, which is useful but limited. It typically runs on a schedule tied to closing the file, does not protect against the backup destination itself failing, and does not address ransomware scenarios where an attacker could encrypt both the live file and any locally stored backup copies at the same time.

Applying the 3-2-1 rule to QuickBooks

• Three copies: the live company file plus at least two backup copies
• Two different media types: for example, local server storage and a cloud backup destination
• One copy offsite: a cloud or remote backup that survives a fire, theft, or ransomware event at the office
• A backup schedule that runs when QuickBooks is closed, or through a supported snapshot method, to avoid an inconsistent copy

What a complete QuickBooks backup should capture

1. The company file itself (.qbw) along with its transaction log (.tlg)
2. Any custom templates, letters, and memorized report definitions stored outside the company file
3. The QuickBooks license and installation details, documented separately so reinstallation is not blocked
4. Server configuration details for the hosting machine, in case a full server rebuild is needed

Backup software and QuickBooks interaction

Backup agents that copy an open company file mid-write can produce a backup that looks complete but fails to restore cleanly. Backup jobs should be scheduled outside the hours QuickBooks is actively in use, or configured to use volume shadow copy or application-aware snapshot features that capture a consistent state. We use Acronis Cyber Protect Cloud for exactly this kind of application-aware backup across the servers we manage.

Testing recovery, not just backup completion

A backup job reporting success tells you the copy process ran, not that the file will actually open and pass data integrity checks after a restore. Periodic test restores, ideally to an isolated environment, followed by a Verify Data check on the restored file, are the only reliable way to know recovery will work when it matters. Our backup and disaster recovery services build this testing into the ongoing backup process rather than treating it as optional.

Recovery time expectations firms should set in advance

How quickly a firm can be back in QuickBooks after a server failure depends on whether spare or replacement hardware is available, whether the backup destination is fast to restore from, and whether hosting configuration is documented well enough to rebuild quickly. Firms that have never discussed a target recovery time with their IT provider are often surprised by how long an unplanned recovery actually takes compared to what they assumed.

How this fits with server and workstation planning

Backup planning should be reviewed any time the hosting server changes, covered in our server migration considerations guide, and whenever ransomware risk is discussed as part of broader cybersecurity services planning for the firm.

Sources and further reading

• Canadian Centre for Cyber Security: Back up your data

Frequently asked questions