Immutable object locking for snapshot management
Methods, systems, and devices for data management are described. A data management system (DMS) may receive an indication of a storage configuration for an object storage location within a cloud environment. The DMS may generate a snapshot of a computing system in accordance with a backup policy associated with the computing system. The DMS may cause one or more data objects corresponding to the snapshot to be stored in the object storage location within the cloud environment in accordance with the storage configuration. The DMS may apply immutable object locks to the one or more data objects within the object storage location. The DMS may execute, in accordance with the backup policy associated with the computing system, one or more jobs that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot.
1. A method for data management, comprising:
receiving, at a data management system configured to manage data for a computing system in accordance with a backup policy, an indication of a storage configuration for an object storage location within a cloud environment;
transferring, by the data management system and in accordance with the storage configuration, one or more data objects corresponding to a snapshot of the computing system for storage in the object storage location within the cloud environment, wherein the snapshot comprises a computing file that represents a state of the computing system, and wherein respective immutable object locks are applied to the one or more data objects within the object storage location; and
outputting, by the data management system and in accordance with the backup policy associated with the computing system, one or more object lock commands that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot, the retention period based at least in part on the backup policy.
2. The method of claim 1 , wherein the one or more object lock commands are configured to extend an incremental object lock on a first data object after the retention period based at least in part on determining that the first data object is referenced in a subsequent snapshot of the computing system.
3. The method of claim 1 , wherein the one or more object lock commands are configured to delete a first data object from the object storage location after the retention period based at least in part on determining that the first data object is not referenced in any subsequent snapshots of the computing system.
4. The method of claim 1 , wherein the one or more object lock commands are configured to extend the respective immutable object locks on the one or more data objects for a threshold lock duration specified in the storage configuration for the object storage location.
5. The method of claim 1 , wherein:
the one or more object lock commands are configured to periodically extend an immutable object lock on a first data object two or more times during the retention period of the snapshot in accordance with the backup policy associated with the computing system.
6. The method of claim 1 , wherein the one or more object lock commands are configured to extend a first immutable object lock on a first data object stored in the object storage location prior to a scheduled expiration of the first immutable object lock.
7. The method of claim 1 , further comprising:
receiving, at the data management system, an indication of an updated backup policy for the computing system, the updated backup policy indicating an updated retention period for the snapshot; and
determining, by the data management system, whether to extend the respective immutable object locks on the one or more data objects based at least in part on the updated backup policy for the computing system.
8. The method of claim 1 , wherein the one or more object lock commands are configured to extend an immutable object lock on a first data object stored in the object storage location for a duration that is less than a threshold lock duration based at least in part on a difference between an expiration time associated with the immutable object lock and an end of the retention period for the snapshot.
9. The method of claim 1 , wherein causing the one or more data objects to be stored in the object storage location comprises:
determining, by the data management system, that two or more instances of a data object are stored in the object storage location in association with different snapshots of the computing system,
wherein the one or more object lock commands are configured to apply an immutable object lock to at most one of the two or more instances of the data object stored in the object storage location.
10. The method of claim 1 , further comprising:
detecting, by the data management system, a lock extension failure associated with transmission of the one or more object lock commands; and
outputting, by the data management system, an indication of the lock extension failure.
11. The method of claim 1 , wherein the one or more data objects are transferred a threshold time duration after generating the snapshot, the threshold time duration specified in the backup policy associated with the computing system.
12. The method of claim 1 , wherein the snapshot is a part of a snapshot chain that comprises at least one full snapshot of the computing system and one or more incremental snapshots of the computing system.
13. The method of claim 12 , wherein the one or more object lock commands are configured to extend an immutable object lock on a data object from a different snapshot in the snapshot chain for at least the retention period of the snapshot based at least in part on determining that the data object is referenced in the snapshot.
14. The method of claim 1 , wherein the respective immutable object locks comprise time-based object settings that prevent users from deleting or modifying the one or more data objects while the respective immutable object locks are active.
15. The method of claim 1 , wherein the snapshot comprises a full snapshot of the computing system or an incremental snapshot of the computing system, the full snapshot indicating a state of the computing system at a first time, the incremental snapshot indicating changes to the computing system between the first time and a second time.
16. The method of claim 1 , wherein:
the snapshot comprises backup data associated with the computing system; and
the backup data from the snapshot is partitioned into the one or more data objects.
17. An apparatus for data management, comprising:
a processor;
memory coupled with the processor; and
instructions stored in the memory and executable by the processor to cause the apparatus to
receive, at a data management system configured to manage data for a computing system in accordance with a backup policy, an indication of a storage configuration for an object storage location within a cloud environment;
transfer, by the data management system and in accordance with the storage configuration, one or more data objects corresponding to a snapshot of the computing system for storage in the object storage location within the cloud environment, wherein the snapshot comprises a computing file that represents a state of the computing system, and wherein respective immutable object locks are applied to the one or more data objects within the object storage location; and
output, by the data management system and in accordance with the backup policy associated with the computing system, one or more object lock commands that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot, the retention period based at least in part on the backup policy.
18. The apparatus of claim 17 , wherein the one or more object lock commands are configured to extend an incremental object lock on a first data object after the retention period based at least in part on determining that the first data object is referenced in a subsequent snapshot of the computing system.
19. The apparatus of claim 17 , wherein the one or more object lock commands are configured to delete a first data object from the object storage location after the retention period based at least in part on determining that the first data object is not referenced in any subsequent snapshots of the computing system.
20. A non-transitory computer-readable medium storing code for data management, the code comprising instructions executable by a processor to:
receive, at a data management system configured to manage data for a computing system in accordance with a backup policy, an indication of a storage configuration for an object storage location within a cloud environment;
transfer, by the data management system and in accordance with the storage configuration, one or more data objects corresponding to a snapshot of the computing system for storage in the object storage location within the cloud environment, wherein the snapshot comprises a computing file that represents a state of the computing system, and wherein respective immutable object locks are applied to the one or more data objects within the object storage location; and
output, by the data management system and in accordance with the backup policy associated with the computing system, one or more object lock commands that cause the respective immutable object locks for the one or more data objects to be extended one or more times during a retention period for the snapshot, the retention period based at least in part on the backup policy.