4.8.x Backups Failing

[scharbag 19]

28 minutes ago, Happy2Play said:

I am a little confused but would suggest the plugin cannot pause the database to back it up via your setup/system?  So in theory you can shutdown Emby and backup the database manually and reuse it correct.

Yeah, I can shutdown Emby and copy ll the config files to a new Docker and everything works.  I just dislike when things throw errors...

[scharbag 19]

On 17/03/2024 at 12:24, Happy2Play said:

I am a little confused but would suggest the plugin cannot pause the database to back it up via your setup/system?  So in theory you can shutdown Emby and backup the database manually and reuse it correct.

Likely yes - I can copy the /config folder to a new instance and it works fine.

BUUUUT - I would prefer if the backup system worked.

I have tried everything I can find on the forums for reseting DBs, verifying DB integrity, restoring DBs etc.  Nothing helps.

Dev system I do not care about - easy rebuild.  Prod system, I can easily rebuild but I want to keep play states.  For now, I am not too worried as I have a good Veeam history of the VM so recovery will not be too hard if something goes snaky.  Still, my OCD hates silly things like this.

Thanks for the help and suggestions to date.

[Luke 42077]

That’s really odd. Are you sure the two dockers are configured identically?

[scharbag 19]

19 hours ago, Luke said:

That’s really odd. Are you sure the two dockers are configured identically?

I execute everything in a single docker compose file.  I have 2 different instances running and I have added a 3rd for testing (only changed the name and where the config files are stored).

The new testing one works FINE until I copy the config files from one of my production Emby dockers (containers are stopped during copy).  Then I get the backuop issues again.

Very strange, really annoying but not debilitating.

[Luke 42077]

OK let us know if you find anything else. Thanks.

[scharbag 19]

Yeah, still no joy on backups working - not worried to much as I have Veeam backing up my systems.  But I would love to fix this some day...

 

On 4.8.10.0 now...

[Carlo 4560]

Sorry, haven't read the whole thread but

Have you checked permissions of files/folders that you are reading/writing to for the Backup plugin?
Depending on platform, have you given permission to the Internal Emby user and Emby group to this same share?

Carlo

[scharbag 19]

Was still failing - it was not a critical thing cause I have Veeam, but FML, I needed to have this solved.

Running Version 4.8.11.0 on Compose.  Bakcups go to:

That directory shares back over SMB through the fstab mount.

Was still getting this error:

Notice that it is trying to use a cache folder that is also on an fstab share.  So, given I increased the space of my Docker host, I set it to use the default cache location (removed the cache folder setting) and BLAMMO - the gosh darn thing works...

So, it seems that I have a weee bit of an issue with the cache directory...  I will remember that for the future...

Odd, but solved.

Yippee!

[Luke 42077]

13 hours ago, scharbag said:

Was still failing - it was not a critical thing cause I have Veeam, but FML, I needed to have this solved.

Running Version 4.8.11.0 on Compose.  Bakcups go to:

That directory shares back over SMB through the fstab mount.

Was still getting this error:

Notice that it is trying to use a cache folder that is also on an fstab share.  So, given I increased the space of my Docker host, I set it to use the default cache location (removed the cache folder setting) and BLAMMO - the gosh darn thing works...

So, it seems that I have a weee bit of an issue with the cache directory...  I will remember that for the future...

Odd, but solved.

Yippee!

Thanks for following up !