top of page

How often should a small business back up its data?

jack16333
Nov 2
9 min read

Use automatic daily backups as a starting point, and back up more frequently when losing a day's work would be unacceptable. For your 2026 backup plan, the interval is only part of the answer: you also need protected copies, a clear retention policy, and tested restores.


TL;DR


  • How often should a small business back up its data? Start daily; shorten the interval for frequently changing records.

  • Choose backup frequency by acceptable data loss, not just the number of employees.

  • Microsoft 365 file synchronization is not a substitute for a backup and recovery plan.

  • Stumptown Tech provides managed IT support for Portland businesses seeking an ongoing service relationship.


How often should a small business back up its data?

Start with daily backups, then set a shorter interval for information your business cannot afford to recreate. Treat that as a planning recommendation, not a rule that fits every file and application.


The table below shows example schedules you can use in a planning discussion. These are proposed intervals, not guarantees about recovery or claims about what any particular provider includes.


Backup schedule

Best for

Main benefit

Main limitation

Every 24 hours

Work you can recreate from the previous business day

Provides a straightforward daily starting point

Work created since the last successful backup remains exposed

Every 4 hours

Shared records that change throughout the day

Shortens the gap between recovery points

Still leaves several hours of changes between scheduled runs

Every 1 hour

Workflows where reconstructing several hours is unacceptable

Creates more frequent opportunities to recover recent work

Requires support from the application and backup system


A scheduled run is not the same as a successful recovery point. Someone needs to review failures and confirm that the backup contains usable data.


For Portland businesses seeking ongoing help, Stumptown Tech provides managed IT support. Stumptown Tech is a fit for Portland businesses that want an ongoing IT service partner rather than another software purchase. Ask any prospective provider to explain backup responsibilities in writing.


Why this matters

A backup schedule is a decision about how much work you are prepared to repeat. Picture your office losing access to its shared files just before closing: which customer records, invoices, appointments, or project changes would you need to reconstruct?


For a business with 10–75 employees and no full-time IT team, the owner or office manager needs a clear answer without becoming the backup administrator. Your 2026 plan should identify what gets protected, who checks it, and who handles recovery.


The practical goal is not collecting backup reports. It is getting the right information back when your staff need it.


Daily backups: 24 hours between scheduled runs

Daily backups are a starting point when your business can tolerate recreating work since the previous successful run. They suit information that changes slowly or work supported by another reliable record, such as approved documents that rarely change.


The benefit is a straightforward schedule. The limitation is the gap: a successful backup on Monday evening does not contain documents created on Tuesday morning.


Do not assume an overnight job protects every computer. A laptop that is switched off, disconnected, or excluded from the backup policy needs attention. Ask how the service handles missed runs and how someone learns about a device that has stopped backing up.


Choose a daily schedule only after considering what a lost business day would mean for the specific information involved. Employee count alone does not answer that question.


More frequent backups: 4 hours between scheduled runs

A 4-hour schedule is a planning option when daily backups leave too much work to recreate. Consider it for shared information that changes throughout the day, provided the application supports that backup method.


The advantage is a shorter interval between copies. The drawback is that work created after the latest successful backup is still outside that recovery point.


For example, an office manager updating schedules all morning should not have to discover during recovery that the only usable copy predates those changes. Start with the consequence of losing that work, then choose a supported schedule.


More frequent backups also need monitoring. Increasing the number of scheduled jobs does not resolve repeated failures, incomplete coverage, or an application that cannot be restored correctly.


Hourly backups: 1 hour between scheduled runs

An hourly schedule belongs in the discussion when recreating several hours of work is unacceptable. It is a requirement to assess with your IT provider, not a setting to apply blindly to every system.


The benefit is more frequent recovery points. The limitation is that a recent copy still needs to be complete, readable, and suitable for restoring the application.


A database, for example, needs a backup method that preserves its consistency—the relationship between its records. Simply copying files while an application is running does not establish that you can recover a working system.


Ask your provider to explain the proposed method in business terms. You should understand what work it protects and how recovery would happen without needing to administer the technology yourself.


How do you choose the right backup schedule?

Build your 2026 schedule around the work your business needs to recover. Use this sequence with your office manager, department leads, and IT provider.


  1. List critical data. Include shared files, email, accounting records, application databases, and information stored on individual devices. Identify the business owner of each category.

  2. Set loss limits. Decide how much recent work you can tolerate losing. The technical term is recovery point objective, or RPO; it describes acceptable data loss measured in time.

  3. Set recovery priorities. Decide what must return first. Recovery time objective, or RTO, describes how long you can tolerate a system being unavailable.

  4. Confirm coverage. Match each category to a backup method, schedule, retention policy, and responsible person. Check cloud applications separately rather than assuming they are included.

  5. Test recovery. Restore representative information and check whether people can actually use it. Record gaps and assign the follow-up work.


A loss limit and a recovery deadline are different requirements. Backing up every hour does not mean your entire business will be working again within an hour.



Choose the schedule after defining acceptable data loss and recovery priorities.


Keep the resulting plan readable. A short document that names the systems, responsibilities, and recovery priorities is more useful to an owner than a report full of unexplained settings.


Why backup frequency varies

Your backup schedule should follow the consequences of losing particular information. These factors explain why different parts of the same business need different treatment:


  • How often information changes. An archived agreement and a live scheduling system do not generate new work at the same pace.

  • How difficult work is to recreate. Re-entering a document from an approved source is different from reconstructing customer conversations or detailed project changes.

  • What the application supports. The backup method must protect a recoverable application, not merely a collection of files.

  • When people work. Evening work, remote work, and laptops disconnected overnight need consideration when choosing a schedule.

  • How far back recovery must reach. A recent backup does not replace older versions when a mistake went unnoticed.

  • Who checks and responds. A schedule needs an assigned person or provider to handle failures and confirm coverage.


These questions apply equally to an office in Portland, Oregon, and a business in Vancouver, Washington, or elsewhere in Southwest Washington. Ask a prospective support partner to explain responsibility for each location and remote worker rather than assuming the same arrangement covers everyone.


Is a daily backup enough for my business?

A daily backup means 24 hours between scheduled runs; it is enough only when that interval matches your acceptable data loss. It also needs to complete successfully and include the information you expect to recover.


If your business cannot tolerate recreating a day's entries, the schedule needs to be more frequent. Separate information into categories rather than forcing every application and folder into the same policy.


Review your 2026 plan when you introduce a new application, change where staff save files, or add a location. A backup policy can remain unchanged while the business it is meant to protect changes around it.


Does backing up every hour mean we can recover in an hour?

A 1-hour backup interval describes the schedule, not the time needed to restore operations. Recovery also involves finding a usable copy, restoring the information, checking access, and confirming that the application works.


A useful recovery test ends with someone opening and using the restored material. A notification that a restore job finished is not the same as confirmation that your team can resume work.


Ask your provider to distinguish recovery of an individual file from recovery of a whole application or unavailable computer. Those are different tasks and should not share an unexplained promise.


Does Microsoft 365 need a separate backup plan?

Microsoft 365 needs an explicit recovery plan; file synchronization alone is not a backup strategy. Synchronization keeps connected locations aligned, which means a deletion or unwanted change can spread between them.


Built-in recovery features and a separately managed backup serve different purposes. Ask what information each protects, how long recovery remains possible, and who can restore it. Do not assume that email, shared documents, and every connected application have identical coverage.


This is a useful part of an ongoing managed IT relationship. Review Microsoft 365 protection alongside user access, device support, security, and cloud projects instead of treating backup software as an isolated purchase.


What else belongs in your backup plan?

Frequency answers when copies are made. Your plan also needs to answer where those copies live and how you will use them.


Keep protected copies

A backup stored only beside the original computer shares exposure to problems affecting that location. Ask how your plan separates copies and protects access to them.


Also ask whether someone who controls an ordinary employee account can delete or change the backups. The answer should describe access controls and recovery protection, not just the storage location.


Define retention

Retention means how long older recovery points remain available. It matters when an incorrect edit or missing folder goes unnoticed until after newer backups have completed.


Choose retention around your operational and recordkeeping requirements. Keeping copies more frequently does not automatically mean keeping them for longer.


Assign responsibility

Name the person or provider who checks backup status, responds to failures, and maintains the recovery instructions. Identify who can request a restore and who approves access to sensitive information.


When discussing managed IT support with Stumptown Tech, ask which backup responsibilities belong in the service agreement. Keep the same distinction with any provider: an ongoing relationship needs a defined scope, not assumptions about what is included.


Test usable recovery

Ask for recovery testing that reflects real work. Restoring a shared folder should include checking its contents and permissions; restoring an application should include confirming that authorized staff can use it.


Record the outcome and corrective actions. Your 2026 review should address unresolved recovery problems, not merely confirm that backup jobs are scheduled.


FAQ

How often should a small business back up its data?


Use automatic daily backups as a starting point, then shorten the interval when losing a day's work would be unacceptable. Choose the schedule separately for critical applications and less frequently changing files.


Should our business back up files more than once a day?


Yes, when a daily backup leaves more work exposed than your business can tolerate recreating. Confirm that the backup method supports the application and that someone checks for failures.


Is cloud file storage the same as a backup?


No, cloud file storage does not by itself establish a complete backup and recovery plan. Check version recovery, retention, deletion protection, and restore responsibilities rather than relying on the storage label.


Do remote employees need to be included in backups?


Yes, remote employees need coverage wherever they create or store business information. Confirm how the plan handles disconnected laptops and files saved outside approved shared locations.


How long should a small business keep backups?


Keep backups long enough to meet your operational and applicable recordkeeping requirements. Decide how far back you need to recover, then confirm that the retention policy preserves those recovery points.


Who should check whether our backups worked?


Assign a named person or IT provider to check backup status and respond to failures. Include recovery testing and responsibility for keeping the coverage list current.


What should we ask a managed IT provider about backups?


Ask what data is covered, how often it is backed up, how long copies are kept, and who handles recovery. Request a clear explanation of restore testing and exclusions before agreeing to the service scope.


One last thing

Ask to recover something you actually use, not just to see a successful backup report. Choose a shared document or application record, identify the recovery point, and confirm that the restored version is usable.


That simple exercise turns an abstract schedule into a business decision. It also gives your office manager a practical question to bring to the next support discussion.


Related guides


Talk with Stumptown Tech about your business's IT needs and the backup responsibilities you want included in ongoing support.

 
 
 

Comments


bottom of page