Cloudron Forum

Yes, you are all correct, I just did Hetzner bucket w/ S3 credentials, backed up to it, and restored the apps from there. Super easy. Thank you.

yes, if the backup config has a password set, the UI will expect it to be entered before you can restore. You can use the top right menu to mark this as resolved.

@jdaviescoates The first one is from redis, it can be ignored. The second is the healtheck bot. It appears when the app is not up yet. That can be ignored as well. The final one is because the apache config has ServerName unset. Which app is this? Setting the ServerName to some dummy name makes it go away.

Thanks, it works.

@nebulon you were right. With the new version 7.3 the restore worked immediately and now baserow is running again. Thank you for the great support!

@nebulon Yeah I did. Forgot to mention it here. Thank you @girish !!

Thank you, it helped

@girish perfect! Thank you so much! I really highly appreciate the effort! Thanks! I see it now!

@RoboMod said in Restore backup doing nothing: "$scope.backupFolder https://forum.cloudron.io/topic/6388/scope-configurebackup-is-undefined/12 was the thread

@scooke I went to each individual app and pointed to the fileshare with the full path "/media/fileshare/2020-07-01-0500/app_backup.tar.gz.enc" and restored those backups. As for the second part, Azure adds the following "actimeo=30" switch to the cifs share that goes in your /etc/fstab file that causes the connection to time out if the backup takes too long. Once that is removed, reboot the server and the new backups will complete without issues.

@therealwebmaster If you mount it manually, use the Filesystem provider. Then, the backup path is simply /mounted-old-cloudron/var/backups/<timestamp>/box_<timestamp>_v<box_version>. See https://docs.cloudron.io/guides/download-backups/#backup-file-names for some hints.

@therealwebmaster https://aws.amazon.com/premiumsupport/knowledge-center/ec2-launch-issue/ is another idea to cleanup the disk. But otherwise, do you have external Cloudron backups? It's quite easy to recover from cloudron backups - see https://docs.cloudron.io/backups/#restore-cloudron .

@girish Thank you!! It worked with the version parameter!

@3246 yes, kind of like a torrent file where you can select priority per file/dir and which ones to skip. not sure a pause is needed, but more like a pre-start selection. I'm sure @staff can enumerate mail and other core services as required items but with flexible priority/order. Not only that, but while we're pondering that manual selection process with manual clicks, the essential bits can already be restored and ready for the next prioritized components.

Just to let anyone else know, I ran into the same issue with 7.2.0 when migrating servers and made the change that @girish mentioned and it still didn't work until I restarted docker (systemctl restart docker) and then it worked!

@MOrochena Ah yes, restores across different versions is not supported. Ideally, the error message could have been better though, I will fix that (i.e it should have said the version does not match instead of saying 'remotePath' must be a string!

Note to self: Use an external drive that has twice the disk space needed by the apps as a temporary mount point to restore to! Because it will need to download a copy of the whole backup, then unpack and finally bin the download. D'oh! Step 1: Find a disk with sufficient space to restore to (apps space x 2) Step 2: Mount the disk and symlink to the original location in the backup file Step 3: Restore and then reset the storage location (or point it to where ever your new mount point is). Got it all working now. Perhaps it's time to invest in a bigger SSD for my home server

@WaffleUncle So you are using the Import button in the app section, correct - https://docs.cloudron.io/backups/#import-app-backup ? In your case, it looks like your backups were in the file system and not external. If that is the case, you have to fill up the 'Import Backup' dialog manually: Upload the backup app_client.xxx.tar.gz to somewhere in the server like /tmp/app_client.xxx.tar.gz. In the import UI, Choose Filesystem Put the path as /tmp/app_client.xxx.tar.gz It should import now.

@3246 said in Restore Error - Cannot access 'error' before initialization: Do I always have to use the backup config (I did manage to change the path manually to point it to the latest backup after uploading the restore file)? No you don't need the backup file. https://docs.cloudron.io/backups/#restore-cloudron did you try to completely remove the mount and the configure it new?

@mehdi this was indeed a bug in the restore code path. the setupToken, as you guessed, should be sent in the top level object and not as part of the backupConfig . Fixed now.