Correct. Restoring a system needs to be done outside the system. But imaging one can always be done "hot."
No, you can run backups when Windows is running. As explained in this AI summary from Google.The only true backup is when complete filesystem is in static (not modifiable) state.
Windows image backups rely on the Volume Shadow Copy Service (VSS) to create a consistent snapshot of your system while files are in use. When running a backup, the VSS service takes a "snapshot" of the volumes being backed up, allowing the backup to proceed without interruption and capturing files in a consistent state.
How Volume Shadow Copy works during backups
- Creates a snapshot: The VSS service creates a point-in-time, read-only copy of the data on a volume.
- Backup targets the snapshot: The Windows backup process then creates the system image from this shadow copy, not the live, active files.
- Enables "hot" backups: This process allows for system image backups to be performed while the computer is running and programs are in use, without affecting the running system.
Suppose the Windows build-in System Image Backup process is running and backing up the active Windows partition or disk (assume only one partition and disk). While the backup is running (being created and being written to external storage) you are meanwhile working on a Word doc and save the changes you made to disk.
Question is what Word doc is being written to the backup, the old version prior to last save or the just saved one?
Now instead of changing a Word doc yourself suppose Windows itself modifies data or system files on the disk, what will be on created backup the old or new data / files?
I'm just wondering.
I personally don't keep docs or any such files on C:\ which I image, so in my case the situation will never arise as all files are on a separate drive, added to which I never rely on a single image, imaging C:\ frequently & testing at least one image every week or so by restoring the image means I know its a perfect image (IF that should fail I know I have ones that haven't) - It probably does make sense before doing a critical image to reboot windows & run hasleo/macrium/whatever straight after booting, but as I can't remember the last time an image failed that's really just a precaution, which I don't always do as in real life as there is no need - What can happen in theory does not mean it will actually happen.
The term safer was used in an earlier comment, safer is a relative term, for me & IMO frequent backups which take 25 seconds for a full image (while making coffee) are safer than doing difficult to do imaging that is done rarely??
Edit: For what its's worth 'system restore' is something I haven't used for years & is disabled, so for me that does not come into the imaging situation either.
Does that mean that Windows has to make shadow copies of really everything first before the actual backup starts?All that is on the Pc the moment the backup starts.
Does that mean that Windows has to make shadow copies of really everything first before the actual backup starts?
Where does Windows keep all the shadow copies of all files when the disk is nearly full?
Creating a full system Snapshot takes storage space somewhere, not?As mentioned in an earlier post, it takes a snapshot of the system and creates an image based on that.
Creating a full system Snapshot takes storage space somewhere, not?
Correct. It's been that way for ages now.I admit how it works : Volume Shadow Copy Service (VSS)
After VSS has created a snapshot applications are free to resume writing data to the disk...
After VSS has created a drive mirror the original volume continues to accept write I/O requests...
Hasleo Backup Suite V5.5.2.1 Released!
What's new in this version:
1. Removed the expiration time limit
2. Fixed an issue with mounting file backup images
3. Fixed the issue where system backup did not automatically select partitions in WinPE
4. Updated Dutch and Ukrainian translations
5. Fixed other minor bugs
Here are the download links:
X86/X64
ARM64