I have been trying to do restores from one server to another for a couple of days now. The original server was started back in 2016, so has had some legacy issues. I started to tackle this problem when an old cert expired, and then got bogged down into a range of problems during the backup/restore c…

Have you tried turning off s3 uploads prior to creating the backup? Just turning off S3 and not rebaking should not do any harm. Then restore and switch S3 back on.

Soooo. I’m still stuck on this one. I managed to get my old server up and running again by messing around with putting it behind an nginx server and getting the cert that way (has a different site running on the same domain). But I would still like to migrate. I’m also afraid I wouldn’t be able to …

Yep, that did it! Wow! That was a much simpler solution than I would have guessed.

Ripristino non riuscito: "Alcuni caricamenti non sono stati migrati al nuovo schema"

Supporto

RGJ (Richard - Communiteq) 9 Luglio 2020, 10:56pm 4

Hai provato a disattivare i caricamenti su S3 prima di creare il backup? Disattivare solo S3 senza rifare il backup non dovrebbe causare danni. Quindi ripristina e riattiva S3.

Restore process cancelled at migrating uploads to S3 step

Argomento		Risposte	Visualizzazioni
Unable to migrate to S3, therefore unable to restore from backup Self-hosting	3	1217	Aprile 8, 2022
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1093	Giugno 10, 2022
Restore fails when including S3 uploads Self-hosting backups , s3	4	552	Giugno 20, 2024
Restore process cancelled at migrating uploads to S3 step Support	49	2857	Gennaio 24, 2026
Restore from backup fails due to S3 migration Support	9	1278	Ottobre 10, 2019

Ripristino non riuscito: "Alcuni caricamenti non sono stati migrati al nuovo schema"

Argomenti correlati