Cannot import app backup from other cloudron

[guyds]

I'm trying to import an app backup from one server into another. The app is wordpress and the backups are stored on an sshfs backend.

First of all I noticed there is no sshfs storage provider available on the "import backup" screen on the new cloudron.
So I exported the app's backup config json file on the old cloudron and upload that file on the new one.
Unfortunately that doesn't work either because it's giving the following error:

Error : External Error - Error loading fsmetadata.json:ENOENT: no such file or directory, open '/home/yellowtent/appsdata/e6c7c611-a2ed-4b1b-8456-f3d95729ad40/fsmetadata.json'

So 2 issues here:

• sshfs provider is missing
• import from backup config gives error

[nebulon]

@guyds indeed, the logic behind the mountpoint backup storages is more complex and is not yet supported by the app import.

You have to fallback to the filesystem provider and place all the files from the backup into a custom folder on the new system, then fill out that form accordingly.

[guyds]

@nebulon I see, but how is this any different from the "restore to this backup" action? I mean, if you backup a Cloudron and its apps to an sshfs storage provider it is possible - I hope - to restore an individual app to a previous state. In this case the files also have to be retrieved from an ssh backend.

Regarding the app import process you suggest: is it sufficient to only copy over the most recent folders or should I copy the full backup (which can become quite large)?

Is there any ETA on when sshfs will be supported?

Maybe it's also a good idea to add a notification about this "incompatibility" in the backup configuration screen when selecting sshfs or another storage provider that's currently not supported?
E.g. "Note: this storage provider is currently not supported for app import".

[nebulon]

@guyds I will try to add this to the next version.

You have to copy the latest backup this should contain the full set. The backup config json file you can download via the dashboard will contain some information to find it on disk by the backup ID.

[guyds]

@nebulon said in Cannot import app backup from other cloudron:

@guyds I will try to add this to the next version.

That would be great, thanks!

You have to copy the latest backup this should contain the full set. The backup config json file you can download via the dashboard will contain some information to find it on disk by the backup ID.

Ok, thanks for the clarification. I'll try it that way.

[guyds]

Much to my disappointment I just noticed that this issue still exists.
In other words, I still cannot import a backup from an sshfs location because it's still giving the error

Error : External Error - Error loading fsmetadata.json:ENOENT: no such file or directory

The only way to get the app imported on a new cloudron is by manually copying over the backup to the local filesystem.

(Edit: typo)

[girish]

@guyds yes, unfortunately, the fix did not make it to 7.4.

[girish]

I think https://forum.cloudron.io/topic/8672/move-local-backup-to-another-server was the same issue.

[guyds]

@girish said in Cannot import app backup from other cloudron:

@guyds yes, unfortunately, the fix did not make it to 7.4.

Any timeframe for when the fix will be available?

@girish said in Cannot import app backup from other cloudron:

I think https://forum.cloudron.io/topic/8672/move-local-backup-to-another-server was the same issue.

Hmmm, I'm don't see any issues mentioned in that post, it just seems to be a request for best practices regarding backups

[girish]

@guyds Whoops, you are right. I meant https://forum.cloudron.io/topic/8707/backup-restore-is-not-working and specifically https://forum.cloudron.io/topic/8707/backup-restore-is-not-working/5. There is a bug in the import functionality that it doesn't mount SSHFS/CIFS/NFS correctly before import.

[guyds]

@girish that sounds as being the same issue indeed.
So if I understand correctly you already know what the issue is and how to fix it and now it's just a matter of finding some time to actually implement it

[girish]

Fixed in 7.5.1

[guyds]

@girish Thanks!