Increasing file storage scale using federated repositories

Abstract

A storage management system using federated repositories directs content to child repositories in a hierarchical structure. A service for managing the storage maintains a list of active and historic repositories and routing of the content for storage is performed based on a file plan that includes the structure of the child repositories, policies for storage, and the like. Repositories reaching their capacity are retired to historic status, where they are available for search purposes, but not for further storage. File plan is updated as new repositories are added or old ones retired. File plan changes and other information such as content types, search terms, workflow, etc. is made available to child repositories when they query the service.

Description

Background technique [0001] Many companies and organizations have large collections of electronic content that need to be stored and maintained for defined periods of time. Over time, these sets of content have a tendency to grow and eventually reach a size that is often too large for a single repository However, organizations need to manage these content in a unified manner, even though the content itself is divided across several physical stores superior. [0002] Managing such electronic content presents additional challenges, as policies associated with the content also need to be modified over time. For example, in its first year of business, a company may have 20 million documents detailing studies and trials, each of which must be retained for ten years, and its repository may be limited to a total of 20 million documents. There is no way to scale the physical size of existing repositories, and because their records must be kept for many years, companies can end up wi...

AI Technical Summary

Problems solved by technology

For example, in its first year of business, a company may have 20 million documents detailing studies and trials, each of which must be retained for ten years, and its repository may be limited to a total of 20 million documents

Inability to scale the physical size of existing repositories, and since their records must be retained for many years, companies may end up with several disjointed repositories that need to be managed individually

This heightens the challenge of managing corporate records, especially if policies applicable to content across repositories must be modified

Images