Problems Restoring Full Snapshot - Cloudron 8.0.3 - CIFS Restore Method
-
The main problem
I can't restore any of the previous cloudron backups/snapshot into a new instance of cloudron successfully. Seams to load with errors and corrupt services. Not sure what to do.https://www.loom.com/share/d28ed53d01d848459937e13e114a79c8
issues.
Mail not importing
Multiple service failure
as soon I i restart any service, error messages popup and if I restart msql the may Linux high powered server service crashesThe apps look like they are together but I can't restart any red services as soon as i do it crashes everything.
I have tried several differnt backups dating back up to two weeks, and the errors still persist.
Fresh Ubuntu 20.04
Cloudron 8.0.3 install -
I was able to restore access through by uploading the backups to amazon S3, however it was not without one syntax issue that delayed the process
if the backup id is anything other then 2024-08-15-030000-742/box_v8.0.3 , it will through an error message, we had a slash like this /2024-08-15-030000-742/box_v8.0.3 it will through a broken path error, which was difficult to debug since we did not have the config file.
Still not sure why the CIFS mounts throughs an error though.
-
@affinity said in Problems Restoring Full Snapshot - Cloudron 8.0.3 - CIFS Restore Method:
it will through an error message, we had a slash like this /2024-08-15-030000-742/box_v8.0.3 it will through a broken path error, which was difficult to debug since we did not have the config file.
I guess the error message simply said "Not found" ? Unfortunately, those paths are quite backend specific. Meaning paths can sometimes start with "/" depending on the s3 implementation . For example, https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html does not mention it. In fact, in the DeleteObject example at the very end, it uses "/" as starting character ....
I think the best way to fix it is to make the restore code show the listing of backups in the remote and they you can select the backup path. However, this requires a lot of work.
I am looking to see if we have a regression with CIFS restore.
-
G girish marked this topic as a question on
-
Since I see some mongodb errors in the video you posted, I wonder - are you trying to restore from AVX to non-AVX server or vice-versa?
-
Can't reproduce this. If you can reach out to us at support@cloudron.io with the logs of the failed instance (if you happen to have it), I can look into it further .
-
G girish has marked this topic as solved on
-
@girish it said gzip tarExtract pipeline error: Backup not found: affinitydesign-backup/2024-04-08-030000-684/app_academyoflifemontessori.com_v2.25.0.tar.gz
Its just really picky with the syntax. We did end up restoring successfully by uploading our backups to S3 and then setting the correct path.
We have abadoned the CIFS method now since it caused to much headache. A rep in our company pointed out that with that method, mnt/cloudronbackup was being appended to the backup path on the front end after the restore button was pressed, which you can see in the loom video, however it clearly failed to mount all the data and that was indeed what was throwing all those errors.
-
@girish One thing to note, all stopped apps where not imported through the restore method even tho they had backups retained with them. We are still trying to find and recover those apps atm, but they must be buried in a random 2024-04-08-030000-684 folder. Never the less.
Is it possible to recover data from the snapshot folder? what is that for if backups pull from the other folders? I think our stopped apps are in there but Im not sure how to recover them through the front end that way.
One thing that would have made this process so much more seamless is just including that restore config file in the snapshot folder, and the corresponding configs for each app backup, would have saved us hours of finding the correct backup id manually for each method, since Im assuming they are slightly different?
