The recommendation to perform the backups when your instance runs fewer operations is related to performance. Changes are not recommended because the backup is going to use resources.
In this document, it tells that writes and other operations are unaffected, which means that writes and other operations will not be part of the backed up data. So, the on-demand backup is atomic and it is not recommended to run your risky operations at the same time as they may impact the use of resources. Check this Stack Overflow post or more details on Postgres backups.
Hi guys,Was wondering if the on demand backup is atomic - i.e. once I start it, it freezes the current state and any changes after starting (and before finishing) are not reflected?I.e. do I need to wait for the backup to finish before running my risky operations or I can just go ahead once it's acknowledged?
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/fe2e2c4e-22a8-4066-8031-ec76ce4538b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment