Instantly bucket size is increasing. What could be the issue? What is the best practice to follow here? My concern is GCP storage.
Solved
Instantly Bucket Size Increased
+4Best answer by matheusgiovanini
When you see the bucket size growing very fast or “instantly”, in most cases this is expected behavior rather than an issue, but it does require validation.
In object storage (including GCP Cloud Storage), Veeam does not overwrite data. Every new restore point creates new objects, especially when immutability is enabled. Old objects remain stored until their retention period expires, even if they are no longer referenced by active backups.
The most common reasons for rapid bucket growth are:
Immutability enabled, Short backup intervals or high change rate, Active Fulls or Backup Chain Changes, Retention not yet reached, Object Storage behavior is not “real-time cleanup”
+9When you see the bucket size growing very fast or “instantly”, in most cases this is expected behavior rather than an issue, but it does require validation.
In object storage (including GCP Cloud Storage), Veeam does not overwrite data. Every new restore point creates new objects, especially when immutability is enabled. Old objects remain stored until their retention period expires, even if they are no longer referenced by active backups.
The most common reasons for rapid bucket growth are:
Immutability enabled, Short backup intervals or high change rate, Active Fulls or Backup Chain Changes, Retention not yet reached, Object Storage behavior is not “real-time cleanup”
+21Check your job settings to see how it is configured - is GFS enabled which can cause bucket growth as well. Also check the job settings for the sizing of the blocks when sending to your object storage because if they were changed at some point this can cause growth too.
+12Instantly bucket size is increasing. What could be the issue? What is the best practice to follow here? My concern is GCP storage.
There are several possible causes for the anomaly you reported:
- Retention settings are too long
- Incremental backups accumulating
- GFS (Grandfather-Father-Son) retention
- Deleted VMs still in backups
- Large change rate
- Backup copy jobs - Secondary copies duplicate your data
Do you have any further details to provide?
+4Check your job settings to see how it is configured - is GFS enabled which can cause bucket growth as well. Also check the job settings for the sizing of the blocks when sending to your object storage because if they were changed at some point this can cause growth too.
In my case GFS not exist backup happening throguh the gcp appliance and it is web base but no option for GFS
+4Instantly bucket size is increasing. What could be the issue? What is the best practice to follow here? My concern is GCP storage.
There are several possible causes for the anomaly you reported:
- Retention settings are too long
- Incremental backups accumulating
- GFS (Grandfather-Father-Son) retention
- Deleted VMs still in backups
- Large change rate
- Backup copy jobs - Secondary copies duplicate your data
Do you have any further details to provide?
Summary:
- Retention settings are too long ( less then 3 months )
- Incremental backups accumulating ( Daily )
- GFS (Grandfather-Father-Son) retention no GFS
- Deleted VMs still in backups ( In GCP if any VM deleted no more consider in backup it give warning message only )
- Large change rate ( as of now i cannot see anything yet )
- Backup copy jobs - Secondary copies duplicate your data ( No copy job configure )
+21Is immutability set on GCP? That to me seems like the only culprit otherwise support might be able to shed some light.
+4Is immutability set on GCP? That to me seems like the only culprit otherwise support might be able to shed some light.
Point to be noted will check this from the GCP side.
+4thanks you
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.