Incremental backups capture only the changes made since the last backup, using the archive bit to identify modified files and minimizing the time and storage required between full backups. Restoring from incremental backups requires applying the full backup first, followed by each incremental backup in sequence up to the desired recovery point.
Incremental Backups
The problem with a full backup is that it could take a long time, possibly even days, to do a backup, so it might not be efficient to do that. Same thing with a differential: if a lot of changes are happening between the times that we're taking that differential backup, that can be problematic.
An incremental backup solves that problem, because what it does is it does little backups all throughout maybe the day, or whenever you run it. What it's doing is it's just backing up the changes since the last backup.
So what we do at the beginning of the day is maybe we capture a full backup, and then every hour we're going to be doing an incremental backup. So at 9:00 a.m. we're backing up file one, because that's what's changed. At 10:00 a.m. it's file two and three. At 1:00 p.m. it's files four and five. At 2 p.m. it's file six.
So how does it know what files have changed? Well, it's that archive bit. That archive bit gets checked and then it backs those up. Now what will happen is, after it's done, it will uncheck those boxes. So they get unchecked and they don't get backed up the next archive bit. Instead, if another file changes then it gets backed up on that next archive, or that next incremental, and then that gets erased there. So only the files since the last backup get changed when you're doing incremental backups.
It's pretty great, because we do a full backup maybe overnight and then all those archive bits get unchecked, and then at 9:00 a.m. it sees that there's a file with a checked archive bit and it backs that up and then removes the archive bit. And then at 10:00 a.m. it sees that there's two more files that have the archive bit checked, so it backs those up and then unchecks that. And then at 1 p.m. it sees that there's two more files with the archive bit checked.
Incremental backups on things like databases function a little differently than what we've been talking about, so we're not going to get too in depth into that. But just know that what it's doing there again is it's backing up some of the transaction logs on the server.
When restoring incremental backups, we're going to have to, first of all, restore the first full, so we get all the files in there. Then we restore all the changes that have happened since then. So we see that there's a change at 9:00 a.m., so we have to restore that. Same thing at 10:00 a.m., we have to restore those. And then at 1:00 p.m. we have to restore those. And at 2 p.m. we have to restore that. So we have to restore all of the files, all of the incremental backups, up to the point in time where we want to do that restore.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →