I’ve been running into issues trying to run a restore on our Staging Discourse instance. Staging is running v2.4.0.beta1 +36 . Any idea where the breakdown might be or where to look? Thanks in advance! Below is the end of the log output: [2019-07-16 20:08:12] ALTER TABLE [2019-07-16 20:08:12] ALTER…

Discourse keeps a backup schema so it can roll back when a restore goes bad. You can go into your Postgres and issue drop schema backup cascade; If you don’t know how to do that you shouldn’t probably be doing it.

[immagine] ljpp: not remapped to new S3 I think that the code that does the check is here: lib/file_store/to_s3_migration.rb main base_url = File.join(SiteSetting.Upload.s3_base_url, prefix) count = Upload.by_users.where("url NOT LIK…

discourse(prod)> prefix = @migrate_to_multisite ? “uploads/#{RailsMultisite::ConnectionManagement.current_db}/original/” : “original/” discourse(prod)> base_url = File.join(SiteSetting.Upload.s3_base_url, prefix) discourse(prod)> bad_uploads = Upload.by_users.where(“url NOT LIKE ‘#{base_url}%’”) …

Did you do that on the original server? Or you need to do it after the database has restored before it does that check, using the --pause switch

I did on the old server. Restoring I got the same error [2026-01-16 13:45:52] EXCEPTION: 3 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’. [2026-01-16 13:45:52] /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log’

[immagine] Saiano: This check gave me 0 errors Well. Darn. Not sure what else to tell you. Did the good find your uploads? I’d probably just use the --pause switch and stop the restore before it does that check. I’d do what Richard said.

I’m not sure about your exact situation but you might simply want to turn off s3 uploads, make the backup, restore, and turn it on again. This has saved me many times.

So, I have to turn off this options, correct? [image]

Correct. uncheck “enable s3 uploads” backup / download upload / restore check “enable s3 uploads”

[immagine] RGJ: Correct. uncheck “enable s3 uploads” backup / download upload / restore check “enable s3 uploads” While checking “enable s3 uploads” I got an error [IMG_8462]

I don’t speak Italian when it’s not about food… maybe you can do us all a favor and copy/paste it into Google Translate :slight_smile:

Processo di ripristino annullato durante la migrazione dei caricamenti a S3

Supporto

RGJ (Richard - Communiteq) 17 Gennaio 2026, 3:49pm 35

Non sono sicuro della tua situazione esatta, ma potresti semplicemente voler disattivare i caricamenti s3, eseguire il backup, ripristinare e riattivare. Questo mi ha salvato molte volte.

2 Mi Piace

Argomento		Risposte	Visualizzazioni
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1072	Giugno 10, 2022
Restore from backup fails due to S3 migration Support	9	1241	Ottobre 10, 2019
Restore to New Host Support	13	609	Gennaio 15, 2026
Intended path to migrate S3 to local Self-hosting uploads , s3	5	809	Maggio 13, 2023
Unable to migrate to S3, therefore unable to restore from backup Self-hosting	3	1195	Aprile 8, 2022

Processo di ripristino annullato durante la migrazione dei caricamenti a S3

Argomenti correlati