Backup in JSON format
1 vote
Hello,
I am writing to request a feature enhancement for Devolutions Server. Currently, the system allows for exporting data in various formats, but I would like to suggest adding an option to export the data in JSON format with encryption.
This feature would be incredibly valuable for users who wish to store their backups externally (e.g., in cloud storage or Blob storage) while ensuring that sensitive data is securely protected. By exporting the data in encrypted JSON format, users would be able to leverage both the flexibility of the JSON format and the security of encrypted backups, all within one solution.
Moreover, having the ability to export backups in an encrypted JSON format would be particularly beneficial in emergency scenarios. If the entire system goes down, the backup could be quickly and securely loaded into Devolutions Hub for recovery, enabling businesses to resume operations with minimal downtime.
The ability to export data in an encrypted JSON file would greatly enhance both the flexibility and security of backup management. It would also streamline the recovery process in case of system failure, ensuring that users can quickly access their critical data without relying on the entire Devolutions Server system being online.
All Comments (3)
Hello,
I have a few questions for you to help ensure I understand your needs properly.
- Are you looking to backup only the entry list from your vaults? If that's the case, we already have a feature to export entries in RDM (which includes the JSON format), so we could extend this to Devolutions Server as Hub as well
- Are you looking for the encryption to apply to the entire JSON file? When we export as JSON in RDM, we can currently encrypt the file with a password, meaning the entire file will be encrypted with it, and not only the sensitive data
If you're looking for a complete backup (think disaster recovery), I would recommend instead looking into those two articles in our knowledgebase, which will help you perform a more comprehensive backup of your entire server:
https://docs.devolutions.net/server/kb/how-to-articles/dvls-disaster-recovery/
https://docs.devolutions.net/server/web-interface/administration/backup/backup-manager/
Assuming you'd like to backup your entries, then I believe the JSON export we have in RDM would work for what you need and we would need to support it in DVLS and Hub's web interfaces.
Let me know what you think.
Regards,
Hubert Mireault
Hi Hubert,
Thanks for the clarification.
To better explain our use case:
We already use the built-in disaster recovery options in Devolutions Server, including database backups, server backups and application backups. For standard recovery scenarios, this works well.
Our request is specifically for a full-environment outage scenario.
We also store backups externally in Blob storage. In the event that our complete DVLS environment becomes unavailable (server failure, infrastructure outage, corruption, ransomware recovery scenario, etc.), restoring the full environment can take time.
What we are looking for is an additional recovery layer.
The ability to export the complete contents of a vault as a single encrypted JSON file, including ideally:
- all entries
- folder structure
- metadata / permissions where possible
This file could then be:
- automatically backed up to external Blob storage
- quickly imported into Devolutions Hub
This would allow us to become operational again very quickly while the full (DVLS) infrastructure is being restored in parallel.
So this is not intended to replace existing disaster recovery mechanisms, nor is it simply an entry export equivalent to RDM.
The value would be a portable encrypted vault snapshot for rapid operational failover / temporary cloud recovery.
That is the distinction we are trying to make.
Thank you for the additional information. I understand what you mean. We will have to discuss this internally and see what kinds of solutions we could come up with.
I will also get back to you if we have any alternative methods that already exist that you may not have yet explored.
Regards,
Hubert Mireault