Abstract: A tape drive (226) for use in a tape library (10) that retains at least one tape cartridge (220) that retains magnetic tape (250) includes a drive housing (226A) and a media conditioner (255). The drive housing (226A) is configured to receive the tape cartridge (220). The media conditioner (255) is coupled to the drive housing (226A). The media conditioner (255) is configured to condition the magnetic tape (250) when the tape cartridge (220) is received within the drive housing (226A). The media conditioner (255) can be configured to remove at least one of abrasives, contaminants and lubricants that are on the magnetic tape (250) when the tape cartridge (220) is received within the drive housing (226A). The magnetic tape (250) is configured to move along a predefined path (251) within the drive housing (226A), which is defined by one or more rollers (254).

Abstract: A tape drive includes a tape transport assembly, the tape transport assembly including a drive member, the drive member of the tape transport assembly configured to displace tape media in the tape drive; and a tape roller assembly, the tape roller assembly including a roller member, the roller member having one or more slanted grooves or protrusions formed in an outer surface of the roller member, the roller member configured to support and/or guide the tape media as the tape media is displaced by the tape transport assembly, the one or more slanted grooves or protrusions of the roller member configured to burnish and/or clean the tape media so as to prevent damage to a tape head, and the one or more slanted grooves or protrusions of the roller member being angled so as to prevent the tape media from sliding in an axial direction of the roller member.

Abstract: Example apparatus and methods control an error correcting code (ECC) approach for data stored on a solid state device (SSD). The control may be based on a property (e.g., reliability, error state, speed) of an SSD, or on an attribute of the data to be stored. Approaches including a hybrid rateless Reed-Solomon ECC approach or a fountain code ECC approach may be selected. Example apparatus and methods may store padded portions of an ECC at different locations in an SSD. Example apparatus and methods may dynamically generate performance test data about the SSD, and dynamically control the ECC approach based on the performance test data. Different types or numbers of ECC may be produced, stored, and provided for different data sets stored at different SSDs or at different physical locations within an SSD. The SSD may be local, or may be part of a cloud-based storage system.

Abstract: Example apparatus and methods control whether and when hybrid rateless Reed Solomon (RS) error correcting codes (ECC) for a message are produced, stored, and distributed. The control may be based on a property (e.g., reliability, error state, speed) of a message recipient. Example apparatus and methods may also control whether and when fountain codes for the message are produced, stored, and distributed. Once again, the control may be based on a property of a message or ECC recipient. Both the hybrid rateless RS ECC and the fountain codes may be produced from data stored in a modified RS matrix. The modified RS matrix may store row-centric error detection codes (EDC) instead of conventional cyclic redundancy check (CRC) characters. The modified RS matrix may store column-centric ECC that may be produced serially. Different types or numbers of ECC may be produced, stored, and provided for different messages stored at different recipients.

Abstract: A servo system for a magnetic tape storage system includes a magnetic tape (550) including a first servo band (573), and a first data band (575). An auxiliary servo pattern (575A) is embedded within the first data band (575). The auxiliary servo pattern (575A) is modified to generate an updated auxiliary servo pattern (688A) during a writing pass as data is being written to the first data band (575). The servo system can further include a magnetic tape drive (326) including a head assembly (456) having (i) a first write head (482) that writes data to the magnetic tape (550) as the magnetic tape (550) moves relative to the head assembly (456) in a first tape direction, (ii) a second write head (484) that writes data to the magnetic tape (550) as the magnetic tape (550) moves relative to the head assembly (456) in a second, opposite tape direction, and (iii) an auxiliary servo reader (487) positioned in a shadow of one of the first write head (482) and the second write head (484).

Abstract: A tape cartridge for retaining a magnetic tape, the tape cartridge being configured to be selectively positioned substantially within a tape drive, includes a cartridge body and a cartridge hub. The cartridge body includes a cartridge length from a front to a rear of the cartridge body, and a cartridge width from a first side to a second side of the cartridge body. The cartridge hub is positioned within the cartridge body. The cartridge hub is configured so that the magnetic tape is wound around the cartridge hub within the cartridge body. The cartridge hub includes a hub diameter. The cartridge length and the cartridge width provide boundaries for a maximum wound tape diameter as the magnetic tape is wound around the cartridge hub within the cartridge body. A ratio of the maximum wound tape diameter to the hub diameter is at least approximately 3.50:1.

Abstract: A servo system for a magnetic tape storage system includes a magnetic tape (550) including a first servo band (573), and a first data band (575). An auxiliary servo pattern (575A) is embedded within the first data band (575). The auxiliary servo pattern (575A) is modified to generate an updated auxiliary servo pattern (688A) during a writing pass as data is being written to the first data band (575). The servo system can further include a magnetic tape drive (326) including a head assembly (456) having (i) a first write head (482) that writes data to the magnetic tape (550) as the magnetic tape (550) moves relative to the head assembly (456) in a first tape direction, (ii) a second write head (484) that writes data to the magnetic tape (550) as the magnetic tape (550) moves relative to the head assembly (456) in a second, opposite tape direction, and (iii) an auxiliary servo reader (487) positioned in a shadow of one of the first write head (482) and the second write head (484).

Abstract: A tape drive (226) for use in a tape library (10) that retains at least one tape cartridge (220) that retains magnetic tape (250) includes a drive housing (226A) and a media conditioner (255). The drive housing (226A) is configured to receive the tape cartridge (220). The media conditioner (255) is coupled to the drive housing (226A). The media conditioner (255) is configured to condition the magnetic tape (250) when the tape cartridge (220) is received within the drive housing (226A). The media conditioner (255) can be configured to remove at least one of abrasives, contaminants and lubricants that are on the magnetic tape (250) when the tape cartridge (220) is received within the drive housing (226A). The magnetic tape (250) is configured to move along a predefined path (251) within the drive housing (226A), which is defined by one or more rollers (254).

Abstract: A tape cartridge for retaining a magnetic tape, the tape cartridge being configured to be selectively positioned substantially within a tape drive, includes a cartridge body and a cartridge hub. The cartridge body includes a cartridge length from a front to a rear of the cartridge body, and a cartridge width from a first side to a second side of the cartridge body. The cartridge hub is positioned within the cartridge body. The cartridge hub is configured so that the magnetic tape is wound around the cartridge hub within the cartridge body. The cartridge hub includes a hub diameter. The cartridge length and the cartridge width provide boundaries for a maximum wound tape diameter as the magnetic tape is wound around the cartridge hub within the cartridge body. A ratio of the maximum wound tape diameter to the hub diameter is at least approximately 3.50:1.

Abstract: Example apparatus and methods control whether and when hybrid rateless Reed Solomon (RS) error correcting codes (ECC) for a message are produced, stored, and distributed. The control may be based on a property (e.g., reliability, error state, speed) of a message recipient. Example apparatus and methods may also control whether and when fountain codes for the message are produced, stored, and distributed. Once again, the control may be based on a property of a message or ECC recipient. Both the hybrid rateless RS ECC and the fountain codes may be produced from data stored in a modified RS matrix. The modified RS matrix may store row-centric error detection codes (EDC) instead of conventional cyclic redundancy check (CRC) characters. The modified RS matrix may store column-centric ECC that may be produced serially. Different types or numbers of ECC may be produced, stored, and provided for different messages stored at different recipients.

Abstract: Example apparatus and methods control a data storage system to store data in a self-describing logical data storage capsule using a logical cylindrical recording format. Example apparatus and methods assign a searchable, globally unique identifier to the capsule and associate the globally unique identifier with a user. The logical data storage capsule is migrated from a first data storage medium to a second data storage medium without translating or reformatting the data storage capsule. The data storage capsule contains information describing to a data storage device how to migrate the capsule without translating or reformatting the data storage capsule. Example apparatus and methods dynamically select an error correction approach for storing data in the data storage capsule, de-duplicate, and encrypt the data storage capsule. The data storage capsule may be local, or may be part of a cloud-based storage system.

Abstract: Example apparatus and methods control whether and when hybrid rateless Reed Solomon (RS) error correcting codes (ECC) for a message are produced, stored, and distributed. The control may be based on a property (e.g., reliability, error state, speed) of a message recipient. Example apparatus and methods may also control whether and when fountain codes for the message are produced, stored, and distributed. Once again, the control may be based on a property of a message or ECC recipient. Both the hybrid rateless RS ECC and the fountain codes may be produced from data stored in a modified RS matrix. The modified RS matrix may store row-centric error detection codes (EDC) instead of conventional cyclic redundancy check (CRC) characters. The modified RS matrix may store column-centric ECC that may be produced serially. Different types or numbers of ECC may be produced, stored, and provided for different messages stored at different recipients.

Abstract: Example apparatus and methods control an error correcting code (ECC) approach for data stored on a solid state device (SSD). The control may be based on a property (e.g., reliability, error state, speed) of an SSD, or on an attribute of the data to be stored. Approaches including a hybrid rateless Reed-Solomon ECC approach or a fountain code ECC approach may be selected. Example apparatus and methods may store padded portions of an ECC at different locations in an SSD. Example apparatus and methods may dynamically generate performance test data about the SSD, and dynamically control the ECC approach based on the performance test data. Different types or numbers of ECC may be produced, stored, and provided for different data sets stored at different SSDs or at different physical locations within an SSD. The SSD may be local, or may be part of a cloud-based storage system.

Abstract: Example apparatus and methods control an error correcting code (ECC) approach for data stored on a solid state device (SSD). The control may be based on a property (e.g., reliability, error state, speed) of an SSD, or on an attribute of the data to be stored. Approaches including a hybrid rateless Reed-Solomon ECC approach or a fountain code ECC approach may be selected. Example apparatus and methods may store padded portions of an ECC at different locations in an SSD. Example apparatus and methods may dynamically generate performance test data about the SSD, and dynamically control the ECC approach based on the performance test data. Different types or numbers of ECC may be produced, stored, and provided for different data sets stored at different SSDs or at different physical locations within an SSD. The SSD may be local, or may be part of a cloud-based storage system.

Abstract: Example apparatus and methods control whether and when hybrid rateless Reed Solomon (RS) error correcting codes (ECC) for a message are produced, stored, and distributed. The control may be based on a property (e.g., reliability, error state, speed) of a message recipient. Example apparatus and methods may also control whether and when fountain codes for the message are produced, stored, and distributed. Once again, the control may be based on a property of a message or ECC recipient. Both the hybrid rateless RS ECC and the fountain codes may be produced from data stored in a modified RS matrix. The modified RS matrix may store row-centric error detection codes (EDC) instead of conventional cyclic redundancy check (CRC) characters. The modified RS matrix may store column-centric ECC that may be produced serially. Different types or numbers of ECC may be produced, stored, and provided for different messages stored at different recipients.

Abstract: Example apparatus and methods control a data storage system to store data in a self-describing logical data storage capsule using a logical cylindrical recording format. Example apparatus and methods assign a searchable, globally unique identifier to the capsule and associate the globally unique identifier with a user. The logical data storage capsule is migrated from a first data storage medium to a second data storage medium without translating or reformatting the data storage capsule. The data storage capsule contains information describing to a data storage device how to migrate the capsule without translating or reformatting the data storage capsule. Example apparatus and methods dynamically select an error correction approach for storing data in the data storage capsule, de-duplicate, and encrypt the data storage capsule. The data storage capsule may be local, or may be part of a cloud-based storage system.

Abstract: Example apparatus and methods control whether and when hybrid rateless Reed Solomon (RS) error correcting codes (ECC) for a message are produced, stored, and distributed. The control may be based on a property (e.g., reliability, error state, speed) of a message recipient. Example apparatus and methods may also control whether and when fountain codes for the message are produced, stored, and distributed. Once again, the control may be based on a property of a message or ECC recipient. Both the hybrid rateless RS ECC and the fountain codes may be produced from data stored in a modified RS matrix. The modified RS matrix may store row-centric error detection codes (EDC) instead of conventional cyclic redundancy check (CRC) characters. The modified RS matrix may store column-centric ECC that may be produced serially. Different types or numbers of ECC may be produced, stored, and provided for different messages stored at different recipients.

Abstract: Example apparatus and methods control a data storage system to store data in a self-describing logical data storage capsule using a logical cylindrical recording format. Example apparatus and methods assign a searchable, globally unique identifier to the capsule and associate the globally unique identifier with a user. The logical data storage capsule is migrated from a first data storage medium to a second data storage medium without translating or reformatting the data storage capsule. The data storage capsule contains information describing to a data storage device how to migrate the capsule without translating or reformatting the data storage capsule. Example apparatus and methods dynamically select an error correction approach for storing data in the data storage capsule, de-duplicate, and encrypt the data storage capsule. The data storage capsule may be local, or may be part of a cloud-based storage system.

Abstract: A tape cartridge for retaining a magnetic tape, the tape cartridge being configured to be selectively positioned substantially within a tape drive, includes a cartridge body and a cartridge hub. The cartridge body includes a cartridge length from a front to a rear of the cartridge body, and a cartridge width from a first side to a second side of the cartridge body. The cartridge hub is positioned within the cartridge body. The cartridge hub is configured so that the magnetic tape is wound around the cartridge hub within the cartridge body. The cartridge hub includes a hub diameter. The cartridge length and the cartridge width provide boundaries for a maximum wound tape diameter as the magnetic tape is wound around the cartridge hub within the cartridge body. A ratio of the maximum wound tape diameter to the hub diameter is at least approximately 3.50:1.

Abstract: Example apparatus and methods control an error correcting code (ECC) approach for data stored on a solid state device (SSD). The control may be based on a property (e.g., reliability, error state, speed) of an SSD, or on an attribute of the data to be stored. Approaches including a hybrid rateless Reed-Solomon ECC approach or a fountain code ECC approach may be selected. Example apparatus and methods may store padded portions of an ECC at different locations in an SSD. Example apparatus and methods may dynamically generate performance test data about the SSD, and dynamically control the ECC approach based on the performance test data. Different types or numbers of ECC may be produced, stored, and provided for different data sets stored at different SSDs or at different physical locations within an SSD. The SSD may be local, or may be part of a cloud-based storage system.