Long Path UNC

[Sylvain Donnet]

Hi,

I need to backup network shares on a Windows guest, and the shares are coming from a branded NAS. No capability to install Bareos client on this NAS.

So, I discovered on this forum an old post, telling that UNC, in long path format (\\?\UNC\server\share) works for Bareos.

My tests didn't work. But I discovered that at least one prerequisite is required : a regedit key (HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled) to declare.




So, my questions are :

- are there other prerequisites ?

- is the Bareos windows client compatible with such call ? (or above a specific version ?)

- how do I have to write the files instruction in the Fileset (native \\?\UNC\..., \\\\?\\UNC\\, //?/UNC/, ...)





Any help will be greatly greatly appreciated... I am going to be completely mad with, for me, a simple+old problem...




Sylvain


[Spadajspadaj]

Apart from all the possible other prerequisites, you have to remember that the paths have to be accessible from the context of the user from which the bareos-fd is running. So if you - for example - mount the NAS share as a g: drive from your normal user, it won't be visible to the bareos-fd process since it's running from another user session. If you want to call UNC-paths you might have to do some windows-voodoo with credentials.

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/bc51bde5-9073-4346-a3ef-ec8d0ba2518bo%40googlegroups.com.

[Sylvain Donnet]

Hi,

Thanks. I knew about that. Bareos-fd service run under an account having the maximum rights, and having also "net share" declared.

I am looking to the special writing of "Files=..." with UNC...

My job failed, but I don't know if it is due to the writing, or a missing prerequisite, or both...

Le mercredi 24 juin 2020 12:31:10 UTC+2, Spadajspadaj a écrit :

Apart from all the possible other prerequisites, you have to remember that the paths have to be accessible from the context of the user from which the bareos-fd is running. So if you - for example - mount the NAS share as a g: drive from your normal user, it won't be visible to the bareos-fd process since it's running from another user session. If you want to call UNC-paths you might have to do some windows-voodoo with credentials.

On 24.06.2020 10:17, Sylvain Donnet wrote:

Hi,

I need to backup network shares on a Windows guest, and the shares are coming from a branded NAS. No capability to install Bareos client on this NAS.

So, I discovered on this forum an old post, telling that UNC, in long path format (\\?\UNC\server\share) works for Bareos.

My tests didn't work. But I discovered that at least one prerequisite is required : a regedit key (HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled) to declare.




So, my questions are :

- are there other prerequisites ?

- is the Bareos windows client compatible with such call ? (or above a specific version ?)

- how do I have to write the files instruction in the Fileset (native \\?\UNC\..., \\\\?\\UNC\\, //?/UNC/, ...)





Any help will be greatly greatly appreciated... I am going to be completely mad with, for me, a simple+old problem...




Sylvain


--
You received this message because you are subscribed to the Google Groups "bareos-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bareos...@googlegroups.com.