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.

Restauración fallida: "Algunas cargas no se pudieron migrar al nuevo esquema"

Soporte

RGJ (Richard - Communiteq) 9 Julio, 2020 22:56 4

¿Has probado desactivar las cargas en S3 antes de crear la copia de seguridad?
Solo desactivar S3 y no volver a crear la copia no debería causar ningún daño. Luego, restaura y vuelve a activar S3.

Restore process cancelled at migrating uploads to S3 step

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

Restauración fallida: "Algunas cargas no se pudieron migrar al nuevo esquema"

Temas relacionados