Volume group garbage collection

A system comprising:

• a container orchestration platform configured to host containers capable of executing applications having access to an object store;
• and
• an active data connector hosted within a container of the container orchestration platform, wherein the active data connector is configured to:
• determine that a volume group backup is to be deleted from the object store, wherein the volume group backup is of a volume group comprised of a plurality of constituent volumes backed up to the object store as a plurality of constituent volume backups;
• generate a group garbage collection workflow for deleting the volume group backup from the object store;
• implement the group garbage collection workflow to modify a group level metafile to indicate that the volume group backup is ready for deletion;
• generate a set of individual garbage collection workflows for the plurality of constituent volume backups;
• orchestrate the execution of the set of individual garbage collection workflows to modify item level metafiles for the plurality of constituent volume backups to indicate that the plurality of constituent volume backups are ready for deletion;
• and
• in response to receiving notifications that the item level metafiles have been modified to indicate that the plurality of constituent volume backups are ready for deletion, execute a garbage collection process to free slots within objects of the object store that store backup data unique to the plurality of constituent volume backups and not shared with other volume group backups or snapshots.

A non-transitory machine readable medium comprising instructions, which when executed by a machine, causes the machine to:

• determine that a volume group backup is to be deleted from an object store, wherein the volume group backup is of a volume group comprised of a plurality of constituent volumes backed up to the object store as a plurality of constituent volume backups;
• generate a group garbage collection workflow for deleting the volume group backup from the object store;
• implement the group garbage collection workflow to modify a group level metafile to indicate that the volume group backup is ready for deletion;
• generate a set of individual garbage collection workflows for the plurality of constituent volume backups;
• orchestrate the execution of the set of individual garbage collection workflows to modify item level metafiles for the plurality of constituent volume backups to indicate that the plurality of constituent volume backups are ready for deletion;
• and
• in response to receiving notifications that the item level metafiles have been modified to indicate that the plurality of constituent volume backups are ready for deletion, execute a garbage collection process to free slots within objects of the object store that store backup data unique to the plurality of constituent volume backups and not shared with other volume group backups or snapshots.