determine GFS points in object storage

[lowlander]

How can I determine what GFS backup files ( monthly e.g. ) are present in object storage ( capacity tier ) of an SOBR ?

It's hard to determine which objects are present and which are not when using object lock for the capacity tier.

[Mildur]

Hi lowlander

Have you tried backup properties?

It's hard to determine which objects are present and which are not when using object lock for the capacity tier.

Can you tell me what‘s the hard part of it? All restore points will be offloaded. It doesn‘t depend on the object lock setting.

Thanks
Fabian

[lowlander]

Hi Fabian,

Backup properties is the way to go, however...

the amount of storage for object storage is tripple the data capacity of the backup files in the performance tier. We use copy mode, and we are aware that the immutable setting on the capacity tier is causing a +10 days retention on restorepoint ( holding the lock ), causing a storage increase.

the hard part is that we want to verify that GFS points are still located in the object storage, while they are not visible in the backup properties. In the object storage environment we can't relate the objects stored in the S3 structure, to the specific monthly GFS points.

So basically we want to check if there are any "orphaned" GFS restore points that causing additional storage consumption.

[Mildur]

Thanks.

the amount of storage for object storage is tripple the data capacity of the backup files in the performance tier. We use copy mode,

That doesn‘t sound right. I recommend to check it out with our support.

So basically we want to check if there are any "orphaned" GFS restore points that causing additional storage consumption.

A GFS backup doesn‘t use the entire space in object storage. Even if you delete a gfs restore points, only unique blocks can be removed. Blocks which are never changed between the backups will be references by other restore points and therefore can not be removed from the capacity tier.
It‘s definitely something for our support to check. The relation of objects to restore point is not available for the enduser. And we don‘t support manipulation in the bucket. This can lead to more issues.

[veremin]

the amount of storage for object storage is tripple the data capacity of the backup files in the performance tier.

Agree with Fabian here - the situation does not look correct. So want to ask a question - how exactly did you determine the space consumption? In object storage or in backup server UI? Thanks!