@KluthR thank you for this plugin, very helpful. I faced the issue during backup image verification. Is it working well? Should I turn off backup verification? Here is screenshot and attached debug log file.

ab.debug.logab.debug.log

10 hours ago, KluthR said:

For what reason? To exclude it? If yes, the exclusion filter will adapt a more things in the next update. 

Yes exactly, cause right now exclusions don't seem to work on internal volumes

On 4/18/2023 at 2:45 AM, KluthR said:

Exact same reason

 

I could remove a mapping once it appeared but it could be backed up within wrong container context which causes confusion.

I think at the very least the duplicates should be cleared from the generated tar command because listing the volume twice in the tar command like this is redundant:
 

[19.04.2023 12:10:01][debug] Generated tar command: --exclude '/mnt/user/appdata/plex/*' -c -P -f '/mnt/user/Backups/Appdata Backup/ab_20230419_120957/tautulli.tar' '/mnt/user/appdata/tautulli' '/mnt/user/appdata/tautulli' '/mnt/user/appdata/plex/Library/Application Support/Plex Media Server/Logs'

 

I'm getting some warning notifications, even tho the log seems kind of fine.

 

 

ab.debug.log

Edited April 19, 20233 yr by Kazino43

Thanks @KluthR, I installed 04/15 version and everything just works.

Includes all the functionality I needed from this plugin. Works beautifully!

On 4/19/2023 at 5:32 PM, DimaS70 said:

I faced the issue during backup image verification

This is because of a bug which is fixed within latest BETA version (volume mapping nesting). You are also mapped the whole appdata - this is being ignored as well within next update

 

On 4/19/2023 at 6:12 PM, halorrr said:

Yes exactly, cause right now exclusions don't seem to work on internal volumes

They are working - but not, if you exclude a whole volume. Only subcontents of it. This seems to be a limitation from tars verify command. The next update remove volumes/exclusion pairs.

 

On 4/19/2023 at 6:16 PM, halorrr said:

because listing the volume twice in the tar command like this is redundant

Should be self solving as well then.

 

On 4/19/2023 at 11:15 PM, Kazino43 said:

I'm getting some warning notifications, even tho the log seems kind of fine.

Warnings are no errors. Just warnings. They tell you, there might be an issue. Some functions change the behavior if some conditions are met. Those produce warnings to let you know.

 

 

That being said: There is a new beta version with all current issues fixed. Before public relleasing, I want you (all quoted ones, and @MothyTim - did I forgot someone?) to test it. Note: This require to configure the beta version from scratch (or your simply copy over the confoig.json from appdata.backup to appdata.backup.beta - yes, automating that would be nice, noted)

@schreibman: Regarding

Not a real bug here - I dont thought, that there will be the same mapping twice - at least for host point of view. Is a nice to have to deduplicate detected volumes - noting.

 

But how does your plex was working before? You just changed the mapping paths as I see, or do you reorganized the files as well? All files were in the same place at first.

Hi, thanks for the great work maintaining this - I've had to use restore recently and you saved my a$$. 

 

Is this the right spot for feature requests? If not feel free please to move or delete.

 

Ideally, looking for an option (or even default behaviour?) to shut down a docker only when the backup is going to start happening, then immediately restart it once the backup is complete? (this assumes the user has selected separate .tar backups) My use case is that I use Agent-DVR and Zoneminder which I'd love to have backed up, but ideally don't want to wait for the massive and time consuming plex backup to complete before the DVR dockers restart. For now they are excluded and set not to stop.

 

thank you!!

I believe you are refering to ca.backup2?

because your requested feature is availble inside the new appdata.backup.

Hi,

thanks for support v6.12.x with your plugin.

 

Is a global exlcuding list possible? I want to exlude file like cache.db,.DS_Store,.log,.log.,.tmp completely?

8 hours ago, sonic6 said:

Is a global exlcuding list possible?

It is! Noted.

Is it a bug that my Plex Appdata folder is treated as "External"? 

I have to force backups of externals and then create omissions to get it to not skip Plex

Depends. Show a screenshot of your config. Whats set as allowed source paths? What mapping paths are affected?

Im getting "Invalid source

The selected source seems invalid." on a backup from a day ago.

Then please post your debug log. I cant tell whats going on without it.

There is no debug log to post. It never attempts to do anything. Logs only had "The log is not existing or empty"

 

I ended up just unpacking them by hand.

Edited May 5, 20233 yr by Ewok

Sorry, I need more infos. What are you trying to do? Are you talking about a restore?

Just used this to back up my app data I can see this being a life saver so thank you for that. 
my question is when I come to do a restore do I have to have say Sonarr already installed or just restore the back up and that takes care of that too

Once again thank you 

26 minutes ago, vipermo said:

my question is when I come to do a restore do I have to have say Sonarr already installed or just restore the back up and that takes care of that too

Its described at the restore page: it only restores the data, any container action (like stopping or creating) must be done by you.

 

Restoring isnt that powerful currently. Maybe I add some logic later to do a full automated container restore.

Edited May 5, 20233 yr by KluthR

Hi there,

Keep getting backup failures. I'm still learning a lot here, so please forgive me. Attached is the debug file. Thanks in advance! 

backup.debug.log

Edited May 5, 20233 yr by Inch

Tdarr and tdarr node sharing (some) same volumes. Backup at tdarr failed because tdarr node wrote to the logfiles. Verification failed.

 

exclude the shared share in one of these two.

 

you should also check your npm mappings, none of these seem to exist??

4 hours ago, KluthR said:

Tdarr and tdarr node sharing (some) same volumes. Backup at tdarr failed because tdarr node wrote to the logfiles. Verification failed.

 

exclude the shared share in one of these two.

 

you should also check your npm mappings, none of these seem to exist??

Thank you so much! RE NPM - this is just an old docker, i've added this to the excludes also. 

Thanks again 

having an issue while trying to restore,

select backup drop-down doesn't display any backups, always just displays the one shown below, (01.05.2023) the backup source shows my backups,

any ideas ?

 

 

 

 

Sorry, the old backups are not compatible with the new plugin and therefore not available for restore. If you need something unpack it by yourself. After some time you can discard they.

Edited May 9, 20233 yr by KluthR

is the file ab_20230501_030001 an old version of the backup also ?