Snapshot Lifecycle Management Systems and Methods

2. The method according to claim 1, wherein the snapshot gathering parameters comprises a schedule that identifies when new snapshots are to be created and when expired snapshots are to be deleted.

3. The method according to claim 1, further comprising assigning a unique name to each of the snapshots, and wherein the snapshots includes identifying metadata.

4. The method according to claim 1, further comprising establishing configurations for each of the snapshots that includes any of an array of index names or wildcard pattern of index names included in snapshots and cluster states.

5. The method according to claim 1, further comprising applying an ignore index parameter that allows a snapshot to be obtained even when an index of the indices is missing.

6. The method according to claim 1, wherein the retention parameters include an indication of a time period after which a snapshot is considered expired and eligible for deletion, an indication of a maximum number of the snapshots to retain, even if the snapshots have not yet expired, and an indication of a minimum number of the snapshots to retain, even if the snapshots have expired, wherein when a number of the snapshots in the repository exceed the maximum number, the most recent snapshots are retained and older snapshots are deleted.

10. The method according to claim 9, further comprising establishing a deletion schedule that comprises deletion cycles that have a deletion timeframe, wherein when stored snapshots are deleted during a first deletion cycle but there are remaining stored snapshots, the remaining stored snapshots are deleted in one or more subsequent deletion cycles.

12. The system according to claim 11, wherein the snapshot gathering parameters comprises a schedule that identifies when new snapshots are to be created and when expired snapshots are to be deleted.

13. The system according to claim 11, wherein the processor executes the instructions to assign a name to each of the snapshots, and wherein the snapshots includes identifying metadata.

14. The system according to claim 11, wherein the processor executes the instructions to establish configurations for each of the snapshots that includes any of an array of index names or wildcard pattern of index names included in snapshots and cluster states.

15. The system according to claim 11, wherein the processor executes the instructions to apply an ignore index parameter that allows a snapshot to be obtained even when an index of the indices is missing.

16. The system according to claim 11, wherein the retention parameters include an indication of a time period after which a snapshot is considered expired and eligible for deletion, an indication of a maximum number of the snapshots to retain, even if the snapshots have not yet expired, and an indication of a minimum number of the snapshots to retain, even if the snapshots have expired.

17. The system according to claim 16, wherein when a number of the snapshots in the repository exceed the maximum number, the most recent snapshots are retained and older snapshots are deleted.

19. The system according to claim 18, wherein the processor executes the instructions to establish a deletion schedule that comprises deletion cycles that have a deletion timeframe.

20. The system according to claim 19, wherein when stored snapshots are deleted during a first deletion cycle but there are remaining stored snapshots, the remaining stored snapshots are deleted in one or more subsequent deletion cycles.