How to backup Firebase realtime database when the payload is too large (256MB)
1–10 of 11 posts
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#2There seems to be a misunderstanding here, backups in cloud storage are a fraction of the cost of data in Firebase. I used to work with a 300GB Firebase instance and we never worried about backup costs.
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#3I clicked the link to the script at the bottom of the blog post thinking it would be a github link. It downloaded a file with the contents "Please provide your databaseURL." Seems like the script is being executed by the author's web server instead of returning the contents of the file. It was also a (hopefully) friendly reminder to myself to not click random links on the internet without checking where they go.
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#4This is a poorly written article with a broken link to the script.
Also for some reason Cmd+C causes your selection to go away on this site?
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#5I think the backups end up stored in a GCS bucket in your account and can be removed manually or with an object lifecycle.
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#6I think the backups end up stored in a GCS bucket in your account and can be removed manually or with an object lifecycle.
That is correct, but it adds a step and also doesn't give you the freedom of deciding which backups to keep older than 1 month.
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#7I think the author has a fundamental misunderstanding of how the built in backups work. The backup likely goes into Google Cloud Storage which is relatively cheap.
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#8I think the backups end up stored in a GCS bucket in your account and can be removed manually or with an object lifecycle.
That is correct, but it adds a step and also doesn't give you the freedom of deciding which backups to keep older than 1 month.
Isn't it easier and cheaper to download the backup from GCS than to pull data from Realtime Database?
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#9I clicked the link to the script at the bottom of the blog post thinking it would be a github link. It downloaded a file with the contents "Please provide your databaseURL." Seems like the script is being executed by the author's web server instead of returning the contents of the file. It was also a (hopefully) friendly reminder to myself to not click random links on the internet without checking where they go.
thanks for catching that! Fixed.
Re: How to backup Firebase realtime database when the payload is too large (256MB)
#10I think the author has a fundamental misunderstanding of how the built in backups work. The backup likely goes into Google Cloud Storage which is relatively cheap.
That is correct but personally I like to be able to decide the backup intervals and not have to create a whole script to connect to GCS.