Volume Shadow Copy backups and QuickBooks files: what bookkeepers need to know

Shadow-copy backups (Volume Shadow Copy Service, or VSS) run on most Windows servers and desktops. They snapshot whole disks while people keep working, which makes them attractive: no downtime, no closing windows, no evening routine. The catch is that a snapshot of a file being written to is not the same as a clean copy of that file. This matters a great deal when the file is a set of books.

What crash consistent actually means

A VSS snapshot captures the disk at an instant. If QuickBooks is mid-write at that instant, the snapshot holds a file whose internal structures are only partly updated. The industry term is "crash consistent": the copy resembles what would be left on disk after a power cut.

Some applications register with VSS as writers, so the service coordinates with them and produces a coherent copy. QuickBooks is not one of them. The application does not participate in the shadow-copy handshake, so the snapshot gets whatever bytes happened to be on disk. A backup taken this way may restore, may open with errors, or may open and be quietly wrong.

How a bad backup shows up in the ledger

The failure modes are worth separating, because they look different at the desk.

The obvious one is a restore that will not open, or that fails a verify. That is a nuisance, but at least it announces itself.

The quieter one is a file that opens and reconciles, but is missing the tail of a session. Transactions entered late in the day, a reconciliation saved just before the snapshot, a memorized report: any of these can be absent while the file looks healthy. If nobody compares against source documents, the gap surfaces weeks later as a reconciliation difference or a mismatch with the bank feed.

What this does to the close and the reconciliations

A crash-consistent backup restored mid-month costs you the cleanest thing a bookkeeper has: a known point-in-time. The opening balances for the period may not match the closing balances you signed off previously. Prior-month reconciliations can show as broken, because the snapshot predates the final reconciliation write.

The practical rule is simple. Treat any restore from a shadow copy as an unverified opening balance until you have reconciled the bank and compared the trial balance to the last approved close. Do not roll forward on faith.

Telling a bad backup apart from a posting mistake

A posting error is bounded. One transaction is wrong, duplicated, or in the wrong period, and the rest of the ledger is intact. You fix it with a journal entry or an edit, and the reconciliation difference explains itself.

Snapshot damage is structural. Symptoms include totals that do not foot, lists that fail to sort correctly, a verify or rebuild that reports errors repeatedly, or balances that disagree with a prior close by amounts no single entry explains. If the file's arithmetic disagrees with itself, that is not bookkeeping anymore.

What to preserve before anyone touches the file

Before any repair attempt, keep everything.

• The restored file exactly as it came off the backup, untouched.
• A second copy of the backup media or image itself.
• The most recent known-good backup from before the incident.
• Notes on the date and time of the snapshot, and what was open at the time.

Every repair pass writes to the file, and each pass can destroy evidence the previous one needed. Work on copies, never on the only original.

Where the bookkeeper's job ends

If the file fails verification after a restore, or balances disagree structurally, stop. Repeated rebuild attempts on damaged data can make things worse, and the judgement calls involved (what to re-enter, what to trust) need a verified baseline first. Data damage of this kind is a specialist repair job, not a close task. Our sister service handles QuickBooks data repair directly; if that is what you are facing, go there rather than working the file yourself.

Backups that do work

Two habits avoid the whole problem. Use the backup facility built into QuickBooks, which quiesces writes and produces a file meant to be restored. Or schedule backups for a window when every user has closed the company file, typically overnight. Shadow copies remain useful as disaster recovery for the machine. Just do not treat them as the backup of record for the books.