No. That's the problem. It should be my C: drive HD0. Edit: No, the other script that I have been using for ages says HD1.
I think I better stop this. It is only at 2%. It normally backs up my entire system drive very quickly.
I know what has happened. Yesterday, I upgraded my Microsoft NVMe Driver to the Samsung NVMe Driver and it switched my Disk Order around. I hate when it does that. I have just removed it and am using the Microsoft driver, and now my system drive is back on top. I have just run the script again, and it is done already. By the way. You don't know how to deal with Disk orders when they get jumbled by drivers, do you? I have never found an answer. Most people seem to just live with it.
I thought it must be a change in disk number because HD1 worked for you in the past. We all get caught with that. I didn't know the Samsung driver could change disk numbering. I use that driver and my OS drive is HD1 in one computer and HD3 in the other. I do have scripts for DS restores but they are dangerous if you get a change in disk numbers. It's better to do manual DS restores. They are so easy.
I ran the differential also. Lovely. The full is 24.6 GB, and the differential is 173 MB. This is the differential script I used without needing to change the date format. Code: @echo off CD /d %~dp0 if not defined RunTask set RunTask=1 & start "Snapshot" /min %SystemRoot%\system32\cmd.exe /c "%0" & goto :EOF set hh=%time:~0,2% if "%time:~0,1%"==" " set hh=0%hh:~1,1% set timestamp=%time:~0,8% if @%timestamp:~0,1% == @ set timestamp=0%timestamp:~1,7% set timestamp=%timestamp::=% echo.Timestamp :: %timestamp% snapshot64.exe HD1:* "D:\System_Backup\Drive_Snapshot\Entire-1\$disk-diff-%timestamp%.sna" -h"D:\System_Backup\Drive_Snapshot\Entire-1\$disk.hsh" -R -L0 --UseVSS -W
Yes, it does. It really is something that Microsoft could work on. I guess they think it's not their problem because Microsoft drivers don't cause the Disk numbering jumbles. I did a speed test with the Microsoft driver and the Samsung driver for my Samsung SSD 970 Pro 1TB NVMe, and there is not much difference in speed between the two, so I think I will just stick with the Microsoft one until one day I can figure out how to have my OS drive on top.
In Win10 my OS drive is third, in BootIt BM it is third and in Linux it is first. I accept this. In my other computer, in Win10 my OS drive is first, in BootIt BM it is fourth and in Linux it is first. Edit... In my other computer I uninstalled the Samsung driver but there was no change in the drive numbering.
The only difference to my previous full backup script is you removed: $date-$hour-$minute-$second and MOVE *.hsh Backup I can't see how the hash was created as there is no -h there.
I find fulls to be fast, now the diffs will be extremely fast. Have you tested a restoration with fulls and diffs?
A manual DS restore was performed from a WinPE. Selected "Restore complete Disk from Images" Browsed to the images. You can choose any of the full or diff images. Only one file needs to be selected. After clicking Open you see all the image files that will be restored. One for each partition. Select the disk to restore to... HD1, etc. Make sure it is the correct disk from the graphic area. Leave tick in "Restore the partition structure" Next Yes for Last warning The images are restored click OK Exit Done. So easy. You can restore to a blank disk. The blank disk shows as FREE.
I don't think I need 5 full backups now that I have differentials. So, I cut it back to 3 fulls. See how that goes. Code: IF EXIST Entire-3 (RD Entire-3 /s /q) IF EXIST Entire-2 (REN Entire-2 Entire-3) IF EXIST Entire-1 (REN Entire-1 Entire-2) REN Backup Entire-1
Differentials will only go into the Entire-1 folder. I have set schedules for both scripts and made a couple of shortcuts to the schedules for quick access. DS is getting better all the time...