How to Back Up Windows 11 to a NAS or Network Drive

A NAS is one of the most convenient places to keep Windows backups. It sits on your network, can protect several PCs, usually offers far more capacity than a USB stick, and does not have to be plugged into the computer every time a scheduled job runs.

But if you want to back up Windows 11 to a NAS or network drive, the network changes the failure model. A USB disk either appears or it does not. A NAS can be powered on yet unreachable because of credentials, SMB security, a changed hostname, Wi-Fi trouble, a full quota, a sleeping device or permissions that work in File Explorer but not for an unattended backup job.

The best setup therefore has two parts: make the network destination dependable, then use a backup method that keeps useful history instead of merely copying today's state.

The short answer

Windows 11 can back up personal files to a NAS or other network location with File History. Configure a network share on the NAS, make sure Windows can access it with an authenticated account, then open Control Panel > System and Security > File History. If the network destination is not already selected, choose Select drive and pick the network location.

For more control over source folders, schedules and backup types, you can create a dedicated file-backup job. Perfect Backup supports Network Folder destinations, so a Files and Folders Backup job can protect local Windows data to an accessible NAS share using Full, Incremental, Differential or Mirror methods.

For most PCs, versioned backup is safer than Mirror as the only NAS copy. A mirror is excellent when you want the destination to resemble the current source, but a deletion or unwanted change can also be reflected there. Full, Incremental and Differential workflows are better suited to preserving restore points from different dates.

1. Understand what a NAS changes about backup

An external hard drive is physically attached to one computer. A NAS is a small storage server. Windows reaches it over the network, usually through SMB file sharing, and that difference is why a NAS can be both more convenient and more complicated.

The convenience is obvious. The NAS can remain in a closet or office, several computers can back up to separate folders, and scheduled jobs can run without somebody remembering to connect a cable. A desktop PC can back up overnight while a laptop catches up whenever it returns to the home network.

The less obvious part is that there are now several components between the source file and the backup:

• The Windows PC must be awake long enough for the job to run.
• The network must be available and stable.
• Name resolution must still point Windows to the correct NAS.
• SMB access must be compatible with current Windows security requirements.
• Credentials and permissions must allow the backup process—not just you interactively—to write to the share.
• The NAS volume must have enough free space and no quota blocking the backup account.
• The backup history must remain readable when you actually need a restore.

This is not a reason to avoid NAS backup. It is a reason to monitor it. A network destination can fail quietly for weeks while the PC itself continues to work normally.

A NAS is a destination, not automatically a backup strategy

Putting a second copy on another device is useful, but the recovery quality depends on how that copy is created. A manual drag-and-drop copy gives you one point in time. A synchronization job keeps a current replica. A versioned backup preserves earlier states. A NAS snapshot can protect the NAS volume itself from some later changes.

Those are different tools. The strongest setup combines them deliberately instead of assuming that the word “NAS” guarantees history, ransomware resistance or off-site protection.

2. Prepare the NAS share before configuring Windows

Do the storage work first. If Windows cannot reliably create, rename, read and delete a harmless test file in the destination, a backup application will not magically make the share reliable.

Create a dedicated backup share

On the NAS, create a folder or share specifically for Windows backups—for example PC-Backups. Keeping backups separate from family media, shared documents and application storage makes permissions, quotas and cleanup much easier to reason about.

If several computers will use the same NAS, give each PC its own subfolder. A simple layout might be:

\\NAS-NAME\PC-Backups\DESKTOP-OFFICE
\\NAS-NAME\PC-Backups\LAPTOP-ALEX
\\NAS-NAME\PC-Backups\FAMILY-PC

You do not need those exact names. The point is to avoid one undifferentiated folder where multiple backup jobs can overwrite or confuse one another.

Use an authenticated backup account

Create a NAS user for backups instead of relying on anonymous or guest access. Give that account the rights it needs on the backup share and avoid broader administrative permissions.

This matters more on modern Windows 11 than it did on many older home networks. Windows 11 24H2 and later hardened SMB defaults, including SMB signing requirements. Guest-only shares and older NAS firmware can therefore fail even though they worked on an older Windows installation.

Plan capacity for versions, not just source size

If the PC has 600 GB of important data, a 600 GB quota leaves no room for change history. Documents, photo catalogs, databases and project files can create substantial version growth even when the live data set stays roughly the same size.

Allow room for the initial backup, multiple restore points and future growth. If the NAS supports per-user or per-share quotas, verify the effective quota for the backup account rather than looking only at total free space on the RAID volume.

3. Connect Windows 11 to the network location

Before configuring File History or any backup software, prove that Windows 11 can reach the share consistently.

Test the UNC path first

In File Explorer, enter the network path in the address bar, for example:

\\NAS-NAME\PC-Backups

Sign in with the NAS account when prompted. Create a small text file, rename it, open it and delete it. That simple test checks more than merely seeing the NAS in the Network pane.

Use the NAS hostname where practical instead of depending on a raw IP address. It is easier to keep stable across DHCP changes, and Microsoft recommends name-based connections for modern SMB security scenarios.

Map a drive letter when it makes daily use easier

Windows 11 can map a network share to a drive letter:

1. Open File Explorer and select This PC.
2. Open the More menu and choose Map network drive.
3. Choose an available drive letter.
4. Enter the share path, such as \\NAS-NAME\PC-Backups.
5. Enable Reconnect at sign-in if you want Windows to remap it for your account.
6. Finish the connection and confirm you can write to it.

A mapped drive is convenient, but it is not inherently more reliable than the UNC path. Later in this guide we will look at why scheduled jobs sometimes see \\NAS-NAME\Share but not Z:.

Make sure you are on the network you think you are

A laptop may have access to the NAS at home but not from a coffee-shop Wi-Fi or a guest VLAN. If the NAS is only intended for the local LAN, that is good separation. Just remember that a scheduled backup cannot reach a destination that the computer is physically or logically disconnected from.

4. Use File History with a NAS or network share

File History remains the simplest built-in Windows option when your goal is versioned protection for personal files rather than a complete system image.

Microsoft currently documents both external drives and network locations as valid File History destinations. To configure it:

1. Make sure the NAS share is reachable from Windows.
2. Open Control Panel.
3. Choose System and Security and then File History.
4. If needed, select Select drive.
5. Choose the network location you prepared.
6. Select Turn on.
7. Run the initial backup and wait for it to complete.

Do not stop after the green status message. Open the destination from another Explorer window and make sure backup data is being created where you expected. Then restore one harmless file through File History to prove the recovery path.

What happens when the network disappears?

File History cannot write to a network target that is offline. Microsoft documents a reconnect workflow for both disconnected external drives and unavailable network locations. Once the NAS or network returns, File History can continue, and you can use Run now if you want to catch up immediately.

The important operational lesson is simple: an automatic feature can be configured correctly and still have stale backups because the laptop spent two weeks away from the network. Check the date of the newest successful backup, not just whether File History is technically enabled.

Check what File History is actually protecting

File History is a file-versioning tool, not a whole-PC image. It is designed around personal files and libraries. That makes it excellent for recovering yesterday's document or a deleted photo folder, but it does not recreate Windows, installed applications, boot partitions and every system setting after a dead system disk.

Microsoft's current guidance emphasizes libraries. If an important folder lives outside the normal protected set, include it in a library or use a backup tool that lets you select arbitrary source folders directly.

Do a source inventory instead of assuming “my user profile” means everything

Commonly missed data includes:

• project folders stored directly under another drive such as D:\Projects;
• virtual machine files;
• local application databases;
• email archives such as PST files stored outside Documents;
• development repositories and build artifacts in custom paths;
• large media libraries deliberately kept outside the default user folders.

If those files matter, either add them to the appropriate File History coverage or protect them with a dedicated backup job.

Keep system recovery separate

If you want to recover an entire Windows installation after an SSD failure, keep a separate drive-image strategy. Our Windows 11 system image guide explains that recovery layer. NAS file backup and system imaging solve different problems and work well together.

5. Automate NAS backups with Perfect Backup

File History is useful when its folder model matches your data. A dedicated backup job is more flexible when you want to select specific folders across several drives, choose the backup method, control retention, or keep multiple jobs with different schedules.

Perfect Backup supports Network Folder destinations. A practical Windows 11 NAS job looks like this:

1. Open Perfect Backup and create a Files and Folders Backup job.
2. Select the local folders you actually need to recover.
3. Choose the NAS or network folder as the destination.
4. Select Full, Incremental, Differential or Mirror according to the recovery history you want.
5. Set a schedule that matches how much work you can afford to lose.
6. Run the first backup while the PC is awake and preferably on a stable wired connection.
7. Review the log and perform a small restore from the NAS.

The first run is the important one. It proves not only that the share is writable, but that the backup format, path length, permissions and available space work with your actual data set.

Do not make the NAS job your only job

A NAS is excellent for frequent local backups because it is always nearby and usually fast. For irreplaceable files, duplicate the protection to another failure domain as well: a removable drive that is normally disconnected, an off-site repository, FTP storage or a separate cloud backup destination.

That is the practical reason the 3-2-1 backup rule still matters. A PC and a NAS in the same room are two copies, but they can still share fire, theft, power and ransomware risks.

6. Choose mapped drives, UNC paths and credentials carefully

Many network-backup problems are not really backup problems. They are Windows session and authentication problems.

Mapped drive letters are user-session conveniences

A drive such as Z: is normally created in the context of a signed-in Windows account. Another user, an elevated process, a service or a scheduled background task may not see the same mapping.

That is why an unattended job can report “destination not found” even while you can open Z: in File Explorer. If the backup application supports a UNC network folder directly, a path such as \\NAS-NAME\PC-Backups is often easier to reason about than relying on a drive letter created at sign-in.

This is not a universal rule that UNC is always better. It is a troubleshooting rule: know which identity owns the mapping and which identity runs the backup.

Credentials should survive a reboot without becoming overpowered

Test the final configuration after restarting Windows. Do not assume a share is ready for automation because it worked once immediately after you entered a password interactively.

Use a dedicated NAS account with permission to the backup destination and no unnecessary administrative rights. If credentials change, update the backup connection promptly and run a test job. Password rotation is good security; an unnoticed stale backup credential is bad recovery.

Avoid guest access as a compatibility shortcut

Windows 11's newer SMB hardening deliberately makes unauthenticated guest access harder. If an older NAS only works when Windows security is weakened, treat that as a NAS configuration or lifecycle problem. Enable current SMB support, authenticate properly, and update or replace devices that cannot meet current security requirements.

7. Choose backup type, retention and NAS snapshots

A NAS gives you capacity, but capacity is not the same thing as useful history. Decide what you want to recover after a bad edit, a deletion discovered three weeks later, or ransomware that modifies thousands of files.

For a primary backup history, Full plus Incremental or Differential is usually more forgiving than a mirror alone. Mirror can still be valuable for a working replica, but give it another layer of history if recovery from older states matters.

NAS snapshots are a useful second layer

Many NAS platforms can snapshot a volume or shared folder. A snapshot can make recovery from accidental deletion or ransomware much faster because the NAS preserves an earlier filesystem state without copying the entire data set again.

Use snapshots as additional retention, not as the only backup. A snapshot usually lives on the same NAS and depends on the same device, storage pool and administrative plane. It does not protect against the NAS being stolen, destroyed or catastrophically failing.

RAID is availability, not history

RAID can keep the NAS available after certain disk failures. It faithfully preserves bad changes too. Delete a folder, encrypt it with ransomware or overwrite it with corrupted data, and RAID does not produce yesterday's version. Backup history and snapshots solve that problem; RAID solves a different one.

8. Plan for network speed and unattended reliability

The initial NAS backup is often much larger than daily changes. A 1 TB first backup over mediocre Wi-Fi can take many hours, and sleeping the laptop halfway through may leave you with an incomplete job.

Use wired Ethernet for the first large backup when practical

Gigabit Ethernet is predictable, low-latency and does not compete with every phone and streaming device for radio airtime. Wi-Fi is perfectly workable for incremental daily backups, especially when only a few gigabytes change, but the first seed is where a cable can save a great deal of time.

If the NAS and PC support faster networking, the disks and backup format may become the bottleneck instead. Do not judge a backup only by headline network speed.

Schedule around sleep and roaming

A desktop that stays on overnight is easy. A laptop is not. Pick a time when the PC is usually awake and on the same network as the NAS. If the software can run a missed job later, still check logs periodically instead of assuming every missed schedule repaired itself.

Watch three “full” conditions

• The NAS volume can run out of physical capacity.
• The backup account quota can fill while the NAS still has terabytes free.
• The retention policy can keep too much history and crowd out newer restore points.

A good cleanup policy removes old backup sets deliberately. Randomly deleting files inside a backup repository from File Explorer can break chains or leave the software's catalog inconsistent.

Read logs after network changes

Router replacements, NAS firmware upgrades, password changes, hostname changes and VLAN redesigns are all reasons to inspect the next backup. The source data can be perfectly healthy while the destination has silently moved out from under the job.

9. Protect the NAS backup from ransomware and account compromise

The biggest weakness of an always-available NAS is the same feature that makes it convenient: Windows can reach it all the time.

If ransomware runs under an account that can browse and rewrite the backup share, the NAS may be another reachable target. If the backup repository is a plain mirror, encrypted source files can be copied over the clean destination. If the attacker obtains NAS administrator credentials, even snapshots may be at risk depending on how the appliance protects them.

Reduce what the Windows account can do

• Use a dedicated backup share rather than an all-purpose writable folder.
• Use a dedicated backup account with only the permissions the job requires.
• Avoid using the NAS administrator account for routine backups.
• Keep NAS firmware current and disable obsolete SMB versions when the vendor supports modern alternatives.
• Use protected snapshots or retention features where available.
• Keep another copy that is not continuously writable from the same Windows environment.

Our ransomware backup protection guide goes deeper into offline copies, credentials, immutability and clean recovery.

Do not expose an ordinary SMB share directly to the internet

A home NAS should not become “remote backup” simply by forwarding SMB ports through the router. Remote access needs a secure architecture—typically vendor-supported secure access, VPN, or another protocol designed for the job—not raw public SMB exposure.

10. Test restores before the PC or NAS fails

A backup is not complete when the job says “Finished.” It is complete when you can recover useful data from it.

Run several small recovery tests while the system is healthy:

1. Single-file restore: recover yesterday's version of a document to a temporary folder.
2. Deleted-folder restore: copy a test folder, back it up, delete the source, then recover it.
3. New-location restore: restore to a different folder or drive so you know the backup is not tied to one original path.
4. Credential test: reboot the PC and confirm the backup software still reaches the NAS without manual Explorer intervention.
5. NAS outage test: deliberately make the destination unavailable for one scheduled window, reconnect it, and verify you understand how the job recovers.

For important data, go one step further: document the NAS hostname, share name, backup account recovery process and where a second copy lives. During a real failure, you do not want the only record of the backup path stored on the dead PC.

Common mistakes when backing up Windows 11 to a NAS

• Treating RAID as the backup. RAID keeps storage online; it does not preserve good older versions.
• Using a Mirror job as the only history. A mirror can reproduce deletion and corruption.
• Depending on guest SMB access. Modern Windows security intentionally blocks or restricts insecure patterns that older NAS devices used.
• Assuming a mapped drive exists for every process. The drive letter you see in Explorer may not exist for an unattended job.
• Ignoring quotas. A user quota can fill while the NAS dashboard still reports plenty of free space.
• Running the first multi-hundred-gigabyte backup over unstable Wi-Fi. Seed the job on a stable connection when practical.
• Never reading the logs. A NAS can be offline for weeks while the backup software continues to launch on schedule.
• Leaving the NAS as the only backup. Theft, fire, ransomware and administrator compromise can still affect PC and NAS together.

11. Frequently asked questions

Use the NAS for convenience, then design for independence

A NAS is arguably the best local destination for a Windows PC that needs frequent automatic backups. It is always nearby, can hold long version history, and can serve several computers without a pile of USB drives.

Its convenience should not hide the remaining risks. Authenticate properly, use current SMB security, prefer versioned backups when history matters, monitor failed jobs, protect the NAS with snapshots where useful, and keep another recovery copy outside the same writable network path.

If you do those things, “backup to NAS” becomes more than a destination setting. It becomes a recovery system you can actually trust.

← Back to the Learning Center