Errorcode: BASE_DIR_LOST (7) -> can't seem to figure out how to fix it

client
#1

debug.log.1.txt.zip (40.1 KB) GM fellow urbackers!
so I am getting this infamous error on a few clients…: :cry:

Errorcode: BASE_DIR_LOST (7)

I have been looking through the docs and forums article about it but I can’t seem to get rid of the problem…
so far, I have tried the following using a tiny empty workstation client (windows 10) as a sample.

from the doc:

  1. confirmed the drive has plenty of spare disk space

  2. confirmed that nothing is going on at the time of the backup on the client

  3. tried to increase the shadow storage

from the forums:

  1. deleted all existing shadow copies that I could find…

  2. tried to switch from default settings to client specific listing individual drives instead of all: (ie: from ALL -> C:;D:;F:)

  3. urbackupsrv remove-unknown

  4. urbackupsrv repair-database

Any suggestions? :thinking:

here is the log from the client as seen by the server (debug)
I am also attaching a debug file from the client side which seems to have more details from an earlier attempt…

10/04/19 08:53 DEBUG Reflink copying is enabled
10/04/19 08:53 DEBUG Reflink copying is enabled
10/04/19 08:53 INFO Starting unscheduled full file backup…
10/04/19 08:53 DEBUG dodo: Connecting for filelist…
10/04/19 08:53 DEBUG dodo: Waiting for filelist
10/04/19 08:53 DEBUG dodo: Connecting for filelist (async)…
10/04/19 09:00 INFO Selected no components to backup
10/04/19 09:00 INFO Indexing of “ALL” done. 57615 filesystem lookups 0 db lookups and 0 db updates
10/04/19 09:00 DEBUG dodo: Doing backup with hashed transfer…
10/04/19 09:00 INFO dodo: Loading file list…
10/04/19 09:00 INFO dodo: Started loading files…
10/04/19 09:00 DEBUG Starting shadowcopy “ALL”.
10/04/19 09:00 DEBUG Loading file “BOOTNXT”
10/04/19 09:00 ERROR Error getting complete file “mqqwRzvWqEhNwRNKjz0l|ALL/BOOTNXT” from dodo. Errorcode: BASE_DIR_LOST (7)
10/04/19 09:00 INFO Hint: Current root backup path does not exist anymore. Usually this is because the current file system snapshot it was backing up was deleted because it ran out of snapshot storage space. See https://www.urbackup.org/faq.html#base_dir_lost for details and for how to fix this issue
10/04/19 09:00 ERROR Client dodo went offline.
10/04/19 09:00 INFO Waiting for file transfers…
10/04/19 09:00 INFO Waiting for file hashing and copying threads…
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Metadata of “…” missing
10/04/19 09:00 DEBUG Some metadata was missing
10/04/19 09:00 DEBUG Syncing file system…
10/04/19 09:00 INFO Transferred 21.0363 MB - Average speed: 116.019 MBit/s
10/04/19 09:00 DEBUG Script does not exist urbackup/post_full_filebackup
10/04/19 09:00 INFO Time taken for backing up client dodo: 7m 22s
10/04/19 09:00 ERROR Backup failed

#2

I just want to be sure about this. (D:) is typically a optical disc drive; is it one?
You may just be using it as an example, but if you are using it then it may be your issue.

If the drives are not present, meaning that if (F:) is a thumb-drive or external hard-drive that gets removed from time to time then it will break your backup if it is not present.

You can use what I used for clusters, which worked out really well when the drives flopped from one machine to the other – assuming this is the issue: https://www.urbackup.org/administration_manual.html#x1-640008.3.4

I’m referring to C:;D:/optional;F:/optional which should still allow you to backup the root of each drive, but will not error out if the drives are not present.

A possible issue, although it certainly may just be a personal preference, you could try adding (\) marks after the colon: C:\;D:\/optional;F:\/optional
I only suggest that due to how I have my backups setup, and they’ve been green for over 2 years now.

#3

So , here is the interesting thing… I did try to use these /optional flags… earlier and it looked like the backup were still failing from the main urbackup status window… but then as soon as I upgraded to the latest version of the server… it got reset and they are now completing…
I am wondering if there are actually 2 separate issues… the VSS one (addressed by using the /optional flag) but also a GUI problem on the webpage (addressed by upgrading the server)?

anyway thanks a lot for your help…