Just looking for some guidance and to understand potential differences in methods.
I'm using Box Sync with two PCs. I've followed the guidance on syncing KeePass with cloud systems (i.e. local 'real' kdbx's on each PC plus the designated 'cloud' kdbx's) and I've set up a trigger, as in the Trigger Examples help page, to sync these two kdbx's with an event of "saved database". Everything appears to work as promised.
However it struck me I really need to sync on opening the database as well to make sure I'm always working with the latest version. Surely the 'real' copy I use needs to get updated from the 'cloud' copy on opening, and the 'cloud' copy needs to get updated from the 'real' copy when I save? Is there any reason why only syncing on save is mentioned in the example, or have I overlooked something?
Tied in to this is how I implement the two sync actions. Is there any significant difference between having two separate triggers (each with one event), and having one trigger with two separate events? I assume the two events are OR'd in evaluation?
I feel like I'm very slowly inching my way through KeePass' features, gathering capabilities as I go. It's just little bits like this that I like to check to ensure I don't blunder in to potential future self-created problems.
Thanks and regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And yes, I have a separate backup regime to help in the event of catastrophes. I'm just trying to reduce the likelihood of catastrophes by understanding what I'm doing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all
Just looking for some guidance and to understand potential differences in methods.
I'm using Box Sync with two PCs. I've followed the guidance on syncing KeePass with cloud systems (i.e. local 'real' kdbx's on each PC plus the designated 'cloud' kdbx's) and I've set up a trigger, as in the Trigger Examples help page, to sync these two kdbx's with an event of "saved database". Everything appears to work as promised.
However it struck me I really need to sync on opening the database as well to make sure I'm always working with the latest version. Surely the 'real' copy I use needs to get updated from the 'cloud' copy on opening, and the 'cloud' copy needs to get updated from the 'real' copy when I save? Is there any reason why only syncing on save is mentioned in the example, or have I overlooked something?
Tied in to this is how I implement the two sync actions. Is there any significant difference between having two separate triggers (each with one event), and having one trigger with two separate events? I assume the two events are OR'd in evaluation?
I feel like I'm very slowly inching my way through KeePass' features, gathering capabilities as I go. It's just little bits like this that I like to check to ensure I don't blunder in to potential future self-created problems.
Thanks and regards
The examples are just that, examples. You can use them in any way you like.
Trigger Events are ORed, trigger Conditions are ANDed.
The best way to limit issues caused by anything is to backup regularly. I backup daily.
cheers, Paul
Excellent - thank you Paul.
And yes, I have a separate backup regime to help in the event of catastrophes. I'm just trying to reduce the likelihood of catastrophes by understanding what I'm doing.