Persistent Snap Shot
Are taken in an incremental fashion. What happens is that, by default is making use of GCS in the background that takes a full back-up. If the data changes when taking the second snapshot, it will actually capture the incremental change. For example: If a snap shot was taken at 1pm - 2pm, it will only capture the data after 2pm for the next hour. The longer the back-up the higher the risk. You have to be strategic when designing your architecture to optimize cost.
The back-up will be stored in form of object. Technically, snap shot is global in nature. For example, you have a snapshot in us-east1, you can call out the snapshot in us-west-2. You can share snapshot across different projects in your organization with the use of one single operation.
TWO MODES OF SNAP SHOT
Every snapshot is encrypted by default. And the data is protected.
1. Manual : You can make use of gcloud(CLI). One of the challenges with manual snap is error, more engineer, time consuming, cost, inconsistent.
2. Automated Approach: Snapshot scheduler will help your automate snapshot. Snapshot scheduler will require you to set up a policy, one of the policy will be, how often do you want to take the snapshot, everyday, weekly, monthly. You can specify the start time and end time. You need to define the snapshot retention period( 10, 20, 50 copies).
Referencing : Google Cloud
No comments:
Post a Comment