New Drive Snapshot build released.

I am using the latest version of Drive Snapshot with a Windows 10 64 bit.

During my last restoration, when Windows restarted, I have the right to a window which indicates that an analysis and repair is in progress.

I also tried to restore via WinPE ... to see if the result was the same. And indeed, same observation, on a freshly installed Windows.

Does the latest version have a problem? Or is it normal that this offers an analysis and repair at boot after a restoration?

Thank you

 

Another question: do you have a recent WinPE to easily restore with Drive Snapshot, if Windows does not start anymore?

I like this software for its minimalist side. It is the opposite of Acronis, which has become the Nero of backups.

 

I haven't updated DS for a while and with the version I'm using (Dec. 2019) I won't see that unless DS is given a test instruction (via DOS command) or it finds a file inconsistency. I suspect that DS found it necessary to examine the image file you're attempting to restore for readability and consistency.

 

I'm confused; judging from your prior post it seems you already have/used a WinPE boot disk to perform a restore?

 

Yes In the second attempt

 

If you create a backup while the system is active, the disk will most likely, but not always be flagged as dirty after restoring . If you backup the system while it is offline, then you should not have this problem. When you restore your backup, you can check the status before booting with the following command from another windows system:

Code:

fsutil dirty query <drive letter:>

If found dirty, you can do a chkdsk /f and that will clear the dirty flag. Chkdsk never found any errors when the disk was flagged dirty. That has been my experience.

 

Adric,

Do you get any warnings from Windows that the file system is dirty? Or just when you run
fsutil dirty query <drive letter:>

 

I get warnings if I don't clear the flag beforehand, but I don't recall exactly if dirty is mentioned in the warning. I mostly do offline backups from another system unless I want to try something on the active system. Then I do a live backup to have the current state in case I need to go back.

 

Fwiw I do hot DS backups (always using VSS) and have never seen any 'dirty message'.

 

Same here.

 

Hello.

I made a first backup with a WinPE containing Drive Snapshot version 1.46, WinPE which TheRollbackFrog had sympathetically helped me to create, because I do not have especially enough competence for that. It is a WinPE which automatically launches Drive Snapshot when WinPE starts.

And a second backup made under Windows, with the latest version of Drive Snapshot.

During restoration attempts (via Drive Snapshot on the next restart, or via WinPE), always this analysis / repair is indicated, while no problem is detected.

 

I don't always get get this. I guess it depends what VSS does during the backup. Never found out what was causing this though.

 

@zorro51,
If you would like to pursue this... Are you selecting to restore a single partition or the complete disk (multiple partitions)? What is the exact wording of that analysis/repair notice? Do you see it as soon as DS restarts into its DOS environment (if not, at what point does it appear)? ...finally, on what storage device are your .sna (image) files located?

 

I only restore the Windows partition since the other partitions are intact.

I just wanted to test the restoration, after installing Windows clean.

Otherwise it tells me that an analysis is underway, and a repair, just before Windows starts.

The image files are on an external hard drive, the integrity of which is ok.

 

Can you be more specific on this? What is the exact wording DS presents? When you say "just before Windows starts" does that mean you don't receive the notice until after the restore is complete and Windows is about to restart?

 

New version available (Digital Signature: April 21, 2020)
Drive Snapshot (x86) 1.48.0.18774 - (458.200 bytes)
Drive Snapshot (x64) 1.48.0.18775 - (461.784 bytes)
Website

 

@mood,
Appreciate your update notifications. Fwiw to DS users, the file-size of this month's x64 update has changed - likely indicating functional changes!

 

New version available (Digital Signature: April 29, 2020)
Drive Snapshot (x86) 1.48.0.18784 - (458.200 bytes)
Drive Snapshot (x64) 1.48.0.18785 - (461.784 bytes)
Website

 

'New build' released: May 5, 2020 (3rd release in past 2 weeks! - what is going on?)
Drive Snapshot (x86) 1.48.0.18789 (458,200 bytes)
Drive Snapshot (x64) 1.48.0.18790 (461,784 bytes)

Home Page: http://www.drivesnapshot.de/en/index.htm
Download Page: http://www.drivesnapshot.de/en/down.htm

 

New version available (Digital Signature: May 18, 2020)
Drive Snapshot (x86) 1.48.0.18798 - (458.200 bytes)
Drive Snapshot (x64) 1.48.0.18799 - (459.280 bytes)
Website

 

I'm still using an old October 2016 version and there is absolutely no reason whatsoever to update as it just works on every single computer that I've used it on.

This is exactly what software should be like instead of playing the update game.

 

As long as the file system (NTFS, EXT4, etc) and partition protocols are not changed, I see no need to update a disk imaging software, unless there is new features introduced in the new versions.

 

Well that's what I thought too. In times past there were instances where an upgrade introduced issues not there previously before. (Not that there is likely an expectation of it).

Results from various other softs proved the same although not many. Some settle in (like DS) and also in my case (SD) and as such since they work at 100% efficiency without error it's not on the agenda in this camp to risk upsetting a balanced well rounded (flawless for years on end) program that already is metal tested and at top performance.

 

What's SD?

 

Hi @Hadron

Shadow Defender (SD) and Drive Snapshot (DS) along with Sandboxie have been 100% error-free without so much as a minor hiccup ever since 98SE then XP

Frankly, color me completely amazed at those apps durability and their long extended time tested performances w/o so much as a single fail on my units over the years