@alturismo Perfect. Thanks

Hey everyone, I hope replying in this thread for new LB questions is the way to go, otherwise, I could create a new post on the forum, but seeing as this is a LB specific thread I thought I'd try here first.  

 

I have LB installed on Unraid, and backups configured to a remote host via tailscale, and it's working great.  However I'm having trouble exporting the profiles, and incidentally, other weird issues I think having to do with hidden directories (starting with a dot) like /luckybackup/.luckyBackup, where the profiles are stored.  

 

If I try to use the export feature to export a profile, It either fails (if I try to export it to an unraid share (mapped in the container to a local directory), or if I export it to the /luckybackup directory right in the container, it says it is successful, but then I will end up with an empty profile directory there with no actual profile backed up.

 

I know the profiles are being saved, because I can see them in /luckybackup/.LuckyBackup/profiles if I browse there in the console.

 

Those files are all owned by the luckybackup user, but I am running the container with the "Run as root user" set to true.  

 

I am able to manually copy those profiles into my unraid shares from the console.  But I'd love to have an automated backup task that backs up those profiles. (Because it seems they get deleted if I rebuild the container for any reason).  

 

Do I have something set wrong so luckybackup is not able to read those profiles from the gui for some reason?  Thanks in advance.

 

Edit:  It's also not creating the profile backups in the snapshot directories like it should.  It is is creating the profile directory, but not putting anything in there.

Edited January 29, 20251 yr by paqman

On 1/29/2025 at 10:48 PM, paqman said:

Hey everyone, I hope replying in this thread for new LB questions is the way to go, otherwise, I could create a new post on the forum, but seeing as this is a LB specific thread I thought I'd try here first.  

You'll find the support thread here:

 

On 1/29/2025 at 10:48 PM, paqman said:

If I try to use the export feature to export a profile

May I first ask why you are trying to do that?

 

On 1/29/2025 at 10:48 PM, paqman said:

Because it seems they get deleted if I rebuild the container for any reason

This should definitely not happen, can you please describe what you did how?

 

In the support thread there is also a tutorial how luckyBackup should be used and everything should be stored in /luckybackup not in /root because if you enable "Run as root" everything is copied from /luckybackup to /root

 

On 1/29/2025 at 10:48 PM, paqman said:

Do I have something set wrong so luckybackup is not able to read those profiles from the gui for some reason?  Thanks in advance.

I don't think so but you have to keep in mind that luckyBackup was initially designed as a Desktop app and not to run in a container, not everything is working as expected.

 

On 1/29/2025 at 10:48 PM, paqman said:

It's also not creating the profile backups in the snapshot directories like it should.  It is is creating the profile directory, but not putting anything in there.

I don't understand what you are saying here but luckyBackup creates the snapshot directories but you actually have to restart the container to see the snapshots.

Thanks so much for responding, my bad for not even looking at the link for the support thread.

 

9 hours ago, ich777 said:

May I first ask why you are trying to do that?

If you're asking why I'm trying to export the profile, it's mainly so that I can back it up in case I need to restore it.  It took me a while to build the different remote tasks in my profile and I'd rather not do it again if I lose them. I assumed that's what the export feature is there for.

 

9 hours ago, ich777 said:

This should definitely not happen, can you please describe what you did how?

If I just restart the container, or stop it and start it, everything is fine.  The profiles and schedule persist no problem.  But if say I want to add a path to the container, so I modify the container (in the unraid UI), and add a new path, I have to hit "Apply", which re-builds the container.  When I do this, all my profiles are gone.  I assumed this was because the /luckybackup directory gets recreated when the container is built, no?  Is that not supposed to be happening?  This is why I want to back up the profiles, so I can easily import them in the event I have to rebuild the container.

 

9 hours ago, ich777 said:

In the support thread there is also a tutorial how luckyBackup should be used and everything should be stored in /luckybackup not in /root because if you enable "Run as root" everything is copied from /luckybackup to /root

I will look through that tutorial thoroughly thanks.  But yes, everything is stored in /luckybackup, not in /root.  Sorry if I gave that impression somehow.  There are links in /root that point to the profiles in /luckybackup, but as you say, everything is stored in /luckybackup.

 

9 hours ago, ich777 said:

I don't think so but you have to keep in mind that luckyBackup was initially designed as a Desktop app and not to run in a container, not everything is working as expected.

That is good to remember, and honestly I am fine with the way it is working, I am able to back up my profiles and schedule manually from the console to a share on my array, so i'm not worried, just figured I was doing something wrong as I'm unable to use the export and import feature properly.

 

9 hours ago, ich777 said:

I don't understand what you are saying here but luckyBackup creates the snapshot directories but you actually have to restart the container to see the snapshots.

What I'm referring to is when I'm backing up the directory "/pictures", and I have snapshots set to 10.  If I delete a file on my source directory, on the next backup, Luckybackup creates a directory called ".luckybackup-snapshots" where it puts snapshots of the deleted file for a while until the snapshot time has passed.  But it also looks like it creates directories for the backup profiles in there as well.  It creates the directories for each profile, but there is nothing in them.  Again, this isn't something that I need, just a symptom I thought was related to the issue.

 

Thanks again for responding, I will check out that documentation, and you could be right, this could just be quirks of it running in a container.  Was just hoping to verify if this was normal or if I had something configured wrong.  Thanks!

Edit: here is a screenshot of the .luckybackup-snapshots directory that gets created, and the profile directories.  

Edited January 31, 20251 yr by paqman

On 1/31/2025 at 6:28 PM, paqman said:

If you're asking why I'm trying to export the profile, it's mainly so that I can back it up in case I need to restore it.  It took me a while to build the different remote tasks in my profile and I'd rather not do it again if I lose them. I assumed that's what the export feature is there for.

Then please simply backup the files directly from the directory, it seems that the export function is broken in root mode.

 

On 1/31/2025 at 6:28 PM, paqman said:

I assumed this was because the /luckybackup directory gets recreated when the container is built, no?

No, this isn't the case, to what path did you set the Config directory in the template?

Please note if you are using /mnt/cache/appdata/... then your appdata share has to stay on the Cache drive and must not be moved to the Array or another pool.

If your appdata share is however moved to the Array then you have to use the path /mnt/user/appdata/... in the Docker template.

This could be what is causing the issue for you.

 

On 1/31/2025 at 6:28 PM, paqman said:

It creates the directories for each profile, but there is nothing in them.  Again, this isn't something that I need, just a symptom I thought was related to the issue.

This is not done by luckyBackup, this is done by rsync since luckyBackup is just a Frontend for rsync (the name for the snapshot directory is set statically to .luckybackup-snapshots IIRC -> I don't use the snapshot feature anymore since it's a bit overkill for my use case).

Hey Guys

 

Cron jobs arent working for me in the container. I tried debugging, but couldnt find anything proper in the logs.

Anyone that uses a different way to backup to an external server? I do it manually now, but i want to automate it. The Backup PC turns on in the night, and I want to trigger the backup at that time too since it is quite an extensive copy.

 

The only thing I can think of is writing my own script that uses rsync to copy, but it was so nice that LuckyBackup does that for me. (Although it does have to recopy all the Appdata copies that I have new each day, it's technically still copying chunks of data every data instead of refreshing only what has changed.)

 

 

5 hours ago, Kees Fluitman said:

Cron jobs arent working for me in the container.

and console mode is enabled like described ?

 

5 hours ago, Kees Fluitman said:

but couldnt find anything proper in the logs.

what is in the logs ?

 

 

5 hours ago, Kees Fluitman said:

(Although it does have to recopy all the Appdata copies that I have new each day, it's technically still copying chunks of data every data instead of refreshing only what has changed.)

then there is also something wrong in your setup ... sample from appdata here

 

On 2/14/2025 at 4:57 PM, alturismo said:

and console mode is enabled like described ?

 

what is in the logs ?

 

 

then there is also something wrong in your setup ... sample from appdata here

 

It  seems I failed to debug properly myself. A classic mistake I was hoping I could avoid. The log shows the error and Ive fixed all the automatic Starting of my Backup Server. I recently changed the Network Card and OS of my backup server. And Wake-on wasnt set to g for this interface. And also the IP changed of course. So double trouble and me being an idiot. Im sure it will work now.