Urbackup on a Windows Server 2022 with shared drives

Server
1

Good Morning Everyone,

I am new here and I have a couple of Questions.

I have setup Urbackup v2.5.38 as a server (On Windows Server 2022) in our network and I have it working for one storage path. However I have a shared storage path which I would like to backup but I can’t seem to, for instance (Urbackup Client v2.5.32)

image
image713×231 30.8 KB

Path 1 is: A: (This one works fine) to F: (Drive)

Path 2 is a Shared Drive called G: (named Vol1) also to F: (I am hoping), however I get an error when trying to back it up:

image
image832×850 30.8 KB

This is where I want to back it up to and it works fine.

image
image928×925 32.4 KB

Here is the errors I get:

image
image885×483 21.5 KB

I hope I have explained this clearly…

Can someone please point me to the correct way to backup the shared drive/storage (if it is possible) to the current server F: drive/path? Step by Step would be awesome.

Thank you very much in advance,
Michael (nexusguy59)

2

Hi Michael,

G: is a mapped network drive (it shows under “Network locations”). The UrBackup client runs as a Windows service under the Local System account, and drive mappings only exist for the user who created them, so the service simply doesn’t see G:. That’s the “cannot find the path specified” error.

The best fix is to install the UrBackup client on the machine/NAS that actually holds Vol1 and back it up from there as a normal local disk. Then it shows up as a second client on your server and its backups also land on F:. Remove G:\ from the HyperV-02 paths afterwards.

If you can’t install a client there, you can back up the share through HyperV-02 instead:

  1. Use the UNC path instead of the drive letter, e.g. \fileserver\Vol1 instead of G:\ (Settings > File Backups > Default directories to backup, or “Add/Remove backup paths” in the client tray icon).
  2. Local System accesses shares with the computer’s account. If the share doesn’t allow that, open services.msc, go to “UrBackup Client Service for Backups” > Properties > Log On, set an account that can read the share, and restart the service.
  3. Start a full file backup.

With this second method the client can’t create a snapshot of the share, so you’ll see a “Creating snapshot … failed” error in the log, but the backup still runs. Files that change during the backup may be inconsistent, which is why the first option is better.

The backup storage path F: is fine as is. All clients share it.

3

Thank you sir, I will give that a shot I appreciate it very much.