-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Labels
bugProblem when deploying a Data Safe Haven.Problem when deploying a Data Safe Haven.
Milestone
Description
✅ Checklist
- I have searched open and closed issues for duplicates.
- This is a problem observed when managing a Data Safe Haven.
- I can reproduce this with the latest version.
- I have read through the documentation.
- This isn't an open-ended question (open a discussion if it is).
💻 System information
- Operating System:
- Data Safe Haven version: 5.0.1
📦 Packages
List of packages
Paste list of packages here
🚫 Describe the problem
Backup not functional, workaround in docs doesn't work.
A major problem here is, the storage account types we have chosen (for good reasons of performance, ability to upload/download to/from) are not compatible with Azure backup services.
🚂 Workarounds or solutions
Because of the incompatibility, I think our two options are
- Change the type of storage accounts we use to ones which are compatible
- This will mean we loose nice features like performance, nice integration with NFS, upload/download using Azure storage explorer
- Quite a significant infrastructure change to make
- Implement our own backup
- Requires writing/supporting our own solution
- There are off-the-shelf tools we could use (I think Borg/Borgmatic)
- Should be fairly simple to implement with a VM or container, as we can mount all of our storage as NFS
- I have a proposal for how this would look using Borg/Borgmatic in the comments below
Metadata
Metadata
Assignees
Labels
bugProblem when deploying a Data Safe Haven.Problem when deploying a Data Safe Haven.
Type
Projects
Status
In progress