Method and system for backup and recovery

A system for data backup and recovery based on linked file repositories, wherein the system includes at least one of:

• at least one server system;
• the linked file repositories, wherein each of the linked file repositories representing an individual file system capable of storing at least one version of a file, and in communication with the at least one server system;
• and
• at least one processor device, in communication with each the linked file repositories and the at least one server system, operable in the system, wherein the at least one processor device:
• places each of the linked file repositories in one of a plurality of positions for storing the at least one version of the file,
• continuously numbers each of the plurality of positions of each of the linked file repositories,
• determines a number of the at least one version of the file by the one of a plurality of positions of the one of the linked file repositories,
• for each of the linked file repositories, performs at least one function operation for each file stored in the linked file repositories matching at least one rule, wherein the at least one function operation includes at least one of a deduplication function allowing deduplicating files based on the version number, an indexing function allowing to index the file and providing search and discovery capabilities, and an expiration function for moved files determining when a moved file expires and is being deleted time-based or event-based;
• wherein the at least one rule includes a file extension matching a certain pattern, a file name matching one of a plurality of patterns, a file path name matching the one of a plurality of patterns, a file owner matching the one of a plurality of patterns, a file creation, and a modification or last access time matching a specified date and a specified time range,
• receives a write operation and a new one of the at least one version of the file to be written from one of the at least one server system and a preceding one of the linked file repositories,
• determines if the new one of the at least one version of the file to be written exists in the one of the linked file repositories,
• if the new one of the at least one version of the file to be written exists in the one of the linked file repositories performs one of:
• verifying versioning policies,
• moving an existing one of the at least one version from the corresponding one of the linked file repositories to a subsequent one of the linked file repositories if the versioning policies indicate a higher number of the at least one version that are to be saved as compared to a position number of the one of the linked file repositories, otherwise:
• deleting the existing one of the at least one version in the one of the linked file repositories, and
• storing the new one of the at least one version of the file to be written from one of the at least one server system and the preceding one of the linked file repositories, and
• if the new one of the at least one version of the file to be written does not exist in the one of the linked file repositories:
• storing the new one of the at least one version of the file to be written from the one of the linked file repositories.

A computer program product of data backup and recovery based on linked file repositories with each of the linked file repositories representing an individual file system capable of storing at least one version of a file and being connected to at least one server system, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

• a first executable portion that places each of the linked file repositories in one of a plurality of positions for storing the at least one version of the file;
• a second executable portion that continuously numbers each of the plurality of positions of each of the linked file repositories;
• a third executable portion that determines a number of the at least one version of the file by the one of a plurality of positions of the one of the linked file repositories;
• a fourth executable portion that, for each of the linked file repositories, performs at least one function operation for each file stored in the linked file repositories matching at least one rule, wherein the at least one function operation includes at least one of a deduplication function allowing deduplicating files based on the version number, an indexing function allowing to index the file and providing search and discovery capabilities, and an expiration function for moved files determining when a moved file expires and is being deleted time-based or event-based;
• wherein the at least one rule includes a file extension matching a certain pattern, a file name matching one of a plurality of patterns, a file path name matching the one of a plurality of patterns, a file owner matching the one of a plurality of patterns, a file creation, and a modification or last access time matching a specified date and a specified time range;
• and
• a fifth executable portion that:
• receives a write operation and a new one of the at least one version of the file to be written from one of the at least one server system and a preceding one of the linked file repositories,
• determines if the new one of the at least one version of the file to be written exists in the one of the linked file repositories,
• if the new one of the at least one version of the file to be written exists in the one of the linked file repositories performs one of:
• verifying versioning policies,
• moving an existing one of the at least one version from the corresponding one of the linked file repositories to a subsequent one of the linked file repositories if the versioning policies indicate a higher number of the at least one version that are to be saved as compared to a position number of the one of the linked file repositories, otherwise:
• deleting the existing one of the at least one version in the one of the linked file repositories, and
• storing the new one of the at least one version of the file to be written from one of the at least one server system and the preceding one of the linked file repositories, and
• if the new one of the at least one version of the file to be written does not exist in the one of the linked file repositories:
• storing the new one of the at least one version of the file to be written from the one of the linked file repositories.