Automated Snapshots
-
goldmember
- Posts: 8
- Joined: 09 Aug 2022, 20:59
Is there any way of achieving automated snapshots? If this action was available through the API we could trigger it that way, but I don't see an option.
We have this on our roadmap. We're still kicking around requirements, e.g. once your snapshot quota is full do you just overwrite or do you notify the user and get them to delete? Should we allow you to lock some snapshot so they are not deleted/overwritten. Any thoughts would be welcomed.
What is the snapshot quota in Essential Cloud? Haven't reached it (just yet), but it's good to know.
I'd suggest that for automated snapshots, if the quota is reached, it should be removing the older automated snapshot, but keep all the manual snapshots.
I'd suggest that for automated snapshots, if the quota is reached, it should be removing the older automated snapshot, but keep all the manual snapshots.
-
goldmember
- Posts: 8
- Joined: 09 Aug 2022, 20:59
IMO, I would follow the approach of "do no harm". If the quota has been reached then the API call should return a meaningful error. Presumably, if we had full management of snapshots over API, users could accommodate automatic deletes as well based on their requirements.JohnM wrote: 06 Jun 2024, 12:43 We have this on our roadmap. We're still kicking around requirements, e.g. once your snapshot quota is full do you just overwrite or do you notify the user and get them to delete? Should we allow you to lock some snapshot so they are not deleted/overwritten. Any thoughts would be welcomed.
-
francis.bb.udes
- Posts: 2
- Joined: 18 Aug 2025, 18:59
If you are still working on requirements, being able to have different schedules with a "keep num of backup" would be best. We could automate a weekly keep 52 and do a daily keep14 and always be withinn the quota
-
neil.walsh
- Posts: 482
- Joined: 16 Feb 2009, 13:45
- Contact:
The auto snapshot feature will create a "backup" of a repository separate from the manual snapshots.
In addition to the manual snapshots, for each repository, it will keep:
7 daily backups
4 weekly backups
3 monthly backups
These backups cannot be deleted or modified but obviously can be restored. The backup schedule is managed by us and non-configurable. We've taken this approach to make sure all customers benefit from this feature without requiring user intervention and also to allow us to optimise performance and resource usage. The feature development is complete however we require some technical improvements to the underlying platform before we can roll this out. This is scheduled for Q4 this year but until that work is underway, I wouldn't be able to give a firm date.
We are also hoping to add an API endpoint for manual snapshots to improve our coverage in this area and meet the needs where our auto-snapshot feature isn't enough.
Hope that helps!
In addition to the manual snapshots, for each repository, it will keep:
7 daily backups
4 weekly backups
3 monthly backups
These backups cannot be deleted or modified but obviously can be restored. The backup schedule is managed by us and non-configurable. We've taken this approach to make sure all customers benefit from this feature without requiring user intervention and also to allow us to optimise performance and resource usage. The feature development is complete however we require some technical improvements to the underlying platform before we can roll this out. This is scheduled for Q4 this year but until that work is underway, I wouldn't be able to give a firm date.
We are also hoping to add an API endpoint for manual snapshots to improve our coverage in this area and meet the needs where our auto-snapshot feature isn't enough.
Hope that helps!
