Verify the files you care about are actually included

To verify that the files you care about are actually included, check the backup or sync app’s exact folder list, review any exclusions that could override it, and restore one real file to prove it opens. If you set up backup once and never checked it again, do not trust a screen that only says “protected” or “synced” until you’ve matched it against your invoices, client work, and shared documents. The safest check is to compare the app’s inclusion list with the folders on disk, confirm nothing is silently filtered out, and then test a restore.

Prerequisites

• Access to the backup or sync app that protects the machine, server, or account
• Permission to view backup settings, exclusions, and restore options
• A test file you can safely restore, such as a recent invoice PDF or harmless document
• The real folder paths, shared drives, or cloud-synced locations you want to protect
• Enough storage or a temporary folder to restore a sample file without overwriting the live copy

Start with the folders you cannot afford to lose

Before you open the backup app, make a short list of the real places that matter. Keep it specific. You are not checking “the business computer”; you are checking the folders and shares that hold active work.

• Invoices
• Client projects
• Shared documents
• Any department or team share on a network drive
• Any cloud-synced folder that contains files you still need locally protected

If a folder has been renamed over time, write down both the old and current name. If the files live in nested folders, note the parent path too. For example, C:\Work\Clients\Acme\2024 is more useful than just “Acme.” That gives you a target to compare against later, instead of assuming a parent folder means every child is covered.

Find the inclusion list in your backup or sync tool

Open the app and look for the place where it defines what is protected. Different products label this differently, but common names are Sources, Backup set, Included folders, Selection, Scope, or Folders to sync.

What you want is the exact list, not a summary. Read the full paths the app says it will protect. If the tool shows a tree, expand it all the way down so you can see nested folders. If it shows only parent folders, confirm whether subfolders are included by default or whether each one needs to be added separately.

If the app has separate tabs for backup and sync, check both. A folder may be selected for sync but excluded from backup, or the reverse. If there is a files only or folder only mode, make sure you know which one is active.

If the app has a view for included files or source details, use it. Some tools show folders on the main screen but hide the actual path list deeper in settings or logs.

Check for exclusions that override what you picked

Now look for anything that can cancel out the folders you selected. Exclusions are often buried in advanced settings, filters, or rules.

Check for:

• Excluded folders or paths
• File-type filters, such as skipping .pst, .db, .tmp, or archive files
• Size limits that skip large files
• Age rules that skip old files
• Hidden-file or system-file settings
• Case-sensitive path rules, if the app uses them
• Duplicate rules that treat one path as more important than another

An exclusion can override an included folder without making that very obvious. A folder can look selected and still have key files skipped inside it.

If the tool lets you add wildcard rules, look carefully for broad patterns like .zip or C:\Work\\Temp. Those can wipe out files you care about if they match a shared name or a nested folder. If you find a rule you do not fully understand, compare it against one of your important file types before trusting the setup.

Also check for settings that only look harmless until they are combined. A path can be included, but a file type, size cap, or age filter can still remove the exact files you meant to protect. If the app shows an exceptions list, read it line by line and make sure nothing there matches your invoice files, client exports, or shared documents.

Compare what the tool sees with what is actually on the drive

Once you know what the app says it includes, compare that with the actual folders on the computer or server. This is where you catch cases where a parent folder exists but a child folder is missing, renamed, or pointing somewhere unexpected.

Check these cases carefully:

• Nested folders under the main work folder
• Shared locations that are mapped differently for different users
• Folders that were renamed after the backup job was created
• Shortcut links that look like folders but are not the real storage location

If the backup app lists C:\Work, open File Explorer and confirm the actual subfolders under C:\Work. If the app lists a network path like \\Server\Share\Accounts, make sure it is the same share the team actually uses, not a local copy or an old mapped drive letter.

A parent folder does not always mean full coverage. Some apps protect only the folder you selected and whatever was inside it at the time, while others follow future subfolders automatically. Check how your tool handles new nested folders, because that decides whether fresh client work is covered without extra setup.

Run a small restore on one real file

Pick one file you can afford to test, such as a recent invoice PDF or a harmless document from a client project, and restore it from backup. A file that appears in the list is not enough. You want to prove the data can actually come back and open.

1. Choose a known file from one of your protected folders.
2. Restore it to a different location, such as a temp folder or your desktop.
3. Open the restored copy and confirm it is readable.
4. Compare the restored version with the original if you need to confirm the right file and date were pulled back.

Restore to a separate location first, not over the live file, unless you are sure you want to replace it.

If the app lets you choose a restore point, pick a recent one and then, if useful, an older one. That helps you confirm the file is present in the backup history, not just on the current device. If the restore fails, note whether the file was missing from the backup set, blocked by permissions, or present but unreadable after recovery. The exact message varies by app, so focus on which step failed.

Watch out for files that look included but are not protected yet

Some items are technically selected but still not safe to rely on. The most common issue is that the backup has not finished uploading or indexing yet. Another is that the app skipped a file because it was open, locked, or in use when the job ran.

Check for these cases:

• The backup job is still running or waiting to upload
• The file was open during the last backup and got skipped
• The external drive is only backed up when connected
• A network share is only protected when the office VPN or server is available
• The app has a queue or pending state that has not cleared yet

If you use external drives for project archives, verify the app is set to include them and that it actually sees the drive by name, not just by a letter that changes. If files live on a laptop that moves around, confirm the job still runs when the device is offsite or asleep. The main trap here is assuming “selected” means “already protected.” It often does not.

Check the status for the specific files or folders you care about, not just the job as a whole. A backup can report success while still leaving one open workbook, one disconnected share, or one external drive behind.

What to do when important files live outside the main folder

People often keep work in places they forget to include: the Desktop, Downloads, Documents, a cloud-synced folder, or a network location. Check each of those directly instead of assuming the main backup folder catches them.

For Desktop and Downloads, look at the actual path used by the operating system for that user account. For cloud-synced folders, make sure you know whether the backup app is protecting the local synced copy or only the cloud service itself. For network locations, confirm the machine can reach the share and that the backup account has permission to read it.

If a file sits in more than one place, decide which copy is the source of truth. For example, if client drafts live in both Documents and a shared drive, pick the one that should be restored after a loss and make sure that location is in the backup set. Do not count on a folder being “covered somewhere” just because the file also appears in another app.

If you use a network drive, an external drive, or a folder under another user profile, test that path directly in the app. These edge cases fail quietly when permissions change, the drive letter changes, or the user signs out. Nested folders deserve the same check: if a parent is included but the new subfolder is not, the newest client files can miss the backup even though the top-level folder looks fine.

Make a simple check you can repeat after changes

Write down the final protected set in plain language so you can recheck it later. Keep it short enough that you will actually use it.

A useful record usually includes:

• The exact included paths
• Any exclusions or file-type filters
• The backup destination or target account
• The date you last checked
• The test file you restored and where you restored it
• Any locations that are intentionally not protected

Store that note where you keep other admin settings, and update it whenever you add a folder, rename a share, change devices, or edit filters. If you want a quick repeatable check, compare three things: the app’s inclusion list, the exclusion rules, and one restored test file. If all three still match your expected folders, you can trust the setup much more than you could from the status screen alone.

If the app exports settings or lets you copy the source list, save that record too. That gives you a second place to check after a staff change, a device replacement, or a cleanup of old folders.

Completion

You are done when the app’s inclusion list matches the folders you wrote down, the exclusion rules do not block the files you care about, and a restored sample file opens outside the backup location. Your note should show the exact paths you protect, the filters that still apply, the test restore you ran, and the date you last checked it.

Conclusion

Once you’ve checked the inclusion list, the exclusions, and a real restore, you’re no longer guessing. Keep the record you made and reuse it after any change to folders, devices, or backup settings. That way, the next time someone says “the backup is on,” you’ll know exactly which files are actually in it and which ones still need to be added.

Frequently Asked Questions

How often should I recheck what’s included in backup?

Check again any time you add a new shared folder, rename a path, change devices, or edit backup rules. If nothing changes for a while, a periodic review is still worth doing so quiet exclusions do not slip in.

Is a selected folder enough, or do I still need a restore test?

You still need a restore test. A selected folder only shows what the app thinks it should protect. A restore proves the file is present, retrievable, and readable.

Why does my folder look included but some files are missing?

That usually means an exclusion, filter, size limit, file lock, or pending upload is blocking the files inside the folder. Check the rules first, then test a sample restore from the missing file type.