Keep in mind that stopping an instance will not stop all costs generated by it: it stops the costs associated with the instance itself, but the storage used and any IPs continue to be charged [1].
Regarding the storage usage increase:
· If you have storage auto increase enabled, the disk could have increased during a time in which the available amount of storage was not enough
· Binary logs can also impact the amount of storage used [2], so if this option is not necessary for your use case you can disable it
· Also keep in mind that you get charged by storage capacity and not by storage used.
If this is a billing related question I suggest you to try the billing troubleshooter [3] or contact the Billing team [4]
___________
[1]: https://cloud.google.com/sql/docs/mysql/start-stop-restart-instance#stop
[2]: https://cloud.google.com/sql/docs/mysql/backup-recovery/pitr#disk-usage
[3]: https://support.google.com/cloud/troubleshooter/7279311
[4]: https://cloud.google.com/support/billing/
On Thursday, July 1, 2021 at 10:04:16 AM UTC+2 sergey.s...@gmail.com wrote:
Why do I get increasing storage usage even though my db instance is shut down most of the time, I use it only for a few hours a week, and it has data that takes less than 20mb in size.There was initial usage of ~1GB, but why did it increased to 3GBs?
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/cb5c5eec-af33-4858-9faf-064f03ae969bn%40googlegroups.com.
No comments:
Post a Comment