3 hours ago, Masterwishx said:

 

Please use 

urbackupsrv remove-unknown -u root 

and

urbackupsrv repair-database

Then restart urBackup, Fixed for me

 

😮 That seems to remove all the "problems" the log spitted out

Sorry, but I'm confused on this.  Is the ZFS support for Client or Server and what does it do?  My cache pool is formatted ZFS, but my array (where the data will live) is xfs....  Shouldn't it all just store as files either way...why does it care what the backing file system is?

What's your recommended method for installing the client on unRAID?  Do you just do this from terminal? 

`With Docker (web interface accessible from client)` - Is there any issue setting up containers this way on unRAID?

12 hours ago, NeoMatrixJR said:

Sorry, but I'm confused on this.  Is the ZFS support for Client or Server and what does it do?  My cache pool is formatted ZFS, but my array (where the data will live) is xfs....  Shouldn't it all just store as files either way...why does it care what the backing file system is?

Yes it's just store, about zfs you can read more in urbackup docs

12 hours ago, NeoMatrixJR said:

What's your recommended method for installing the client on unRAID?  Do you just do this from terminal? 

`With Docker (web interface accessible from client)` - Is there any issue setting up containers this way on unRAID?

I'm not using client on unraid, but you can install it, you can find about in binhex-urbackup thread

6 hours ago, Masterwishx said:

Yes it's just store, about zfs you can read more in urbackup docs

It looks like the options to use ZFS's features are built around specifically storing to a strictly ZFS array device.  I'm guessing if I'm storing everything on my unRAID XFS array in the end I should just ignore the zfs stuffs?

2 minutes ago, NeoMatrixJR said:

ignore the zfs stuffs

Yes, I'm using clients on Ubuntu cloud servers not zfs and Windows clients

Anyone here know what the 'Create symbolically linked views for each user on the clients after file backups' setting does? There are several questions about it in the Urbackup forum, but no answers. I can see "Creating user views..." in the log after a backup, but how can I access it?

On 11/7/2024 at 4:56 PM, lsaranto said:

Anyone here know what the 'Create symbolically linked views for each user on the clients after file backups' setting does? There are several questions about it in the Urbackup forum, but no answers. I can see "Creating user views..." in the log after a backup, but how can I access it?

In theory, while doing an incremental file backup it replaces any unchanged folder holding more than ten items inside with a symlink to the original in previous backups. See: https://www.urbackup.org/administration_manual.html#x1-750008.6

 

I'm having a severe problem with it and my Windows PC's backups, though. UrBackup's GUI shows them and their contents, and I can restore them or their items with no issues. BUT:

• Unraid's built-in file browser doesn't show them inside the share where the backup is stored (a RAID-Z one).
• The share, mounted on in my PC via SMB doesn't show them either.
• Kommander shows the symlinks but says they are broken.
  
• Via Bash, I can ls in that directory and see the symlink: "EIAS@". Doing ls -l EIAS gives me:

  lrwxrwxrwx 1 nobody users 64 Mar 17 23:55 EIAS -> /media/MY-PC-NAME/.directory_pool/DM/DMthUhIsJj17422521537920821

  which seems valid.

 

I've tried a few SMB recipes to make symlinks accessible, unsuccessfully. That Unraid's own file browser doesn't see them feels even more concerning.

Does this happen to anybody else? Should we disable this default setting when dealing with backups of Windows data (doing so gives me the normal, expected behavior)? Or is it a ZFS issue?

I'm on Unraid 7.0.1.

 

Edited March 18, 20251 yr by MetricTonto
More precise context data

I was having an issue with this container blowing up my docker image size.  It turns out urbackup was creating very large temp files in /tmp.  I solved the docker image size issue by manually mapping /tmp to /mnt/user/appdata/urbackup/tmp.  I would suggest adding /tmp as a standard config option in the container settings.

Edited April 1, 20251 yr by kingbuzz0

10 hours ago, kingbuzz0 said:

very large temp files in /tmp.

What exactly files you found here? 

I can see only cbs.* 40 bytes

 

Seems related to advanced settings in urbackup 

I am not certain what urbackup temp files are used for, but in my case there were large files created that were related to active backup jobs.  These easily ballooned to 16GB and pushed my docker image to 100%.    It took a bit of digging around but I found the tmp dir was to blame.  In addition to the 3 or 4 very large files there were also 30-40 other smaller files.  I had problems with my scheduled backups running because I had run out of space on one of my shares and didn't notice for some time.  So I think the root of my problem was because there were multiple failed backup jobs over that period and when I finally added more space the backlog of backup jobs resulted in huge temp files. 

 

In any case, if there are scenarios where urbackup will create huge files in /tmp, I think it's best to bring that mapping option to the container config and hopefully prevent this scenario for everyone else.

Edited April 2, 20251 yr by kingbuzz0

Iam not able to run this container. Container starts but it seems, the service isn't running (can't connect to webinterface). In my log this appears:

12 hours ago, busha said:

Iam not able to run this container. Container starts but it seems, the service isn't running (can't connect to webinterface). In my log this appears:

Check for permission of folder in container

What's the Benefit of ZFS/btrfs Support?

Any one this Issue too: https://github.com/funilrys/aur-urbackup2-client/issues/11

Or working your Client Installation?