Any tips/recommendations for syncing the backup files to the cloud? Ideally OneDrive or something similar. 

hi anyone know why its doing it like this?

the [nextcloudaio] is the tag i created for nextcloud-aio-mastercontainer. there's no docker exactly called nextcloudaio.

so its giving out an error saying there's no volume to back up



 

i have never used the aio docker to give more info :s try asking in the specific docker thread

On 10/4/2024 at 6:35 PM, PANiCnz said:

Any tips/recommendations for syncing the backup files to the cloud? Ideally OneDrive or something similar. 

I'm in the same boat if someone can give tips i likely appreciate it. Currently using duplicati but every time i do the backup it uploads all the time 45gb and it should be less because data is supposed to be dedupped. 

4 hours ago, i1mran92 said:

hi anyone know why its doing it like this?

Share debug log

3 hours ago, KluthR said:

Share debug log

This is enough? or would i need to upload the whole file?
Debug Log ID: a0067ec4-0822-4d0e-8271-2c664f498ff4

I have a problem with plex

my debug id: 2e862448-94ff-431d-946c-895ae542e282

6 hours ago, i1mran92 said:

This is enough? or would i need to upload the whole file?

Did you read the debug log upload confirm dialog?

 

However, it seems to be a bug. All of your nextcloudaio members should be ignored. So the group is left empty. I bet I did not catch this state. It seems the backup script skips some group magic and keeps nextcloudaio as a container name.

 

remove the group when you not plan to backup any member. The bug will get fixed when Iam back from my holidays.

4 hours ago, PilaScat said:

have a problem with plex

Put plex and tautulli in one group. They share volumes with each other. There should also a warning in the container settings secrion.

A few days ago I started getting an error in my backup about not being able to back up the VM XMLs. I tried looking in the debug log as it said, but either I looked in the wrong file or just didn't know what I was looking at or something, but I didn't see anything meaningful.

 

Here's my debug log ID. Hopefully you can help figure out what's going on! 

dc0c0c39-62e1-4b26-b37e-c610b363e470

I keep getting Error because one container Bazarr seems to not start after the update.

Logs in Bazarr does not say anything about it trying to start up but manually starting it works fine.

Anyone have same issue?

Debud log b3c70168-4ab1-4565-94d2-775a0396b4e7

Edited October 7, 20241 yr by nekromantik

Hi,
when trying to install Appdata backup from "APPS" the process soon stops with the following info:
 

plugin: installing: appdata.backup.plg
Executing hook script: pre_plugin_checks
plugin: downloading: appdata.backup.plg ...
plugin: appdata.backup.plg download failure: SSL verification failure
Executing hook script: post_plugin_checks

Any idea what's wrong (or what I did wrong)?

Smells like temporary issue on githubs end. Try again later.

On 10/7/2024 at 6:54 PM, nekromantik said:

I keep getting Error because one container Bazarr seems to not start after the update.

Logs in Bazarr does not say anything about it trying to start up but manually starting it works fine.

Anyone have same issue?

Debud log b3c70168-4ab1-4565-94d2-775a0396b4e7

anyone?

On 10/7/2024 at 3:43 PM, gacpac said:

I'm in the same boat if someone can give tips i likely appreciate it. Currently using duplicati but every time i do the backup it uploads all the time 45gb and it should be less because data is supposed to be dedupped. 

I've started using the rclone plugin and so far its doing what I want.

On 10/7/2024 at 11:37 AM, ms4sman said:

A few days ago I started getting an error in my backup about not being able to back up the VM XMLs. I tried looking in the debug log as it said, but either I looked in the wrong file or just didn't know what I was looking at or something, but I didn't see anything meaningful.

 

Here's my debug log ID. Hopefully you can help figure out what's going on! 

dc0c0c39-62e1-4b26-b37e-c610b363e470

Any chance you've had an opportunity to look at this issue? Still getting the error every day.

 

Thanks!

is there a service name that's used that i can use in a script to detect if appdata backup is running? i'm not having any luck locating it in there is one. 

In my Parity Check Tuning plugin I use the following statement

	$ret = (file_exists('/tmp/appdata.backup/running')
		  ||file_exists('/tmp/ca.backup2/tempFiles/backupInProgress')
		  ||file_exists('/tmp/ca.backup2/tempFiles/restoreInProgress'));

and it seems to work OK.    I guess it could change in the future if the backup plugin changes things.

Hi,

 

I have two problems with my AppDataBackup plugin:

1. I have several containers connected to GlueTun - when gluetun is updated automatically the connected containers are tagged for "rebuild" - AppDataBackup doesn't seem to know what to do here so it just tries to start the containers, but technically they "don't exist" as they need to be rebuilt. So the plugin sends me 15 warning/emails errors instead....  If I go to the Docker tab in the morning all the slave containers are sitting there stopped and waiting for rebuild - which they then do automatically, and then I can start them again. Aside from stopping GlueTun from updating automatically is there anything else I can do, or is this just a bug/known issue?
2. I get an error every run that the VM data needs to be backed up but the VM Manager isn't running. It's not running because I'm not using it. However there isn't an option (that I can see) to exclude VM backups? I could of course run it with no VMs, but that seems a bit unnecessary?

Any tips?

 

My debug log is: e78f91bd-7896-47f3-85dc-569b52350eb8

 

Thanks!

 

CP.

On 10/7/2024 at 10:54 PM, KluthR said:

Did you read the debug log upload confirm dialog?

 

Sorry, i did. just wanted to confirm.

 

On 10/7/2024 at 10:54 PM, KluthR said:

 

However, it seems to be a bug. All of your nextcloudaio members should be ignored. So the group is left empty. I bet I did not catch this state. It seems the backup script skips some group magic and keeps nextcloudaio as a container name.

 

remove the group when you not plan to backup any member. The bug will get fixed when Iam back from my holidays.

Put plex and tautulli in one group. They share volumes with each other. There should also a warning in the container settings secrion.

remove the group when you not plan to backup any member. The bug will get fixed when Iam back from my holidays.

So for now i just remove all the nextcloud-aio group tag. Not plannining to have them back up, dont think i even can since there's nothing can be back up. there's only nextcloud-aio-mastercontainter and it created the the other nextcloud aio containers . I back them up using nextcloud itself.

Thank you btw for checking it out. Will wait for an update then.

On 7/24/2024 at 6:44 AM, ifihaffto said:

As others have said, thanks for your hard work on this plugin.

 

I've recently upgraded Unraid to 6.12.10 and updated your plugin.

The Status/Log indicates that the backups are all successful, but my [binhex-plex] container seems to get wiped out every time the backup runs.

 

[23.07.2024 03:47:26][ℹ️][binhex-plex] Starting binhex-plex... (try #3) Container did not started! - Code: No such container

 

I don't know if it's my docker config or backup.

 

Any help would be greatly appreciated.

 

Thanks again.

Did you ever figure this out? It's happening with one of my containers.

It occurs to me the following (for "start, backup, start for each container") would reduce downtime significantly:

1. Untar container's latest backup into temp directory
2. Stop container
3. rsync container's appdata directory to temp directory
4. Start container
5. Tar temp directory as new backup
6. Verify
7. Clear temp directory

 

No downsides I can think of besides the extra space required. 

Backup Issue with Plex - Tar Creation Failed, "Structure Needs Cleaning" Error
 

Hi everyone,

I'm encountering an issue when trying to back up my Plex server using the "Appdata Backup" tool. The backup process fails with the following error:

 

[❌][plex] tar creation failed! Tar said: tar: /mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Media/localhost/2/80a9a8e3b87819fba3f0b3a874d68512b980b6e.bundle/Contents/Chapters/: Cannot savedir: Structure needs cleaning; tar: Exiting with failure status due to previous errors

It seems like there’s an issue with a specific file or folder, and the error "Structure needs cleaning" suggests there might be some kind of file system corruption. 

Do you have any idea?

I have 130+ containers running in docker via compose. I'm unable to save the configuration settings to set all of the containers to skip so I may only back up my USB. After the first 100 or so it starts throwing 429 errors and doesn't reflect changes upon saving.

 

Is there an alternate way to disable the containers, else how can I backup my USB only with the plugin?

 

I edited the config.json manually with the additional empty array entries, eg below, but they were removed from the file upon reloading the webui.

 

        "wizarr": {
            "skip": "yes",
            "group": "",
            "backupExtVolumes": "no",
            "updateContainer": "",
            "exclude": "",
            "skipBackup": "no",
            "verifyBackup": "",
            "ignoreBackupErrors": ""
        },

 

Thank you.

Edited October 15, 20241 yr by adamfl

8 hours ago, Monokel said:

Do you have any idea?

Sounds like file system error. Check filesystem

 

4 hours ago, adamfl said:

how can I backup my USB only with the plugin?

I dont remember but is there a advanced config option to skip container backup?

17 hours ago, KluthR said:

Sounds like file system error. Check filesystem

 

I dont remember but is there a advanced config option to skip container backup?

 

There is not, unfortunately, it's listed as a bullet in the roadmap post.