Recovering data lost in data de-duplication system
First Claim
Patent Images
1. A method, comprising:
- receiving an indication that a data object is to be deleted, wherein the data object comprises data stored in a segment within a container;
determining no currently alive data object references any segment within the container, wherein an alive data object refers to a data object being actively used or stored by one or more of the following;
a user, a system, and an administrator;
placing the container in a delete-ready state, wherein a delete-ready state is a state indicating the container is ready for deletion but not yet reclaimable;
recording metadata reflecting a temporal order in which the container was placed in the delete-ready state relative to one or more other containers being placed in the delete-ready state;
retaining in a segment index, at least for as long as the container remains in the delete-ready state, a segment index data associated with the container;
receiving an indication that a trigger event to reclaim storage space has occurred; and
changing the container from the delete-ready state to a deleted state in which storage space associated with the container is subject to being reclaimed based at least in part on the indication that the trigger event has occurred and said metadata reflecting the temporal order in which the container was place in the delete-ready state.
9 Assignments
0 Petitions
Accused Products
Abstract
An indication is received that a data object is to be deleted, wherein the data object comprises data stored in a segment within a container. It is determined no currently alive data object references any segment within the container. The container is placed in a delete-ready but not yet reclaimable state.
27 Citations
20 Claims
-
1. A method, comprising:
-
receiving an indication that a data object is to be deleted, wherein the data object comprises data stored in a segment within a container; determining no currently alive data object references any segment within the container, wherein an alive data object refers to a data object being actively used or stored by one or more of the following;
a user, a system, and an administrator;placing the container in a delete-ready state, wherein a delete-ready state is a state indicating the container is ready for deletion but not yet reclaimable; recording metadata reflecting a temporal order in which the container was placed in the delete-ready state relative to one or more other containers being placed in the delete-ready state; retaining in a segment index, at least for as long as the container remains in the delete-ready state, a segment index data associated with the container; receiving an indication that a trigger event to reclaim storage space has occurred; and changing the container from the delete-ready state to a deleted state in which storage space associated with the container is subject to being reclaimed based at least in part on the indication that the trigger event has occurred and said metadata reflecting the temporal order in which the container was place in the delete-ready state. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A system, comprising:
-
a garbage collector coupled to a container manager and configured to; determine no currently alive data object references any segment within the container, wherein an alive data object refers to a data object being actively used or stored by one or more of the following;
a user, a system, and an administrator;the container manager configured to; receive an indication that a data object is to be deleted, wherein the data object comprises data stored in a segment within the container; place the container in a delete-ready state after the determination, wherein a delete-ready state is a state indicating the container is ready for deletion but not yet reclaimable; record metadata reflecting a temporal order in which the container was placed in the delete-ready state relative to one or more other containers being placed in the delete-ready state; retain in a segment index, at least for as long as the container remains in the delete-ready state, a segment index data associated with the container; receive an indication that a trigger event to reclaim storage space has occurred; and change the container from the delete-ready state to a deleted state in which storage space associated with the container is subject to being reclaimed based at least in part on the indication that the trigger event has occurred and said metadata reflecting the temporal order in which the container was place in the delete-ready state; a processor configured to execute instructions for the garbage collector and the container manager; and a memory coupled to the processor and configured to provide the processor with said instructions. - View Dependent Claims (16, 17)
-
-
18. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
-
receiving an indication that a data object is to be deleted, wherein the data object comprises data stored in a segment within a container; determining no currently alive data object references any segment within the container, wherein an alive data object refers to a data object being actively used or stored by one or more of the following;
a user, a system, and an administrator;placing the container in a delete-ready state, wherein a delete-ready state is a state indicating the container is ready for deletion but not yet reclaimable; recording metadata reflecting a temporal order in which the container was placed in the delete-ready state relative to one or more other containers being placed in the delete-ready state; retaining in a segment index, at least for as long as the container remains in the delete-ready state, a segment index data associated with the container; receiving an indication that a trigger event to reclaim storage space has occurred; and changing the container from the delete-ready state to a deleted state in which storage space associated with the container is subject to being reclaimed based at least in part on the indication that the trigger event has occurred and said metadata reflecting the temporal order in which the container was place in the delete-ready state. - View Dependent Claims (19, 20)
-
Specification