# Dashboard & Reports

By default, multiple widgets display information about files, volume, and task reports. You can add, remove, or rearrange these widgets as needed.

<figure><img src="/files/7kYAv5ty2gZg0cw5UMNi" alt=""><figcaption></figcaption></figure>

## Trend Analytic

### Overview

Administrators need to manage the storage location of their data efficiently. This feature offers a dynamic reporting system that includes:

* **Detailed Reports & KPIs:** Track storage usage based on criteria such as creation date, last access date, and data location.
* **Comprehensive Analysis:** Provides insights by users, user groups, categories, data types, and file sizes.
* **Deep Dive Analytics:** Offers in-depth examination into specifics of users, user groups, data type categories, and file sizes.

### Storage Global Overview

**Global Overview of Data Storage Classification**

In today's data-driven environment, effective storage management is crucial for maintaining operational efficiency. This overview classifies stored data by type, focusing on three key storage solutions: Network Attached Storage (NAS), Cloud storage, and Tape storage.

#### Storage Types:

1. **Network Attached Storage (NAS):**
   * NAS devices provide a centralized location for storing files accessible over a network.
   * Ideal for small to medium-sized enterprises needing scalable and efficient data storage.
2. **Cloud Storage:**
   * Services like Amazon S3 offer flexible, scalable, and remote storage solutions.
   * Suitable for businesses requiring high availability and disaster recovery options.
3. **Tape Storage:**
   * Tape drives offer cost-effective long-term storage solutions.
   * Best suited for archival purposes and storing large volumes of data that are infrequently accessed.

By understanding these storage types, organizations can effectively manage their data and resources, optimizing both accessibility and cost-efficiency.

<div data-full-width="false"><figure><img src="/files/XUfZ3IFh7n2Y6kK8b7pM" alt=""><figcaption></figcaption></figure></div>

### Data Life cycle

### Understanding the Impact of Data Archiving Policies

Analyze your data archiving (active archive) strategies by exploring the types of data stored and their respective storage solutions. This overview provides insights into the lifecycle of your data, presenting information categorized by both file size and type.

**Example:** Manage storage for containers using an active archive workflow.

<figure><img src="/files/XfuWaOvJKJKGnWDVtroj" alt=""><figcaption></figcaption></figure>

### Tape Reporting

The Tape Reporting feature in Nodeum offers crucial insights into the usage of tapes and tape drives. Its goal is to enhance data integrity and streamline tape management by gathering information via TapeAlert error reporting. TapeAlert is an industry standard for monitoring the status and detecting issues in tape devices and drives directly from the tapes.

<figure><img src="/files/PDfXNlQP3JCJAOiZJTGY" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Helps in the prevention of any problems on Tapes or Tape Drives.
{% endhint %}

<details>

<summary>Tape Drive Information Reporting</summary>

* <mark style="color:blue;">Load operations</mark> : Number of times the drive has been loaded in its lifetime.
* <mark style="color:blue;">Meters processed</mark> : Total number of meters of tape that have been processed by the drive mechanism in either direction.
* <mark style="color:blue;">Power-on cycles</mark> : Total number of times the drive has detected a power-on event.
* <mark style="color:blue;">Power-on time</mark> : Number of seconds the drive has been powered on over its lifetime.
* <mark style="color:blue;">Read errors</mark> : 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.
* <mark style="color:blue;">Read processed</mark> : Each count represents a kebibyte (1024 bytes) of data processed across the host interface during read-type commands.
* <mark style="color:blue;">Read retries</mark> : Total number of read temps
* <mark style="color:blue;">Write errors :</mark> 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.
* <mark style="color:blue;">Write processed</mark> : Each count represents a kebibyte (1024 bytes) of data processed across the host interface during write-type commands.
* <mark style="color:blue;">Write retries</mark> : Total number of write temps

</details>

<details>

<summary>Tape information Reporting</summary>

* <mark style="color:blue;">Bytes Read</mark> : The total number of bytes of data read to tape
* <mark style="color:blue;">Bytes Written</mark> : The total number of bytes of data written to tape
* <mark style="color:blue;">Compression Enabled</mark> : 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.
* <mark style="color:blue;">Datasets read</mark> : The total number of data sets read from the medium in the volume over the lifetime of the volume.
* <mark style="color:blue;">Datasets written</mark> : The total number of data sets written to the medium in the volume over the lifetime of the volume.
* <mark style="color:blue;">Mount time</mark> : 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.
* <mark style="color:blue;">Read Compression Ratio</mark> : 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
* <mark style="color:blue;">Read Retries</mark> : Total number of read temps
* <mark style="color:blue;">Ready time</mark> : 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.
* <mark style="color:blue;">Tapes Mounts (#)</mark> : 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.
* <mark style="color:blue;">Unrecovered Read Errors</mark> : 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.
* <mark style="color:blue;">Unrecovered Write Errors</mark> : 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.
* <mark style="color:blue;">Write Compression Ratio</mark> : 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
* <mark style="color:blue;">Write Retries</mark> : Total number of write temps

</details>

#### Forget a tape

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

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'.

{% hint style="danger" %}
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.
{% endhint %}

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.

<figure><img src="/files/kFdGH4itIgQSRGwIbyP4" alt=""><figcaption></figcaption></figure>

#### Tape Status

Understanding the different lifecycle stages of tapes is crucial for maintaining data integrity and efficient tape management.

#### Barcode

<table><thead><tr><th width="160" align="center">Barcode</th><th>Description</th></tr></thead><tbody><tr><td align="center"><img src="/files/02WRPGtSkuVDj2frJoXs" alt="" data-size="original"></td><td>To prepare the tape for use, format the LTFS partition as it is currently unrecognized</td></tr><tr><td align="center"><img src="/files/xDuT9A3JarPqNBV4kp4J" alt="" data-size="original"></td><td>The tape is ready and can be used</td></tr><tr><td align="center"><img src="/files/LSpUSUCtV1hDOgLhPCRi" alt="" data-size="original"></td><td>The tape has a write protection enabled</td></tr><tr><td align="center"><img src="/files/nOroBqu7w6F2ogQ8455R" alt="" data-size="original"></td><td>The tape's capacity is full, no space left</td></tr></tbody></table>

#### Protect

<table><thead><tr><th width="165" align="center">Protect</th><th>Description</th></tr></thead><tbody><tr><td align="center"><img src="/files/g2o8cBgyn1ZwHFYTbXeN" alt="" data-size="original"></td><td>No tape protection is set</td></tr><tr><td align="center"><img src="/files/1ANrFZ6u34l6I3VYkR6Z" alt="" data-size="original"></td><td>The tape is protected by Nodeum software in using the lock feature</td></tr><tr><td align="center"><img src="/files/u6CPVSBLJPulS1eR6uNN" alt="" data-size="original"></td><td>The tape's physical write protection lock is enabled</td></tr><tr><td align="center"><img src="/files/ysOHTJIpNdhNAT3Pd0iP" alt="" data-size="original"></td><td>Nodeum software and physical write protection are both enabled</td></tr></tbody></table>

#### Status

<table><thead><tr><th width="236" align="center">Status</th><th>Description</th></tr></thead><tbody><tr><td align="center"><img src="/files/Sd7Ms2uENum2GW6qV8uC" alt="" data-size="original"></td><td>The tape is in good condition and ready</td></tr><tr><td align="center"><img src="/files/V3gKLFPY8A9IUla9cvz3" alt="" data-size="original"></td><td>The tape is flagged for review; a tape verification task must be performed</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nodeum.io/data-archiving/console/dashboard-and-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.