cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
We love to hear how every person gets the most from Dropbox, and it seems everyone has a slightly different use for it - tell us yours here!

Dropbox files & folders

Get in sync with the Dropbox Community. Our members can answer all your questions on Dropbox files and folders. Join a discussion or start your own today.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

On system restored from a backup: stop Dropbox pushing old state as though it's new modifications?

On system restored from a backup: stop Dropbox pushing old state as though it's new modifications?

OwenAR
Explorer | Level 3

How do I make sure that Dropbox,
when it's running on a system that was just restored from a backup (eg using timeshift or whatever),
doesn't push old versions of files as though they're new modifications?

 

For example, let's say I have two computers running Dropbox:

- computer_one

- computer_two

and a file synced between them:

- file_X

 

And then let's say I:

 

- make a backup of computer_two

(

using something like timeshift for example

(

which basically just uses rsync
both to make a copy for backups,
and to put everything back for restores

)

)

 

- modify file_X on computer_one

 

- restore computer_two to its previous state (ie, before file_X was modified)

 

In the past, in at least similar situations,
I've had problems with Dropbox on the restored computer_two
where it would try to push the older version of file_X
(ie, from before it was modified)
rewriting the newer version (on the Dropbox cloud and on computer_one),
as though the restored, unmodified, older version of file_X
was actually the *latest* new modification to file_X.

 

Obviously, I can avoid this problem by simply removing Dropbox from the restored computer_two
and manually adding it back,
but that involves having the restored computer_two download all the synced file from scratch.

 

And obviously, that's much slower and more annoying and non-ideal,
but I don't want to risk messing around experimenting with any quicker ways,
unless I can be confident I won't accidentally revert file_X to an out-of-date state.


---
As far as I can tell, relevant stuff might be contained in all of:

~/.dropbox/
~/.dropbox-dist/
~/Dropbox/

 

Is there just some config/cache file/directory in there I could simply delete?
(and just exclude from my backups in the first place)

 

ie, the desired end result is that,
when I first boot up the restored computer_two,
and start Dropbox,
it knows to only propagate state from the cloud *to* computer_two's Dropbox,
and never *from* computer_two's Dropbox,
until computer_two's Dropbox is up to date again.


Thank you if you can help!

1 Reply 1

Re: On system restored from a backup: stop Dropbox pushing old state as though it's new modificat...

Hannah
Dropboxer
Hey @OwenAR, thanks for posting on our Community!

The way the Dropbox application works is, it detects changes in your Dropbox folder and syncs them to your account.

So, if you make any changes to a syncing Dropbox folder, those changes will sync as the most recent.

You can always use our version history feature, to return a file back to a previously synced version.

Also, I would suggest you post your ideas about this on our idea board, so other users can upvote them and perhaps they can be implemented.

Let me know if you have any questions.

Hannah
Community Moderator @ Dropbox
dropbox.com/support


Heart Did this post help you? If so, please give it a Like below.
:arrows_counterclockwise: Still stuck? Ask me a question!
:pushpin: Tips & Tricks Find new ways to stay in flow or share your tips on how you work smarter with Dropbox.

Who's talking

Top contributors to this post

  • User avatar
    Hannah Dropboxer
What do Dropbox user levels mean?
Need more support?