# Restore process cancelled at migrating uploads to S3 step

**URL:** https://meta.discourse.org/t/restore-process-cancelled-at-migrating-uploads-to-s3-step/123233
**Category:** Support
**Created:** [7월 17, 2019, 8:58오후 UTC](https://meta.discourse.org/t/restore-process-cancelled-at-migrating-uploads-to-s3-step/123233 "2019-07-17T20:58:20Z")
**Posts on this page:** 1
**Showing post:** 24

<div class="post-metadata">

### Author: ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)
#### Post date: [12월 13, 2020, 6:50오후 UTC](https://meta.discourse.org/t/restore-process-cancelled-at-migrating-uploads-to-s3-step/123233/24 "2020-12-13T18:50:18Z")

</div>

@gerhard

다시 시도해 봤지만 여전히 \_44개의 게시물이 재매핑되지 않았습니다\_라는 오류에서 복원 실패가 반복되고 있습니다.

백업 전에 S3 업로드를 일시적으로 비활성화하는 방법(@RGJ가 제안한 방식)으로는 문제가 해결되지 않으며, 현재 제대로 작동하는 백업 구성이 전혀 없는 상태라 상당히 심각한 상황입니다.

> [@복원 실패: "일부 업로드를 새 스키ماً 이식할 수 없음"](https://meta.discourse.org/t/restore-failed-some-uploads-could-not-be-migrated-to-the-new-scheme/157061/4?u=ljpp):
>
> Have you tried turning off s3 uploads prior to creating the backup? Just turning off S3 and not rebaking should not do any harm. Then restore and switch S3 back on.

어떤 방법을 시도해 볼 수 있을까요? 조언을 부탁드립니다.

---

_[View the full topic](https://meta.discourse.org/t/restore-process-cancelled-at-migrating-uploads-to-s3-step/123233)._