LinkedIn
Twitter
Hello! We are exploring the use of the firestore scheduled backup and restore operations, especially since it has graduated out of alpha and into general availability.
We ran backup and restore test with our development Firestore database to determine . Our development database is 80GB in size. When we ran the restore operation, we observed that we were billed for a restoration operation of 2,400GB, exactly 30x the size of the backup. Below is an image that showcases we have a single backup copy of 80.07GB (we know its one copy as our database is billed for a size of 80.13GB) and a restoration operation billed for 2,402.11GB.
These are the commands run to create the backup schedule and create the restoration:
```
# creation
gcloud alpha firestore backups schedules create \
--database=(default) \
--retention=3d \
--recurrence=daily
# restoration
gcloud alpha firestore databases restore \
--source-backup=projects/<project>/locations/nam5/backups/<unique-backup-identifier> \
--destination-database='delete_me_restored_db_2024_06_25'
```
Is this 30x cost expected? I anticipated a backup restortation cost billed at 80GB. We would love to use native firestore backups instead of our current export method of taking backups, but given our production database's size of 6TB, this would be cost prohibitive. I anticipate that this is a billing error, but want to make sure I'm not misunderstanding a core concept of how firestore backups are performed. Thanks!
