# Snapshot Migrated - How to change ownership

**URL:** <https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152>\
**Category:** Support\
**Created:** [August 3, 2024, 4:49am UTC](https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152 "2024-08-03T04:49:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dunny53](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@dunny53](https://kopia.discourse.group/u/dunny53)\
**Post date:** [August 3, 2024, 4:49am UTC](https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152/1 "2024-08-03T04:49:17Z")

</div>

I have migrated a repository to an S3 Bucket on a different host PC.  
I now want to refresh the snapshots but cannot because they have retained the original owner.  
How can I change the ownership.  
I have changed the maintenance Owner Ok.

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [August 3, 2024, 5:42am UTC](https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152/2 "2024-08-03T05:42:17Z")

</div>

> **[snapshot move-history](https://kopia.io/docs/reference/command-line/common/snapshot-move-history/)**
>
> $ kopia snapshot move-history \[destination\] Performs a move of the history of snapshots from another user or host. This command will move snapshot manifests of the specified source to the respective destination. This is typically used when renaming...

---

<div class="post-metadata">

**Author:** ![dunny53](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@dunny53](https://kopia.discourse.group/u/dunny53)\
**Post date:** [August 3, 2024, 10:38am UTC](https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152/3 "2024-08-03T10:38:41Z")

</div>

Thanks. This worked OK.  
I still have issues with the interaction between cmd line versus kopia-ui.  
To reflect the ownership changes I had to disconnect the kopia-ui session , this then forces you to recreate the connection again. If you leave all configured sessions connected on the gui all OK but don’t disconnect.  
I guess this relates the gui just creating multiple web sessions in the background. A tad frustrating.

I tried to go headless and ssh cmd line management but could never get multiple repositories connected.  
Sheer frustration made me install desktop and use kopia-ui.

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [August 3, 2024, 11:32am UTC](https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152/4 "2024-08-03T11:32:29Z")

</div>

> [@dunny53](#):
>
> I tried to go headless and ssh cmd line management but could never get multiple repositories connected.  
> Sheer frustration made me install desktop and use kopia-ui.

This is weird… I mostly use cmd and connecting to multiple repos works without any issues. Make sure you use `--config-file` flag to specify unique config file name. Otherwise new connection will overwrite previous one.

---

<div class="post-metadata">

**Author:** ![dunny53](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@dunny53](https://kopia.discourse.group/u/dunny53)\
**Post date:** [August 3, 2024, 9:22pm UTC](https://kopia.discourse.group/t/snapshot-migrated-how-to-change-ownership/3152/5 "2024-08-03T21:22:16Z")

</div>

Thanks for your help , I’m a GUI user normally , still learning cmd line approach.