Hi all - since 6.9.2, my backups are created using wrong/no permissions and I have to rely on the "Docker Safe New permissions" thing in Tools to fix it.

 

The permissions the urBackup docker for the folders are set as:

d--------- 1 nobody users

 

and the files within:

---------- 1 nobody users

 

I tried changing the UMASK from 000 to 777 and no changes.

 

Other than the update to 6.9.2, and routine docker updates, there were no changes in configuration or anything else (that I am aware of)...

Would one of you know what to do in this scenario?

 

Thanks in advance!

 

3 minutes ago, xxxliqu1dxxx said:

I tried changing the UMASK from 000 to 777 and no changes.

a umask of 777 means no permissions for user, group, or world, you need to change it back to 000 then re-run 'Docker Safe New permissions' one last time to fix up the damage.

Just now, binhex said:

a umask of 777 means no permissions for user, group, or world, you need to change it back to 000 then re-run 'Docker Safe New permissions' one last time to fix up the damage.

Done - changed to 000, restarted docker, Ran docker safe new permissions, then did another full image backup... and still no permissions given.

5 minutes ago, xxxliqu1dxxx said:

Done - changed to 000, restarted docker, Ran docker safe new permissions, then did another full image backup... and still no permissions given.

I got it to work I think... with 0000, not 000. Did 6.9.2 change something and makes it not interpret the UMASK properly?

3 hours ago, xxxliqu1dxxx said:

Did 6.9.2 change something and makes it not interpret the UMASK properly?

not that i have noticed, nope, im on 6.9.2 running this image with no issues.

hi,

can anyone please provide a  urbackup.subdomain.conf  to set this up for a internet backup

4 hours ago, Danuel said:

hi,

can anyone please provide a  urbackup.subdomain.conf  to set this up for a internet backup

Not directly what you are asking for, but you should be able to adapt it.

https://forums.unraid.net/topic/82198-support-binhex-urbackup/?do=findComment&comment=977896

 

does anyone have problems with this docker ? for some reason client is not working with the server :(, client is all the time in idle

23 minutes ago, Danuel said:

does anyone have problems with this docker ? for some reason client is not working with the server :(, client is all the time in idle

Hey folx, noob here, running urbackup on an unRaid system.

I've been able to get urbackup to launch and run and even make backups. But, I want to change where the backup images are saved. Currently they are saved in my /media folder on the array. I want to instead save them to a shared folder in my QNAP NAS.  I've mounted and shared the NAS folder, I can access it with File Explorer on my windows laptop, and I can even browse to it within the unRaid UI. But, when I go into urbackup settings and point it to that shared location, it can't find it. I get this error:

 

 

urbackup can't seem to see anything under the /mnt folder.

 

I even tried pointing it to the NAS's IP address on my LAN and that was even a greater failure.

 

This is my current working settings for urbackup:

 

 

Any ideas?

 

1 hour ago, Lonewolf147 said:

urbackup can't seem to see anything under the /mnt folder.

Because nothing is mapped there. Think of containers like tiny virtual machines. They can only access their own folder structure, which is NOT shared with the host, unless you map the location. Whatever you put in the "Backup Location" line will show up in the /media folder inside the container. If you want to point the /media folder to /mnt/remote/Computer_Images that's what you need to put there.

 

Right now you have it pointing at /media in unraid, which exists only in RAM and will be gone when you reboot.

4 minutes ago, jonathanm said:

Because nothing is mapped there. Think of containers like tiny virtual machines. They can only access their own folder structure, which is NOT shared with the host, unless you map the location. Whatever you put in the "Backup Location" line will show up in the /media folder inside the container. If you want to point the /media folder to /mnt/remote/Computer_Images that's what you need to put there.

 

Right now you have it pointing at /media in unraid, which exists only in RAM and will be gone when you reboot.

Correct, but my problem is that when I DO point it to the Computer_Images location, I get the error shown in the first image. I just posted the second two to show the setup for when it does work to the array, not the NAS.

1 minute ago, Lonewolf147 said:

Correct, but my problem is that when I DO point it to the Computer_Images location, I get the error shown in the first image. I just posted the second two to show the setup for when it does work to the array, not the NAS.

NOT the application itself. That always points to /media. You need to change the container mapping. Update container, Backup Location

10 minutes ago, jonathanm said:

NOT the application itself. That always points to /media. You need to change the container mapping. Update container, Backup Location

Ok, so I left the app at /media. Then I launched it's UI and changed to /mnt/remotes/Computer_Images

 

and this is back to the status screen:

 

Edited May 22, 20215 yr by Lonewolf147
spelling issue

1 minute ago, Lonewolf147 said:

Ok, so I left the app at /media.

No, You didn't.

 

In your initial post, second screenshot,

16 minutes ago, jonathanm said:

Whatever you put in the "Backup Location" line will show up in the /media folder inside the container. If you want to point the /media folder to /mnt/remote/Computer_Images that's what you need to put there.

 

So I switched it around. Left it /media in the UI settings, and made it /mnt/remotes/ for the path and /Computer_Images for the container in the docker app itself.

 

No errors when I go to the status, but when I try to run a backup, I get a notice that the backup failed. There are no entries in the Log to say why and there are no new files created in the Computer_Images location.

4 minutes ago, Lonewolf147 said:

made it /mnt/remotes/ for the path and /Computer_Images for the container in the docker app itself.

What do you mean? The container side should be /media, the host side should be /mnt/remotes/Computer_Images. That's assuming you see the remote content at that path in the Unraid console command line.

So this is incorrect:

 

I've seen other apps (so I assumed this one too) create whatever folder is listed in Container Path, at the Host Path location. I didn't need to have Computer_Images two deep.

 

So do I make Host Path /mnt/remotes/Computer_Images and leave the container path blank?

It should look like this then if I'm reading you correctly

1 minute ago, Lonewolf147 said:

It should look like this then if I'm reading you correctly

Yes, that is mapping /mnt/remotes/Computer_Images to /media inside the container. You may need to change the access mode to slave r/w.

There it goes!  Whew.  Thank you very much for walking me through that. I was totally misunderstanding how the folder/container structure was working.

Images over 2TB - what do you do?  I tried to backup a couple of 3TB drives to XFS formatted UNRAID system and got the error:

 

Data on volume is too large for VHD files with 2.8054 TB. VHD files have a maximum size of 2040GB. Please use another image file format.

 

As there is no other image format, is my only choice File Mode backups?

Hello, I restarted my system and now th docker is asking for a password. I never set one up. Whats the default password? Also how do I change in it when logged in?

25 minutes ago, Supershocker said:

I never set one up. Whats the default password?

there isn't a default as no passwords are set in the image, can you post a screenshot of the prompt to enter the password.

20 minutes ago, binhex said:

there isn't a default as no passwords are set in the image, can you post a screenshot of the prompt to enter the password.

This happens when I clicked the urBackup logo in the top left

Edited June 22, 20215 yr by Supershocker
more info