# Bucket recovery

**URL:** <https://forum.storj.io/t/bucket-recovery/22938>\
**Category:** Product Discussions\
**Created:** [June 13, 2023, 1:21pm UTC](https://forum.storj.io/t/bucket-recovery/22938 "2023-06-13T13:21:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![litecactus](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/litecactus/32/1135_2.png) [@litecactus](https://forum.storj.io/u/litecactus)\
**Post date:** [June 13, 2023, 1:21pm UTC](https://forum.storj.io/t/bucket-recovery/22938/1 "2023-06-13T13:21:31Z")

</div>

Soooooo I moved some files using Minio `mc` command line tool from Storj to Minio and for whatever reason, the files are broken on the Minio cluster. Maybe I used the wrong passphrase but because some work some don’t, I need to recover and redo.

Is there a way of recovering a bucket? Muppet here used `mv` not `cp`

---

<div class="post-metadata">

**Author:** ![zeebo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zeebo/32/7300_2.png) [@zeebo](https://forum.storj.io/u/zeebo)\
**Post date:** [June 13, 2023, 7:20pm UTC](https://forum.storj.io/t/bucket-recovery/22938/2 "2023-06-13T19:20:32Z")

</div>

It’s unlikely you used the wrong password as decryption will fail if the wrong password is used. If the files are gone, then they’re gone and there’s nothing that can be done.

The only thing is to confirm they really are gone: if you try to list a bucket with the wrong password it won’t show any files, so with the uplink command line you can try `uplink ls --encrypted` which skips decryption of the filenames and see if the files are still there with their encrypted names.

I’m happy to answer any more questions. Good luck!

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [June 14, 2023, 3:45am UTC](https://forum.storj.io/t/bucket-recovery/22938/3 "2023-06-14T03:45:14Z")

</div>

Yes, I would suggest the same - please check the bucket without decryption, maybe your objects are still there. But you would have a different problem in this case - you would need to remember, what encryption phrase you have used when uploaded these objects to the Storj bucket.

But if you deleted a bucket too, then there is no way to recover it back, unless you did a server-side copy before moving/deletion, i.e.

```auto
uplink mb sj://mybucket-backup
uplink cp --recursive sj://my-bucket sj://mybucket-backup

```

---

<div class="post-metadata">

**Author:** ![litecactus](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/litecactus/32/1135_2.png) [@litecactus](https://forum.storj.io/u/litecactus)\
**Post date:** [June 14, 2023, 8:31am UTC](https://forum.storj.io/t/bucket-recovery/22938/4 "2023-06-14T08:31:37Z")

</div>

Thanks all so far. I didn’t delete the bucket so I tried the `--encrypted` command but got nothing back.

I connected to Storj using Minio `mc` CLI with S3 credentials, so its not like the objects might still be encrypted is it?

Weirdly some of the larger video files work but the photos don’t, I don’t see how that works, let me know if anything comes to mind.

---

<div class="post-metadata">

**Author:** ![litecactus](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/litecactus/32/1135_2.png) [@litecactus](https://forum.storj.io/u/litecactus)\
**Post date:** [June 14, 2023, 9:02am UTC](https://forum.storj.io/t/bucket-recovery/22938/5 "2023-06-14T09:02:37Z")

</div>

I FIXED IT! (on the other side)

people, don’t use `mv`

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [June 15, 2023, 4:37am UTC](https://forum.storj.io/t/bucket-recovery/22938/6 "2023-06-15T04:37:08Z")

</div>

> [@litecactus](#):
>
> Weirdly some of the larger video files work but the photos don’t, I don’t see how that works, let me know if anything comes to mind.

In that case you had an access, so encryption phrase behind used s3 credentials was correct.

> [@litecactus](#):
>
> I FIXED IT! (on the other side)

I’m glad to read, that you fixed an issue!  
`mv` command could be safe, if the destination is reliable.
