On 6/23/2024 I lowered number of days of backups stored from 35 to 14.
I think when TermHub development stops, we should lower this to a lower number. It looks like the minimum is 7.
Additionally, it'd be nice to back up like 1x/week rather than 1x/day, but it doesn't look like there's an option for that.
Also, it is set to 'geo-redundant'. I think if we didn't have it this way, it might be cheaper. But it looks like this setting for backups is coupled to the actual DB deployment, which is set to geo-redundant. Maybe that's a good thing though. And IDK how much money we'd save by changing this.
I did get set up with someone who was supposed to look into these options with me, especially the geo-redundancy (though now I understand more), but I accidentally just archived the email and now I can't find it.
Overview
On 6/23/2024 I lowered number of days of backups stored from 35 to 14.
I think when TermHub development stops, we should lower this to a lower number. It looks like the minimum is 7.
Additionally, it'd be nice to back up like 1x/week rather than 1x/day, but it doesn't look like there's an option for that.
Also, it is set to 'geo-redundant'. I think if we didn't have it this way, it might be cheaper. But it looks like this setting for backups is coupled to the actual DB deployment, which is set to geo-redundant. Maybe that's a good thing though. And IDK how much money we'd save by changing this.
I did get set up with someone who was supposed to look into these options with me, especially the geo-redundancy (though now I understand more), but I accidentally just archived the email and now I can't find it.
Additional information