Incremental Backup Script for Windows
Automate Backups with Windows Scripts
An incremental backup script can be a simple way to copy new and changed files without transferring the entire data set every time. On Windows, this is often done with Robocopy, PowerShell, and Task Scheduler.
For a small backup job, a script may be all you need. For example, you can automatically copy a working folder to another drive or NAS every evening and transfer only files that have changed since the previous run.
However, there is an important difference between copying changed files and maintaining a real incremental backup chain with multiple recovery points. This guide explains both approaches and shows where a simple script works well and where dedicated backup software becomes more practical.
What Is an Incremental Backup Script?
In everyday use, an incremental backup script is usually a script that detects new or modified files and copies only those files to another location. This reduces the amount of data transferred after the first backup.
Suppose a folder contains 100 GB of data. After the first copy, only 500 MB changes. Instead of copying all 100 GB again, a script can transfer only the files that were added or modified.
This approach works particularly well for documents, project folders, photos, website files, and other data stored as regular files.
It should not automatically be confused with a traditional full-and-incremental backup scheme. A file-copy script may update the destination so that it reflects the latest state of the source, while a backup application can preserve separate recovery points and maintain a controlled chain of full and incremental backups.
Simple Incremental Backup Script with Robocopy
Robocopy is included with modern versions of Windows and is one of the easiest ways to create a basic incremental-style file copy.
@echo off
robocopy "C:\Data" "D:\Backup\Data" /E /XO /R:3 /W:5 /LOG:"C:\BackupLogs\backup.log"
Save the commands in a file such as daily-backup.bat and run it whenever you want to update the backup copy.
The script copies data from C:\Data to D:\Backup\Data.
What the options mean: /E includes subfolders, /XO excludes source files older than their destination copies, /R:3 limits retry attempts to three, /W:5 waits five seconds between retries, and /LOG creates a log of the operation.
After the initial copy, subsequent runs generally transfer only files that need to be updated. This makes Robocopy useful for relatively simple recurring backup jobs.
Automate the Script with Windows Task Scheduler
A backup script becomes much more useful when it does not depend on someone remembering to run it.
Windows Task Scheduler can launch the batch file automatically at a selected time. You can create a task, specify when it should run, and use the batch file as the program or script to start.
For example, a workstation folder can be copied to an external drive every evening, or a server directory can be copied to a network location overnight.
Task Scheduler also allows the task to run under a selected Windows account and can start the job without requiring someone to launch it manually.
Incremental Backup with PowerShell
PowerShell is useful when you need more control around the backup process.
It can create folders, generate dated log files, check whether a destination is available, launch Robocopy, and process its return code.
$source = "C:\Data"
$destination = "D:\Backup\Data"
$logFolder = "C:\BackupLogs"
if (!(Test-Path $logFolder)) {
New-Item -ItemType Directory -Path $logFolder | Out-Null
}
$logFile = Join-Path $logFolder ("backup-" + (Get-Date -Format "yyyy-MM-dd") + ".log")
robocopy $source $destination /E /XO /R:3 /W:5 /LOG:$logFile
$robocopyResult = $LASTEXITCODE
if ($robocopyResult -ge 8) {
Write-Host "Backup completed with errors. Check $logFile"
} else {
Write-Host "Backup completed. Log: $logFile"
}
This version still uses Robocopy to transfer the files, but PowerShell handles the surrounding logic and creates a separate log for each day.
More advanced scripts can add notifications, destination checks, archive folders, retention logic, or other actions. At that point, however, the script itself begins to become a small backup system that must also be maintained and tested.
Is Robocopy Really an Incremental Backup?
Robocopy can perform incremental-style copying because it does not have to transfer every file during every run. Only files that meet the copy conditions need to be transferred.
Incremental File Copy
Imagine that a document is changed on Monday, Tuesday, and Wednesday. A simple copy job may leave only the latest Wednesday version at the destination.
If you later need Monday's version, it may no longer exist.
Incremental Backup Chain
A full backup establishes a starting point, and subsequent incremental backups contain changes made after the previous backup.
The backup system can then use the required parts of the chain to restore data from a selected recovery point.
The key difference: copying only changed files does not automatically mean that you are maintaining historical recovery points.
Where Incremental Backup Scripts Become Complicated
A script is attractive because it starts simple. A few commands may be enough to copy one folder from one disk to another.
Backup Versions
Keeping historical recovery points requires additional logic for file versions, dates, retention, and cleanup.
More Destinations
Cloud storage, FTP, SFTP, encryption, and compression often require more commands, scripts, or third-party utilities.
Reliable Recovery
You also need to decide how failed jobs are detected and how older copies are found and restored when they are needed.
When a Script Becomes a Backup System
This is where incremental backup software becomes a practical alternative to building and maintaining your own scripts.
Handy Backup provides incremental backup as part of a complete backup workflow, with scheduling, storage management, backup versions, encryption, and restore tools available from the same application.
Learn more about windows incremental backup software - Handy Backup
Incremental Backup with Handy Backup
Handy Backup can create scheduled full, incremental, and differential backups without requiring users to write batch files or PowerShell scripts.
You select the data to protect, choose a destination, configure the schedule and backup type, and let the task run automatically.
Incremental backups can be combined with periodic full backups. For example, a task can create a full backup once a week and incremental backups on the remaining days.
This provides multiple recovery points while reducing the amount of data copied during routine backup runs.
Handy Backup can work with local and external drives, network storage, FTP and SFTP servers, supported cloud services, and other destinations. It also supports AES-256 and AES-128 encryption and can keep multiple backup versions.
Incremental Backup Script vs Backup Software
A script works well for straightforward file-copy tasks. Backup software adds the management functions needed when the backup process becomes more complex.
| Capability | Robocopy / PowerShell | Handy Backup |
|---|---|---|
| Copy new and changed files | Yes | Yes |
| Automatic scheduling | Task Scheduler | Built in |
| Full and incremental backup chains | Custom logic | Yes |
| Multiple backup versions | Requires scripting | Yes |
| Encryption | Additional tools or code | AES-256 / AES-128 |
| Cloud, FTP and SFTP backup | Additional tools | Supported |
| Database backup | Database-specific scripts | Supported |
| Restore workflow | Mostly manual | Built in |
When Is a Backup Script Enough?
Use a Script for Simple Jobs
A Robocopy or PowerShell script is often perfectly adequate when you only need to keep an additional copy of one or two folders on another disk or network location.
It is also useful for administrators who deliberately want complete control over the process and are comfortable maintaining their own scripts.
Use Backup Software for Managed Backups
Dedicated backup software becomes more useful when you need multiple recovery points, scheduled full and incremental cycles, encryption, different storage destinations, database protection, notifications, and predictable restores.
The right choice depends less on whether scripting is possible and more on how much backup logic you want to build and maintain yourself.
Start with the Backup Method That Fits the Job
For a straightforward second copy of changing files, Robocopy and PowerShell provide useful tools that are already available in Windows. They are easy to experiment with and can automate many small backup jobs.
For data that requires version history, structured incremental backup chains, encryption, different storage destinations, and repeatable recovery, dedicated software removes much of the scripting and maintenance work.
Handy Backup allows both simple and advanced backup tasks to be configured through a graphical interface, making it possible to automate backups without building your own backup scripts.
See also: Incremental vs Differential Backup
FAQ
Is Robocopy an incremental backup tool?
Robocopy can copy only new or changed files, so it is often used for incremental-style file copying. However, it does not automatically create a traditional full-and-incremental backup chain with separate recovery points. If files at the destination are simply updated, older versions may not be available for recovery.
Can Windows Task Scheduler run an incremental backup?
Yes. Windows Task Scheduler can automatically launch a Robocopy batch file or PowerShell script on a daily, weekly, or other schedule. Task Scheduler starts the job, while the script controls which files are copied and how the operation is handled.
What is the difference between incremental backup and copying changed files?
Copying changed files usually updates a second copy of the current data. Incremental backup normally refers to a backup scheme in which a full backup is followed by incremental backups containing changes since the previous backup. This can preserve multiple recovery points instead of only the latest copy.
Can PowerShell create incremental backups?
Yes. PowerShell can compare files, launch Robocopy, create logs, check destinations, and automate other parts of a backup job. More advanced functions such as version retention, encryption, backup chains, and recovery management require additional scripting or external tools.
When should I use incremental backup software instead of a script?
A script is usually enough for simple file-copy jobs. Incremental backup software is more convenient when you need multiple recovery points, automated full and incremental cycles, encryption, cloud or network destinations, database protection, retention rules, monitoring, and a structured restore process.