In an approach to automatically reconciling data in HSM without affecting system performance, responsive to migrating a file on a hierarchical storage system from a primary storage to one or more tape drives, one or more file migration records are recorded in a reconcile database. Responsive to the occurrence of a file event on the primary storage, the one or more file migration records in the reconcile database are updated. Responsive to receiving a command to unmount a first mounted tape on one of the one or more tape drives, a reconcile function is performed on the first mounted tape, wherein the reconcile function updates the first mounted tape with the one or more file migration records in the reconcile database.

In an approach to automatically reconciling data in HSM without affecting system performance, responsive to migrating a file on a hierarchical storage system from a primary storage to one or more tape drives, one or more file migration records are recorded in a reconcile database. Responsive to the occurrence of a file event on the primary storage, the one or more file migration records in the reconcile database are updated. Responsive to receiving a command to unmount a first mounted tape on one of the one or more tape drives, a reconcile function is performed on the first mounted tape, wherein the reconcile function updates the first mounted tape with the one or more file migration records in the reconcile database.

In an approach to automatically reconciling data in HSM without affecting system performance, responsive to migrating a file on a hierarchical storage system from a primary storage to one or more tape drives, one or more file migration records are recorded in a reconcile database. Responsive to the occurrence of a file event on the primary storage, the one or more file migration records in the reconcile database are updated. Responsive to receiving a command to unmount a first mounted tape on one of the one or more tape drives, a reconcile function is performed on the first mounted tape, wherein the reconcile function updates the first mounted tape with the one or more file migration records in the reconcile database.

In an approach to automatically reconciling data in HSM without affecting system performance, responsive to migrating a file on a hierarchical storage system from a primary storage to one or more tape drives, one or more file migration records are recorded in a reconcile database. Responsive to the occurrence of a file event on the primary storage, the one or more file migration records in the reconcile database are updated. Responsive to receiving a command to unmount a first mounted tape on one of the one or more tape drives, a reconcile function is performed on the first mounted tape, wherein the reconcile function updates the first mounted tape with the one or more file migration records in the reconcile database.

Aspects of the present disclosure relate to rewinding a tape medium. Data is written to the tape medium under a first tension. An end data region of the tape medium is identified, where the end data region is not the end of the tape medium. An indication that the tape medium is to be unmounted is received. The position of the tape medium is moved to the end data region. The tape medium is then rewound from the end data region under a second tension, the second tension being lower than the first tension.

Aspects of the present disclosure relate to rewinding a tape medium. Data is written to the tape medium under a first tension. An end data region of the tape medium is identified, where the end data region is not the end of the tape medium. An indication that the tape medium is to be unmounted is received. The position of the tape medium is moved to the end data region. The tape medium is then rewound from the end data region under a second tension, the second tension being lower than the first tension.

A drive-implemented method according to one embodiment includes determining that unthreading of a tape is to be performed, and in response to the determination that the unthreading of the tape is to be performed, determining whether to write an index on the tape prior to unthreading the tape. In response to a determination to write the index on the tape, the index is written on the tape prior to unthreading the tape. The tape is then unthreaded. The drive-implemented method further includes receiving a write request after the unthreading, rethreading the tape, and writing data corresponding to the write request on the tape. The index stored on the tape prior to the unthreading is overwritten with the data corresponding to the write request.

A drive-implemented method according to one embodiment includes determining that unthreading of a tape is to be performed, and in response to the determination that the unthreading of the tape is to be performed, determining whether to write an index on the tape prior to unthreading the tape. In response to a determination to write the index on the tape, the index is written on the tape prior to unthreading the tape. The tape is then unthreaded. The drive-implemented method further includes receiving a write request after the unthreading, rethreading the tape, and writing data corresponding to the write request on the tape. The index stored on the tape prior to the unthreading is overwritten with the data corresponding to the write request.

A drive-implemented method according to one embodiment includes determining that unthreading of a tape is to be performed, and in response to the determination that the unthreading of the tape is to be performed, determining whether to write an index on the tape prior to unthreading the tape. In response to a determination to write the index on the tape, the index is written on the tape prior to unthreading the tape. The tape is then unthreaded. The drive-implemented method further includes receiving a write request after the unthreading, rethreading the tape, and writing data corresponding to the write request on the tape. The index stored on the tape prior to the unthreading is overwritten with the data corresponding to the write request.

A drive-implemented method according to one embodiment includes determining that unthreading of a tape is to be performed, and in response to the determination that the unthreading of the tape is to be performed, determining whether to write an index on the tape prior to unthreading the tape. In response to a determination to write the index on the tape, the index is written on the tape prior to unthreading the tape. The tape is then unthreaded. The drive-implemented method further includes receiving a write request after the unthreading, rethreading the tape, and writing data corresponding to the write request on the tape. The index stored on the tape prior to the unthreading is overwritten with the data corresponding to the write request.