Nodeum provides into the tape reporting feature some relevant information about tape and tape drives usage. The objective is to improve the reliability of the data integrity when using magnetic tapes and to facilitate the overall tape management. The information are collected by Nodeum from the TapeAlert error reporting. This is an industry standard that provides a status monitoring and problem detection capability for tape devices and tape directly from the tape and the tape drive.
This help in the prevention of any dysfunction on tapes or drives.
Drive Information Reporting
| Drive Information | Definition |
| Load operations |
This is the number of times the drive has been loaded in its lifetime. |
| Meters processed | Total number of meters of tape that have been processed by the drive mechanism in either direction. |
| Power-on cycles |
Total number of times the drive has detected a power-on event. |
| Power-on time | This is the number of seconds the drive has been powered on over its lifetime. |
| Read errors | The total number of error errors that could not be corrected by ECC, no servo error was reported, and the error was not a transient error. Each count represents one block in error that was not corrected, but was recovered by ERPs and successfully written. |
| Read processed |
Each count represents a kebibyte (1024 bytes) of data processed across the host interface during read-type commands |
| Read retries | Total number of read temps |
| Write errors | The total number of write errors that could not be corrected by ECC, no servo error was reported, and the error was not a transient error. Each count represents one block in error that was not corrected, but was recovered by ERPs and successfully written. |
| Write processed |
Each count represents a kebibyte (1024 bytes) of data processed across the host interface during write-type commands. |
| Write retries | Total number of write temps |
Tape information Reporting
| Tape information | Definition |
| Bytes Read | The total number of bytes of data read to tape |
| Bytes Written | The total number of bytes of data written to tape |
| Compression Enabled |
Indication of whether logical blocks will be compressed before they are written to the medium. The value reported indicates the current state of the device and does not indicate that logical blocks previously written to the medium were compressed. "yes" indicates that logical blocks will be compressed before being written to the medium during write type commands. "no" indicates that logical blocks will not be compressed before being written to the medium during write type commands. |
| Datasets read | The total number of data sets read from the medium in the volume over the lifetime of the volume. |
| Datasets written | The total number of data sets written to the medium in the volume over the lifetime of the volume. |
| Mount time |
Time in milliseconds from the time when the system would first report GOOD status to a "TEST UNIT READY" command upon successful completion of a load operation until the system did not detect a volume present. |
| Read Compression Ratio |
The average data compression ratio multiplied by 100 for all user data read from the medium since the last time this parameter was reset to zero. This parameter may include user data that was read from the medium but not returned to the application client (e.g., data that was read as part of a read ahead operation). The calculation is (number of bytes transferred out of the logical object buffer to an application client ÷ the number of bytes in logical objects read from the medium) x 100 |
| Read Retries | Total number of read temps |
| Ready time |
Time in milliseconds from the time the system was able to process medium access commands until the system started the processing of an unload operation. |
| Tapes Mounts (#) | The total number of successful cartridge unloads performed during the lifetime of a cartridge. This field may not be updated for mounts that occur with the volume physically write-protected. |
| Unrecovered Read Errors | The total number of times that a read type command was terminated with CHECK CONDITION status and a sense key of MEDIUM ERROR or HARDWARE ERROR over the lifetime of the volume. |
| Unrecovered Write Errors | The total number of times that a write type command was terminated with CHECK CONDITION status and a sense key of MEDIUM ERROR or HARDWARE ERROR over the lifetime of the volume. |
| Write Compression Ratio |
The average data compression ratio multiplied by 100 for all user data written by the device since the last time this parameter was reset to zero. The calculation is (number of bytes transferred from an application client into the logical object buffer ÷ the number of bytes in logical objects written to the medium) x 100 |
| Write Retries | Total number of write temps |
%20W%26G%20Dark%20Back_150px.png?width=70&name=Nodeum(Single)%20W%26G%20Dark%20Back_150px.png)
Let Us Know What You Thought about this Post.
Put your Comment Below.