Creation and implementation of designated time points in a version expiration environment
In one example, a method includes defining one or more curtains, each of which corresponds to a respective one or more designated points in time, using a calendar that is common to all of the curtains, defining one or more backup policies, defining, for each of the one or more backup policies, a respective set of one or more rules, associating each of the one or more backup policies with a respective curtain, and applying, to a backup version whose currency span includes one of the curtains, one of the backup policies that is associated with that curtain.
1. A method, comprising:
defining one or more curtains, each of which corresponds to a respective one or more designated points in time, using a calendar that is common to all of the curtains;
defining one or more backup policies;
defining, for each of the one or more backup policies, a respective set of one or more rules;
associating each of the one or more backup policies with a respective curtain; and
applying, to a backup version whose currency span includes one of the curtains, one of the backup policies that is associated with that curtain.
2. The method as recited in claim 1 , wherein the currency span of the backup version is based on a creation time of that backup version and a creation time of another backup version.
3. The method as recited in claim 1 , wherein the applied backup policy is applied, at the designated point in time, to the backup version whose currency span includes that designated point in time.
4. The method as recited in claim 1 , wherein the currency span includes one or more additional curtains.
5. The method as recited in claim 1 , wherein one of the one or more curtains corresponds to a plurality of designated points in time.
6. The method as recited in claim 1 , wherein the method is performed on an object-by-object basis.
7. The method as recited in claim 1 , wherein one of the rules of one of the backup policies does not specify an expiration time for a backup version.
8. The method as recited in claim 1 , wherein applying one of the backup policies comprises deleting a backup version that has expired, wherein the deleted backup version is a backup version that is not a current backup version.
9. The method as recited in claim 1 , wherein one or more of the rules defines a respective amount of time that can be added to a life of an associated backup version whose currency span crosses one or more curtains with which the one or more rules are respectively associated.
10. The method as recited in claim 1 , wherein one of the rules, when applied, assigns an expiration time to an associated backup version.
11. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, implement and/or cause the performance of operations comprising:
defining one or more curtains, each of which corresponds to a respective one or more designated points in time, using a calendar that is common to all of the curtains;
defining one or more backup policies;
defining, for each of the one or more backup policies, a respective set of one or more rules;
associating each of the one or more backup policies with a respective curtain; and
applying, to a backup version whose currency span includes one of the curtains, one of the backup policies that is associated with that curtain.
12. The non-transitory storage medium as recited in claim 11 , wherein the currency span of the backup version is based on a creation time of that backup version and a creation time of another backup version.
13. The non-transitory storage medium as recited in claim 11 , wherein the applied backup policy is applied, at the designated point in time, to the backup version whose currency span includes that designated point in time.
14. The non-transitory storage medium as recited in claim 11 , wherein the currency span includes one or more additional curtains.
15. The non-transitory storage medium as recited in claim 11 , wherein one of the one or more curtains corresponds to a plurality of designated points in time.
16. The non-transitory storage medium as recited in claim 11 , wherein the operations are performed on an object-by-object basis.
17. The non-transitory storage medium as recited in claim 11 , wherein one of the rules of one of the backup policies does not specify an expiration time for a backup version.
18. The non-transitory storage medium as recited in claim 11 , wherein applying one of the backup policies comprises deleting a backup version that has expired, wherein the deleted backup version is a backup version that is not a current backup version.
19. The non-transitory storage medium as recited in claim 11 , wherein one or more of the rules defines a respective amount of time that can be added to a life of an associated backup version whose currency span crosses one or more curtains with which the one or more rules are respectively associated.
20. The non-transitory storage medium as recited in claim 11 , wherein one of the rules, when applied, assigns an expiration time to an associated backup version.