Note This only makes sense if Enpass is setup to sync.

If Enpass is setup to sync, I'm thinking it would make sense to:

1. Backup locally to a default location that can be changed by the user & offer the option to move existing backups if the directory changes.
2. Backup remotely based on the Sync settings - no user control here

Furthermore, when setting up Enpass if a user selects the option to restore data:

1. Enpass would check the sync location for the restore data and if data is found, ask if they want to restore data
2. If they choose yes, allow them to choose which data point to restore (e.g.: Tuesday 12/27, Sunday 12/25 etc.)

Thanks for your inputs @Phylum

1 hour ago, Phylum said:

Backup locally to a default location that can be changed by the user & offer the option to move existing backups if the directory changes.

Enpass doesn't take multiple backups for syncing data. The latest data on the device is synced with the latest data on the cloud and then merged with the file on the device. Though in the latest release, we have introduced that option of Auto backups in the desktop versions where you can change the location also.

1 hour ago, Phylum said:

Backup remotely based on the Sync settings - no user control here

All the popular cloud services generally keep the version history of any file and you can have a look at them by logging into your cloud service. 

 

1 hour ago, Phylum said:

Enpass would check the sync location for the restore data and if data is found, ask if they want to restore data

Enpass works in the same fashion.

 

1 hour ago, Phylum said:

1. If they choose yes, allow them to choose which data point to restore (e.g.: Tuesday 12/27, Sunday 12/25 etc.)

This is something we can really look into where Enpass will check all the previous versions stored by the cloud service and will list all of them to let the user choose the backup file he wants to restore.

Hope this helps!

For what its worth, I'm a WebDAV/ownCloud user with versioning setup.