[image]Set up file and image uploads to S3 Once these are done (and the uploads are working well) you no longer need to include uploads in your backups. And as a bonus, you will be able to Restore a backup from command line in the event of catastrophe (just keep a copy of app.yml somewhere). Unfortunately this does not work. I have 10 full backs ups and I can’t restore any of them, they’re all giving me the same errors: Reconnecting to the database... Reloading site settings... Disabling outgoing emails for non-staff users... Disabling readonly mode... Clearing category cache... Reloading translations... Remapping uploads... Restoring uploads, this may take a while... Migrating uploads to S3 for 'default'... Uploading files to S3... - Listing local files => 5 files - Listing S3 files .. => 1911 files - Syncing files to S3 ..... Updating the URLs in the database... Removing old optimized images... Flagging all posts containing lightboxes for rebake... 285 posts were flagged for a rebake EXCEPTION: 509 of 1823 uploads are not migrated to S3. S3 migration failed for db 'default'. /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log' /var/www/discourse/lib/file_store/to_s3_migration.rb:79:in `migration_successful?' /var/www/discourse/lib/file_store/to_s3_migration.rb:373:in `migrate_to_s3' /var/www/discourse/lib/file_store/to_s3_migration.rb:66:in `migrate' /var/www/discourse/lib/file_store/s3_store.rb:328:in `copy_from' /var/www/discourse/lib/backup_restore/uploads_restorer.rb:62:in `restore_uploads' /var/www/discourse/lib/backup_restore/uploads_restorer.rb:44:in `restore' /var/www/discourse/lib/backup_restore/restorer.rb:61:in `run' script/discourse:149:in `restore' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor/base.rb:485:in `start' script/discourse:290:in ` ' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:58:in `load' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:58:in `kernel_load' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:23:in `run' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/cli.rb:483:in `exec' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/cli.rb:31:in `dispatch' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/cli.rb:25:in `start' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/exe/bundle:48:in `block in ' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.3.13/exe/bundle:36:in ` ' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in ` ' Trying to rollback... Why is this happening? I’ve seen many folks report the issue but there’s no solution that I’ve come across as yet. Backup and restore is a very fundamental need.

Yes, the entire solution was posted here [image] Help restoring - system hung at midnight Self-hosting Okay this was bound to happen, things were just too good for too long. Years of running on cruise control, the system would automatically update itself and I would update Discourse every few weeks. At midnight last night, Amazon showed the system was unresponsive, discourse was down and the CPU was pegged at 100% until it ran out of AWS CPU resources. Couldn’t login to the system, the one time after several reboots I was able to login momentarily, I saw this in htoptaking up a lot of CPU snap l…

(I’m cleaning up the replies to the other topic so that they can be cleared out. It’s not clear that you got this resolved, so I didn’t want to delete it.) Did you get this resolved? It has to do with the fact that it’s trying to upload images to S3 and/or assure that they are all there and they are not. A solution I think I’ve seen is to turn off upload to S3 during the restore and then turn it back on.

Can't restore backup with images on S3

Product Support

RBoy (RBoy) December 8, 2022, 4:55am 3

Yes, the entire solution was posted here

Topic		Replies	Views
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1253	June 10, 2022
Restore fails due to s3 migration failure Product Support	2	166	August 12, 2026
Restore from a Backup Product Support	4	760	June 16, 2020
Restore fails when including S3 uploads Self-hosting backups , s3	4	669	June 20, 2024
Unable to migrate to S3, therefore unable to restore from backup Self-hosting	2	1366	March 9, 2022

Can't restore backup with images on S3

Related topics