# Dvc copy/merge repo strategy?

**URL:** <https://discuss.dvc.org/t/dvc-copy-merge-repo-strategy/1785>\
**Category:** Questions\
**Created:** [September 28, 2023, 12:23pm UTC](https://discuss.dvc.org/t/dvc-copy-merge-repo-strategy/1785 "2023-09-28T12:23:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnAtl](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.dvc.org/johnatl/32/365_2.png) [@JohnAtl](https://discuss.dvc.org/u/JohnAtl)\
**Post date:** [September 28, 2023, 12:23pm UTC](https://discuss.dvc.org/t/dvc-copy-merge-repo-strategy/1785/1 "2023-09-28T12:23:16Z")

</div>

Context:  
I have a repo I used through ssh on my iMac Pro. I’ve since begun using a local repo at `/tank/data`. It would be cool to combine them into one massive blob-o-data.

Thoughts?:  
I have backups of .dvc along with its cached files. Let’s say .dvc/config used to point to the iMac. Would it be feasible to:

- Remove the iMac as the remote
- Add /tank/data as the remote
- dvc push --all-commits --all-tags --all-branches

Restore another backup whose .dvc/config (and cached files) previously pointed to /tank/data.

- dvc push --all-commits --all-tags --all-branches

Now all commits are in /tank/data (?)  
If the commits already exist, are they skipped? The docs for dvc push seem to indicate they would be.

Thanks!