Persist backup app doesn't work

[imc67]

@girish that “test” was manually de-marked when I discovered that was part of the box update backup.
Very strange your instance is preserving like it should be. I will test again with this Cloudron en two others.

[imc67]

@girish I tested it on 3 different Cloudrons (Premium) in a Wordpress Unmanaged app, marked the oldest available app backup as persistent and within 24 hours ALL are gone!!!
The only similarity between the Cloudrons: they use a (each its own) Hetzner StorageBox with CIFS in tgz 2 times a day and 7 days retention.

[imc67]

@girish any idea? Shall I give you access to one or all?

[jdaviescoates]

@imc67 just to test I've just edited the most recent backup of a bunch of my WordPress (Developer) installs and checked the persist box... let's see what happens on my Cloudron too...

I use one big Hetzner StorageBox with CIFS in tgz for everything (just once a day)

[imc67]

@jdaviescoates said in Persist backup app doesn't work:

the most recent

Thanks!!

maybe easier to select the oldest then you don't have to wait for the retention period to pass

[girish]

@imc67 yes, please. I can't reproduce this. My backups are still persisting.

[jdaviescoates]

@imc67 said in Persist backup app doesn't work:

maybe easier to select the oldest then you don't have to wait for the retention period to pass

I'll do that now...

Edit: I went for the oldest backup of the current package version (last copy of previous packages versions persisting due to rules about that).

[imc67]

@girish said in Persist backup app doesn't work:

@imc67 yes, please. I can't reproduce this. My backups are still persisting.

just sent you an email to support@

[jdaviescoates]

@jdaviescoates said in Persist backup app doesn't work:

@imc67 said in Persist backup app doesn't work:

maybe easier to select the oldest then you don't have to wait for the retention period to pass

I'll do that now...

Edit: I went for the oldest backup of the current package version (last copy of previous packages versions persisting due to rules about that).

I realise now I should've done screenshot, but I can confirm that all of those "oldest backup of the current package version" that I had edited to persist have now disappeared and have not persisted at all!

Something is clearly very wrong somewhere.

I've just edited another "oldest backup of the current package version". Presumably it'll also disappear...

[jdaviescoates]

@jdaviescoates said in Persist backup app doesn't work:

I've just edited another "oldest backup of the current package version". Presumably it'll also disappear...

Yep, as predicted, it did disappear:

[jdaviescoates]

@girish said in Persist backup app doesn't work:

I can't reproduce this.

Are you trying with WordPress (Developer), as I was very easily able to reproduce it with that (not tried anything else... yet).

[jdaviescoates]

I'm testing with Calibre now (just to try another random app that isn't WordPress Developer):

[jdaviescoates]

@jdaviescoates said in Persist backup app doesn't work:

I'm testing with Calibre now (just to try another random app that isn't WordPress Developer):

Yep, that's disappeared too:

[girish]

Thanks @imc67 and @jdaviescoates for helping narrow this down. Indeed, this is a bug when using the fs backend, this is why I couldn't reproduce it. Fix is in https://git.cloudron.io/cloudron/box/-/commit/243a254f3e2fe80d62d248e76f1a751b7af44b72

[jdaviescoates]

@girish great, thanks. Which version of Cloudron will this fix be included in?

[imc67]

@girish thanks for the fix!

[girish]

Should be in next release (8.0), but otherwise you have to apply that one liner manually.