# Help restoring - system hung at midnight **URL:** \ **Category:** Self-hosting\ **Created:** [June 9, 2022, 9:14am UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486 "2022-06-09T09:14:20Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\ **Post date:** [June 9, 2022, 11:49am UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/8 "2022-06-09T11:49:18Z")
I think this may be because your backup contains a mix of S3 and local uploads. I’m afraid it’s not my area of expertise, but there is some discussion and a workaround in this topic which allows you to bypass the failure. However, it was for a much smaller number of errors so you may want to take that into account: > [@Migrate\_to\_s3 fails](https://meta.discourse.org/t/migrate-to-s3-fails/209499/26): > > Looking at the error message from your previous post, it’s the count on line 85 which is of interest. @Falco’s suggestion for editing the script is to increase that count to ignore some number of failures. The simplest way to achieve that is by entering the container and using sed to make an in-place substitution on that specific line. cd /var/discourse ./launcher enter app sed -i '85s/0/100/' lib/file\_store/to\_s3\_migration.rb Run the rake task again after that and it will ignore up to 100 “p… --- _[View the full topic](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486)._