Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My backups may have stopped working and nobody was told

Short answer

Backups usually fail without noise: the disk fills, a password or token expires, the scheduled job stops, or the alert goes to an unread inbox. Check the date of the newest backup you can see. If it is old, tell your developer today, and do not delete files yourself to make room.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The newest backup I can find is weeks or months old.
  • The backup storage shows nearly full, or an error like out of space.
  • Nobody gets an email when a backup fails.
  • The backup folder keeps growing even though the site has not.
  • The job was set up by a person who has since left.

Why does this happen?

  1. The storage fills up and new copies stop

    Each night adds another copy. If old ones are never removed, the space runs out and later jobs fail. Some tools keep failing quietly, others delete the newest data first, depending on how they were set up.

  2. A credential or token expired

    A job that writes to remote storage uses a key or token. When it is changed or expires, the job can no longer write and often only logs the error.

  3. The scheduled job no longer runs

    A server move, an operating system change or a stopped service can switch the schedule off. Nothing complains, there is just no new file.

  4. Alerts go to an address nobody reads

    Failure emails are sent to the original developer or to a mailbox that no longer exists, so the failure is real but unseen.

  5. The copies sit on the same disk as the data

    When backups live on the server itself, they fill the same disk the site needs. A full disk can then break the site as well as the backups.

What can I do about it today?

  1. Find the date of the newest backupAsk your host or developer for the date and size of the last successful backup, and the one before it. Size that suddenly shrinks is a warning sign.
  2. Do not delete files to free spaceRemoving the wrong folder can destroy the only good copy. Leave cleanup to the person who knows what each file is.
  3. Ask where failure messages goRequest the address that receives them and put a monitored company address on it.
  4. Ask for a copy off the serverEven one fresh manual copy stored somewhere separate gives you a safety net while the real fix is made.
  5. Write the date you noticedA short note of when you found it helps work out how much data is at risk.

When should I bring someone in?

  • The newest good backup is older than you can afford to lose.
  • The site started showing errors at the same time the disk filled.
  • Nobody knows how the backup job was configured.

How do I handle it?

  1. Take a fresh safe copy firstBefore touching the job I make a copy to a separate place, so the fix cannot make things worse.
  2. Find why it stoppedSpace, credentials, schedule or a changed path. The logs usually name the cause.
  3. Set retention that fits the spaceA written rule for how many daily, weekly and monthly copies are kept, with room to spare.
  4. Make failure loudA failed or missing backup sends a message to a monitored address, and a missing run is treated as a failure too.
  5. Prove it with a restoreOne restore into an empty place confirms the new copies are usable.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is my data lost if the backup failed?

Not by itself. The live data is still there. What you lost is the safety net for the period since the last good copy.

Can I just buy more storage?

More space is part of it, but without a retention rule and alerts it fills again. Ask for all three.

How do I know it is fixed?

A new backup appears on the next schedule, an alert is shown to work, and one copy has been restored successfully.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.