CA2788750A1 - Method and system for electronic file lifecycle management - Google Patents
Method and system for electronic file lifecycle management Download PDFInfo
- Publication number
- CA2788750A1 CA2788750A1 CA2788750A CA2788750A CA2788750A1 CA 2788750 A1 CA2788750 A1 CA 2788750A1 CA 2788750 A CA2788750 A CA 2788750A CA 2788750 A CA2788750 A CA 2788750A CA 2788750 A1 CA2788750 A1 CA 2788750A1
- Authority
- CA
- Canada
- Prior art keywords
- file
- virtual
- drawer
- managing
- cabinet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000003860 storage Methods 0.000 claims abstract description 82
- 238000012217 deletion Methods 0.000 claims abstract description 24
- 230000037430 deletion Effects 0.000 claims abstract description 24
- 230000009471 action Effects 0.000 claims description 28
- 238000007726 management method Methods 0.000 claims description 22
- 230000010076 replication Effects 0.000 claims description 4
- 238000013500 data storage Methods 0.000 claims 1
- 230000003287 optical effect Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 14
- 230000014759 maintenance of location Effects 0.000 description 14
- 230000008569 process Effects 0.000 description 7
- 238000005192 partition Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 238000004064 recycling Methods 0.000 description 3
- 238000010348 incorporation Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- HRANPRDGABOKNQ-ORGXEYTDSA-N (1r,3r,3as,3br,7ar,8as,8bs,8cs,10as)-1-acetyl-5-chloro-3-hydroxy-8b,10a-dimethyl-7-oxo-1,2,3,3a,3b,7,7a,8,8a,8b,8c,9,10,10a-tetradecahydrocyclopenta[a]cyclopropa[g]phenanthren-1-yl acetate Chemical compound C1=C(Cl)C2=CC(=O)[C@@H]3C[C@@H]3[C@]2(C)[C@@H]2[C@@H]1[C@@H]1[C@H](O)C[C@@](C(C)=O)(OC(=O)C)[C@@]1(C)CC2 HRANPRDGABOKNQ-ORGXEYTDSA-N 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000000796 flavoring agent Substances 0.000 description 1
- 235000019634 flavors Nutrition 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 239000010813 municipal solid waste Substances 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000008929 regeneration Effects 0.000 description 1
- 238000011069 regeneration method Methods 0.000 description 1
- 230000003362 replicative effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/122—File system administration, e.g. details of archiving or snapshots using management policies
- G06F16/125—File system administration, e.g. details of archiving or snapshots using management policies characterised by the use of retention policies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/185—Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Storage Device Security (AREA)
Abstract
A method for managing a file lifecycle incorporates a virtual file cabinet having virtual drawers. Files are moved from drawer to drawer throughout their lifecycle in accordance with policies associated with each drawer. The files are moved automatically and as such, a file's lifecycle is managed from file creation to file deletion in an automated fashion. By using an archiving device such as magneto optical storage media, the files are automatically moved to their final archived location in an archiving drawer once certain policies of their present drawer are met.
Description
Method and System for Electronic File Lifecycle Management Field of the Invention The invention relates generally to storage devices for storing electronic data and more particularly to virtual storage devices for electronic file lifecycle management.
Background of the Invention In the past, files were stored as paper documents within a physical file. A
physical file has a physical lifecycle from file creation to file destruction.
Commonly, during this process, the file goes through the process of file building, file reference, file non-use, and file archiving. These steps often occur in that order though this need not be the case.
Because of the way files are maintained within present day computer systems, it is often difficult to retrieve files when lost. This is not because of backup failures and so forth, so much as due to poor organization and non-standard file lifecycle management.
Typically, files are relocated manually which necessitates human interaction and the new location of the file has to be manually recorded. This process is prone to errors since it relies heavily on the individual to update the current location. For example, it is often only a guess when a specific file is archived. The name and location of the file may also be inexact. This leads to difficulties in accessing data once archived. It also leads to difficulty in accessing data during normal use.
The adoption of the concept of electronic file storage has increased the demand for storage on an ongoing basis. Huge networked storage repositories, which were once considered as unattainable, are now more widely available. The potential existence of such systems raises many questions of how to organize and coordinate were the files will be stored and for how long. These issues have plagued system administrators through out the evolution of the electronic age, and will continue in the future as the demand for electronic data increases. In most organizations their storage requirements are evolving at an exponential rate exceeding all expectations. This phenomenon along with the ongoing advancements in storage technologies that are occurring at a very fast rate are making existing storage repositories obsolete shortly after their deployment.
Object of the Invention In order to overcome these and other limitations of the prior art, it is an object of the present invention to provide a method and system for automatic management of electronic file lifecycles.
Summary of the Invention The embodiment of this invention enables organizations to salvage their existing investments in current storage technologies while allowing the adoption and incorporation of up and coming technology in one comprehensive system.
Existing systems that are currently in production may be utilized to maintain some data while the newer more efficient storage systems may maintain the most current data. The invention supports incorporation of the widest variety of storage technologies and systems into a cohesive and homogeneous storage system that can expand and incorporate newer storage technologies as they become available and continue to meet the ever expanding demand for storage.
Typically, the file lifecycle allows the file to be accessed throughout its existence, regardless of where it is located within the network. A file may exist on any of the storage components or servers that comprise a virtual storage space. All relevant information regarding file management policies is maintained and enforced according to the invention for the entire file lifecycle. Several instances of a file may exist within a virtual space allowing the overall system to perform such tasks as load balancing, high availability, replication, backup and mirroring. This implies that for the entire lifespan of the file it will remain accessible.
According to the present invention there is provided a method of managing a file lifecycle comprising the steps of:
storing the file on a storage medium having associated therewith a set ofpolicies relating to file storage locations;
Background of the Invention In the past, files were stored as paper documents within a physical file. A
physical file has a physical lifecycle from file creation to file destruction.
Commonly, during this process, the file goes through the process of file building, file reference, file non-use, and file archiving. These steps often occur in that order though this need not be the case.
Because of the way files are maintained within present day computer systems, it is often difficult to retrieve files when lost. This is not because of backup failures and so forth, so much as due to poor organization and non-standard file lifecycle management.
Typically, files are relocated manually which necessitates human interaction and the new location of the file has to be manually recorded. This process is prone to errors since it relies heavily on the individual to update the current location. For example, it is often only a guess when a specific file is archived. The name and location of the file may also be inexact. This leads to difficulties in accessing data once archived. It also leads to difficulty in accessing data during normal use.
The adoption of the concept of electronic file storage has increased the demand for storage on an ongoing basis. Huge networked storage repositories, which were once considered as unattainable, are now more widely available. The potential existence of such systems raises many questions of how to organize and coordinate were the files will be stored and for how long. These issues have plagued system administrators through out the evolution of the electronic age, and will continue in the future as the demand for electronic data increases. In most organizations their storage requirements are evolving at an exponential rate exceeding all expectations. This phenomenon along with the ongoing advancements in storage technologies that are occurring at a very fast rate are making existing storage repositories obsolete shortly after their deployment.
Object of the Invention In order to overcome these and other limitations of the prior art, it is an object of the present invention to provide a method and system for automatic management of electronic file lifecycles.
Summary of the Invention The embodiment of this invention enables organizations to salvage their existing investments in current storage technologies while allowing the adoption and incorporation of up and coming technology in one comprehensive system.
Existing systems that are currently in production may be utilized to maintain some data while the newer more efficient storage systems may maintain the most current data. The invention supports incorporation of the widest variety of storage technologies and systems into a cohesive and homogeneous storage system that can expand and incorporate newer storage technologies as they become available and continue to meet the ever expanding demand for storage.
Typically, the file lifecycle allows the file to be accessed throughout its existence, regardless of where it is located within the network. A file may exist on any of the storage components or servers that comprise a virtual storage space. All relevant information regarding file management policies is maintained and enforced according to the invention for the entire file lifecycle. Several instances of a file may exist within a virtual space allowing the overall system to perform such tasks as load balancing, high availability, replication, backup and mirroring. This implies that for the entire lifespan of the file it will remain accessible.
According to the present invention there is provided a method of managing a file lifecycle comprising the steps of:
storing the file on a storage medium having associated therewith a set ofpolicies relating to file storage locations;
2 determining from the associated policies when the file is to be moved;
moving the file to another storage location within a same or different storage medium when the file is to be moved.
According to another embodiment of the invention there is provided a method of managing a file lifecycle comprising the steps of.
providing a virtual storage medium having a plurality of storage media associated therewith and having associated therewith a set of policies relating to file storage locations within the storage media;
storing the file on a storage medium within the virtual storage medium;
at intervals, determining from the associated policies actions dictated by the policies for performance on the files;
performing the dictated actions on the file.
According to another embodiment of the invention there is provided a method of managing a file lifecycle comprising the steps of providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least a storage medium and a single drawer associated with storage media of a similar nature;
providing a plurality of policies, a policy associated with each virtual drawer, storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
at intervals, determining from the policy associated with the virtual drawer an action dictated by the policy; and, performing the dictated action on the file.
The process of relocating a file could be triggered externally by an administrator, or be triggered by usage policies such as high & low watermarks or by a predefined event or interval.
moving the file to another storage location within a same or different storage medium when the file is to be moved.
According to another embodiment of the invention there is provided a method of managing a file lifecycle comprising the steps of.
providing a virtual storage medium having a plurality of storage media associated therewith and having associated therewith a set of policies relating to file storage locations within the storage media;
storing the file on a storage medium within the virtual storage medium;
at intervals, determining from the associated policies actions dictated by the policies for performance on the files;
performing the dictated actions on the file.
According to another embodiment of the invention there is provided a method of managing a file lifecycle comprising the steps of providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least a storage medium and a single drawer associated with storage media of a similar nature;
providing a plurality of policies, a policy associated with each virtual drawer, storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
at intervals, determining from the policy associated with the virtual drawer an action dictated by the policy; and, performing the dictated action on the file.
The process of relocating a file could be triggered externally by an administrator, or be triggered by usage policies such as high & low watermarks or by a predefined event or interval.
3 According to yet another embodiment of the invention there is provided a method of managing a file lifecycle comprising the steps of:
providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least a storage medium and a single drawer associated with storage media of a similar nature;
providing a plurality of policies, general policies on a virtual cabinet basis as well as policies associated with each virtual drawer;
storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
upon receiving an access request to access the file, determining from the policy associated with the virtual drawer an action dictated by the policy;
performing the dictated action on the file.
Advantageously, maintaining an index of the relevant information to access the files regardless of the location allows a single file to have several extents potentially spanning across several of the storage components within a virtual drawer or across several virtual drawers within a virtual cabinet. The entire file remains accessible and appears to the user completely intact as one whole file even though it might be spliced across different partitions on different servers, but this need not be so.
Brief Description of the Drawings The invention will now be described in conjunction with the drawings in which:
Fig. 1 is a simplified diagram of a filing cabinet;
Fig. 2 is a simplified diagram of a virtual filing cabinet;
Fig. 3a is a simplified diagram of a visualization of a virtual volume comprising three virtual filing cabinets;
Fig. 3b is a simplified block diagram of physical storage devices relating to the virtual volume of Fig. 3a;
Fig. 4 is a simplified flow diagram of a method of file lifecycle management;
Fig. 5 is a simplified flow diagram of an implementation of the system for Windows NT ; and,
providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least a storage medium and a single drawer associated with storage media of a similar nature;
providing a plurality of policies, general policies on a virtual cabinet basis as well as policies associated with each virtual drawer;
storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
upon receiving an access request to access the file, determining from the policy associated with the virtual drawer an action dictated by the policy;
performing the dictated action on the file.
Advantageously, maintaining an index of the relevant information to access the files regardless of the location allows a single file to have several extents potentially spanning across several of the storage components within a virtual drawer or across several virtual drawers within a virtual cabinet. The entire file remains accessible and appears to the user completely intact as one whole file even though it might be spliced across different partitions on different servers, but this need not be so.
Brief Description of the Drawings The invention will now be described in conjunction with the drawings in which:
Fig. 1 is a simplified diagram of a filing cabinet;
Fig. 2 is a simplified diagram of a virtual filing cabinet;
Fig. 3a is a simplified diagram of a visualization of a virtual volume comprising three virtual filing cabinets;
Fig. 3b is a simplified block diagram of physical storage devices relating to the virtual volume of Fig. 3a;
Fig. 4 is a simplified flow diagram of a method of file lifecycle management;
Fig. 5 is a simplified flow diagram of an implementation of the system for Windows NT ; and,
4 Fig. 6 is a simplified flow diagram of a method of using retention dates to track file = lifecycles.
Detailed Description of the Invention Referring to Fig. 1, a simplified diagram of a file cabinet 1 is shown. The drawers 2, 3, 4, and 5 each hold a finite number of files. The drawers are of equal size and typically, each drawer is labeled, as shown, to indicate its contents. The file cabinet I
contains files organized into A-J (drawer 2), K-Z (drawer 3), archives (drawer 4) and accounting (drawer 5). Such organization methods and filing systems are well known and their use in offices is widespread.
As noted above, the concept of file folders has been adopted for use in graphical user interfaces. The file folder is a graphical representation of a directory.
A file folder may contain documents or further file folders and so forth. This is seen in the Macintosh operating system and in Windows operating systems. The use of these file folders is merely a convenient visualization tool for users. In actual practice, a single file folder is rarely comprised of many nested file folders and so forth.
Referring to Fig. 2, a simplified diagram of a virtual file cabinet 21 used as an aid for visualizing a computer file system is shown. The virtual cabinet 21 has a number of drawers, each labeled to reflect their contents. The drawers are indefinite in size and may span more than a single physical storage medium. Some drawers may reflect storage '= =
media types as opposed to permanent storage. For example, the drawer 22 is a cache. The cache is shown labeled "cache drawer" but may in fact be labeled disk surface or to be filed or so forth. The drawer 23 is a storage medium that is currently available. Because the system uses virtual volumes, it is possible that a storage medium is offline. Of course, even when virtual volumes are not used, a network drive may be offline at a particular time. Drawer 24 relates to a magneto-optical drive for storing large volumes of data on removable media. Drawer 25 relates to a recycle bin or trash where deleted files are stored prior to being permanently erased. Finally, an offline media drawer 26 is a placeholder that retains information about for all components of the specific virtual cabinet that are currently unavailable and may be inaccessible. An Offline Media Drawer
Detailed Description of the Invention Referring to Fig. 1, a simplified diagram of a file cabinet 1 is shown. The drawers 2, 3, 4, and 5 each hold a finite number of files. The drawers are of equal size and typically, each drawer is labeled, as shown, to indicate its contents. The file cabinet I
contains files organized into A-J (drawer 2), K-Z (drawer 3), archives (drawer 4) and accounting (drawer 5). Such organization methods and filing systems are well known and their use in offices is widespread.
As noted above, the concept of file folders has been adopted for use in graphical user interfaces. The file folder is a graphical representation of a directory.
A file folder may contain documents or further file folders and so forth. This is seen in the Macintosh operating system and in Windows operating systems. The use of these file folders is merely a convenient visualization tool for users. In actual practice, a single file folder is rarely comprised of many nested file folders and so forth.
Referring to Fig. 2, a simplified diagram of a virtual file cabinet 21 used as an aid for visualizing a computer file system is shown. The virtual cabinet 21 has a number of drawers, each labeled to reflect their contents. The drawers are indefinite in size and may span more than a single physical storage medium. Some drawers may reflect storage '= =
media types as opposed to permanent storage. For example, the drawer 22 is a cache. The cache is shown labeled "cache drawer" but may in fact be labeled disk surface or to be filed or so forth. The drawer 23 is a storage medium that is currently available. Because the system uses virtual volumes, it is possible that a storage medium is offline. Of course, even when virtual volumes are not used, a network drive may be offline at a particular time. Drawer 24 relates to a magneto-optical drive for storing large volumes of data on removable media. Drawer 25 relates to a recycle bin or trash where deleted files are stored prior to being permanently erased. Finally, an offline media drawer 26 is a placeholder that retains information about for all components of the specific virtual cabinet that are currently unavailable and may be inaccessible. An Offline Media Drawer
5 contains information related to all removable media that is not currently accessible. Of course, any drawer can be in an unavailable state due to a network or hardware related problem. Each Drawer has its own independent operational status that reflects its current state; these states include on-line/off-line, locked/unlocked as well as replicating, mirror synchronization, and backup in progress. A virtual cabinet or an individual drawer can be online or offline indicating that it is accessible or not. Additionally, they may be locked or unlocked indicating that for some administrative purpose the drawer is not accessible to a particular user/group or to the entire enterprise.
Associated with the virtual cabinet 21 is a set of cabinet policies relating to version control of files, security access, deletion, file archiving, and so forth. Further, associated with each drawer is a set of policies-relating to that drawer. Some examples of policies for each drawer are set out herein below.
Referring to Fig. 3a, a simplified block diagram of a system 30*having a virtual volume 31 in the form of a virtual storage space, and virtual filing cabinets 32 defined therein is shown. A lifecycle of a file stored within a virtual drawer is controlled in a fashion that makes use of policies of that drawer, of the virtual cabinet in which the drawer is located and of the virtual volume. In combination, these policies define a set of policies for governing files in the specified virtual drawer 33. Typically, the files within a single virtual cabinet 32 are inside a single virtual subdirectory, but this need not be so.
Additionally, the files within a single virtual drawer 33 may be inside an associated single virtual subdirectory, but this need not be so.
Individual data files are stored within virtual drawers 33. These drawers 33 expand and shrink dynamically and are typically constituted by a homogeneous media type. Besides storage, virtual drawers 33 are also defined for other purposes such as caching, redundancy control (such as backup, mirror & replica), file recycling and offline media management, as well as recycling. For example, the caching drawer 21 would reflect a storage medium providing high performance such as RAM.
Associated with the virtual cabinet 21 is a set of cabinet policies relating to version control of files, security access, deletion, file archiving, and so forth. Further, associated with each drawer is a set of policies-relating to that drawer. Some examples of policies for each drawer are set out herein below.
Referring to Fig. 3a, a simplified block diagram of a system 30*having a virtual volume 31 in the form of a virtual storage space, and virtual filing cabinets 32 defined therein is shown. A lifecycle of a file stored within a virtual drawer is controlled in a fashion that makes use of policies of that drawer, of the virtual cabinet in which the drawer is located and of the virtual volume. In combination, these policies define a set of policies for governing files in the specified virtual drawer 33. Typically, the files within a single virtual cabinet 32 are inside a single virtual subdirectory, but this need not be so.
Additionally, the files within a single virtual drawer 33 may be inside an associated single virtual subdirectory, but this need not be so.
Individual data files are stored within virtual drawers 33. These drawers 33 expand and shrink dynamically and are typically constituted by a homogeneous media type. Besides storage, virtual drawers 33 are also defined for other purposes such as caching, redundancy control (such as backup, mirror & replica), file recycling and offline media management, as well as recycling. For example, the caching drawer 21 would reflect a storage medium providing high performance such as RAM.
6 Referring to Fig. 3b a physical system is shown comprising different storage media for storing different data within different drawers. A network is shown comprising a plurality of computer systems 34. Each system includes RAM 35, non-volatile storage devices and so forth. The non-volatile storage devices include hard drives 36, magneto optical drives 37, CD ROM writers 38, DVD with its different flavours of DVD-RAM, DVD-ROM, DVD-R, DVD-RW, DVD+RW, etc. as well as flash disks, tape and other forms of storage. Each physical device is associated with one or more cabinets and with one or more drawers.
Referring to Fig. 4 a simplified flow diagram of a method of file lifecycle management is presented. The goal of file lifecycle management is generally to control a file from its inception, throughout all stages of its existence. If a lifecycle management system is complete, it safely ensures information availability and simultaneously provides a cost effective storage location for each file, according to predefined administration policies. The life cycle of the file could include policies that determine when it will expire and at the administrators discretion be automatically disposed of and deleted securely or moved to the recycle bin.
Each virtual cabinet contains general policies to be applied for the files under its control; in turn, each Virtual Drawer in a cabinet includes further rules for administering files in its domain. Further, it is possible that within a virtual storage space, there are high-level policies that apply to all files.
A file is created and placed within a file folder. The file folder is similar to those known in the art and, typically, relate-directly to directories. The drawer typically relates to a higher-level directory. The drawer has policies, which include policies of the cabinet and may further include system level policies such as those of the virtual volume and so forth. These policies are used to evaluate a lifecycle stage of a file within the drawer and to determine a subsequent drawer where the file folder will be stored within the virtual cabinet. Upon storage of the file within a folder within the drawer, the policies are monitored, as is the file to determine when each or any policy is applicable.
When a policy is applicable, it is applied to the file or to the drawer as required.
The use of
Referring to Fig. 4 a simplified flow diagram of a method of file lifecycle management is presented. The goal of file lifecycle management is generally to control a file from its inception, throughout all stages of its existence. If a lifecycle management system is complete, it safely ensures information availability and simultaneously provides a cost effective storage location for each file, according to predefined administration policies. The life cycle of the file could include policies that determine when it will expire and at the administrators discretion be automatically disposed of and deleted securely or moved to the recycle bin.
Each virtual cabinet contains general policies to be applied for the files under its control; in turn, each Virtual Drawer in a cabinet includes further rules for administering files in its domain. Further, it is possible that within a virtual storage space, there are high-level policies that apply to all files.
A file is created and placed within a file folder. The file folder is similar to those known in the art and, typically, relate-directly to directories. The drawer typically relates to a higher-level directory. The drawer has policies, which include policies of the cabinet and may further include system level policies such as those of the virtual volume and so forth. These policies are used to evaluate a lifecycle stage of a file within the drawer and to determine a subsequent drawer where the file folder will be stored within the virtual cabinet. Upon storage of the file within a folder within the drawer, the policies are monitored, as is the file to determine when each or any policy is applicable.
When a policy is applicable, it is applied to the file or to the drawer as required.
The use of
7 storage cabinet or drawer is completely transparent to the user. As far as the user is concerned the file is stored in a particular directory on a particular drive.
Internally to the system the file may redirected to an entirely different location and may even be split across different devices across the network. The internal directory structures as well all the policy enforcement and file management is handled and maintained according to the inventive method (metadata).
Similarly, in the other portion of the flow diagram of Fig. 4, a file is accessed.
Upon the file being accessed, the policies are checked to determine any that relate to files being accessed that are within the drawer. Those applicable policies are implemented and the policies of the drawer are maintained. Of course, numerous other actions may trigger policies. Typical examples of these include deleting files, moving files, copying files, and so forth. Each of these actions may be considered a file access operation.
. In essence, implementation of policies allows for automated file lifecycle management. For example, a virtual cabinet is constituted by virtual drawers and sets of rules. The rules relate to aspects of file lifecycle management. Some examples of policy areas and implementations are set out below.
File retention policies are one of the most important aspects of file lifecycle management. These policies determine how files are removed from a system. For example, in Windows 980 a file, when deleted from 'a hard disk drive is placed in a recycle bin from which it is only removed when the recycle bin is emptied.
Though this provides convenient retrieval of accidentally deleted files, it is not akin to file lifecycle management.
For example, using policies, a cause and a respective action are set out. For file retention, these actions include file deletion, file deletion with security to prevent retrieval, file archiving, file locking to prevent deletion, moving a file to a different drawer and so forth. A typical file retention policy for the virtual cabinet of Fig. 2 is as follows:
Internally to the system the file may redirected to an entirely different location and may even be split across different devices across the network. The internal directory structures as well all the policy enforcement and file management is handled and maintained according to the inventive method (metadata).
Similarly, in the other portion of the flow diagram of Fig. 4, a file is accessed.
Upon the file being accessed, the policies are checked to determine any that relate to files being accessed that are within the drawer. Those applicable policies are implemented and the policies of the drawer are maintained. Of course, numerous other actions may trigger policies. Typical examples of these include deleting files, moving files, copying files, and so forth. Each of these actions may be considered a file access operation.
. In essence, implementation of policies allows for automated file lifecycle management. For example, a virtual cabinet is constituted by virtual drawers and sets of rules. The rules relate to aspects of file lifecycle management. Some examples of policy areas and implementations are set out below.
File retention policies are one of the most important aspects of file lifecycle management. These policies determine how files are removed from a system. For example, in Windows 980 a file, when deleted from 'a hard disk drive is placed in a recycle bin from which it is only removed when the recycle bin is emptied.
Though this provides convenient retrieval of accidentally deleted files, it is not akin to file lifecycle management.
For example, using policies, a cause and a respective action are set out. For file retention, these actions include file deletion, file deletion with security to prevent retrieval, file archiving, file locking to prevent deletion, moving a file to a different drawer and so forth. A typical file retention policy for the virtual cabinet of Fig. 2 is as follows:
8 Cache Drawer: If file is saved, transfer file to online one (drawer 23).
Online One: If file is not accessed for 30 days transfer to MO One (drawer 24).
If file is deleted, transfer to Recycle Bin (drawer 25).
MO One: If file is not accessed within 30 days, Store the file on a removable WORM storage medium.
If file is accessed more than 5 times within 30 days, Transfer file back to online one (drawer 23).
Recycle Bin: If file is not restored in 30 days, Store file on a non-volatile storage medium and delete.
Here, a file is stored in the cache until it is saved or it may be saved to any other -drawer according to a predefined policy. Once saved it is placed in the file drawer automatically. It remains there during use. Once the file is not accessed for a period of time, the file is transferred to an MO drawer where it is stored in a less conveniently accessible medium. It remains there during a period of intermittent use.
Should the file be used often, it will be transferred back to one of the more accessible drawers such as the active file drawer 23. When no use of the file is made for a period of time, it is archived.
Archiving of the file takes the form of,transferring it to a removable medium.
This operation may take place at intervals depending on the size of the removable media, the size of the organisation and the size of the virtual cabinet. As noted, even deleted files may be archived for later retrieval according to the invention. By maintaining an index of files and their locations, it becomes a simple matter to find a file whether deleted, archived, or active.
Though the above example is quite simple, far more complex file management policies are possible. For example, some files may be deleted without archiving. These would include highly secure files, which are subject to secure deletion, personal files that
Online One: If file is not accessed for 30 days transfer to MO One (drawer 24).
If file is deleted, transfer to Recycle Bin (drawer 25).
MO One: If file is not accessed within 30 days, Store the file on a removable WORM storage medium.
If file is accessed more than 5 times within 30 days, Transfer file back to online one (drawer 23).
Recycle Bin: If file is not restored in 30 days, Store file on a non-volatile storage medium and delete.
Here, a file is stored in the cache until it is saved or it may be saved to any other -drawer according to a predefined policy. Once saved it is placed in the file drawer automatically. It remains there during use. Once the file is not accessed for a period of time, the file is transferred to an MO drawer where it is stored in a less conveniently accessible medium. It remains there during a period of intermittent use.
Should the file be used often, it will be transferred back to one of the more accessible drawers such as the active file drawer 23. When no use of the file is made for a period of time, it is archived.
Archiving of the file takes the form of,transferring it to a removable medium.
This operation may take place at intervals depending on the size of the removable media, the size of the organisation and the size of the virtual cabinet. As noted, even deleted files may be archived for later retrieval according to the invention. By maintaining an index of files and their locations, it becomes a simple matter to find a file whether deleted, archived, or active.
Though the above example is quite simple, far more complex file management policies are possible. For example, some files may be deleted without archiving. These would include highly secure files, which are subject to secure deletion, personal files that
9 are not necessary for the company operations, and so forth. Also, some files that are replaced may be deleted in order to replace same instead of simply accessed and modified. Another added variable is time. Files may be "non-volatile" for a period of time after creation or during certain times of day. This would prevent an after-hours assault on a computer network from damaging files stored thereon.
Recycle bin retention is another policy-based issue. It may be desirable to maintain an index of all files deleted from a recycle bin, or this may be unnecessary. If necessary, the index is stored as part of the recycle bin and may itself be archived at intervals or when of sufficient size to free up space in the recycling bin drawer 25. Other variables affecting policies include size capacity and a number of files relating to each drawer.
Another policy that affects either a cabinet or its drawers is the quota on user space. Quotas are enforced on a user basis. This is based on a unique User or Group identifier. A maximum amount of storage space and a maximum quantity of files is controllable. This Quota may be enforced at different levels such as, on a drawer-by-drawer basis or on a cabinet wide basis or even on an entire virtual volume basis.
As such, the functions currently handled manually by each individual user of a system are handled automatically. Since archiving storage media are cheaper than active storage media, the system results in considerable cost savings. Further, since none must waste time in ensuring the policies of the virtual cabinet, in contrast to a file clerk who performs these functions for physical file cabinets, there is cost savings in the policy based organisation structure.
In the exemplary embodiment, a messaging system is implemented to route error and other messages to appropriate entities. An example of the problem is as follows: if a file is not accessed for 30 days and is being transferred to the archiving drawer 24 and an error occurs, who gets the error message?
Notification of breach of security attempts as well as operator requests are routed to the designated entities according to pre-defined policies. These policies are modified and managed by designated personnel. Notification policies are optionally defined for each of the actions taken by the system to enable auditing, trouble shooting, configuration management as well as system optimization. The notification process allows for numerous notification messages across different protocols with varying levels of severity to be declared for different errors and warnings. For example, the offline media management process optionally has one of a number of predefined policies;
If a specific user or user group requests access for a file that is located on a media that is currently offline then Pause the request indefinitely;
o Notify the user that the file is currently is offline or not, o Allow the user to cancel the request, o Notify the operator or administrator that there is an outstanding request for an offline media when applicable, o Allow the administrator or operator to cancel the request, o Notify the user that the request was cancelled when applicable, But this need not be so.
Pause the request for a specified time period:
o Notify the user that the file is currently offline when this is so, o Notify the user of the request time out period when applicable, o Allow the user to cancel the request, o Notify the operator or administrator that there is an outstanding request for an offline media, o Allow the administrator or operator to cancel the request, o Notify the user that the request. was cancelled, o If the request timed out then;
^ Notify the operator or administrator that there is an outstanding request for an offline media that timed out, .
a Notify the user that the request timed out, Of course other variations are also applicable and user notification is often optional as is the option to cancel a request.
Fail the request immediately:
o Notify the user that the file is currently offline and inaccessible, o Notify the operator or administrator that there was a cancelled request for a file located on an offline storage media, o Notify the user that the request was cancelled, Therefore, these errors are trapped and are passed onto an administrator of the cabinet or of the virtual volume. Messages may also be routed to users/groups according to predefined policies. A hierarchy of notifications is typically implemented to determine whom to notify. An example of a hierarchy is operators, file owners, group administrators, drawer administrators, cabinet administrators, and volume administrators.
Also, notification to other parties such as individual users is possible based on policies and a status of a requested file or file operation. Optionally, notification is sent to the user requesting the file(s) irrespective of the operating environment.
In the virtual cabinet of Fig. 2, there is shown an offline drawer 26. Offline media require management policies of their own. In particular, those virtual drawers that may be offline, need policies relating to that event. This is analogous to physical drawers that may be locked. When the drawer is locked, provision is made for files outside the drawer belonging therein and for files within the drawer that are needed.
Before setting a drawer of line, policies are reviewed to determine that the drawer is one supporting offline activity and that according to preset policies; the drawer can be taken offline at present. Similarly, policies are verified before a drawer that is offline is returned to online operation. These policies may be significantly more complex than a lock and key scenario. A drawer may automatically go off line in some situations -security breaches, too much activity, reorganisation, etc. That same drawer may require certain events before returning online. In the case of security concerns, an indication from a trusted individual that security concerns are not real is commonly required.
This may require a password or some other identification code. Even once restored, the restoration may not restore the drawer to full information accessibility as before. There may be time periods of partial availability or other policies to enhance security or to improve performance.
Preferably, information is logged relating to virtual cabinet operations for later use in trouble-shooting, tune-up and optimization purposes.
Another drawer (not shown) is a Mount-point drawer or cabinet reflecting data for retrieval from a communication medium in the form of the Internet. This drawer/cabinet may have, for example, known world wide web information addresses stored therein indicative of information location(s) for retrieval. Thus, accessing this drawer/cabinet provides a user with commonly available but updated information such as exchange rates, associated company data for contacting them, weather and traffic information and so forth. Instead of storing this data locally, it is stored on the World Wide Web but accessed as if it were in the local electronic file cabinet. Typically, this data is not managed using the lifecycle management method of the virtual cabinet/drawer since it is drawn from somewhere else, from a system belonging to someone else. That said, the inclusion of the data in a local virtual drawer/cabinet is beneficial in simplicity of access and up to date information content.
Another virtual cabinet may be a Read-Only cabinet that may contain data created outside the context of the virtual volume/cabinet/drawer. This data could be contained on distribution media such as CD-ROM/CD-R/DVD-R/DVD-ROM. Such a cabinet would be in a read-only state, even though it might contain a cache drawer as well as an off line media drawer and potentially a number of read-only drawers. This implies that data contained on such read-only media may be indexed, cross-referenced and cached by the virtual volume for quick access and incorporated into the virtual volume.
Though a virtual drawer is described as being entirely within a single virtual directory, this virtual directory could be a single physical directory.
Alternatively, the files are inside a single physical subdirectory absent a virtual directory.
Further alternatively, the files are inside a plurality of physical and virtual subdirectories.
In an alternative embodiment, the file cabinet is formed of physical volumes instead of virtual volumes wherein a cabinet is comprised of a plurality of drawers each associated with a physical storage device.
In an embodiment, many Virtual Cabinets may share a single Virtual Drawer. As such, using any of several virtual cabinets provides access to a same virtual drawer. This allows for system load balancing wherein virtual drawers are shared to allow a predetermined amount of load on each physical storage device within each virtual device.
As such, portions of a physical storage device are associated with different drawers in order to balance the load such that access to the drawers is optimized for speed.
Because of the structure of the virtual cabinet, existing data stored on electronic media is easily incorporable within newly created virtual volumes and virtual cabinets.
Referring to Fig. 5, a simplified diagram of an implementation of the system is shown. Here all native file system features are supported, but this need not be so. The filing cabinet has tremendous expandability. When using 64 bit addressing the virtual volume is expandable to 264 -1 partitions and files. This is a very large number.
Expansion of the volume or of the cabinets or drawers optionally takes place on the fly or on demand.
Partitions are formatted in the native file system format such as NTFS and are allocated from an appropriate Media Pool, but this need not be so.
Administrative processes allow for compacting of information on members.
Empty media remain allocated to the virtual volume. Optionally, these members may be automatically or manually removed once emptied, depending on a pre-defined policy.
Further administrative options allow definition of different techniques to optimize removable media usage, balancing between performance and storage space utilization such as selecting options, i.e.: always write contiguously - split to utilize available space -split only when file size exceeds media size. Specialized caches for read, write or both operations are provided.
Each virtual volume supports pre-migration techniques for off-peak hours and pre-fetch techniques for improving scheduling.
The implementation supports several storage types including:
Fixed: Hard disk partitions - RAID, Flash disks. (SCSI, IDE Fibre Channel, etc.) Removable: MO - WORM - DVD-RAM - DVD-ROM - DVD-R - DVD+RW
- Tape A local or remote server provides these services. The complete range of native operating system security features are supported. Further security features relating to policies of the virtual cabinet are also supported. The native operating system security features and the policies are enforced at a file level and a directory level.
The invention supports mirroring merely by setting mirroring policies for particular drawers. This is typically achieved using two or more physical media for storing identical data. Of course, the use of an archiving medium and a cache allows for data to be mirrored in an archiving medium during use without slowing performance of the system. Similarly, should a portion of the storage medium fail, the mirrored data is retrieved from the archiving storage medium into the cache for rapid access.
Mirroring is neither limited nor confined to different drawers of different media types, but rather is a policy that allows files to be mirrored to similar typed drawers as well or instead.
Further, the archiving storage device is then an accurate replica of the data that is useful as an archive or for data transfer. Further, the use of several archiving storage media is supported to form a plurality of replicas on different media.
Optionally, replication is performed between drawers of a same type enabling the files to be accessed at all times with same identical performance.
Optionally, ajournaling file system is implemented to make rebuilding of data for faster recovery in case of storage device failure. Preferably, concurrent access is provided during data rebuild. Alternatively stated, as data is being scanned, already parsed information is available to users, typically, in a read-only state. The basic concept of metadata regeneration is achieved by reconstructing the metadata from the individual components that make up the virtual drawers/cabinets and virtual volumes. The metadata is replicated, either partially or fully, through out the virtual volume on the individual components, allowing the metadata to be regenerated in its entirety from these components, but this need not be so. The metadata may be replicated or even mirrored on the local server or across the network to another set of storage components, perhaps an identical set to the original, that would provide plurality of access and enhance performance and provide a redundant fail over mechanism.
Referring to Fig. 6, a simplified flow diagram of a method of using retention dates to track file lifecycles is shown. File expiration dates are stored in association with each file. The expiration dates are indicative of a minimum time before deletion, if any; a date on which to delete the file; and any policies relating to the deletion such as archiving or moving the file to other storage media and so forth. Retention policies within a drawer effect the expiration dates. For example, every time a file is accessed, the retention date is updated The update may differ depending on the access type - read, write, copy, etc. -or may remain the same across all access functions. Also, the policies are capable of supporting distinctions based on user identifications, file types, security levels, and so forth. Another example would allow files that are no longer required for the organization to expire after they reached the legal statute of limitations to be disposed of automatically without delay.
The pseudo file system uses expiration dates on files to track the use of the file.
The expiration dates aid the disposal of seldom-used files, selecting. them to be backed up and/or deleted from the virtual drawer. A minimum and a maximum retention period are specified for the files in the volume.
To determine the expiration date of a newly created file the maximum retention time value is added to the current time, and every time the file is accessed or modified its expiration is updated with a minimum retention time value + current time if it is after the previously stored expiration date. On the other hand expiration policies could be defined to allow files to expire based on strictly the creation date, but this need not be so.
Similarly, a volatility period for a file is selectable during which a user is unable to delete the file. Optionally, the volatility period is stored with an indication preventing renaming of the file when set and allowing it when cleared.
Also, with each file are stored policies on file deletion within the scope of those policies supported by the virtual drawer. Policies for file deletion include the following:
delete with security; delete without security; delete with archive; prevent deletion but allow renaming; prevent deletion prevent renaming; send to recycle bin;
maintain version control data; and delete prior versions.
Version control is a significant aspect of file lifecycle management. When a file is modified, a new version is created. The newer version may be created by duplicating and modifying the previous file and maintained as a completely intact file or as a differential file relative to the previous version of the file. The previous version is typically discarded - replaced or deleted. This need not be so. Policies on file retention can maintain previous versions and if so desired, will maintain a list of previous versions including when last modified and by whom. These old versions are typically stored throughout the virtual cabinet and exist in-any drawer, according to the governing policies that are set by an administrator. Users may have access to only the most recent version of a file, but this also need not be the case. Policies may limit a number of generated versions or an .
interval between new versions in order to limit storage requirements.
Typically, when version control is enabled, only a last file version is available other than by special request. When a file is opened for writing, a modification flag is maintained to ensure that new information has been written to the file. This reduces the amount of versions saved by eliminating those reflecting no changes. If the flag is set, a new version of the file is created - a copy - and the data is stored in this new file.
Typically, a version identifier is maintained as a sequential number included in the file ID
and is incremented every time a new version is created. Of course, other forms of version numbering such as date and time and so forth are also possible. Preferably, in the file properties list, the history of modifications to a file stored through version control appears. Depending on the governing policies set by the administrator and the underlying operating system,.the different versions of the file may be visible to the user but this need not be so.
Another version control policy is Selective/discretionary version control.
Selective version control is a suitable file retention policy to thin versions of a file based on age such that, for example, one version per week is stored for versions over one month old and one version a day is stored for versions over a week old and one version an hour is stored for versions less than one week and over one day, and finally all versions are stored for the last day. By selectively reducing the number of versions maintained, storage requirements do not balloon while, for most applications, reasonable version control is maintained.
Of course, once the file is moved to the archiving drawer 24, the older versions are archived since they are unlikely to be accessed. Similarly, if the file is moved to the recycle bin, the older versions may be archived, deleted, or moved to the recycle bin with the file.
The invention embodies a complete suite of access rights that any administrator may define which will be enforced by the system. They allow the administrator to specify who can perform a specific administrative task if any, and who will get notified in the case 'of a particular event or for all events and how. The enforcement of access rights may be completely or partially disabled at the administrator's discretion, or who ever is designated with the privilege to do so. Every aspect of the system is configurable.
Numerous other embodiments may be envisaged without departing from the spirit or scope of the invention.
Appendix A;
Virtual Volume:
Name Volume Label (Same as Name) Metadata Information (partition list) Data Members (partition list) Space available - Maximum number of files Scan Parameters (schedule info) Virtual Cabinet:
Name = Subdirectory name (always linked to the directory ID) Path Selector (where the VC is located) File Retention Policies Automatic Deletion Prevent Deletion (Access Control Rules) Recycle Bin Version Control Movement Rules between Virtual Drawers Move from Source-DR to Destination-DR files in <criteria>:
<criteria> :._ Any File Include only files that match (Age, Size, Attributes, File-Mask, User/Owner/Creator) [alo]
All files, excluding files that match (Age, Size, Attributes, File-Mask) [alo]
Age:
n days since (CRT, LMT, LAT) Attributes:
Read-Only/Archive/Hidden/System/Compressed (disabled) Size:
Files smaller than n [size unit) Files larger than n [size unit]
File-Mask:
Name pattern/extension pattern User/Owner/Creator Files created by a particular user or Group Files whos ownership is currently held by a specific user or user group File will always be created in one of the virtual cabinet's drawers according to a pre-defined policy.
Virtual Drawer:
Name Server:
Local/Remote Class:
Class: Cache - Storage - Mountpoint Function:
Primary Storage - Recycle - Replica - Backup - Mirror - Archive -Offline Media Type:
Fixed/Removable (Online - Nearline) Media:
Magneto Optical / WORM / DVD-RAM I DVD-ROM / DVD-R/ DVD+RW I
TAPE I CD-ROM ! CD-R / FLASH / RAM
Replication I Mirroring Drawer Access Mode (Read/Write (RW), Read-Only (RO), Archive Mode [AM]) Primary Media Pool Rules for taking Offline (weighting factors, automatically, etc.) - Storage location Rules for Restoration (messaging thru Notification Mgr) Status:
Online - Offline - Locked - Unlocked - Mirror-Synchronization -Replication-In-progress - Backup-In-progress - Accessible - Inaccessible Shared:
Private -- Public Virtual Virtual Virtual Virtual Drawers Volumes Drawers Cabinets in a Virtual Cabinet Name = Volume Label Name Name = Subdirectory Movement Rules Control: Native -Foreign Path Selectors Recycle Bin Policies Scan Parameters Location: Local -Remote Cache Policies User/Group Quotas Class: Cache - Storage - Automatic Deletion Scan Policies Mountpoint Policies Type: Fixed - Version Control Policies User/Group Quotas Removable Media: HD - FLASH - Access Mode: Read/Write MO - WORM - CD-R - - React Only - Archive CD-ROM - DVD-RAM Mode - DVD-ROM - DVD-R
- DVD+RW - RAM -TAPE
Access Mode: Security Deletion Policies Read/Write - Read-Only - Archive Mode Status: Online - Offline Status: Online - Offline Status: Online - Offline --.Locked - Unlocked - - Locked - Unlocked - Locked - Unlocked -Mirror-Synchronization Mirror-Synchronization Mirror-Synchronization -Replication In - Replication-In- Replication-In-progress -progress - Backup-In- progress - Backup-In- Backup-In-progress -progress - Accessible - progress - Accessible - Accessible - Inaccessible Inaccessible Inaccessible Primary Media Pool Type: Virtual Directory -Shared or Not shared Mount-point/Symbolic-link Default Storage Location Function: Primary Storage - Recycle -Replica - Backup -Mirror - Archive -Offline Media Share: Public - Private User/Group Quotas Taking Offline Policies Restoration Policies Hi / Low Watermarks Drawer Direct Access (Read/Write) Table 1: VIRTUAL VOLUMES: PROPERTIES - ATTRIBUTES - POLICIES
Recycle bin retention is another policy-based issue. It may be desirable to maintain an index of all files deleted from a recycle bin, or this may be unnecessary. If necessary, the index is stored as part of the recycle bin and may itself be archived at intervals or when of sufficient size to free up space in the recycling bin drawer 25. Other variables affecting policies include size capacity and a number of files relating to each drawer.
Another policy that affects either a cabinet or its drawers is the quota on user space. Quotas are enforced on a user basis. This is based on a unique User or Group identifier. A maximum amount of storage space and a maximum quantity of files is controllable. This Quota may be enforced at different levels such as, on a drawer-by-drawer basis or on a cabinet wide basis or even on an entire virtual volume basis.
As such, the functions currently handled manually by each individual user of a system are handled automatically. Since archiving storage media are cheaper than active storage media, the system results in considerable cost savings. Further, since none must waste time in ensuring the policies of the virtual cabinet, in contrast to a file clerk who performs these functions for physical file cabinets, there is cost savings in the policy based organisation structure.
In the exemplary embodiment, a messaging system is implemented to route error and other messages to appropriate entities. An example of the problem is as follows: if a file is not accessed for 30 days and is being transferred to the archiving drawer 24 and an error occurs, who gets the error message?
Notification of breach of security attempts as well as operator requests are routed to the designated entities according to pre-defined policies. These policies are modified and managed by designated personnel. Notification policies are optionally defined for each of the actions taken by the system to enable auditing, trouble shooting, configuration management as well as system optimization. The notification process allows for numerous notification messages across different protocols with varying levels of severity to be declared for different errors and warnings. For example, the offline media management process optionally has one of a number of predefined policies;
If a specific user or user group requests access for a file that is located on a media that is currently offline then Pause the request indefinitely;
o Notify the user that the file is currently is offline or not, o Allow the user to cancel the request, o Notify the operator or administrator that there is an outstanding request for an offline media when applicable, o Allow the administrator or operator to cancel the request, o Notify the user that the request was cancelled when applicable, But this need not be so.
Pause the request for a specified time period:
o Notify the user that the file is currently offline when this is so, o Notify the user of the request time out period when applicable, o Allow the user to cancel the request, o Notify the operator or administrator that there is an outstanding request for an offline media, o Allow the administrator or operator to cancel the request, o Notify the user that the request. was cancelled, o If the request timed out then;
^ Notify the operator or administrator that there is an outstanding request for an offline media that timed out, .
a Notify the user that the request timed out, Of course other variations are also applicable and user notification is often optional as is the option to cancel a request.
Fail the request immediately:
o Notify the user that the file is currently offline and inaccessible, o Notify the operator or administrator that there was a cancelled request for a file located on an offline storage media, o Notify the user that the request was cancelled, Therefore, these errors are trapped and are passed onto an administrator of the cabinet or of the virtual volume. Messages may also be routed to users/groups according to predefined policies. A hierarchy of notifications is typically implemented to determine whom to notify. An example of a hierarchy is operators, file owners, group administrators, drawer administrators, cabinet administrators, and volume administrators.
Also, notification to other parties such as individual users is possible based on policies and a status of a requested file or file operation. Optionally, notification is sent to the user requesting the file(s) irrespective of the operating environment.
In the virtual cabinet of Fig. 2, there is shown an offline drawer 26. Offline media require management policies of their own. In particular, those virtual drawers that may be offline, need policies relating to that event. This is analogous to physical drawers that may be locked. When the drawer is locked, provision is made for files outside the drawer belonging therein and for files within the drawer that are needed.
Before setting a drawer of line, policies are reviewed to determine that the drawer is one supporting offline activity and that according to preset policies; the drawer can be taken offline at present. Similarly, policies are verified before a drawer that is offline is returned to online operation. These policies may be significantly more complex than a lock and key scenario. A drawer may automatically go off line in some situations -security breaches, too much activity, reorganisation, etc. That same drawer may require certain events before returning online. In the case of security concerns, an indication from a trusted individual that security concerns are not real is commonly required.
This may require a password or some other identification code. Even once restored, the restoration may not restore the drawer to full information accessibility as before. There may be time periods of partial availability or other policies to enhance security or to improve performance.
Preferably, information is logged relating to virtual cabinet operations for later use in trouble-shooting, tune-up and optimization purposes.
Another drawer (not shown) is a Mount-point drawer or cabinet reflecting data for retrieval from a communication medium in the form of the Internet. This drawer/cabinet may have, for example, known world wide web information addresses stored therein indicative of information location(s) for retrieval. Thus, accessing this drawer/cabinet provides a user with commonly available but updated information such as exchange rates, associated company data for contacting them, weather and traffic information and so forth. Instead of storing this data locally, it is stored on the World Wide Web but accessed as if it were in the local electronic file cabinet. Typically, this data is not managed using the lifecycle management method of the virtual cabinet/drawer since it is drawn from somewhere else, from a system belonging to someone else. That said, the inclusion of the data in a local virtual drawer/cabinet is beneficial in simplicity of access and up to date information content.
Another virtual cabinet may be a Read-Only cabinet that may contain data created outside the context of the virtual volume/cabinet/drawer. This data could be contained on distribution media such as CD-ROM/CD-R/DVD-R/DVD-ROM. Such a cabinet would be in a read-only state, even though it might contain a cache drawer as well as an off line media drawer and potentially a number of read-only drawers. This implies that data contained on such read-only media may be indexed, cross-referenced and cached by the virtual volume for quick access and incorporated into the virtual volume.
Though a virtual drawer is described as being entirely within a single virtual directory, this virtual directory could be a single physical directory.
Alternatively, the files are inside a single physical subdirectory absent a virtual directory.
Further alternatively, the files are inside a plurality of physical and virtual subdirectories.
In an alternative embodiment, the file cabinet is formed of physical volumes instead of virtual volumes wherein a cabinet is comprised of a plurality of drawers each associated with a physical storage device.
In an embodiment, many Virtual Cabinets may share a single Virtual Drawer. As such, using any of several virtual cabinets provides access to a same virtual drawer. This allows for system load balancing wherein virtual drawers are shared to allow a predetermined amount of load on each physical storage device within each virtual device.
As such, portions of a physical storage device are associated with different drawers in order to balance the load such that access to the drawers is optimized for speed.
Because of the structure of the virtual cabinet, existing data stored on electronic media is easily incorporable within newly created virtual volumes and virtual cabinets.
Referring to Fig. 5, a simplified diagram of an implementation of the system is shown. Here all native file system features are supported, but this need not be so. The filing cabinet has tremendous expandability. When using 64 bit addressing the virtual volume is expandable to 264 -1 partitions and files. This is a very large number.
Expansion of the volume or of the cabinets or drawers optionally takes place on the fly or on demand.
Partitions are formatted in the native file system format such as NTFS and are allocated from an appropriate Media Pool, but this need not be so.
Administrative processes allow for compacting of information on members.
Empty media remain allocated to the virtual volume. Optionally, these members may be automatically or manually removed once emptied, depending on a pre-defined policy.
Further administrative options allow definition of different techniques to optimize removable media usage, balancing between performance and storage space utilization such as selecting options, i.e.: always write contiguously - split to utilize available space -split only when file size exceeds media size. Specialized caches for read, write or both operations are provided.
Each virtual volume supports pre-migration techniques for off-peak hours and pre-fetch techniques for improving scheduling.
The implementation supports several storage types including:
Fixed: Hard disk partitions - RAID, Flash disks. (SCSI, IDE Fibre Channel, etc.) Removable: MO - WORM - DVD-RAM - DVD-ROM - DVD-R - DVD+RW
- Tape A local or remote server provides these services. The complete range of native operating system security features are supported. Further security features relating to policies of the virtual cabinet are also supported. The native operating system security features and the policies are enforced at a file level and a directory level.
The invention supports mirroring merely by setting mirroring policies for particular drawers. This is typically achieved using two or more physical media for storing identical data. Of course, the use of an archiving medium and a cache allows for data to be mirrored in an archiving medium during use without slowing performance of the system. Similarly, should a portion of the storage medium fail, the mirrored data is retrieved from the archiving storage medium into the cache for rapid access.
Mirroring is neither limited nor confined to different drawers of different media types, but rather is a policy that allows files to be mirrored to similar typed drawers as well or instead.
Further, the archiving storage device is then an accurate replica of the data that is useful as an archive or for data transfer. Further, the use of several archiving storage media is supported to form a plurality of replicas on different media.
Optionally, replication is performed between drawers of a same type enabling the files to be accessed at all times with same identical performance.
Optionally, ajournaling file system is implemented to make rebuilding of data for faster recovery in case of storage device failure. Preferably, concurrent access is provided during data rebuild. Alternatively stated, as data is being scanned, already parsed information is available to users, typically, in a read-only state. The basic concept of metadata regeneration is achieved by reconstructing the metadata from the individual components that make up the virtual drawers/cabinets and virtual volumes. The metadata is replicated, either partially or fully, through out the virtual volume on the individual components, allowing the metadata to be regenerated in its entirety from these components, but this need not be so. The metadata may be replicated or even mirrored on the local server or across the network to another set of storage components, perhaps an identical set to the original, that would provide plurality of access and enhance performance and provide a redundant fail over mechanism.
Referring to Fig. 6, a simplified flow diagram of a method of using retention dates to track file lifecycles is shown. File expiration dates are stored in association with each file. The expiration dates are indicative of a minimum time before deletion, if any; a date on which to delete the file; and any policies relating to the deletion such as archiving or moving the file to other storage media and so forth. Retention policies within a drawer effect the expiration dates. For example, every time a file is accessed, the retention date is updated The update may differ depending on the access type - read, write, copy, etc. -or may remain the same across all access functions. Also, the policies are capable of supporting distinctions based on user identifications, file types, security levels, and so forth. Another example would allow files that are no longer required for the organization to expire after they reached the legal statute of limitations to be disposed of automatically without delay.
The pseudo file system uses expiration dates on files to track the use of the file.
The expiration dates aid the disposal of seldom-used files, selecting. them to be backed up and/or deleted from the virtual drawer. A minimum and a maximum retention period are specified for the files in the volume.
To determine the expiration date of a newly created file the maximum retention time value is added to the current time, and every time the file is accessed or modified its expiration is updated with a minimum retention time value + current time if it is after the previously stored expiration date. On the other hand expiration policies could be defined to allow files to expire based on strictly the creation date, but this need not be so.
Similarly, a volatility period for a file is selectable during which a user is unable to delete the file. Optionally, the volatility period is stored with an indication preventing renaming of the file when set and allowing it when cleared.
Also, with each file are stored policies on file deletion within the scope of those policies supported by the virtual drawer. Policies for file deletion include the following:
delete with security; delete without security; delete with archive; prevent deletion but allow renaming; prevent deletion prevent renaming; send to recycle bin;
maintain version control data; and delete prior versions.
Version control is a significant aspect of file lifecycle management. When a file is modified, a new version is created. The newer version may be created by duplicating and modifying the previous file and maintained as a completely intact file or as a differential file relative to the previous version of the file. The previous version is typically discarded - replaced or deleted. This need not be so. Policies on file retention can maintain previous versions and if so desired, will maintain a list of previous versions including when last modified and by whom. These old versions are typically stored throughout the virtual cabinet and exist in-any drawer, according to the governing policies that are set by an administrator. Users may have access to only the most recent version of a file, but this also need not be the case. Policies may limit a number of generated versions or an .
interval between new versions in order to limit storage requirements.
Typically, when version control is enabled, only a last file version is available other than by special request. When a file is opened for writing, a modification flag is maintained to ensure that new information has been written to the file. This reduces the amount of versions saved by eliminating those reflecting no changes. If the flag is set, a new version of the file is created - a copy - and the data is stored in this new file.
Typically, a version identifier is maintained as a sequential number included in the file ID
and is incremented every time a new version is created. Of course, other forms of version numbering such as date and time and so forth are also possible. Preferably, in the file properties list, the history of modifications to a file stored through version control appears. Depending on the governing policies set by the administrator and the underlying operating system,.the different versions of the file may be visible to the user but this need not be so.
Another version control policy is Selective/discretionary version control.
Selective version control is a suitable file retention policy to thin versions of a file based on age such that, for example, one version per week is stored for versions over one month old and one version a day is stored for versions over a week old and one version an hour is stored for versions less than one week and over one day, and finally all versions are stored for the last day. By selectively reducing the number of versions maintained, storage requirements do not balloon while, for most applications, reasonable version control is maintained.
Of course, once the file is moved to the archiving drawer 24, the older versions are archived since they are unlikely to be accessed. Similarly, if the file is moved to the recycle bin, the older versions may be archived, deleted, or moved to the recycle bin with the file.
The invention embodies a complete suite of access rights that any administrator may define which will be enforced by the system. They allow the administrator to specify who can perform a specific administrative task if any, and who will get notified in the case 'of a particular event or for all events and how. The enforcement of access rights may be completely or partially disabled at the administrator's discretion, or who ever is designated with the privilege to do so. Every aspect of the system is configurable.
Numerous other embodiments may be envisaged without departing from the spirit or scope of the invention.
Appendix A;
Virtual Volume:
Name Volume Label (Same as Name) Metadata Information (partition list) Data Members (partition list) Space available - Maximum number of files Scan Parameters (schedule info) Virtual Cabinet:
Name = Subdirectory name (always linked to the directory ID) Path Selector (where the VC is located) File Retention Policies Automatic Deletion Prevent Deletion (Access Control Rules) Recycle Bin Version Control Movement Rules between Virtual Drawers Move from Source-DR to Destination-DR files in <criteria>:
<criteria> :._ Any File Include only files that match (Age, Size, Attributes, File-Mask, User/Owner/Creator) [alo]
All files, excluding files that match (Age, Size, Attributes, File-Mask) [alo]
Age:
n days since (CRT, LMT, LAT) Attributes:
Read-Only/Archive/Hidden/System/Compressed (disabled) Size:
Files smaller than n [size unit) Files larger than n [size unit]
File-Mask:
Name pattern/extension pattern User/Owner/Creator Files created by a particular user or Group Files whos ownership is currently held by a specific user or user group File will always be created in one of the virtual cabinet's drawers according to a pre-defined policy.
Virtual Drawer:
Name Server:
Local/Remote Class:
Class: Cache - Storage - Mountpoint Function:
Primary Storage - Recycle - Replica - Backup - Mirror - Archive -Offline Media Type:
Fixed/Removable (Online - Nearline) Media:
Magneto Optical / WORM / DVD-RAM I DVD-ROM / DVD-R/ DVD+RW I
TAPE I CD-ROM ! CD-R / FLASH / RAM
Replication I Mirroring Drawer Access Mode (Read/Write (RW), Read-Only (RO), Archive Mode [AM]) Primary Media Pool Rules for taking Offline (weighting factors, automatically, etc.) - Storage location Rules for Restoration (messaging thru Notification Mgr) Status:
Online - Offline - Locked - Unlocked - Mirror-Synchronization -Replication-In-progress - Backup-In-progress - Accessible - Inaccessible Shared:
Private -- Public Virtual Virtual Virtual Virtual Drawers Volumes Drawers Cabinets in a Virtual Cabinet Name = Volume Label Name Name = Subdirectory Movement Rules Control: Native -Foreign Path Selectors Recycle Bin Policies Scan Parameters Location: Local -Remote Cache Policies User/Group Quotas Class: Cache - Storage - Automatic Deletion Scan Policies Mountpoint Policies Type: Fixed - Version Control Policies User/Group Quotas Removable Media: HD - FLASH - Access Mode: Read/Write MO - WORM - CD-R - - React Only - Archive CD-ROM - DVD-RAM Mode - DVD-ROM - DVD-R
- DVD+RW - RAM -TAPE
Access Mode: Security Deletion Policies Read/Write - Read-Only - Archive Mode Status: Online - Offline Status: Online - Offline Status: Online - Offline --.Locked - Unlocked - - Locked - Unlocked - Locked - Unlocked -Mirror-Synchronization Mirror-Synchronization Mirror-Synchronization -Replication In - Replication-In- Replication-In-progress -progress - Backup-In- progress - Backup-In- Backup-In-progress -progress - Accessible - progress - Accessible - Accessible - Inaccessible Inaccessible Inaccessible Primary Media Pool Type: Virtual Directory -Shared or Not shared Mount-point/Symbolic-link Default Storage Location Function: Primary Storage - Recycle -Replica - Backup -Mirror - Archive -Offline Media Share: Public - Private User/Group Quotas Taking Offline Policies Restoration Policies Hi / Low Watermarks Drawer Direct Access (Read/Write) Table 1: VIRTUAL VOLUMES: PROPERTIES - ATTRIBUTES - POLICIES
Claims (37)
1. A method of managing a file lifecycle comprising the steps of:
providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least storage media of a similar nature;
providing a plurality of policies, a policy associated with each virtual drawer;
storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
at intervals, determining from the policy associated with the virtual drawer an action dictated by the policy; and, performing the dictated actions on the file.
providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least storage media of a similar nature;
providing a plurality of policies, a policy associated with each virtual drawer;
storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
at intervals, determining from the policy associated with the virtual drawer an action dictated by the policy; and, performing the dictated actions on the file.
2. A method of managing a file lifecycle according to claim 1, wherein the action includes the step of deleting the file from the virtual drawer.
3. A method of managing a file lifecycle according to claim 2, wherein the policies relate to the storage medium and to dates stored in association with each file.
4. A method of managing a file lifecycle according to claim 3, comprising the step of: storing in associating with each file an expiration indicator indicative of when the file is to be transferred.
5. A method of managing a file lifecycle according to claim 4, wherein the expiration indicator includes a date on which to delete the file from the drawer in accordance with the action dictated by the policy.
6. A method of managing a file lifecycle according to claim 4, wherein the expiration indicator includes a minimum time before which the file is to be maintained in its current drawer.
7. A method of managing a file lifecycle according to claim 2, wherein the action includes the step of transferring the file from the virtual drawer to another different virtual drawer within the cabinet.
8. A method of managing a file lifecycle according to claim 7, wherein the step of transferring the file includes the step of archiving the file within an archiving virtual drawer.
9. A method of managing a file lifecycle according to claim 2, wherein the step of deleting the file includes the steps of determining based on a policy associated with the drawer and based on data stored in association with the file a mode of deletion, and deleting the file in accordance with the determined mode.
10. A method of managing a file lifecycle according to claim 9, wherein the modes of deletion include secure deletion and insecure deletion.
11. A method of managing a file lifecycle according to claim 1, wherein files stored in the virtual cabinet are stored within a same virtual storage medium and wherein files stored within each drawer from the plurality of virtual drawers are stored on the one or more similar storage media associated with said drawer.
12. A method of managing a file lifecycle according to claim 11, wherein a single virtual drawer forms part of a plurality of virtual cabinets.
13. A method of managing a file lifecycle according to claim 1, wherein the step of determining an action comprises the steps of:
determining from the policy a condition;
evaluating each file to determine a presence of the condition; and, when the condition is met, providing an action associated with the condition as the determined action.
determining from the policy a condition;
evaluating each file to determine a presence of the condition; and, when the condition is met, providing an action associated with the condition as the determined action.
14. A method of managing a file lifecycle comprising the steps of:
providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least a storage medium and a single drawer associated with storage media of a similar nature;
providing a plurality of policies, a policy associated with each virtual drawer;
storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
upon receiving an access request to access the file, determining from the policy associated with the virtual drawer an action dictated by the policy; and, performing the dictated action on the file.
providing a virtual cabinet having a plurality of virtual drawers, each virtual drawer associated with at least a storage medium and a single drawer associated with storage media of a similar nature;
providing a plurality of policies, a policy associated with each virtual drawer;
storing the file in a virtual drawer by storing the file on at least a storage medium associated with the virtual drawer;
upon receiving an access request to access the file, determining from the policy associated with the virtual drawer an action dictated by the policy; and, performing the dictated action on the file.
15. A method of managing a file lifecycle according to claim 14, wherein the determined action comprises the steps of:
storing in association with each file an expiration indicator indicative of when the file is to be transferred, the expiration indicator determined based on the policy.
storing in association with each file an expiration indicator indicative of when the file is to be transferred, the expiration indicator determined based on the policy.
16. A method of managing a file lifecycle according to claim 15, wherein the expiration indicator includes a date on which to delete the file from the drawer in accordance with the action dictated by the policy.
17. A method of managing a file lifecycle according to claim 15, wherein the expiration indicator includes a minimum time before which the file is to be maintained in its current drawer.
18. A method of managing a file lifecycle according to claim 14, wherein the action includes the step of transferring the file from the virtual drawer to another different virtual drawer within the cabinet.
19. A method of managing a file lifecycle according to claim 18, wherein the step of transferring the file includes the step of retrieving the file from an archiving virtual drawer and storing it in another virtual drawer.
20. A method of managing a file lifecycle according to claim 14, comprising the steps of:
determining based on a policy associated with the drawer and based on data stored in association with the file whether the file is to be deleted;
determining based on a policy associated with the drawer and based on data stored in association with the file a mode of deletion for the file; and, deleting the file in accordance with the determined mode.
determining based on a policy associated with the drawer and based on data stored in association with the file whether the file is to be deleted;
determining based on a policy associated with the drawer and based on data stored in association with the file a mode of deletion for the file; and, deleting the file in accordance with the determined mode.
21. A method of managing a file lifecycle according to claim 20, wherein the modes of deletion include secure deletion and insecure deletion.
22. A method of managing a file lifecycle according to claim 14, wherein files stored in the virtual cabinet are stored within a same virtual storage medium and wherein files stored within each drawer from the plurality of virtual drawers are stored on the one or more similar storage media associated with said drawer.
23. A method of managing a file lifecycle according to claim 22, wherein a single virtual drawer forms part of a plurality of virtual cabinets.
24. A method of managing a file lifecycle according to claim 14, wherein the step of determining an action comprises the steps of:
determining from the policy a condition;
evaluating the accessed file to determine a presence of the condition; and, when the condition is met, providing an action associated with the condition as the determined action.
determining from the policy a condition;
evaluating the accessed file to determine a presence of the condition; and, when the condition is met, providing an action associated with the condition as the determined action.
25. A method of managing a file lifecycle comprising the steps of:
requesting a file to be stored in a virtual cabinet in a virtual volume;
evaluating the file storage criteria based on cabinet policies of the virtual cabinet to determine a physical location wherein the file is to be stored; and, storing the file in the determined physical location.
requesting a file to be stored in a virtual cabinet in a virtual volume;
evaluating the file storage criteria based on cabinet policies of the virtual cabinet to determine a physical location wherein the file is to be stored; and, storing the file in the determined physical location.
26. A method of managing a file lifecycle according to claim 25, wherein the cabinet policies relate to file types of the file to be stored.
27. A method of managing a file lifecycle according to claim 26, wherein a virtual cabinet comprises a virtual drawer and wherein a virtual drawer forms part of more than one virtual cabinet.
28. A method of managing a file lifecycle according to claim 27, wherein the virtual cabinet forms a context within a context based file lifecycle management system and wherein a file created within a context of a virtual cabinet being subject to the policies of said virtual cabinet.
29. A method of managing a file lifecycle according to claim 25, wherein the step of storing the file comprises the step of storing the file in association with the virtual cabinet.
30. A method of managing a file lifecycle according to claim 29, wherein the file is governed by policies of the associated virtual cabinet and wherein some actions dictated by those policies are performed on the file throughout its lifecycle.
31. A method of managing a file lifecycle comprising the steps of:
selecting a virtual drawer within a virtual cabinet;
requesting a file to be stored in the virtual drawer; and, evaluating the file storage criteria based on policies associated with the virtual cabinet; in accordance with the file storage criteria, storing the file in association with the virtual cabinet.
selecting a virtual drawer within a virtual cabinet;
requesting a file to be stored in the virtual drawer; and, evaluating the file storage criteria based on policies associated with the virtual cabinet; in accordance with the file storage criteria, storing the file in association with the virtual cabinet.
32. A method of managing a file lifecycle according to claim 31, wherein the file is stored within the virtual drawer and is accessible within the virtual drawer within each of a plurality of virtual cabinets.
33. A method of managing a file lifecycle according to claim 31, wherein the policies relate to duplication of file data within a plurality of files.
34. A method of managing a file lifecycle according to claim 33, wherein the policies relate to load balancing for the virtual cabinet based on access to data that is stored in duplicate.
35. A method of managing a file lifecycle according to claim 31, wherein the policies relate to one of replication, backup, mirroring, and redundancy of file data storage within the virtual cabinet.
36. A method of managing a file lifecycle according to claim 35, wherein the policies relate to load balancing for the virtual cabinet based on access to data that is stored in more than one physical location.
37. A method of managing a file lifecycle according to claim 31, wherein the policies relate to one of version control.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/665,065 | 2000-09-19 | ||
US09/665,065 US7392234B2 (en) | 1999-05-18 | 2000-09-19 | Method and system for electronic file lifecycle management |
CA2393787A CA2393787C (en) | 2000-09-19 | 2001-09-19 | Method and system for electronic file lifecycle management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2393787A Division CA2393787C (en) | 2000-09-19 | 2001-09-19 | Method and system for electronic file lifecycle management |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2788750A1 true CA2788750A1 (en) | 2002-03-28 |
Family
ID=24668563
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2788750A Abandoned CA2788750A1 (en) | 2000-09-19 | 2001-09-19 | Method and system for electronic file lifecycle management |
CA2393787A Expired - Lifetime CA2393787C (en) | 2000-09-19 | 2001-09-19 | Method and system for electronic file lifecycle management |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2393787A Expired - Lifetime CA2393787C (en) | 2000-09-19 | 2001-09-19 | Method and system for electronic file lifecycle management |
Country Status (4)
Country | Link |
---|---|
US (3) | US7392234B2 (en) |
AU (1) | AU2001290167A1 (en) |
CA (2) | CA2788750A1 (en) |
WO (1) | WO2002025445A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111124645A (en) * | 2019-12-20 | 2020-05-08 | 网易(杭州)网络有限公司 | Discontinuous period file data processing method and device |
Families Citing this family (197)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9361243B2 (en) | 1998-07-31 | 2016-06-07 | Kom Networks Inc. | Method and system for providing restricted access to a storage medium |
US7660902B2 (en) * | 2000-11-20 | 2010-02-09 | Rsa Security, Inc. | Dynamic file access control and management |
US20040054656A1 (en) * | 2001-08-31 | 2004-03-18 | Arkivio, Inc. | Techniques for balancing capacity utilization in a storage environment |
US20040039891A1 (en) * | 2001-08-31 | 2004-02-26 | Arkivio, Inc. | Optimizing storage capacity utilization based upon data storage costs |
US7092977B2 (en) * | 2001-08-31 | 2006-08-15 | Arkivio, Inc. | Techniques for storing data based upon storage policies |
US20030115204A1 (en) * | 2001-12-14 | 2003-06-19 | Arkivio, Inc. | Structure of policy information for storage, network and data management applications |
DE10161979A1 (en) * | 2001-12-17 | 2003-06-18 | Bayer Ag | Monodisperse anion exchangers |
JP2003208347A (en) * | 2002-01-16 | 2003-07-25 | Fujitsu Ltd | Access controller, access control program, host device and host control program |
US8204930B1 (en) | 2002-02-15 | 2012-06-19 | F5 Networks, Inc. | Method and system for controlling and accessing content servers |
GB2387683B (en) * | 2002-04-19 | 2007-03-28 | Hewlett Packard Co | Workflow processing scheduler |
JP4387687B2 (en) * | 2002-04-26 | 2009-12-16 | キヤノン株式会社 | Image processing apparatus, control method, and program |
US20040083202A1 (en) * | 2002-08-30 | 2004-04-29 | Arkivio, Inc. | Techniques to control recalls in storage management applications |
AU2003293231A1 (en) * | 2002-12-02 | 2004-06-23 | Arkivio Inc. | Data recovery techniques in storage systems |
US20040117836A1 (en) * | 2002-12-11 | 2004-06-17 | Jeyhan Karaoguz | Method and system for network storage in a media exchange network |
US7478096B2 (en) * | 2003-02-26 | 2009-01-13 | Burnside Acquisition, Llc | History preservation in a computer storage system |
JP4322031B2 (en) * | 2003-03-27 | 2009-08-26 | 株式会社日立製作所 | Storage device |
WO2005001646A2 (en) | 2003-06-25 | 2005-01-06 | Arkivio, Inc. | Techniques for performing policy automated operations |
US20050038766A1 (en) * | 2003-08-12 | 2005-02-17 | International Business Machines Corporation | Agent-based personal object management |
US9489150B2 (en) | 2003-08-14 | 2016-11-08 | Dell International L.L.C. | System and method for transferring data between different raid data storage types for current data and replay data |
EP2385457A3 (en) * | 2003-08-14 | 2012-02-01 | Compellent Technologies | Virtual disk drive system and method |
JP2007502470A (en) | 2003-08-14 | 2007-02-08 | コンペレント・テクノロジーズ | Virtual disk drive system and method |
US8103873B2 (en) * | 2003-09-05 | 2012-01-24 | Emc Corporation | Method and system for processing auditory communications |
US7499531B2 (en) * | 2003-09-05 | 2009-03-03 | Emc Corporation | Method and system for information lifecycle management |
US8209185B2 (en) * | 2003-09-05 | 2012-06-26 | Emc Corporation | Interface for management of auditory communications |
US7457396B2 (en) * | 2003-09-05 | 2008-11-25 | Emc Corporation | Automated call management |
US7117322B2 (en) * | 2003-09-08 | 2006-10-03 | International Business Machines Corporation | Method, system, and program for retention management and protection of stored objects |
US7107416B2 (en) | 2003-09-08 | 2006-09-12 | International Business Machines Corporation | Method, system, and program for implementing retention policies to archive records |
US7146388B2 (en) * | 2003-10-07 | 2006-12-05 | International Business Machines Corporation | Method, system, and program for archiving files |
US7590807B2 (en) * | 2003-11-03 | 2009-09-15 | Netapp, Inc. | System and method for record retention date in a write once read many storage system |
JP2005165516A (en) | 2003-12-01 | 2005-06-23 | Hitachi Ltd | Storage controller, storage system and control method for storage system |
US9075851B2 (en) * | 2003-12-09 | 2015-07-07 | Emc Corporation | Method and apparatus for data retention in a storage system |
JP2005236515A (en) * | 2004-02-18 | 2005-09-02 | Seiko Epson Corp | Scan file generating system |
US7162602B2 (en) * | 2004-03-16 | 2007-01-09 | Hitachi, Ltd. | More granular and more efficient write protection for disk volumes |
JP4551680B2 (en) * | 2004-03-26 | 2010-09-29 | キヤノン株式会社 | Document management system, document management method and program, and storage medium |
US8041713B2 (en) * | 2004-03-31 | 2011-10-18 | Google Inc. | Systems and methods for analyzing boilerplate |
US9009153B2 (en) | 2004-03-31 | 2015-04-14 | Google Inc. | Systems and methods for identifying a named entity |
US7707142B1 (en) * | 2004-03-31 | 2010-04-27 | Google Inc. | Methods and systems for performing an offline search |
US20080040315A1 (en) * | 2004-03-31 | 2008-02-14 | Auerbach David B | Systems and methods for generating a user interface |
US7664734B2 (en) * | 2004-03-31 | 2010-02-16 | Google Inc. | Systems and methods for generating multiple implicit search queries |
US7272601B1 (en) | 2004-03-31 | 2007-09-18 | Google Inc. | Systems and methods for associating a keyword with a user interface area |
US7693825B2 (en) | 2004-03-31 | 2010-04-06 | Google Inc. | Systems and methods for ranking implicit search results |
US8631001B2 (en) * | 2004-03-31 | 2014-01-14 | Google Inc. | Systems and methods for weighting a search query result |
US7788274B1 (en) | 2004-06-30 | 2010-08-31 | Google Inc. | Systems and methods for category-based search |
US8131754B1 (en) | 2004-06-30 | 2012-03-06 | Google Inc. | Systems and methods for determining an article association measure |
US20060004579A1 (en) * | 2004-07-01 | 2006-01-05 | Claudatos Christopher H | Flexible video surveillance |
US8180743B2 (en) * | 2004-07-01 | 2012-05-15 | Emc Corporation | Information management |
US8180742B2 (en) * | 2004-07-01 | 2012-05-15 | Emc Corporation | Policy-based information management |
US7444287B2 (en) * | 2004-07-01 | 2008-10-28 | Emc Corporation | Efficient monitoring system and method |
US7707037B2 (en) * | 2004-07-01 | 2010-04-27 | Emc Corporation | Archiving of surveillance data |
US8244542B2 (en) * | 2004-07-01 | 2012-08-14 | Emc Corporation | Video surveillance |
US20060004818A1 (en) * | 2004-07-01 | 2006-01-05 | Claudatos Christopher H | Efficient information management |
US9268780B2 (en) * | 2004-07-01 | 2016-02-23 | Emc Corporation | Content-driven information lifecycle management |
US8229904B2 (en) * | 2004-07-01 | 2012-07-24 | Emc Corporation | Storage pools for information management |
US8626514B2 (en) * | 2004-08-31 | 2014-01-07 | Emc Corporation | Interface for management of multiple auditory communications |
US7827180B2 (en) * | 2004-11-05 | 2010-11-02 | Intenational Business Machines Corporation | Methods and apparatus for assigning content identifiers to content portions |
US7765400B2 (en) * | 2004-11-08 | 2010-07-27 | Microsoft Corporation | Aggregation of the knowledge base of antivirus software |
JP2006139552A (en) | 2004-11-12 | 2006-06-01 | Hitachi Ltd | Storage device and data life cycle management method for storage device |
US20060106782A1 (en) * | 2004-11-17 | 2006-05-18 | Steven Blumenau | Systems and methods for searching digital assets using virtual folders having labels based on taxonomy tags |
US20060123232A1 (en) * | 2004-12-08 | 2006-06-08 | International Business Machines Corporation | Method for protecting and managing retention of data on worm media |
US7979405B2 (en) * | 2005-01-14 | 2011-07-12 | Microsoft Corporation | Method for automatically associating data with a document based on a prescribed type of the document |
JP2006215954A (en) * | 2005-02-07 | 2006-08-17 | Hitachi Ltd | Storage system and archive management method for storage system |
US7966286B2 (en) * | 2005-02-14 | 2011-06-21 | Microsoft Corporation | Hierarchical management of object schema and behavior |
US7756154B2 (en) * | 2005-03-22 | 2010-07-13 | Netapp, Inc. | Shared implementation for multiple system interfaces |
US20060230086A1 (en) * | 2005-04-06 | 2006-10-12 | International Business Machines Corporation | QoS-enabled lifecycle management for file systems |
US7734869B1 (en) | 2005-04-28 | 2010-06-08 | Netapp, Inc. | Interfaces for flexible storage management |
JP4648751B2 (en) | 2005-05-02 | 2011-03-09 | 株式会社日立製作所 | Storage control system and storage control method |
US7711916B2 (en) * | 2005-05-11 | 2010-05-04 | Oracle International Corporation | Storing information on storage devices having different performance capabilities with a storage system |
US7680830B1 (en) * | 2005-05-31 | 2010-03-16 | Symantec Operating Corporation | System and method for policy-based data lifecycle management |
JP2006350599A (en) * | 2005-06-15 | 2006-12-28 | Hitachi Ltd | Storage system and data migration method thereof |
US7529903B2 (en) * | 2005-07-05 | 2009-05-05 | International Business Machines Corporation | Systems and methods for memory migration |
US20070028291A1 (en) * | 2005-07-29 | 2007-02-01 | Bit 9, Inc. | Parametric content control in a network security system |
US8130759B2 (en) | 2005-07-29 | 2012-03-06 | Opnet Technologies, Inc. | Routing validation |
US8140665B2 (en) * | 2005-08-19 | 2012-03-20 | Opnet Technologies, Inc. | Managing captured network traffic data |
JP4717743B2 (en) * | 2005-08-23 | 2011-07-06 | 株式会社リコー | Information processing device |
US7970743B1 (en) | 2005-09-15 | 2011-06-28 | Emc Corporation | Retention and disposition of stored content associated with multiple stored objects |
US20070083482A1 (en) * | 2005-10-08 | 2007-04-12 | Unmesh Rathi | Multiple quality of service file system |
JP2007128448A (en) * | 2005-11-07 | 2007-05-24 | Sony Corp | File system and file information processing method |
US7636737B2 (en) * | 2005-12-20 | 2009-12-22 | Microsoft Corporation | Web site multi-stage recycling |
US20070185879A1 (en) * | 2005-12-23 | 2007-08-09 | Metacommunications, Inc. | Systems and methods for archiving and retrieving digital assets |
US7552300B2 (en) | 2006-01-03 | 2009-06-23 | International Business Machines Corporation | Method for migrating objects in content management systems through exploitation of file properties, temporal locality, and spatial locality |
EP2100235A2 (en) * | 2006-01-25 | 2009-09-16 | Network Appliance, Inc. | Method and apparatus to automatically commit files to worm status |
US20070179854A1 (en) * | 2006-01-30 | 2007-08-02 | M-Systems | Media predictive consignment |
US8170985B2 (en) * | 2006-01-31 | 2012-05-01 | Emc Corporation | Primary stub file retention and secondary retention coordination in a hierarchical storage system |
US7594082B1 (en) * | 2006-03-07 | 2009-09-22 | Emc Corporation | Resolving retention policy conflicts |
US7818300B1 (en) * | 2006-03-07 | 2010-10-19 | Emc Corporation | Consistent retention and disposition of managed content and associated metadata |
US8577852B2 (en) * | 2006-03-23 | 2013-11-05 | Infaxiom Group, Llc | Automated records inventory and retention schedule generation system |
US20070271308A1 (en) * | 2006-05-22 | 2007-11-22 | Iron Mountain Incorporated | Methods and apparatus for managing retention of information assets |
CN102880424B (en) | 2006-05-24 | 2015-10-28 | 克姆佩棱特科技公司 | For RAID management, redistribute and the system and method for segmentation again |
US8135990B2 (en) | 2006-08-11 | 2012-03-13 | Opnet Technologies, Inc. | Multi-variate network survivability analysis |
US20080077633A1 (en) * | 2006-09-25 | 2008-03-27 | International Business Machines Corporation | Method for policy-based data placement when restoring files from off-line storage |
US9063940B1 (en) * | 2006-09-29 | 2015-06-23 | Emc Corporation | Superseding objects in a retention system |
US9489456B1 (en) * | 2006-11-17 | 2016-11-08 | Blue Coat Systems, Inc. | Previewing file information over a network |
US20080147963A1 (en) * | 2006-12-15 | 2008-06-19 | Accusys. Inc. | Disk array device |
US8918427B1 (en) | 2006-12-29 | 2014-12-23 | Symantec Operating Corporation | Virtualization of file input/output operations |
US7953928B2 (en) * | 2007-02-22 | 2011-05-31 | Network Appliance, Inc. | Apparatus and a method to make data sets conform to data management policies |
US20080208926A1 (en) * | 2007-02-22 | 2008-08-28 | Smoot Peter L | Data management in a data storage system using data sets |
US7747589B2 (en) * | 2007-03-12 | 2010-06-29 | Microsoft Corporation | Transaction time indexing with version compression |
JP5212921B2 (en) * | 2007-03-12 | 2013-06-19 | 日本電気株式会社 | File server system and file management method |
JP4847375B2 (en) * | 2007-03-16 | 2011-12-28 | キヤノン株式会社 | Information processing apparatus, information processing apparatus control method, storage medium, and program |
US7720819B2 (en) * | 2007-04-12 | 2010-05-18 | International Business Machines Corporation | Method and apparatus combining revision based and time based file data protection |
US8621008B2 (en) | 2007-04-26 | 2013-12-31 | Mcafee, Inc. | System, method and computer program product for performing an action based on an aspect of an electronic mail message thread |
US8095649B2 (en) | 2007-05-09 | 2012-01-10 | Opnet Technologies, Inc. | Network delay analysis including parallel delay effects |
US20090063587A1 (en) | 2007-07-12 | 2009-03-05 | Jakob Holger | Method and system for function-specific time-configurable replication of data manipulating functions |
US7921268B2 (en) | 2007-07-12 | 2011-04-05 | Jakob Holger | Method and system for function-specific time-configurable replication of data |
US8161011B2 (en) * | 2007-07-31 | 2012-04-17 | International Business Machines Corporation | Apparatus, system, and method for analyzing a file system |
US8199965B1 (en) | 2007-08-17 | 2012-06-12 | Mcafee, Inc. | System, method, and computer program product for preventing image-related data loss |
US10606901B1 (en) * | 2007-09-28 | 2020-03-31 | Emc Corporation | Data disposition services orchestrated in an information management infrastructure |
US8918603B1 (en) * | 2007-09-28 | 2014-12-23 | Emc Corporation | Storage of file archiving metadata |
US8291179B2 (en) * | 2007-10-05 | 2012-10-16 | Imation Corp. | Methods for implementation of worm enforcement in a storage system |
US20090106815A1 (en) * | 2007-10-23 | 2009-04-23 | International Business Machines Corporation | Method for mapping privacy policies to classification labels |
US20090112789A1 (en) * | 2007-10-31 | 2009-04-30 | Fernando Oliveira | Policy based file management |
US9143561B2 (en) | 2007-11-09 | 2015-09-22 | Topia Technology, Inc. | Architecture for management of digital files across distributed network |
DK2060973T3 (en) | 2007-11-14 | 2012-01-02 | Holger Jakob Informatio | Process and system for feature specific time configurable replication of data manipulation features |
US8266122B1 (en) * | 2007-12-19 | 2012-09-11 | Amazon Technologies, Inc. | System and method for versioning data in a distributed data store |
US20090171965A1 (en) * | 2007-12-28 | 2009-07-02 | Bruce Backa | System and Method For Policy Based Control of NAS Storage Devices |
US8171244B2 (en) | 2008-02-01 | 2012-05-01 | Imation Corp. | Methods for implementation of worm mode on a removable disk drive storage system |
JP5127489B2 (en) * | 2008-02-07 | 2013-01-23 | 株式会社東芝 | Information life cycle management system, information management server device, electronic medium control device, and program |
US8631470B2 (en) | 2008-02-20 | 2014-01-14 | Bruce R. Backa | System and method for policy based control of NAS storage devices |
US8549654B2 (en) | 2008-02-20 | 2013-10-01 | Bruce Backa | System and method for policy based control of NAS storage devices |
US8893285B2 (en) | 2008-03-14 | 2014-11-18 | Mcafee, Inc. | Securing data using integrated host-based data loss agent with encryption detection |
US8745346B2 (en) * | 2008-03-18 | 2014-06-03 | Microsoft Corporation | Time managed read and write access to a data storage device |
US8117165B1 (en) | 2008-04-30 | 2012-02-14 | Netapp, Inc. | Disk-to-disk backup of database archive logs |
US9077684B1 (en) | 2008-08-06 | 2015-07-07 | Mcafee, Inc. | System, method, and computer program product for determining whether an electronic mail message is compliant with an etiquette policy |
JP5183363B2 (en) * | 2008-08-26 | 2013-04-17 | 株式会社日立製作所 | Logical volume data migration method, storage system, and management computer |
JP4576449B2 (en) * | 2008-08-29 | 2010-11-10 | 富士通株式会社 | Switch device and copy control method |
JP2010097359A (en) * | 2008-10-15 | 2010-04-30 | Hitachi Ltd | File management method and hierarchy management file system |
US20110208779A1 (en) * | 2008-12-23 | 2011-08-25 | Backa Bruce R | System and Method for Policy Based Control of NAS Storage Devices |
US20100257218A1 (en) * | 2009-04-03 | 2010-10-07 | Konstantin Iliev Vassilev | Merging multiple heterogeneous file systems into a single virtual unified file system |
EP2441020A4 (en) * | 2009-06-11 | 2013-04-03 | Bruce R Backa | System and method for end-user archiving |
US8725780B2 (en) | 2009-06-12 | 2014-05-13 | Imation Corp. | Methods and systems for rule-based worm enforcement |
US9507793B2 (en) | 2009-09-29 | 2016-11-29 | International Business Machines Corporation | File resharing management |
US9092597B2 (en) * | 2009-12-09 | 2015-07-28 | Sandisk Technologies Inc. | Storage device and method for using a virtual file in a public memory area to access a plurality of protected files in a private memory area |
US8190578B2 (en) * | 2009-12-17 | 2012-05-29 | International Business Machines Corporation | Migration of versioned data between configuration management systems |
US8316197B1 (en) * | 2010-03-01 | 2012-11-20 | Symantec Corporation | Techniques for storage lifecycle policy management |
US10296711B2 (en) | 2010-05-17 | 2019-05-21 | International Business Machines Corporation | Client-server multimedia archiving system with metadata encapsulation |
US8301715B2 (en) | 2010-05-20 | 2012-10-30 | Sandisk Il Ltd. | Host device and method for accessing a virtual file in a storage device by bypassing a cache in the host device |
US8301645B1 (en) | 2010-08-26 | 2012-10-30 | Adobe Systems Incorporated | Aggregated web analytics request systems and methods |
US8706697B2 (en) * | 2010-12-17 | 2014-04-22 | Microsoft Corporation | Data retention component and framework |
JP5871583B2 (en) * | 2011-11-22 | 2016-03-01 | キヤノン株式会社 | Document management apparatus, control method therefor, and program |
US8725741B2 (en) | 2011-12-04 | 2014-05-13 | Riverbed Technology, Inc. | Assessing application performance with an operational index |
US10324893B1 (en) * | 2011-12-15 | 2019-06-18 | Veritas Technologies Llc | Backup application catalog analyzer |
US9391935B1 (en) * | 2011-12-19 | 2016-07-12 | Veritas Technologies Llc | Techniques for file classification information retention |
US10019462B1 (en) * | 2011-12-30 | 2018-07-10 | Emc Corporation | System and method of hierarchical archive management |
US8452741B1 (en) * | 2012-02-27 | 2013-05-28 | Sap Ag | Reconciling data retention requirements |
US9146851B2 (en) | 2012-03-26 | 2015-09-29 | Compellent Technologies | Single-level cell and multi-level cell hybrid solid state drive |
US9098202B2 (en) | 2012-04-27 | 2015-08-04 | Hitachi, Ltd. | Storage apparatus and data management method |
US9171178B1 (en) * | 2012-05-14 | 2015-10-27 | Symantec Corporation | Systems and methods for optimizing security controls for virtual data centers |
US10289685B2 (en) * | 2012-09-07 | 2019-05-14 | International Business Machines Corporation | Information lifecycle governance |
US8984251B2 (en) * | 2012-12-04 | 2015-03-17 | Apple Inc. | Hinting of deleted data from host to storage device |
US8769633B1 (en) | 2012-12-12 | 2014-07-01 | Bruce R. Backa | System and method for policy based control of NAS storage devices |
US9417917B1 (en) | 2012-12-14 | 2016-08-16 | Amazon Technologies, Inc. | Equitable resource allocation for storage object deletion |
US9063946B1 (en) | 2012-12-14 | 2015-06-23 | Amazon Technologies, Inc. | Backoff-based scheduling of storage object deletions |
US9727522B1 (en) | 2012-12-14 | 2017-08-08 | Amazon Technologies, Inc. | Multi-tenant storage service object lifecycle management using transition job objects |
US9658983B1 (en) | 2012-12-14 | 2017-05-23 | Amazon Technologies, Inc. | Lifecycle support for storage objects having multiple durability levels specifying different numbers of versions |
US9052942B1 (en) | 2012-12-14 | 2015-06-09 | Amazon Technologies, Inc. | Storage object deletion job management |
US9002805B1 (en) | 2012-12-14 | 2015-04-07 | Amazon Technologies, Inc. | Conditional storage object deletion |
US9355060B1 (en) | 2012-12-14 | 2016-05-31 | Amazon Technologies, Inc. | Storage service lifecycle policy transition management |
US20140181112A1 (en) * | 2012-12-26 | 2014-06-26 | Hon Hai Precision Industry Co., Ltd. | Control device and file distribution method |
JP6131647B2 (en) * | 2013-03-15 | 2017-05-24 | 富士ゼロックス株式会社 | Information processing apparatus, program, and file management system |
US9418346B2 (en) * | 2013-03-28 | 2016-08-16 | Nokia Technologies Oy | Method and apparatus for providing a drawer-based user interface for content access or recommendation |
US9514150B2 (en) * | 2013-04-19 | 2016-12-06 | Hewlett Packard Enterprise Development Lp | Automatic WORM-retention state transitions |
WO2015010099A1 (en) * | 2013-07-19 | 2015-01-22 | Minder, LLC | Systems and methods for managing and organizing documents |
US10078656B1 (en) * | 2013-07-26 | 2018-09-18 | Amazon Technologies, Inc. | Unmodifiable data in a storage service |
US9262448B2 (en) * | 2013-08-12 | 2016-02-16 | International Business Machines Corporation | Data backup across physical and virtualized storage volumes |
US20150213045A1 (en) * | 2014-01-24 | 2015-07-30 | Alcatel-Lucent Israel Ltd. | Methods And Systems For Storing Replicated Data In The Cloud |
US20150244972A1 (en) * | 2014-02-27 | 2015-08-27 | United Video Properties Inc. | Methods and systems for determining lengths of time for retaining media assets |
JP6344046B2 (en) * | 2014-05-14 | 2018-06-20 | 富士ゼロックス株式会社 | Information processing apparatus and information processing program |
US10503713B1 (en) * | 2014-05-19 | 2019-12-10 | Amazon Technologies, Inc. | Criterion-based retention of data object versions |
WO2016148738A1 (en) * | 2015-03-13 | 2016-09-22 | Hewlett Packard Enterprise Development Lp | File management |
US10783113B2 (en) | 2015-06-11 | 2020-09-22 | Oracle International Corporation | Data retention framework |
WO2016200403A1 (en) * | 2015-06-12 | 2016-12-15 | Hewlett Packard Enterprise Development Lp | Disk storage allocation |
US10042556B2 (en) * | 2015-07-30 | 2018-08-07 | International Business Machines Corporation | Reclamation of storage medium |
US10762041B2 (en) * | 2015-08-31 | 2020-09-01 | Netapp, Inc. | Event based retention of read only files |
US10601894B1 (en) | 2015-09-28 | 2020-03-24 | Amazon Technologies, Inc. | Vector-based encoding for content rendering |
US10691750B1 (en) * | 2015-09-28 | 2020-06-23 | Amazon Technologies, Inc. | Browser configured to efficiently store browsing session state |
US11263171B2 (en) * | 2015-12-09 | 2022-03-01 | Druva Inc. | Unified time-indexed catalogue for multiple archived snapshots |
CN106446201A (en) * | 2016-09-30 | 2017-02-22 | 福建中金在线信息科技有限公司 | Processing method and device of social circle data |
US10095700B2 (en) * | 2017-01-18 | 2018-10-09 | HGST, Inc. | Persistent file handle object container memory expiry |
US10802746B1 (en) * | 2017-03-02 | 2020-10-13 | Amazon Technologies, Inc. | Policy-driven multiple storage class representation in versioned storage |
US10459647B1 (en) | 2017-03-02 | 2019-10-29 | Amazon Technologies, Inc. | Multiple storage class representation in versioned storage |
US10846263B2 (en) * | 2017-09-22 | 2020-11-24 | Microsoft Technology Licensing, Llc | Systems and methods for implementing content aware file management labeling |
US11048671B2 (en) * | 2017-10-18 | 2021-06-29 | Quantum Corporation | Automated storage tier copy expiration |
EP3477490A1 (en) | 2017-10-26 | 2019-05-01 | Druva Technologies Pte. Ltd. | Deduplicated merged indexed object storage file system |
US11416629B2 (en) | 2018-01-30 | 2022-08-16 | EMC IP Holding Company LLC | Method for dynamic pseudofs creation and management in a network filesystem |
US11436354B2 (en) * | 2018-01-30 | 2022-09-06 | EMC IP Holding Company LLC | Sparse creation of per-client pseudofs in network filesystem with lookup hinting |
US10540669B2 (en) | 2018-05-30 | 2020-01-21 | Sas Institute Inc. | Managing object values and resource consumption |
CN109033357B (en) * | 2018-07-24 | 2021-12-03 | 广东浪潮大数据研究有限公司 | Synchronization method and device for WORM attribute |
US11651373B2 (en) * | 2019-06-21 | 2023-05-16 | Bank Of America Corporation | Edge-computing-based bottom-up hierarchical architecture for data administration in a digital network |
GB201913348D0 (en) * | 2019-09-16 | 2019-10-30 | Palantir Technologies Inc | Data deletion system and method |
CN110866291B (en) * | 2019-11-15 | 2023-03-24 | 北京工业大学 | Waste electronic product information clearing method based on dual security mechanisms |
CN111198856B (en) * | 2019-12-31 | 2023-12-29 | 北京旷视科技有限公司 | File management method, device, computer equipment and storage medium |
US11416156B2 (en) * | 2020-02-24 | 2022-08-16 | Netapp, Inc. | Object tiering in a distributed storage system |
US11762806B2 (en) * | 2020-10-15 | 2023-09-19 | EMC IP Holding Company LLC | Hardening system clock for retention lock compliance enabled systems |
US20220222006A1 (en) * | 2021-01-14 | 2022-07-14 | Seagate Technology Llc | In-device handling of file and object life cycle |
US20220300454A1 (en) * | 2021-03-18 | 2022-09-22 | Avaya Management L.P. | Systems and methods of curating data |
US11599296B2 (en) * | 2021-07-30 | 2023-03-07 | Netapp, Inc. | Immutable snapshot copies stored in write once read many (WORM) storage |
CN114153395A (en) * | 2021-11-30 | 2022-03-08 | 浙江大华技术股份有限公司 | Object storage data life cycle management method, device and equipment |
Family Cites Families (168)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4104718A (en) | 1974-12-16 | 1978-08-01 | Compagnie Honeywell Bull (Societe Anonyme) | System for protecting shared files in a multiprogrammed computer |
US4825354A (en) | 1985-11-12 | 1989-04-25 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of file access in a distributed processing computer network |
US4887204A (en) | 1987-02-13 | 1989-12-12 | International Business Machines Corporation | System and method for accessing remote files in a distributed networking environment |
US4914571A (en) | 1987-06-15 | 1990-04-03 | International Business Machines Corporation | Locating resources in computer networks |
US5008853A (en) | 1987-12-02 | 1991-04-16 | Xerox Corporation | Representation of collaborative multi-user activities relative to shared structured data objects in a networked workstation environment |
US5455926A (en) | 1988-04-05 | 1995-10-03 | Data/Ware Development, Inc. | Virtual addressing of optical storage media as magnetic tape equivalents |
US4993030A (en) | 1988-04-22 | 1991-02-12 | Amdahl Corporation | File system for a plurality of storage classes |
US4989206A (en) | 1988-06-28 | 1991-01-29 | Storage Technology Corporation | Disk drive memory |
US5379423A (en) | 1988-09-28 | 1995-01-03 | Hitachi, Ltd. | Information life cycle processor and information organizing method using it |
DE3843218A1 (en) | 1988-12-22 | 1990-06-28 | Grau Gmbh & Co Holdingges | METHOD AND DEVICE FOR OPERATING AN AUTOMATIC DATA CARRIER ARCHIVE |
GB8915136D0 (en) | 1989-06-30 | 1989-08-23 | Inmos Ltd | Method for controlling communication between computers |
JPH05504428A (en) | 1989-08-01 | 1993-07-08 | シリコン・グラフィックス,インコーポレイテッド | File change monitor for computer operating and file management systems |
US5029199A (en) | 1989-08-10 | 1991-07-02 | Boston Technology | Distributed control and storage for a large capacity messaging system |
JPH0388052A (en) | 1989-08-31 | 1991-04-12 | Toshiba Corp | Secrecy protection processing system |
US5276867A (en) | 1989-12-19 | 1994-01-04 | Epoch Systems, Inc. | Digital data storage system with improved data migration |
US5347628A (en) | 1990-01-18 | 1994-09-13 | International Business Machines Corporation | Method of graphically accessing electronic data |
US5095423A (en) | 1990-03-27 | 1992-03-10 | Sun Microsystems, Inc. | Locking mechanism for the prevention of race conditions |
US5193184A (en) | 1990-06-18 | 1993-03-09 | Storage Technology Corporation | Deleted data file space release system for a dynamically mapped virtual data storage subsystem |
US5317728A (en) | 1990-09-07 | 1994-05-31 | International Business Machines Corporation | Storage management of a first file system using a second file system containing surrogate files and catalog management information |
US5222242A (en) | 1990-09-28 | 1993-06-22 | International Business Machines Corp. | System for locating a node containing a requested resource and for selectively verifying the presence of the resource at the node |
US5313631A (en) | 1991-05-21 | 1994-05-17 | Hewlett-Packard Company | Dual threshold system for immediate or delayed scheduled migration of computer data files |
JP2550239B2 (en) | 1991-09-12 | 1996-11-06 | 株式会社日立製作所 | External storage system |
US5377323A (en) | 1991-09-13 | 1994-12-27 | Sun Microsytems, Inc. | Apparatus and method for a federated naming system which can resolve a composite name composed of names from any number of disparate naming systems |
US5367698A (en) | 1991-10-31 | 1994-11-22 | Epoch Systems, Inc. | Network file migration system |
US5434974A (en) | 1992-03-30 | 1995-07-18 | International Business Machines Corporation | Name resolution for a multisystem network |
US5649095A (en) | 1992-03-30 | 1997-07-15 | Cozza; Paul D. | Method and apparatus for detecting computer viruses through the use of a scan information cache |
US5493607A (en) | 1992-04-21 | 1996-02-20 | Boston Technology | Multi-system network addressing |
US5267698A (en) * | 1992-04-28 | 1993-12-07 | Pettit Ashma B | Coconut grinder |
US5425028A (en) | 1992-07-16 | 1995-06-13 | International Business Machines Corporation | Protocol selection and address resolution for programs running in heterogeneous networks |
JPH0659982A (en) | 1992-08-10 | 1994-03-04 | Hitachi Ltd | Method and device for controlling virtual storage |
US5991753A (en) | 1993-06-16 | 1999-11-23 | Lachman Technology, Inc. | Method and system for computer file management, including file migration, special handling, and associating extended attributes with files |
US5408630A (en) * | 1993-08-20 | 1995-04-18 | Iii G.I. Ltd. | Three-state virtual volume system for managing document storage to permanent media |
US5542045A (en) | 1993-10-15 | 1996-07-30 | Software Security, Inc. | Method for interposing a security function in a computer program |
US5771354A (en) | 1993-11-04 | 1998-06-23 | Crawford; Christopher M. | Internet online backup system provides remote storage for customers using IDs and passwords which were interactively established when signing up for backup services |
US5509120A (en) | 1993-11-30 | 1996-04-16 | International Business Machines Corporation | Method and system for detecting computer viruses during power on self test |
US5701462A (en) | 1993-12-29 | 1997-12-23 | Microsoft Corporation | Distributed file system providing a unified name space with efficient name resolution |
US5689700A (en) * | 1993-12-29 | 1997-11-18 | Microsoft Corporation | Unification of directory service with file system services |
US5537585A (en) | 1994-02-25 | 1996-07-16 | Avail Systems Corporation | Data storage management for network interconnected processors |
JPH07302185A (en) * | 1994-03-01 | 1995-11-14 | Microsoft Corp | Folder rack icon |
JP2682811B2 (en) | 1994-03-22 | 1997-11-26 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Data storage management system and method |
US5831606A (en) * | 1994-12-13 | 1998-11-03 | Microsoft Corporation | Shell extensions for an operating system |
EP0826181A4 (en) * | 1995-04-11 | 2005-02-09 | Kinetech Inc | Identifying data in a data processing system |
US5805809A (en) | 1995-04-26 | 1998-09-08 | Shiva Corporation | Installable performance accelerator for maintaining a local cache storing data residing on a server computer |
JPH0944381A (en) | 1995-07-31 | 1997-02-14 | Toshiba Corp | Method and device for data storage |
US5877765A (en) * | 1995-09-11 | 1999-03-02 | Microsoft Corporation | Method and system for displaying internet shortcut icons on the desktop |
US5751287A (en) | 1995-11-06 | 1998-05-12 | Documagix, Inc. | System for organizing document icons with suggestions, folders, drawers, and cabinets |
US5778384A (en) * | 1995-12-22 | 1998-07-07 | Sun Microsystems, Inc. | System and method for automounting and accessing remote file systems in Microsoft Windows in a networking environment |
US5884033A (en) | 1996-05-15 | 1999-03-16 | Spyglass, Inc. | Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions |
US5923848A (en) * | 1996-05-31 | 1999-07-13 | Microsoft Corporation | System and method for resolving names in an electronic messaging environment |
US5768532A (en) * | 1996-06-17 | 1998-06-16 | International Business Machines Corporation | Method and distributed database file system for implementing self-describing distributed file objects |
US5862331A (en) * | 1996-06-21 | 1999-01-19 | Sun Microsystems, Inc. | Name service system and method for automatic updating on interconnected hosts |
US5793970A (en) * | 1996-07-11 | 1998-08-11 | Microsoft Corporation | Method and computer program product for converting message identification codes using a conversion map accesible via a data link |
US5838326A (en) | 1996-09-26 | 1998-11-17 | Xerox Corporation | System for moving document objects in a 3-D workspace |
DE19645128C2 (en) | 1996-11-04 | 1999-02-11 | Anja David | Procedure for managing documents and device drivers for performing the procedure |
US6453345B2 (en) | 1996-11-06 | 2002-09-17 | Datadirect Networks, Inc. | Network security and surveillance system |
US5987506A (en) * | 1996-11-22 | 1999-11-16 | Mangosoft Corporation | Remote access and geographically distributed computers in a globally addressable storage environment |
US5909540A (en) * | 1996-11-22 | 1999-06-01 | Mangosoft Corporation | System and method for providing highly available data storage using globally addressable memory |
US6647393B1 (en) * | 1996-11-22 | 2003-11-11 | Mangosoft Corporation | Dynamic directory service |
US6148377A (en) * | 1996-11-22 | 2000-11-14 | Mangosoft Corporation | Shared memory computer networks |
JP3193880B2 (en) | 1996-12-11 | 2001-07-30 | 株式会社日立製作所 | Data migration method |
US5956481A (en) | 1997-02-06 | 1999-09-21 | Microsoft Corporation | Method and apparatus for protecting data files on a computer from virus infection |
US5936624A (en) | 1997-03-07 | 1999-08-10 | International Business Machines Corporation | Data processing system having a logical containment system and method therefor |
US5969720A (en) | 1997-03-07 | 1999-10-19 | International Business Machines Corporation | Data processing system and method for implementing an informative container for a file system |
US6023744A (en) | 1997-03-07 | 2000-02-08 | Microsoft Corporation | Method and mechanism for freeing disk space in a file system |
US6101506A (en) | 1997-05-01 | 2000-08-08 | Hitachi, Ltd. | Method and system for managing files by version and programs therefor |
US5978815A (en) | 1997-06-13 | 1999-11-02 | Microsoft Corporation | File system primitive providing native file system support for remote storage |
US5946685A (en) * | 1997-06-27 | 1999-08-31 | Sun Microsystems, Inc. | Global mount mechanism used in maintaining a global name space utilizing a distributed locking mechanism |
US6366988B1 (en) | 1997-07-18 | 2002-04-02 | Storactive, Inc. | Systems and methods for electronic data storage management |
US5919257A (en) | 1997-08-08 | 1999-07-06 | Novell, Inc. | Networked workstation intrusion detection system |
US6249866B1 (en) | 1997-09-16 | 2001-06-19 | Microsoft Corporation | Encrypting file system and method |
US5991777A (en) * | 1997-09-19 | 1999-11-23 | Microsoft Corporation | System and method for performing defined actions when grafting the name space of one storage medium into the name space of another storage medium |
US6125373A (en) * | 1997-09-19 | 2000-09-26 | Microsoft Corporation | Identifying a driver that is an owner of an active mount point |
US6240414B1 (en) * | 1997-09-28 | 2001-05-29 | Eisolutions, Inc. | Method of resolving data conflicts in a shared data environment |
US6148369A (en) | 1997-09-30 | 2000-11-14 | Emc Corp | Method and apparatus for providing logical devices spanning several physical volumes |
US6088803A (en) | 1997-12-30 | 2000-07-11 | Intel Corporation | System for virus-checking network data during download to a client device |
US5950203A (en) | 1997-12-31 | 1999-09-07 | Mercury Computer Systems, Inc. | Method and apparatus for high-speed access to and sharing of storage devices on a networked digital data processing system |
US6026402A (en) | 1998-01-07 | 2000-02-15 | Hewlett-Packard Company | Process restriction within file system hierarchies |
US6292844B1 (en) | 1998-02-12 | 2001-09-18 | Sony Corporation | Media storage device with embedded data filter for dynamically processing data during read and write operations |
US5987610A (en) | 1998-02-12 | 1999-11-16 | Ameritech Corporation | Computer virus screening methods and systems |
US6697846B1 (en) * | 1998-03-20 | 2004-02-24 | Dataplow, Inc. | Shared file system |
US6256031B1 (en) * | 1998-06-26 | 2001-07-03 | Microsoft Corporation | Integration of physical and virtual namespace |
JP2000048066A (en) | 1998-07-27 | 2000-02-18 | Hitachi Ltd | Life cycle management method, its system and product |
US6438642B1 (en) | 1999-05-18 | 2002-08-20 | Kom Networks Inc. | File-based virtual storage file system, method and computer program product for automated file management on multiple file system storage devices |
US6366987B1 (en) * | 1998-08-13 | 2002-04-02 | Emc Corporation | Computer data storage physical backup and logical restore |
US6269382B1 (en) | 1998-08-31 | 2001-07-31 | Microsoft Corporation | Systems and methods for migration and recall of data from local and remote storage |
US6240421B1 (en) * | 1998-09-08 | 2001-05-29 | Edwin J. Stolarz | System, software and apparatus for organizing, storing and retrieving information from a computer database |
US6577920B1 (en) | 1998-10-02 | 2003-06-10 | Data Fellows Oyj | Computer virus screening |
US6266774B1 (en) | 1998-12-08 | 2001-07-24 | Mcafee.Com Corporation | Method and system for securing, managing or optimizing a personal computer |
US6356915B1 (en) * | 1999-02-22 | 2002-03-12 | Starbase Corp. | Installable file system having virtual file system drive, virtual device driver, and virtual disks |
US6754696B1 (en) | 1999-03-25 | 2004-06-22 | Micosoft Corporation | Extended file system |
US6654830B1 (en) * | 1999-03-25 | 2003-11-25 | Dell Products L.P. | Method and system for managing data migration for a storage system |
TW460812B (en) * | 1999-03-31 | 2001-10-21 | Ibm | Automated file pruning |
US6389432B1 (en) * | 1999-04-05 | 2002-05-14 | Auspex Systems, Inc. | Intelligent virtual volume access |
US6594675B1 (en) * | 1999-08-26 | 2003-07-15 | International Business Machines Corporation | Method, system for using file name to access application program where a logical file system processes pathname to determine whether the request is a file on storage device or operation for application program |
US6381619B1 (en) | 1999-09-13 | 2002-04-30 | Hewlett-Packard Company | Computer data storage system with migration plan generator |
US6266679B1 (en) * | 1999-10-12 | 2001-07-24 | Amd. Inc. | Method and apparatus for hierarchical storage of data for efficient archiving and retrieval of data |
US20020069214A1 (en) | 1999-12-02 | 2002-06-06 | Smith John M. | Document services architecture |
US6195650B1 (en) * | 2000-02-02 | 2001-02-27 | Hewlett-Packard Company | Method and apparatus for virtualizing file access operations and other I/O operations |
JP3551113B2 (en) * | 2000-02-07 | 2004-08-04 | 日本電気株式会社 | Divider |
US6915435B1 (en) * | 2000-02-09 | 2005-07-05 | Sun Microsystems, Inc. | Method and system for managing information retention |
US6778346B2 (en) | 2000-03-30 | 2004-08-17 | Sony Corporation | Recording and reproducing apparatus and file managing method using the same |
US6971018B1 (en) | 2000-04-28 | 2005-11-29 | Microsoft Corporation | File protection service for a computer system |
US6745207B2 (en) * | 2000-06-02 | 2004-06-01 | Hewlett-Packard Development Company, L.P. | System and method for managing virtual storage |
US20020035696A1 (en) | 2000-06-09 | 2002-03-21 | Will Thacker | System and method for protecting a networked computer from viruses |
US20020111956A1 (en) | 2000-09-18 | 2002-08-15 | Boon-Lock Yeo | Method and apparatus for self-management of content across multiple storage systems |
AU2002211893A1 (en) | 2000-10-10 | 2002-04-22 | Terrance Brown | System and methods for tracking central office equipment and inventory records |
US7054927B2 (en) * | 2001-01-29 | 2006-05-30 | Adaptec, Inc. | File system metadata describing server directory information |
US6718435B2 (en) | 2001-08-14 | 2004-04-06 | International Business Machines Corporation | Method and system for migrating data in a raid logical drive migration |
EP1433086A4 (en) | 2001-09-26 | 2006-07-26 | Emc Corp | Efficient management of large files |
US6892264B2 (en) * | 2001-10-05 | 2005-05-10 | International Business Machines Corporation | Storage area network methods and apparatus for associating a logical identification with a physical identification |
US7024427B2 (en) * | 2001-12-19 | 2006-04-04 | Emc Corporation | Virtual file system |
US6941358B1 (en) | 2001-12-21 | 2005-09-06 | Networks Associates Technology, Inc. | Enterprise interface for network analysis reporting |
US7062783B1 (en) | 2001-12-21 | 2006-06-13 | Mcafee, Inc. | Comprehensive enterprise network analyzer, scanner and intrusion detection framework |
US7154857B1 (en) | 2001-12-21 | 2006-12-26 | Mcafee, Inc. | Enterprise network analyzer zone controller system and method |
US6789117B1 (en) | 2001-12-21 | 2004-09-07 | Networks Associates Technology, Inc. | Enterprise network analyzer host controller/agent interface system and method |
US6754705B2 (en) | 2001-12-21 | 2004-06-22 | Networks Associates Technology, Inc. | Enterprise network analyzer architecture framework |
US6714513B1 (en) | 2001-12-21 | 2004-03-30 | Networks Associates Technology, Inc. | Enterprise network analyzer agent system and method |
US6892227B1 (en) | 2001-12-21 | 2005-05-10 | Networks Associates Technology, Inc. | Enterprise network analyzer host controller/zone controller interface system and method |
US6845431B2 (en) | 2001-12-28 | 2005-01-18 | Hewlett-Packard Development Company, L.P. | System and method for intermediating communication with a moveable media library utilizing a plurality of partitions |
US6847968B2 (en) | 2002-02-08 | 2005-01-25 | William M. Pitts | Method for facilitating access to remote files |
DE10211606B4 (en) | 2002-03-12 | 2017-06-08 | Kip Cr P1 Lp | Data processing device with a metadata backup management |
US7233959B2 (en) | 2002-06-03 | 2007-06-19 | International Business Machines Corporation | Life-cycle management engine |
US7505980B2 (en) | 2002-11-08 | 2009-03-17 | Crossroads Systems, Inc. | System and method for controlling access to multiple physical media libraries |
US20040107417A1 (en) | 2002-11-21 | 2004-06-03 | Teck Chia | Update network with support for lifecycle management of update packages and mobile handsets |
US7113948B2 (en) | 2003-03-21 | 2006-09-26 | Acellion Pte Ltd. | Methods and systems for email attachment distribution and management |
JP4322031B2 (en) | 2003-03-27 | 2009-08-26 | 株式会社日立製作所 | Storage device |
JP2004310621A (en) | 2003-04-10 | 2004-11-04 | Hitachi Ltd | File access method, and program for file access in storage system |
US7007048B1 (en) | 2003-05-29 | 2006-02-28 | Storage Technology Corporation | System for information life cycle management model for data migration and replication |
US7313633B2 (en) * | 2003-06-04 | 2007-12-25 | Intel Corporation | Methods and apparatus for updating address resolution data |
US6950723B2 (en) | 2003-08-22 | 2005-09-27 | International Business Machines Corporation | Method, system, and program for virtualization of data storage library addresses |
US7499531B2 (en) | 2003-09-05 | 2009-03-03 | Emc Corporation | Method and system for information lifecycle management |
US7647327B2 (en) | 2003-09-24 | 2010-01-12 | Hewlett-Packard Development Company, L.P. | Method and system for implementing storage strategies of a file autonomously of a user |
JP2007511820A (en) | 2003-10-27 | 2007-05-10 | アーカイヴァス インコーポレイテッド | Policy-based management for independent node redundant arrays |
US7725936B2 (en) | 2003-10-31 | 2010-05-25 | International Business Machines Corporation | Host-based network intrusion detection systems |
US7590807B2 (en) | 2003-11-03 | 2009-09-15 | Netapp, Inc. | System and method for record retention date in a write once read many storage system |
JP2005165516A (en) | 2003-12-01 | 2005-06-23 | Hitachi Ltd | Storage controller, storage system and control method for storage system |
US20050201297A1 (en) | 2003-12-12 | 2005-09-15 | Cyrus Peikari | Diagnosis of embedded, wireless mesh networks with real-time, flexible, location-specific signaling |
US20050246386A1 (en) | 2004-02-20 | 2005-11-03 | George Sullivan | Hierarchical storage management |
US20050216762A1 (en) | 2004-03-25 | 2005-09-29 | Cyrus Peikari | Protecting embedded devices with integrated reset detection |
US8108429B2 (en) | 2004-05-07 | 2012-01-31 | Quest Software, Inc. | System for moving real-time data events across a plurality of devices in a network for simultaneous data protection, replication, and access services |
US7660999B2 (en) | 2004-06-22 | 2010-02-09 | Microsoft Corporation | MIME handling security enforcement |
US9268780B2 (en) | 2004-07-01 | 2016-02-23 | Emc Corporation | Content-driven information lifecycle management |
US20060004818A1 (en) | 2004-07-01 | 2006-01-05 | Claudatos Christopher H | Efficient information management |
US8229904B2 (en) | 2004-07-01 | 2012-07-24 | Emc Corporation | Storage pools for information management |
US8180742B2 (en) | 2004-07-01 | 2012-05-15 | Emc Corporation | Policy-based information management |
US7171532B2 (en) | 2004-08-30 | 2007-01-30 | Hitachi, Ltd. | Method and system for data lifecycle management in an external storage linkage environment |
US20060059172A1 (en) | 2004-09-10 | 2006-03-16 | International Business Machines Corporation | Method and system for developing data life cycle policies |
US7614058B2 (en) | 2004-09-21 | 2009-11-03 | Dell Products L. P. | System and method for virtual media command filtering |
US7417953B2 (en) | 2004-11-01 | 2008-08-26 | Alcatel Lucent | Port re-enabling by monitoring link status |
JP2006139552A (en) | 2004-11-12 | 2006-06-01 | Hitachi Ltd | Storage device and data life cycle management method for storage device |
JP2006215954A (en) | 2005-02-07 | 2006-08-17 | Hitachi Ltd | Storage system and archive management method for storage system |
US20060230086A1 (en) | 2005-04-06 | 2006-10-12 | International Business Machines Corporation | QoS-enabled lifecycle management for file systems |
JP4648751B2 (en) | 2005-05-02 | 2011-03-09 | 株式会社日立製作所 | Storage control system and storage control method |
US8315993B2 (en) | 2005-05-13 | 2012-11-20 | International Business Machines Corporation | Policy decision stash for storage lifecycle management |
US7529903B2 (en) | 2005-07-05 | 2009-05-05 | International Business Machines Corporation | Systems and methods for memory migration |
JP2007072813A (en) | 2005-09-07 | 2007-03-22 | Hitachi Ltd | Storage system, file migration method and computer program |
US8677499B2 (en) | 2005-12-29 | 2014-03-18 | Nextlabs, Inc. | Enforcing access control policies on servers in an information management system |
US7552300B2 (en) | 2006-01-03 | 2009-06-23 | International Business Machines Corporation | Method for migrating objects in content management systems through exploitation of file properties, temporal locality, and spatial locality |
US8229897B2 (en) | 2006-02-03 | 2012-07-24 | International Business Machines Corporation | Restoring a file to its proper storage tier in an information lifecycle management environment |
US20080002830A1 (en) | 2006-04-14 | 2008-01-03 | Cherkasov Aleksey G | Method, system, and computer-readable medium to maintain and/or purge files of a document management system |
US7519638B2 (en) | 2006-05-08 | 2009-04-14 | International Business Machines Corporation | Method for developing enterprise information life cycle management policies and solutions |
US7831563B2 (en) | 2006-05-17 | 2010-11-09 | International Business Machines Corporation | Active storage and retrieval systems and methods |
US7856424B2 (en) | 2006-08-04 | 2010-12-21 | Apple Inc. | User interface for backup management |
US8346729B2 (en) | 2006-11-18 | 2013-01-01 | International Business Machines Corporation | Business-semantic-aware information lifecycle management |
US8102860B2 (en) | 2006-11-30 | 2012-01-24 | Access Layers Ltd. | System and method of changing a network designation in response to data received from a device |
US8290808B2 (en) | 2007-03-09 | 2012-10-16 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
US7921268B2 (en) | 2007-07-12 | 2011-04-05 | Jakob Holger | Method and system for function-specific time-configurable replication of data |
US8396838B2 (en) | 2007-10-17 | 2013-03-12 | Commvault Systems, Inc. | Legal compliance, electronic discovery and electronic document handling of online and offline copies of data |
-
2000
- 2000-09-19 US US09/665,065 patent/US7392234B2/en not_active Expired - Lifetime
-
2001
- 2001-09-19 AU AU2001290167A patent/AU2001290167A1/en not_active Abandoned
- 2001-09-19 CA CA2788750A patent/CA2788750A1/en not_active Abandoned
- 2001-09-19 CA CA2393787A patent/CA2393787C/en not_active Expired - Lifetime
- 2001-09-19 WO PCT/IB2001/001725 patent/WO2002025445A2/en active Application Filing
-
2008
- 2008-06-23 US US12/213,670 patent/US8782009B2/en not_active Expired - Fee Related
-
2014
- 2014-07-14 US US14/331,015 patent/US20140330800A1/en not_active Abandoned
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111124645A (en) * | 2019-12-20 | 2020-05-08 | 网易(杭州)网络有限公司 | Discontinuous period file data processing method and device |
CN111124645B (en) * | 2019-12-20 | 2023-09-15 | 网易(杭州)网络有限公司 | Method and device for processing file data in discontinuous period |
Also Published As
Publication number | Publication date |
---|---|
WO2002025445A9 (en) | 2003-05-08 |
WO2002025445A2 (en) | 2002-03-28 |
US7392234B2 (en) | 2008-06-24 |
US20140330800A1 (en) | 2014-11-06 |
US8782009B2 (en) | 2014-07-15 |
CA2393787C (en) | 2012-08-28 |
US20080263112A1 (en) | 2008-10-23 |
CA2393787A1 (en) | 2002-03-28 |
AU2001290167A1 (en) | 2002-04-02 |
US20060010150A1 (en) | 2006-01-12 |
WO2002025445A3 (en) | 2003-12-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2393787C (en) | Method and system for electronic file lifecycle management | |
EP1836621B1 (en) | Methods and apparatus for managing deletion of data | |
US7281084B1 (en) | Method and apparatus for modifying a retention period | |
JP4160933B2 (en) | Fast restore of file system usage on very large file systems | |
US7467144B2 (en) | History preservation in a computer storage system | |
US8667274B2 (en) | System and method for WORM data storage | |
US8140602B2 (en) | Providing an object to support data structures in worm storage | |
US7376681B1 (en) | Methods and apparatus for accessing information in a hierarchical file system | |
US20100241613A1 (en) | Co-operative locking between multiple independent owners of data space | |
KR20040053142A (en) | Efficient management of large files | |
JP2004038929A (en) | System and method of managing two or more snapshots | |
US7366836B1 (en) | Software system for providing storage system functionality | |
US7428621B1 (en) | Methods and apparatus for storing a reflection on a storage system | |
US7979665B1 (en) | Method and apparatus for processing access requests in a computer system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |
Effective date: 20180109 |