First of all, thank you for continuously shipping new features for Databasement.
As a practitioner with substantial database experience, I’d like to share and discuss a few real-world scenarios:
Case 1: Multi-DC deployment
In multi-DC environments, based on our experience, we strongly prefer backup and storage to be completed within the same DC, for the following reasons:
-
The total backup data volume within a single DC is often over 10TB, so cross-DC data transfer costs and efficiency issues become very significant.
-
From a recovery/rebuild perspective, having backups in the same DC can significantly shorten recovery time.
-
We usually use a layered backup strategy like this:
- Keep 2–3 days of backups on additional local physical disks for fast recovery/rebuild when an instance has issues, so business can recover quickly.
- Keep 7 days of backups on a dedicated backup machine group in the same DC for fast recovery from host-level catastrophic failures (rarely needed, but important).
- Keep 2–3 months of backups in S3 as the final safety net.
Given this case, it would be excellent if Agent could be deployed on each DB host to handle these tasks.
Case 2: Cold backup vs. hot backup
Most current backup approaches are essentially cold-backup based. In production, however, cold backup alone often cannot fully meet data reliability requirements.
If hot backup capabilities can be combined with existing strategies, the overall value can be maximized. Of course, this is a long journey—we also spent a long time implementing this internally.
First of all, thank you for continuously shipping new features for Databasement.
As a practitioner with substantial database experience, I’d like to share and discuss a few real-world scenarios:
Case 1: Multi-DC deployment
In multi-DC environments, based on our experience, we strongly prefer backup and storage to be completed within the same DC, for the following reasons:
The total backup data volume within a single DC is often over 10TB, so cross-DC data transfer costs and efficiency issues become very significant.
From a recovery/rebuild perspective, having backups in the same DC can significantly shorten recovery time.
We usually use a layered backup strategy like this:
Given this case, it would be excellent if Agent could be deployed on each DB host to handle these tasks.
Case 2: Cold backup vs. hot backup
Most current backup approaches are essentially cold-backup based. In production, however, cold backup alone often cannot fully meet data reliability requirements.
If hot backup capabilities can be combined with existing strategies, the overall value can be maximized. Of course, this is a long journey—we also spent a long time implementing this internally.