Dashboard & Reports

The Administrator user has a global overview about the Data Management activities.

By default, several widgets are display with information about the files, volume and task report. You can add, remove or change the place of the widget.

Trend Analytic

Administrator needs to control the storage location of their data. This feature includes a system with dynamic reporting.

This feature provides reports & KPI showing what is the exact storage usage based on criteria such as: creation date, last access date and location of the data. In addition, it provides a more detailed overview by users, user groups, categories, data types and file sizes.

Also, it will give a deeper drill down into users and user groups, data type categories and file sizes.

Storage Global Overview

Global overview about data stored on Storage and classify by type (NAS, Cloud, Tape).

Example: Information about Storage Management of Secondary Storage (NAS, Cloud/S3 and Tape)

Data Life cycle

Understand how is the effect of your Data Archiving (Active Archive) policies. What type of data do you have and on which type of Storage? This board presents insights about the “life” of your Data. Information based on the size and based on the type of your files are available.

Example : Information about Storage Management of Container with active archive Workflow.

Tape Reporting

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.

Helps in the prevention of any problems on Tapes or Tape Drives.

Tape Drive Information Reporting

• Load operations : 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 : Number of seconds the drive has been powered on over its lifetime.

• Read errors : 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

• 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

Forget a tape

While you forget a tape, Nodeum removes all data related to the selected tape from the catalog and indexation engine.

The contents physically stored in the tapes will stay available, but these are not anymore available from Nodeum, the tape status is seen as 'Unknown'.

To execute the operation to forget a tapes, it is mandatory that the tape is not anymore in the Tape Library or the tape is located into an I/O slot.

The forget feature is available in this menu:

Trend analytic -> Tape Reporting

Select the tape you wish for Nodeum to forget, click the three dots on the right, and choose "Forget" from the list.

Tape Status

Managing tapes effectively requires an understanding of their various lifecycle statuses. This knowledge is essential for ensuring data integrity and tape management.

Barcode

Barcode	Description
	To prepare the tape for use, format the LTFS partition as it is currently unrecognized
	The tape is ready and can be used
	The tape has a write protection enabled
	The tape's capacity is full, no space left

Protect

Protect	Description
	No tape protection is set
	The tape is protected by Nodeum software in using the lock feature
	The tape's physical write protection lock is enabled
	Nodeum software and physical write protection are both enabled

Status

Status	Description
	The tape is in good condition and ready
	The tape is flagged for review; a tape verification task must be performed