QuestionQ130

VerifiedEnsuring the successful operation of a cloud solution

You are working with a Cloud SQL for MySQL database at your company. You need to retain a month-end copy of the database for three years for audit purposes.

What should you do?

Explanation

Cloud SQL backups are managed by Cloud SQL according to retention policies and are stored separately from the instance: standard backups in the same project as the instance, and enhanced backups in a centralized backup management project. Retention length is not the obstacle (standard on-demand backups are stored indefinitely until manually deleted, and enhanced backups support custom retention periods up to 10 years), but a backup is not a file that you can write to a Cloud Storage bucket you choose (B, C) or turn into an export file (D). Exports are different: they are created from the instance's data and written to Cloud Storage, where you manage the lifecycle. To keep an independently controlled month-end copy for three years, schedule an export job on the first of each month that writes a SQL dump file to a Cloud Storage bucket. The Archive storage class fits because it is the lowest-cost storage class and the best choice for data that you plan to access less than once a year; its 365-day minimum storage duration is well within the three-year retention period.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!