I tried to migrate my discourse instance to a new server, and restore via UI and CLI fail during restore operation. It has to do with S3 migration. I also had these settings enabled in rails console SiteSetting.migrate_to_new_scheme = true Jobs::MigrateUploadScheme.new.execute(nil) The relevant log from the failure was: Remapping '//thinnal.s3.dualstack.us-east-1.amazonaws.com/' to '/uploads/default/' incoming_emails=2 optimized_images=3851 post_revisions=86 posts=618 stylesheet_cache=10 topic_links=107 topics=150 uploads=419 user_histories=20 Migrating uploads to S3... Checking if default already migrated... 1971 of 1977 uploads are not migrated to S3. S3 migration failed for db 'default'. 266 posts are not remapped to new S3 upload URL. S3 migration failed for db 'default'. Looking for missing uploads on: default 0 post uploads are missing. No posts require rebaking Migrating uploads to S3 for 'default'... Some uploads were not migrated to the new scheme. Please run these commands in the rails console SiteSetting.migrate_to_new_scheme = true Jobs::MigrateUploadScheme.new.execute(nil) Restore process was cancelled! Trying to rollback... Rolling back... Cleaning stuff up... Dropping function from the discourse_functions schema Removing tmp '/var/www/discourse/tmp/restores/default/2019-09-02-140750' directory... Unpausing sidekiq... Marking restore as finished... Notifying 'system' of the end of the restore... Finished! [FAILED] Restore done.

That’s a known problem. As a workaround, you could temporarily disable the enable_s3_uploads site setting before creating the backup. You can re-enable on the new server after the restore.

There is a similar report of you search. I think the solution was to turn off S3 uploads when you restore?

Thanks @pfaffman Let me try that. Do you know of any command line (rails console) way to disable s3 upload?

Thank you!. Yes, I disabled upload to S3 before taking the backup, and then the restore was successful.

Hi, What to do if a backup was made while it was enabled :slight_smile:

I solved; I open dump.sql with EmEditor program and search enable_s3_uploads, S3 and all “t” to “f” all “true” to “false”. Restore successful :slight_smile:

Well, then you’ll have to get your hands dirty. Sorry about that. I’m planning to start refactoring and improving backups and restores next week, but it can take a while until everything’s peachy again. [image] MuhYal: Restore successful :slight_smile: That’s great! I was going to suggest exactly those steps. :wink: For anyone reading this in the future: If you need to edit the dump.sql (which might be quite large), I suggest Scintilla and SciTE as editor. It handles those large files without problems.

Restore from backup fails due to S3 migration

Product Support

Senthil (Senthil Kumaran) September 2, 2019, 3:01pm 4

The Uploads to S3 was disabled during the restore. It still failed.

Topic		Replies	Views
Restore process cancelled at migrating uploads to S3 step Product Support	48	4025	January 24, 2026
Restore from a Backup Product Support	4	771	June 16, 2020
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1270	June 10, 2022
Intended path to migrate S3 to local Self-hosting uploads , s3	5	990	May 13, 2023
Unable to migrate to S3, therefore unable to restore from backup Self-hosting	2	1375	March 9, 2022

Restore from backup fails due to S3 migration

Related topics