1 hour ago, Kilrah said:

It would really be nice to have start/stop groups to ensure a DB container

as a workaround you can stop/backup/start all containers at the same time, like it the old appdatabackup2.5 did.

11 hours ago, KluthR said:

If the database container stops before backup, all is fine. If you want a dump as backup, you have to write own scripts. Maybe appdata backup could do this for us somehow. I know how to export mysql, pgsql and mongodbs, since I do it at work full automated via remote ssh.

ive heard this is a solution to use,

https://github.com/tiredofit/docker-db-backup

 

you basically dont touch your actual db, and just have that docker run backups periodically from it to a place of your choosing which you back that up.

 

That's what I've been using, and what I'd like per-container scripts. That way the container would be stopped, my script would run backup-now from the db-backup container, then the container's data gets backed up and it's restarted.

Hi,

 

Since updating to Unraid 6.12.2 and switching to this Appdata app, I have a problem creating a backup.

It seems like the "Save external volume" feature is not working.

When the app tries to backup for example Binhex Krusader docker, which contain a large /mnt mount, it sees it as an external volume, the option to save it is toggled to No as default, but the backup process takes forever and it seems like it's creating a very large tar files despite the actual /mnt/appdata/binhex-krusader folder is only a few kb.

Can you help me with this one?

 

Thanks.

Hey,

Does this Plugin still work if all Appdata Folder are ZFS Datasets? 

 

Thanks for the Help! 
BR

This plugin works on top of the filesystem layer. It just does packing commands. 

I have a Tautulli container that has a mapped folder to another container (Plex).

That caused the Tautulli backup to fail so I excluded that Plex folder from the backup:

/mnt/user/appdata/Plex/Library/Application Support/Plex Media Server/Logs

 

Now the target folders of the backups still has "-failed" suffix (i.e. "ab_20230711_043002-failed") ,

but there are no backup.log or backup.debug.log files, so is the backup successful or not?

1 hour ago, Gico said:

so is the backup successful or not?

Take a look to the „Status“ tab. What is it saying?

It says:

"The backup is not running.

The log is not existing or empty"

What happens, if you start the backup by yourself?

The container stopping timeout should be higher or per container customizable.

Some of my containers aren't backuped and also not started when "appdata backup" is finished:

 

-ferdium-server

-OpenSpeedTest

-OnlyOfficeDocumentserver

 

Debuglog is attaced

 

 

ab.debug.log

1 hour ago, sonic6 said:

The container stopping timeout should be higher or per container customizable.

The timeout is the timeout set in the global Docker settings. The Plugin has nothing hardcoded.

 

the plugin should skip backup if stopping was not successful, that doenst seem to work.

8 minutes ago, KluthR said:

the plugin should skip backup if stopping was not successful, that doenst seem to work.

do you know what the difference is to appdata backup 2.5? with that i didn't got that problem.

28 minutes ago, sonic6 said:

do you know what the difference is to appdata backup 2.5?

Yes, its deprecated and not working under 6.12.x

 

28 minutes ago, sonic6 said:

@KluthR  did you forget something? 😂

No, the Rich Text Editor does not play well with iOs‘ Safari. I wanted to delete the block but it wont work.

1 hour ago, KluthR said:

No

 

3 hours ago, KluthR said:

3 hours ago, sonic6 said:

do you know what the difference is to appdata backup 2.5?

Yes, its deprecated and not working under 6.12.x

i meant, what is different to the old appdata backup, when it comes to "stop" and "backup" the container. i wasn't facing this problem with the old version.

Please read the old threads (first posts) there is described why we are here.

8 hours ago, KluthR said:

described why we are here.

that wasn't my question... but okay, everyone has a limit amount of time. nevermind.

On 7/12/2023 at 6:40 AM, KluthR said:

What happens, if you start the backup by yourself?

Backup failed. Attached the web-ui log, backup.log and backup.debug.log files.

 

backup.log backup.debug.log

web-ui.log

Edited July 13, 20232 yr by Gico

Plugin works like a charm. But would it be possible to name the folders created for each backup differently? I don't like the name scheme. Now every folder has a name like "ab_20230713_043001" can we get an option that let us select a different name pattern? Or at least add "-" like yyyy-mm-dd-hh-mm-ss

For what reason? The plugins task is to create and restore backups. For this is creates folders with a fixed name scheme. Why should it be configurable?

Readability. That is how i check from time to time if the backups are done. Sure, I could check the status/log page, but checking the latest folder is much faster, for me at least. Does the plugin sent out notifications?

3 minutes ago, ezek1el3000 said:

Does the plugin sent out notifications?

Yep, if its set.

 

3 minutes ago, ezek1el3000 said:

but checking the latest folder is much faster, for me at least.

What would another naming change?

Failed backups are suffixed with „-failed“.

Edited July 13, 20232 yr by KluthR

Okay, notifications only happen if the backup got errors or warnings, not when its done correctly. I keep that in mind.