Google Cloud Storage backups use Event Scan to reduce scan time for incremental backups. This is especially useful for buckets that contain millions of objects.
Event Scan uses Google Cloud Storage object change events to identify objects that were created, modified, or deleted since the last backup operation. Commvault uses these events to detect changes efficiently instead of scanning the entire bucket during incremental backups.
Requirements
- Configure an object storage for Google Cloud Storage backups with Service account as authentication.
Permissions
Make sure the required permissions are in place before configuring an incremental scan.
For more information, see Permissions to Back Up Google Cloud Buckets.
How incremental backups work with storage events
-
During the initial full backup, Commvault establishes the backup baseline for the bucket.
-
Google Cloud Storage records object change events for objects that are created, modified, or deleted in the bucket.
-
Subsequent incremental backups use these storage events to identify changes since the previous backup operation.
-
Only changed objects are scanned and processed during incremental backups, which reduces scan time and improves performance for large buckets.
Planning considerations
-
Event Scan is most beneficial for buckets that contain millions of objects.
-
Event Scan reduces the need to scan the entire bucket during incremental backups.
-
Changes are detected by using Google Cloud Storage object change events.
What's not supported
-
Event Scan is not supported for buckets with Hierarchical Namespace (HNS) enabled.
-
Object storage for Google Cloud Storage backups is not supported for instances with access key and Secret key as authentication.