# Remotely confused

**URL:** <https://discuss.dvc.org/t/remotely-confused/2006>\
**Category:** Questions\
**Created:** [March 21, 2024, 6:15pm UTC](https://discuss.dvc.org/t/remotely-confused/2006 "2024-03-21T18:15:39Z")\
**Posts on this page:** 2\
**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:** [March 21, 2024, 6:15pm UTC](https://discuss.dvc.org/t/remotely-confused/2006/1 "2024-03-21T18:15:39Z")

</div>

I have a folder with a .dvc/config file.

```plaintext
[core]
    remote = mnt-tank
    autostage = true
['remote "mnt-tank"']
    url = /mnt/tank/data/sleep

```

Previously, this was:

```plaintext
[core]
    remote = tank
    autostage = true
['remote "tank"']
    url = /home/john/tank/data/sleep

```

Everything seems to work fine. I can dvc push in the folder, and it says everything is up to date.  
But, if I want to be sure everything in the cache is in the newer mnt-tank remote, and I do this:  
`dvc push --all-commits --recursive --remote mnt-tank`  
In addition to listing thousands of (MD5-named) files that aren’t found, it tries to push files to the old remote location, `/home/john/tank/data/sleep`.

Can someone enlighten me as to what’s happening, and how I can push everything in the cache to the newer remote?  
Thanks!

---

<div class="post-metadata">

**Author:** ![dberenbaum](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@dberenbaum](https://discuss.dvc.org/u/dberenbaum)\
**Post date:** [March 22, 2024, 1:24pm UTC](https://discuss.dvc.org/t/remotely-confused/2006/2 "2024-03-22T13:24:44Z")

</div>

In the older commits, there is not `mnt-tank` remote found since it was only defined in the newer commit. A workaround is to setup `mnt-tank` in the local config at `.dvc/config.local` so that it will be used even if it’s not part of those older commits.