Logical backup using a storage system
Backing up logical data from a storage system to a backup system includes accessing data on the storage system corresponding to logical file structures of data stored on the storage system, using machine learning to ascertain file access patterns and frequency of file backups, determining backup data based on the logical file structure of data stored on the storage system and the file access patterns and frequency of file backups, and directly transferring data corresponding the backup data from the storage system to the backup system. The logical file structures may be provided by file metadata. The file metadata may include at least one of: a VTOC (volume table of contents), an IXVTOC (indexed VTOC), VSAM (virtual storage access method) information, a VVDS (VSAM volume data set), file attributes, and/or catalog data. The file attributes may include management class information for each of the files.
1. A method of transferring data from a storage system to a backup system that is coupled directly to and communicates with the storage system, comprising:
the storage system accessing file metadata stored thereon by a host system that writes logical data to the storage system, wherein the host system is coupled to the storage system and is separate from the backup system and the storage system and wherein the file metadata corresponds to the logical data and wherein the file metadata includes at least one of: a VTOC (volume table of contents), an IXVTOC (indexed VTOC), VSAM (virtual storage access method) information, and a VVDS (VSAM volume data set);
the storage system using at least one of the VTOC, the IXVTOC, the VSAM, and/or the VVDS of the file metadata to determine logical file structures of data stored on the storage system by the host system;
the storage system using machine learning running exclusively on the storage system to ascertain file access patterns of the logical file structure that is stored on the storage system by the host and to ascertain frequency of file backups;
the storage system determining portions of the logical data based on the logical file structure of data stored on the storage system and the file access patterns and frequency of file backups; and
the storage system directly transferring only the portions of the logical data based on the logical file structures from the storage system to the backup system.
2. The method, according to claim 1 , wherein the file metadata also includes file attributes that provide management class information for each of the files.
3. The method, according to claim 2 , wherein the management class information includes data indicating number of backups, frequency of backups, backup priority, and backup retention policy.
4. The method, according to claim 3 , wherein the management class information is read directly from an SMS (system managed storage) management class definition.
5. The method, according to claim 4 , wherein the SMS management class definition is stored on the storage system.
6. The method, according to claim 1 , wherein backing up logical data from the storage system to the backup system is initiated by a host computing system coupled to the storage system.
7. The method, according to claim 1 , wherein the backup system is a tape unit.
8. The method, according to claim 7 , wherein the tape unit is a tape emulation unit.
9. A non-transitory computer readable medium containing software that transfers data from a storage system to a backup system that is coupled directly to and communicates with the storage system, the software comprising:
executable code that causes the storage system to access file metadata stored thereon by a host system that writes logical data to the storage system, wherein the host system is coupled to the storage system and is separate from the backup system and the storage system and wherein the file metadata corresponds to the logical data and wherein the file metadata includes at least one of: a VTOC (volume table of contents), an IXVTOC (indexed VTOC), VSAM (virtual storage access method) information, and a VVDS (VSAM volume data set);
executable code that causes the storage system to use at least one of the VTOC, the IXVTOC, the VSAM, and/or the VVDS of the file metadata to determine logical file structures of data stored on the storage system by the host system;
executable code running exclusively on the storage system that uses machine learning to ascertain file access patterns of the logical file structure that is stored on the storage system by the host and to ascertain frequency of file backups;
executable code that causes the storage system to determine portions of the logical data based on the logical file structure of data stored on the storage system and the file access patterns and frequency of file backups; and
executable code that causes the storage system to directly transfer only the portions of the logical data based on the logical file structures from the storage system to the backup system.
10. The non-transitory computer readable medium, according to claim 9 , wherein the file metadata also includes file attributes that provide management class information for each of the files.
11. The non-transitory computer readable medium, according to claim 10 , wherein the management class information includes data indicating number of backups, frequency of backups, and backup priority.
12. The non-transitory computer readable medium, according to claim 11 , wherein the management class information is read directly from an SMS (system managed storage) management class definition.
13. The non-transitory computer readable medium, according to claim 12 , wherein the SMS management class definition is stored on the storage system.
14. The non-transitory computer readable medium, according to claim 9 , wherein backing up logical data from the storage system to the backup system is initiated by a host computing system coupled to the storage system.
15. The non-transitory computer readable medium, according to claim 9 , wherein the backup system is a tape unit.
16. The non-transitory computer readable medium, according to claim 15 , wherein the tape unit is a tape emulation unit.
17. A logical backup system, comprising:
a storage system having one or more processors and a non-transitory computer readable storage medium coupled thereto, the non-transitory computer readable storage medium containing software that is executed by the one or more processors;
a host coupled directly to the storage system that writes file metadata and logical data to the storage system, wherein the file metadata corresponds to the logical data and wherein the file metadata includes at least one of: a VTOC (volume table of contents), an IXVTOC (indexed VTOC), VSAM (virtual storage access method) information, and a VVDS (VSAM volume data set; and
a backup system coupled directly to the storage system, wherein the software of the storage system includes executable code that accesses file metadata stored thereon by the host system, executable code that uses at least one of the VTOC, the IXVTOC, the VSAM, and/or the VVDS of the file metadata to determine logical file structures of data stored on the storage system by the host system, executable code running exclusively on the storage system that uses machine learning to ascertain file access patterns of the logical file structure that is stored on the storage system by the host and to ascertain frequency of file backups, executable code determines portions of the logical data based on the logical file structure of data stored on the storage system and the file access patterns and frequency of file backups, and executable code that directly transfers only the portions of the logical data based on the logical file structures from the storage system to the backup system.
18. The logical backup system, according to claim 17 , wherein the file metadata also includes file attributes.