Windows Backup - Unchanged files detected as deleted / backed up repeatedly #923
Description
Version: 2.4.0 (both client and server)
Client: Windows Server 2019
Server: Rocky Linux 9.2
I'm running into an issue when trying to back up a Windows Server 2019 machine. The backup is running against file space that is used for smb/cifs file sharing. burp runs on and points to the local drive/folders/files.
The issue I'm seeing is that every new run detects about 33% of the files as being deleted, but backs them up anyway. Even though only a small number of files and folders have changed, yet every backup always backs up said files over and over again. Most, if not all, of said files haven't been touched in years based on the file metadata (dates, file sizes etc), yet they are always transferred on every single backup presumably because burp thinks they were somehow deleted and then present again within a single run. I may be wrong in that description, but that's the way it looks from doing some basic testing.
At present I have a backup running -- in progress. The following shows the entries from the previous backup for a few files that seem to be part of the issue. I've changed the filenames and path in an attempt to simplify things. Also, I've added the first column which is simply the line number for a given row in the manifest.
manifest.gz
...
3192374 r0038A A IH/ B A A A X8AAA A A Bhk6uP BdWxK/ BdcuWG A g J A A
3192375 f0087D:/Path/To/File/File1.txt
3192376 x002A401604872:92ea966535eb9466ed84ad17cd919fa2
3192377 t0089t/D:/Path/To/File/File2.txt
3192378 r0038A A IH/ B A A A X8AAA A A Bhk6uS BdWxnH BdcuXj A g J A A
3192379 f0087D:/Path/To/File/File2.txt
3192380 x002A401604872:2767b1ce8192f31169c7f45b6d5b2659
3192381 t0089t/D:/Path/To/File/File3.txt
3192382 r0038A A IH/ B A A A X8AAA A A Bhk6uS BdWyDP BdcuYf A g J A A
...
12695838 r0038A A IH/ B A A A X8AAA A A Bhk6uP BdWxK/ BdcuWG A g J A A
12695839 f0087D:/Path/To/File/File1.txt
12695840 x002A401604872:92ea966535eb9466ed84ad17cd919fa2
12695841 t0089t/D:/Path/To/File/File2.txt
12695842 r0038A A IH/ B A A A X8AAA A A Bhk6uS BdWxnH BdcuXj A g J A A
12695843 f0087D:/Path/To/File/File2.txt
12695844 x002A401604872:2767b1ce8192f31169c7f45b6d5b2659
12695845 t0089t/D:/Path/To/File/File3.txt
12695846 r0038A A IH/ B A A A X8AAA A A Bhk6uS BdWyDP BdcuYf A g J A A
...
Also, the following shows the live counters portion of a current run. It demonstrates the approximately 1.7 million fles detected as having been deleted.
burp monitor 2.4.0 2023-08-29 11:05:22 -0600
Client: serv1
Status: running
Backup: 0000010 2023-08-28 12:11:40 -0600
Browse: Live counters
PID: 3078082 (backup)
Start time: 2023-08-28 12:11:40 -0600
End time: 2023-08-29 11:05:22 -0600
Time taken: 22:53:42
New Changed Unchanged Deleted Total Scanned
Files 619606 319 2872658 1722913 3492583 5098315
EFS files 23 0 21 1 44 57
Grand total 619629 319 2872679 1722914 3492627 5098372
Percentage complete: 68%
Warnings: 4123
Bytes estimated: 5840169920187 (5.31 TB)
Bytes: 4164446933223 (3.79 TB)
And finally a grep of the working directory for "File2.txt" from above above...
counters_n:uf0087D:/Path/To/File/File2.txt
counters_n:df0087D:/Path/To/File/File2.txt
unchanged:t0089t/D:/Path/To/File/File2.txt
unchanged:f0087D:/Path/To/File/File2.txt
Any thoughts or recommendations would be greatly appreciated. Thanks!