Backblaze Not Backing Up | Fixes That Make Backups Run

backblaze not backing up? Check schedule, exclusions, bandwidth, and external drive status to restart backups without losing data.

Backups should hum along in the background. When they stall, you need a simple flow that restores uploads without risking the archive you already have. This guide gives you clear tests, matches each cause to a fix, and points to the few settings that matter on Windows and macOS. Every step is safe, reversible, and grounded in the Backblaze interface.

Backblaze Not Backing Up: Fast Checks Before You Dig

Quick check: Start with the app’s own status. Open the Backblaze control panel (Windows) or menu bar item (Mac) and read the status line. If you see Paused, click Resume Backup. If it shows Scheduled, your client runs only during a set window; switch to Continuous to keep uploads moving all day.

Confirm The Schedule — In Settings → Schedule, select Continuous. With Once Per Day, files queue but upload only during that window; outside it, nothing sends.
Look For Exclusions — In Settings → Exclusions, remove folder, file-type, or size rules that hide data you expect to see in your backup view.
Check Network Throttle — In Settings → Performance, turn off Automatic Throttle and raise threads if your line can handle it. Low throttle can make progress look stuck even when the client is alive.
Wake The Laptop — Keep the lid open and power plugged in so the client can scan and upload in the background.
Verify External Drives — Plug each drive in. Backblaze prunes a drive from your backup if it stays unplugged for 30 days; reconnect to keep the cloud copy.

Deeper fix: If status shows Initial Backup with zero files remaining, the client is skipping problem files and retrying later. Clear the blockers below, then resume and let it reindex.

Why Your Backblaze Backup Stalls Or Skips Files

Most stalls trace to four buckets: schedule, exclusions, network limits, or external-drive rules. Less common causes include a missing hidden .bzvol tag on a drive, a replaced disk that needs Inherit Backup State, or permission gaps after an OS change. Use the patterns below to spot which one you have and apply the right fix.

Schedule And Paused States

Resume A Paused Client — Click Resume Backup. If it flips back to paused, change the schedule to Continuous and reboot once to clear a stuck state.
Use Continuous For Catch-Up — With Once Per Day, the app indexes new files but uploads only during the window you set. Swap to continuous until you’re current, then return to a daily window if you prefer.
Know What “Backup Now” Does — On continuous mode, Backup Now resumes a paused session rather than starting a fresh pass. That’s by design, so the client can run hourly cycles without manual nudges.

Exclusions Hide Files

Quick check: Exclusions are powerful and easy to over-use. Broad folder rules hide everything inside, file-type wildcards can block formats you care about, and size caps make large media disappear from the queue.

Remove Broad Folder Rules — If you excluded a top-level project folder, every subfolder goes dark. Trim the rule or delete it.
Trim File-Type Patterns — A wildcard like *.db or *.pkg can hide app data you plan to keep for recovery. Keep patterns narrow.
Check Size Limits — If a max size is set, files above that number never upload. Raise or clear the cap for big media and archives.

Network Limits Slow Or Stall Uploads

Disable Auto Throttle — Uncheck auto throttle and push the slider right during catch-up. Raise backup threads a notch and watch the line; add more only if your system stays responsive.
Keep Heavy Apps Idle — Pausing big sync tools, live streams, or game updates frees sockets and uplink for the backup engine.
Stay On Power — Laptops that sleep mid-scan look like a stall. Keep the lid open while you push the first big upload.

External Drive Rules

Plug The Drive In Monthly — Each external drive must appear at least once every 30 days. If it goes missing longer, the cloud copy gets pruned automatically.
Watch The Hidden .bzvol Tag — Backblaze writes a hidden .bzvol folder with a tiny ID file at the root of each selected drive. If that folder is missing or read-only, the drive won’t back up.
Beware Cloned Disks — A straight clone can copy the .bzvol tag and confuse identity. Exclude the tag on clones or re-create it so each drive is unique.

After A Reinstall Or Disk Swap

Use Inherit Backup State — After a reinstall, drive replacement, or new computer, link the new install to your old archive so the client matches files by checksum instead of re-uploading the world.
Pick The Right License Action — Inherit to continue the same backup, or transfer the license to start a new set cleanly. If you still need data from the old set, make a restore first.

Fix Backblaze Backup Fails On Windows

Quick check: Confirm the service runs, set the schedule to continuous, then tune performance and exclusions. If you changed hardware, inherit the old backup before you push a new full upload.

Open The Control Panel — Search for Backblaze, open the app, and note status plus the last completed upload time.
Set Continuous — Go to Settings → Schedule and choose Continuous, then click Apply.
Raise Threads — In Settings → Performance, uncheck auto throttle and raise the thread count in small steps. Keep an eye on CPU and your line; stop when uploads saturate cleanly.
Review Exclusions — In Settings → Exclusions, remove broad folder rules and sanity-check file-type patterns and size limits.
Force A Rescan — Click Backup Now to resume. If the app lost track of file locations after a big move, use the restore view’s location tools to re-map your drive tree, then let the client reindex.
Check External Drives — Mount each drive. At the drive root, confirm a writable .bzvol folder exists. If not, add the drive in Backblaze and let the app create it.
Inherit If You Reinstalled — From the taskbar icon, choose Inherit Backup State, sign in, pick the old machine name, and let the comparison run.

Deeper fix: If Windows was reinstalled or the primary disk changed, a new install may want to re-upload everything. Inherit the old set to save time and bandwidth.

Fix Backblaze Backup Fails On macOS

Quick check: Open the menu bar icon. If uploads wait, flip to continuous and keep the lid open on power. Then tune performance and verify privacy permissions.

Open Settings — Go to System Settings → Backblaze, then click Settings.
Pick Continuous — Under Schedule, select continuous and apply.
Increase Throughput — Under Performance, uncheck auto throttle; raise thread count in small steps until the line stays busy without lag.
Check Exclusions — Under Exclusions, review folder, type, and size lists. Remove anything that hides active project paths.
Grant Full Disk Access — In Privacy & Security, confirm Backblaze has Full Disk Access so it can index user libraries and app data stores.
Verify External Drives — Mount each drive; at the root, confirm a writable hidden .bzvol folder exists.
Inherit After A Reinstall — From the menu bar icon, choose Inherit Backup State to link to the old archive and avoid a full re-upload.

Network, Bandwidth, And External Drive Rules

By default, Backblaze adapts to your line so normal web use feels smooth. During a catch-up, you can give it more room. If you store data on external media, you also need a simple cadence so cloud copies stay alive.

Auto Throttle Behavior — The client targets roughly seventy to ninety percent of available upload to leave headroom for other apps. Turn it off when you want the fastest push, then turn it back on later if streaming feels rough.
Thread Count Tuning — More threads help small files fly. Raise until the line stays busy without making the desktop sluggish.
Power Settings — Laptops should stay awake and on power during the first large pass. Sleeping systems do not scan or upload.
30-Day External Drive Window — Each external drive must be seen at least once every 30 days or its cloud copy is removed. Set a calendar reminder to mount drives you don’t keep attached.
.bzvol Identity — Each selected drive gets a hidden folder with a tiny XML tag that marks it forever. If the app cannot write that folder, the drive stays out of backup; fix permissions or formatting and try again.

Good habit: When your workflow involves hot-swap SSDs, leave a sticky note on the case with the last mount date. That small routine keeps cloud copies current and avoids surprise gaps.

Backblaze Exclusions, File Types, And Size Limits

Quick check: The app is built to back up user data and skip OS files by default. That keeps restores clean and reduces churn from volatile system files. You can still add your own rules, so a quick review often reveals why a folder seems invisible.

Default Behavior

Backblaze mirrors your drives. Delete a file locally and the cloud copy follows after 30 days. That window lets you pull a restore if you catch a mistake. System folders and program files sit out, which keeps the backup focused on your documents, photos, mail stores, and other user data.

Smart Ways To Use Exclusions

Exclude Build Artifacts — Add temp and cache paths so the client spends time on real content, not throwaway files.
Leave User Libraries In — Documents, desktop, photos, and project folders should stay in scope so restores bring you back fast.
Avoid Broad Wildcards — Keep patterns tight. Wide rules like *.db or *.log can hide data you actually need.
Mind Size Rules — If you set a max size, large media and VM images will never upload. Clear the cap or move giant archives to a different storage plan if needed.

Symptom	Where To Look	What To Change
backblaze not backing up and shows Paused	Backblaze window	Click Resume; switch to Continuous
Files missing from backup	Settings → Exclusions	Remove folder/type/size rules
Upload meter barely moves	Settings → Performance	Disable auto throttle; raise threads
External drive not listed	Finder/Explorer	Mount drive; ensure `.bzvol` exists and is writable
New install wants a full re-upload	Tray/Menu bar	Pick Inherit Backup State

Heads-up: If your Mac or PC just came back from service with a new internal drive, treat it like a new machine from the backup app’s point of view. Use the inherit option before you try anything else, then let the comparison phase run to match files you already uploaded.

One more common thread: people search for “backblaze not backing up” when an initial upload appears to hang on the last few files. In many cases the app is retrying locked items (such as open mail stores or database files). Close the app that owns the file, wait a few minutes, and the counter ticks down again.

When To Contact Support And What To Send

Quick check: If you ran the steps above and your queue still sticks, send a short report. Include a screenshot of the Backblaze app, your OS version, whether the drive is internal or external, and any message about .bzvol, permissions, or a paused initial backup.

Attach Logs — In the app, open Help and collect logs. Add the ticket number from your restore page if you created one.
List What You Tried — Mention schedule, exclusions, throttle, thread count, and any steps you ran here so the agent can skip repeats.
Add Drive Details — USB, Thunderbolt, or network path, plus the last date the drive was mounted.
Note Any Reinstall — Say if you replaced a disk or the whole machine and whether you used inherit.

From Problem To Working Backup

You now have a tight loop: set continuous, trim exclusions, open the throttle during catch-up, and keep external drives present with a healthy hidden tag. If you changed hardware or reinstalled, inherit the old set to reconnect the archive. With those fixes in place, uploads resume, the status flips to green, and your restore set stays current.