# Unable to migrate to S3, therefore unable to restore from backup

**URL:** <https://meta.discourse.org/t/unable-to-migrate-to-s3-therefore-unable-to-restore-from-backup/220484>\
**Category:** Self-hosting\
**Created:** [March 9, 2022, 2:21am UTC](https://meta.discourse.org/t/unable-to-migrate-to-s3-therefore-unable-to-restore-from-backup/220484 "2022-03-09T02:21:40Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![teward](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/teward/32/148702_2.png) [@teward](https://meta.discourse.org/u/teward)\
**Post date:** [March 9, 2022, 2:21am UTC](https://meta.discourse.org/t/unable-to-migrate-to-s3-therefore-unable-to-restore-from-backup/220484/1 "2022-03-09T02:21:41Z")

</div>

So, I have a Discourse backup from our initial server and we’re trying to move the system to a new system.

Unfortunately, there are two problems:

1. During restore, it says that 71 of 1073 uploads are not migrated to S3, and therefore hard-fails during the restore process.

2. Attempting to fix this on the _main_ instance by rebaking, etc. the posts, it indicates some uploads are still not migrated to S3, even when I try and use the `uploads:migrate_to_s3` rake mechanism.

Is there **any** way to get verbose information from `migrate_to_s3` as to _which_ uploads are not migrated, so I can manually fix it? It’s possible also that they are referring to a dead/failed S3 repository from where we were initially uploading to, except that things exploded at that point and we simply switched S3 mechanisms (to MinIO of course), and there was still old stuff sitting in the AWS S3 side of things. Which I don’t think I can easily migrate to our MinIO instance.

Alternatively, is there a way to disable the restore mechanism’s uploads on s3 checker because I just forced the migration of uploads myself already?

---

_[View the full topic](https://meta.discourse.org/t/unable-to-migrate-to-s3-therefore-unable-to-restore-from-backup/220484)._