New in Version 7.4

Volume Verification enables users to verify the integrity of archived data across entire Archive Pools (tape, cloud, or disk), or to filter selections based on archive date or metadata  – using the same selection logic as a migration plan.

Since version 6.0, P5 has stored checksums alongside archived files. During verification, data is read and compared against these stored checksums to confirm file integrity. Any unreadable files are reported in the verification job. For files archived with versions prior to 6.0, a successful read is treated as successful verification.

Pools can be of different types (e.g., tape, cloud, disk) or different generations of LTO. This offers greater flexibility than traditional cloning, supporting diverse storage strategies like tape + cloud or three-tier redundancy.

Each pool is written to via an individual job, which reads from the source and writes to the target independently. These jobs are visible in the job monitor and operate at speeds dependent on the source and destination (e.g., cloud writes may be slower than tape).

Unlike cloning, this feature does not create identical tapes. Instead, it distributes the data across the defined pools. In contrast, cloning writes two identical copies in parallel, with each tape in the pair containing the exact same data. Cloned tapes must be written together until full, and a failed tape can be re-created from its clone. Either tape in a cloned pair can be used for restores.

Creating a second copy of a volume is an effective way to safeguard archived data, especially when one copy can be stored offsite for disaster recovery. This feature enhances long-term data integrity and is ideal for environments where archiving jobs are run without prior planning for redundancy.

To clone a volume, two LTO drives are required: one to read the original volume and one to write the clone. A blank volume must also be available in the same pool as the source. The result is a block-identical copy of the original volume, and both volumes are then marked as a cloned pair in the Volume List. Either tape can be used independently for restore operations. Note that cloning is only supported when using the P5 Native format – LTFS is not compatible, as it does not support the block-level access needed for cloning.

This feature adds flexibility and security to P5’s archiving system, allowing for robust redundancy even after data has been archived.

This method is especially useful for environments that want to eliminate physical media while maintaining archive workflows.

With version 7.4, additional parameters have been introduced to enhance control over the archiving process to S3, particularly around how data is handled in the staging area – the temporary local disk space used before data is bundled and uploaded.

One critical new parameter helps prevent the staging area from overfilling during large or continuous archive jobs, a common risk when dealing with large datasets or limited local storage. By allowing administrators to set thresholds and control batching behavior, P5 can pause or regulate data flow to ensure stability and avoid job interruption.

These new settings improve efficiency and reliability when archiving to the cloud, making it easier to integrate S3 storage into high-volume, long-term archiving strategies without overwhelming local resources.