| Sonstiges: |
- Nachgewiesen in: USPTO Patent Grants
- Sprachen: English
- Patent Number: 11886,724
- Publication Date: January 30, 2024
- Appl. No: 17/108936
- Application Filed: December 01, 2020
- Assignees: International Business Machines Corporation (Armonk, NY, US)
- Claim: 1. A computer-implemented method, comprising: copying data stored on a Linear Tape File System (LTFS)-based storage system from the LTFS-based storage system to blocks of a Random Access Nonvolatile Memory (RANVM) drive, wherein the data is copied in units of the blocks of the drive, wherein the data includes file data, wherein positions at which the file data is written to blocks on the LTFS-based storage system is managed by the LTFS-based storage system according to block numbers in a same manner as file data is managed by the drive.
- Claim: 2. The computer-implemented method of claim 1 , wherein the data is stored on the LTFS-based storage system in blocks, wherein a size of each of the blocks on the LTFS-based storage system is an integer multiple of a size of one of the blocks of the drive, wherein the blocks of the drive are of a file system of the drive.
- Claim: 3. The computer-implemented method of claim 1 , wherein the data copied to the blocks of the drive includes all data stored between a first end of a magnetic recording tape of the LTFS-based storage system and a second end of the magnetic recording tape, wherein no data seek operations are performed on the magnetic recording tape during the copying of the data thereon to the blocks of the drive.
- Claim: 4. The computer-implemented method of claim 1 , comprising: creating a correspondence table during the copying of the data, wherein the correspondence table maps data positions in LTFS to data positions on the drive.
- Claim: 5. The computer-implemented method of claim 1 , wherein the data is stored on the LTFS-based storage system in blocks, wherein a boundary of the file data is aligned to a size of the blocks on the drive during writing of the file data to the blocks on the LTFS-based storage system.
- Claim: 6. The computer-implemented method of claim 5 , wherein a block offset of the file data on the LTFS-based storage system is adjusted such that a remainder of a quotient of the block offset and the size of one of the blocks of the drive becomes equal to the remainder of a quotient of an offset of the file data on the LTFS-based storage system and the size of one of the blocks of the drive.
- Claim: 7. The computer-implemented method of claim 1 , wherein the file data corresponds to multiple files, wherein boundaries of the file data are aligned to a size of the blocks on the drive during writing of the file data to the blocks on the LTFS-based storage system.
- Claim: 8. The computer-implemented method of claim 1 , wherein the data includes at least some invalidated data resulting from overwriting operations performed on the LTFS-based storage system.
- Claim: 9. The computer-implemented method of claim 1 , comprising: writing the file data to the blocks on the LTFS-based storage system prior to copying the data to the blocks of the drive.
- Claim: 10. The computer-implemented method of claim 1 , comprising: constructing file metadata so that the copied data on the drive is accessible as one or more files.
- Claim: 11. A computer program product, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions readable and/or executable by a controller to cause the controller to: copy, by the controller, data stored on a Linear Tape File System (LTFS)-based storage system from the LTFS-based storage system to blocks of a Random Access Nonvolatile Memory (RANVM) drive, wherein the data is copied in units of the blocks of the drive, wherein the data includes file data, wherein positions at which the file data is written to blocks on the LTFS-based storage system is managed by the LTFS-based storage system according to block numbers in a same manner as file data is managed by the drive; and construct, by the controller, file metadata so that the copied data on the drive is accessible as one or more files.
- Claim: 12. The computer program product of claim 11 , wherein the data copied to the blocks of the drive includes all data stored between a first end of a magnetic recording tape of the LTFS-based storage system and a second end of the magnetic recording tape, wherein no data seek operations are performed on the magnetic recording tape during the copying of the data thereon to the blocks of the drive.
- Claim: 13. The computer program product of claim 11 , the program instructions readable and/or executable by the controller to cause the controller to: create, by the controller, a correspondence table during the copying of the data, wherein the correspondence table maps data positions in LTFS to data positions on the drive.
- Claim: 14. The computer program product of claim 11 , the program instructions readable and/or executable by the controller to cause the controller to: write, by the controller, the file data to the blocks on the LTFS-based storage system prior to copying the data to the blocks of the drive.
- Claim: 15. The computer program product of claim 14 , wherein a boundary of the file data is aligned to a size of the blocks on the drive during the writing of the file data to the blocks on the LTFS-based storage system.
- Claim: 16. The computer program product of claim 15 , wherein a block offset of the file data on the LTFS-based storage system is adjusted such that a remainder of a quotient of the block offset and the size of one of the blocks of the drive becomes equal to the remainder of a quotient of an offset of the file data on the LTFS-based storage system and the size of one of the blocks of the drive.
- Claim: 17. The computer program product of claim 11 , wherein the data includes file data of multiple files, and the program instructions readable and/or executable by the controller to cause the controller to: write, by the controller, the file data to the blocks on the LTFS-based storage system prior to copying the data to the blocks of the drive, wherein boundaries of the file data are aligned to a size of the blocks on the drive during the writing of the file data to the blocks on the LTFS-based storage system.
- Claim: 18. The computer program product of claim 11 , wherein the data includes at least some invalidated data resulting from overwriting operations performed on the LTFS-based storage system.
- Claim: 19. A system, comprising: a processor; and logic integrated with the processor, executable by the processor, or integrated with and executable by the processor, the logic being configured to: copy data stored on a Linear Tape File System (LTFS)-based storage system from the LTFS-based storage system to blocks of a Random Access Nonvolatile Memory (RANVM) drive, wherein the data is copied in units of the blocks of the drive, wherein the data includes file data, wherein positions at which the file data is written to blocks on the LTFS-based storage system is managed by the LTFS-based storage system according to block numbers in a same manner as file data is managed by the drive; and construct file metadata so that the copied data on the drive is accessible as one or more files.
- Claim: 20. The system of claim 19 , wherein the data copied to the blocks of the drive includes all data stored between a first end of a magnetic recording tape of the LTFS-based storage system and a second end of the magnetic recording tape, wherein no data seek operations are performed on the magnetic recording tape during the copying of the data thereon to the blocks of the drive.
- Claim: 21. The system of claim 19 , the logic being configured to: create a correspondence table during the copying of the data, wherein the correspondence table maps data positions in LTFS to data positions on the drive.
- Claim: 22. The system of claim 19 , wherein a boundary of the file data is aligned to a size of the blocks on the drive during writing of the file data to the blocks on the LTFS-based storage system.
- Claim: 23. The system of claim 22 , wherein a block offset of the file data on the LTFS-based storage system is adjusted such that a remainder of a quotient of the block offset and the size of one of the blocks of the drive becomes equal to the remainder of a quotient of an offset of the file data on the LTFS-based storage system and the size of one of the blocks of the drive.
- Claim: 24. The system of claim 19 , wherein the data is not copied in units of files of the data.
- Patent References Cited: 10168920 January 2019 Abe et al. ; 20010003829 June 2001 Romine ; 20110276754 November 2011 Bish ; 20120054428 March 2012 Butt et al. ; 20120284587 November 2012 Yu ; 20140160907 June 2014 Davis ; 20140201424 July 2014 Chen et al. ; 20150095566 April 2015 Itagaki ; 20160283493 September 2016 Wideman ; 20160335188 November 2016 Romanovskiy ; 20170052718 February 2017 Abe et al. ; 20180018238 January 2018 Tomii
- Other References: IBM, “IBM LTFS Copy Tool,” IBM Knowledge Center, 2020, 4 pages, retrieved from https://www.ibm.com/support/knowledgecenter/en/STZMZN/com.ibm.storage.hollywood.doc/ltfs_reference_ltfs_copy.html. cited by applicant ; Levens, S., “Moving Tape Content to Backblaze Fireball with Canister,” Backblaze, Sep. 6, 2018, 7 pages, retrieved from https://www.backblaze.com/blog/moving-tape-content-to-cloud-storage/. cited by applicant ; IBM, “Migrating data from tape to DISK or FILE devices,” IBM Knowledge Center, 2020, 3 pages, retrieved from https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.srv.upgrd.doc/t_xplat_mig_data_frm_tape.html. cited by applicant ; AWS, “AWS Black Belt online seminar 2017 Snowball,” Amazon Web Services Japan, Jun. 14, 2017, 47 pages, retrieved from https://www.slideshare.net/AmazonWebServicesJapan/20170614-aws-blackbeltsnowball. cited by applicant ; AWS, “AWS Snowball,” Amazon Web Services, 2020, 17 pages, retrieved from https://aws.amazon.com/snowball/. cited by applicant ; Google Cloud, “Transfer Appliance,” Google Cloud Newsletter, 2020, 2 pages, retrieved from https://cloud.google.com/transfer-appliance/. cited by applicant ; SNIA, “Linear Tape File System (LTFS) Format Specification, Version 2.5,” SNIA Technical Position, May 19, 2019, 97 pages. cited by applicant ; StorEasy, “Cloud Gateway LTFS,” StorEasy, 2018, 10 pages, retrieved from https://www.storeasy.cloud/cloud-gateway-ltfs/. cited by applicant ; SNIA, “LTFS Bulk Transfer, Version 1.0,” SNIA Technical Position, Oct. 11, 2016, 41 pages. cited by applicant ; IBM “LTFS Copy Tool functions,” IBM Knowledge Center, 2020, 2 pages, retrieved from https://www.ibm.com/support/knowledgecenter/en/STQNYL_2.2.2/ltfs_reference_lcp_functions.html. cited by applicant ; Wikipedia, “File system fragmentation,” Wikipedia, 2020, 6 pages, retgrieved from https://en.wikipedia.org/wiki/File_system_fragmentation. cited by applicant ; Microsoft, “How FAT Works,” Oct. 8, 2009, 26 pages, retrieved from https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc776720(v=ws.10). cited by applicant ; IBM, “Rolling back media,” IBM Knowledge Center, 2020, 4 pages, retrieved from https://www.ibm.com/support/knowledgecenter/STQNYL_2.4.1/ltfs_rolling_back_media_win.html. cited by applicant ; International Search Report and Written Opinion from PCT Application No. PCT/EP2021/081990, dated Mar. 2, 2022. cited by applicant
- Primary Examiner: Parikh, Kalpit
- Attorney, Agent or Firm: Zilka-Kotab, P.C.
|
