The support forum

Backup exits and fails on dead symlink

Lurch :

Mar 03, 2019

Not sure if this is expected behaviour or not. I have a job that backs up a folder with 2 symlinks in it. At some point I have edited/moved the target folders (they were located on a NAS and the symlinks pointed to them directly, not via a mapped drive path). Now I notice the job fails and doesn't run when it gets to those links rather than just skipping them and backing up everything else.

2019.03.03 14:46:57.348 (UTC+0) 2 0 Loaded
2019.03.03 14:46:57.348 (UTC+0) 3 1     C:\Users\User\AppData\Local\Bvckup2\engine\backup-0002\settings.ini
2019.03.03 14:46:57.478 (UTC+0) 2 0 Device status
2019.03.03 14:46:57.478 (UTC+0) 3 1     Source: local drive / present
2019.03.03 14:46:57.478 (UTC+0) 3 1     Destination: network share / checking if accessible...
2019.03.03 14:46:58.488 (UTC+0) 2 0 Destination network share is accessible
2019.03.03 14:46:58.488 (UTC+0) 2 0 Setting up the monitoring of source location...
2019.03.03 14:46:58.489 (UTC+0) 3 1     OK
2019.03.03 14:47:00.491 (UTC+0) 2 0 Running the backup ...
2019.03.03 14:47:00.491 (UTC+0) 2 1     Preparing ...
2019.03.03 14:47:00.491 (UTC+0) 3 2         Run number: 20825
2019.03.03 14:47:00.491 (UTC+0) 3 3             Version: 79.21.2
2019.03.03 14:47:00.491 (UTC+0) 3 3             Source: D:\My Documents\
2019.03.03 14:47:00.491 (UTC+0) 3 3             Destination: \\NASNAME\Backup\COMPUTERNAME\My Documents\
2019.03.03 14:47:00.491 (UTC+0) 3 3             Copying: contents, timestamps (modified, created, accessed), attributes
2019.03.03 14:47:00.491 (UTC+0) 2 2         Verifying configuration ...
2019.03.03 14:47:00.492 (UTC+0) 2 2         Checking source...
2019.03.03 14:47:00.492 (UTC+0) 3 3             Normalized path: \\?\D:\My Documents\
2019.03.03 14:47:00.493 (UTC+0) 2 2         Checking destination...
2019.03.03 14:47:00.493 (UTC+0) 3 3             Normalized path: \\?\UNC\NASNAME\Backup\COMPUTERNAME\My Documents\
2019.03.03 14:47:00.500 (UTC+0) 2 2         Checking environment...
2019.03.03 14:47:00.500 (UTC+0) 2 2         Scanning source ...
2019.03.03 14:47:00.500 (UTC+0) 3 3             Setup
2019.03.03 14:47:00.500 (UTC+0) 3 4                 Using 3 threads, depth first, basic info, large fetch
2019.03.03 14:47:00.529 (UTC+0) 3 3             Symbolic link: Work\Company1\Dropbox -> \\NASNAME\Backup\Dropbox - CO1
2019.03.03 14:47:00.529 (UTC+0) 3 4                 Type: external
2019.03.03 14:47:00.529 (UTC+0) 3 4                 Scan action: follow
2019.03.03 14:47:00.576 (UTC+0) 3 3             Symbolic link: Work\Company2\NASNAME & Dropbox -> \\NASNAME\Company2
2019.03.03 14:47:00.576 (UTC+0) 3 4                 Type: external
2019.03.03 14:47:00.576 (UTC+0) 3 4                 Scan action: follow
2019.03.03 14:47:00.642 (UTC+0) 3 3             D:\My Documents\Work\Company2\NASNAME & Dropbox
2019.03.03 14:47:00.642 (UTC+0) 0 4                 FindFirstFileEx() failed with 67
2019.03.03 14:47:00.642 (UTC+0) 3 5                     Context: \\?\D:\My Documents\Work\Company2\NASNAME & Dropbox\
2019.03.03 14:47:00.654 (UTC+0) 0 3             Error: source scan failed
2019.03.03 14:47:00.704 (UTC+0) 2 1     Completed in 214 ms with 2 errors

Alex Pankratov :

Mar 03, 2019



Good catch.

Error 67 is "The network name cannot be found.", so in non-symlink cases it _is_ an error after which it makes little sense to press forward. But in a symlink case it should be handled differently. Will patch this up in the next release.

Lurch :

Mar 04, 2019

Brilliant. Excellent service as always Alex. :)

Alex Pankratov :

Mar 05, 2019

It helps when there's a proper bug report to begin with :)

New topic

Create
Made by Pipemetrics in Switzerland
Support

Updates
Blog / RSS
Follow Twitter
Reddit
Miscellanea Press kit
Testimonials
Company Imprint

Legal Terms
Privacy