need help getting a fresh backups
-
i migrated my backup that was running on a Minio instance on another Minio instance.
Since I've done this it's impossible for me to restore/clone apps. I have this error:External Error: Error loading fsmetadata.json:ENOENT: no such file or directory, open '/home/yellowtent/appsdata/66b1a0bd-7a9e-497b-bba8-c5772ed40fc4/fsmetadata.json'
I tried trick found elsewhere on the forum that consisted changed the backup method ( rsync to tarball then save then back to rsync then cleanup backups) but nothing does it.
thanks
-
@TheNils So, you copied files from one external minio to another external minio ? How did you do the migration ? Note that afaik minio doesn't work by just copying over files. You have to use their API to migrate. I think Cloudron restore is saying that the backup is not found in the new server (the metadata file has information on directories/files).
-
-
@girish yes , my problème is that cloning any apps installed before the new backup configuration fail with the error reported earlier, even from new backups stored on the currently configured minio.
the same happen on my two cloudrin servers -
@TheNils Sorry, the current situation is not clear to me. Is the issue with migration or is the issue with minio in general? The thread started with migration but I think your previous post is now saying that normal minio backup and restore does not work. Can you please clarify?
-
@girish to clarify the situation:
Since I changed the configuration of the backups I can no longer clone the apps that were installed before the change.
example :
"app A" is installed since January 1st 2020
"app B" is installed since January 1st 2024
I changed the configuration on January 1st 2022I can clone "App B" from its backup of January 2nd 2024.
I can't clone "App A" from its backup of January 2nd 2024, I have the error mentioned earlier.I'm only talking about cloning because I don't want to try to restore "App A" for fear of being stuck with the same error
-
@girish App A is up and running
i have made some more test today and results are mitigated...
on Cloudron 1 the problème seem to be gone, i can't explain why...On Cloudron 2 the errors only occure on wordpress(unmanaged) apps.
-
-