1 Introduction

This chapter describes an overview of the Oracle DIVArchive DIVAprotect, new and enhanced features and functionality, and includes the following information:

DIVAprotect Overview

DIVAprotect is an Oracle DIVArchive option that constantly monitors the digital storage infrastructure, and warns about media or tape drive degradation before it results in reduced performance or possible data loss. DIVAprotect provides long term content protection, management, and security to Oracle DIVArchive.

DIVAprotect features include:

  • Continuous monitoring of tape drives and media

  • Complete history of drive and media performance

  • Full integration with Oracle DIVArchive

  • Detailed Performance Analysis

  • Preventive and corrective maintenance aid

  • System Journal

  • System Metrics

DIVAprotect gives you information regarding current and past performance numbers for various system components. You can use the information to project present and future system requirements based on various premises, and plan for appropriate system evolutions.

DIVAprotect collects quality and performance data in real time within the archive environment. You can use the information as an aid for selective migration of content, recycling of defective media, preventative hardware maintenance, network and storage system integrity, and content availability.

DIVAprotect performs the following tasks:

  • Gather operational facts from the following sources:

    • DIVArchive System (software components and equipment)

    • Platforms (servers and operating system)

    • Exchanged Data

  • Process operational facts into metrics by sampling, filtering, normalizing, counting, and aggregating data.

  • Maintain a view of the system's current and past performance.

  • Collect and verify checksum data to expose disk and tape errors, and report Disk, Tape, and Source/Destination failures.

  • Assist in managing large volumes of data.

  • Provide billing data for customers offering DIVArchive as a service to other customers.

  • Predict operational conditions of interest (for example, end of life of a tape or a drive).

  • Provide low-level diagnostic information to assist support staff investigations.

  • Answer a broad range of questions about:

    • Optimal performance (what can the system deliver in an optimal context?).

    • Current performance (is the system performing at its best?).

  • Causes of the current state. That is, what led to the current state. For example, how did so many tapes get consumed in the last month?

  • History (for example, evolution of the capacity, throughput, activity, and so on).

  • Possible solutions or adjustments (for example, what needs fixing or relocation, what should be replaced, what should be reconfigured, and so on).

  • What If scenarios (that is, what is the impact of a proposed change in the system, capacity planning, and so on).

  • Use of the system at various levels (DIVArchive system, DIVArchive component, request type, tape, library, tape drive, disk, category, and so on) as a basis for billing (that is, who, what, when, how much, how many, how long).

DIVAprotect Principles of Operation

The primary purpose of DIVAprotect is to collect operational data generated by activity in the archive system (Archive, Restore, Copy, Insert Tapes, and so on). Each activity generates events, for example, a TAPE READ or a DELETE INSTANCE. Events are collected in real time and stored in the database.

Each event has various information attached to it. For example, the size of a transfer, its duration, the Oracle DIVArchive Actor used, and so on. These are referred to as Event Parameters.

Metrics are generated and updated by processing event parameters using background jobs scheduled every hour. You can break down (aggregate) event data according to various resources or attributes (for example, object name, tape barcode, storage device, and so on), and per hour, day, week, month, or year interval. You can also use no interval to collect a lifetime metric. Various aggregation functions are provided; for example, Count, Sum, and Average.

For example, the TAPE_DRIVE_READ_WRITE_DAY built-in metric sums the transfer sizes of TAPE READ and TAPE WRITE events and breaks down the values per device, and per day.

DIVAprotect supports additional data retrieval such as DIVArchive Resource Statistics and Quick Response Data (QRD), detailed in the Chapter 3. This data is processed separately and is not available in Metric Definitions.

DIVAprotect New and Enhanced Features and Functionality

This section describes new and enhanced features and functionality. These changes became effective in the DIVArchive 7.5 release.

Events

DIVAprotect Archive, Copy, Copy As, Restore, and Oracle DIVArchive Partial File Restore request events will populate the Transfer Size and Duration fields.

The ANALYZE_END and ANALYZE_ERR events were removed from the predefined DIVAprotect events.

Metrics

To standardize the Metric ID across all DIVArchive installations, all predefined metrics have a hard-coded Metric ID instead of using a database sequence. All user defined metrics start with Metric ID 1001. The database upgrade scripts handle this migration for you during upgrades from DIVArchive 7.4 to release 7.6. If you already had any user-defined metrics, they are automatically assigned a new Metric ID starting with 1001.

The following pre-defined metrics were remove in DIVArchive 7.5. However, there is no impact for earlier releases and customers currently using them; those metrics will continue to exist, update, and are not removed during the upgrade process to the 7.6 release. This only affects new installations of DIVArchive 7.6 and later.

  • ANALYZE_NUMBER_DAY

  • ANALYZE_NUMBER

  • ANALYZE_ABORTED_NUMBER_DAY

  • ANALYZE_ABORTED_NUMBER

  • ANALYZE_DATA_DAY

  • ANALYZE_DATA

  • ANALYZE_AVG_THROUGHPUT_DAY

  • ANALYZE_AVG_THROUGHPUT

  • ANALYZE_MIN_THROUGHPUT_DAY

  • ANALYZE_MIN_THROUGHPUT

  • ANALYZE_MAX_THROUGHPUT_DAY

  • ANALYZE_MAX_THROUGHPUT

  • ANALYZE_TIME_DAY

  • ANALYZE_TIME

  • MEDIA_OBJECT_INSTANCE_CREATE_DELETE_DAY

  • MEDIA_OBJECT_INSTANCE_CREATE_DELETE

New Predefined Metrics

The following predefined metrics were added in the DIVArchive 7.5 release. See Metric Definitions for a complete list.

  • ACTOR_READ_WRITE_MONTH

  • ACTOR_READ_WRITE_NUMBER_MONTH

  • ACTOR_TIME_ALL_OPERATION_MONTH

  • ACTOR_TIME_READ_MONTH

  • ACTOR_TIME_WRITE_MONTH

  • DISK_AVG_TRANSFER_RATE_READ_MONTH

  • DISK_AVG_TRANSFER_RATE_WRITE_MONTH

  • DISK_CHECKSUM_FAILURE_COUNT_MONTH

  • DISK_NUMBER_READ_ABORTED_MONTH

  • DISK_NUMBER_READ_MONTH

  • DISK_NUMBER_WRITE_ABORTED_MONTH

  • DISK_NUMBER_WRITE_MONTH

  • DISK_READ_MONTH

  • DISK_TIME_ALL_OPERATION_MONTH

  • DISK_TIME_READ_MONTH

  • DISK_TIME_WRITE_MONTH

  • DISK_WRITE_MONTH

  • DIVARCHIVE_SYSTEM_ACTIVE_ARCHIVE_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_ACTIVE_COPY_AS_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_ACTIVE_COPY_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_ACTIVE_RESTORE_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_AVG_READ_WRITE_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_ARCHIVE_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_CREATED_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_DELETED_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_INSTANCE_COPY_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_INSTANCE_CREATED_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_INSTANCE_DELETED_MONTH

  • DIVARCHIVE_SYSTEM_NUMBER_OBJECT_RESTORE_MONTH

  • DIVARCHIVE_SYSTEM_OBJECT_EXPORT_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_OBJECT_IMPORT_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_OBJECT_INSTANCE_EXPORT_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_OBJECT_INSTANCE_IMPORT_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_READ_WRITE_ABORTED_NUMBER_MONTH

  • DIVARCHIVE_SYSTEM_READ_WRITE_MONTH

  • DIVARCHIVE_SYSTEM_READ_WRITE_NUMBER_MONTH

  • MEDIA_ARCHIVED_OBJECT_DATASIZE_MONTH

  • MEDIA_DATA_SIZE_DAY

  • MEDIA_DATA_SIZE_MONTH

  • MEDIA_OBJECT_INSTANCE_EXTERN_MONTH

  • MEDIA_OBJECT_INSTANCE_ONLINE_MONTH

  • MEDIA_READ_WRITE_MONTH

  • MEDIA_READ_WRITE_NUMBER_MONTH

  • MEDIA_RESTORE_OBJECT_DATASIZE_MONTH

  • MEDIA_TAPE_EXPORT_NUMBER_MONTH

  • MEDIA_TAPE_IMPORT_NUMBER_MONTH

  • SD_ARCHIVE_OBJECT_DATASIZE_MONTH

  • SD_READ_MONTH

  • SD_READ_NUMBER_MONTH

  • SD_RESTORE_OBJECT_DATASIZE_MONTH

  • SD_TIME_MONTH

  • SD_WRITE_MONTH

  • SD_WRITE_NUMBER_MONTH

  • TAPE_DRIVE_DATA_RATE_MONTH

  • TAPE_DRIVE_ERROR_RATE_MONTH

  • TAPE_DRIVE_NUMBER_READ_WRITE_ABORTED_MONTH

  • TAPE_DRIVE_OPERATION_TOTAL_TIME_MONTH

  • TAPE_DRIVE_READ_WRITE_MONTH

  • TAPE_DRIVE_READ_WRITER_NUMBER_MONTH

  • TAPE_DRIVE_TIME_ALL_OPERATION_MONTH

  • TAPE_DRIVE_TIME_READ_MONTH

  • TAPE_DRIVE_TIME_WRITE_MONTH

  • TAPE_LIBRARY_NUMBER_DISMOUNT_ABORTED_MONTH

  • TAPE_LIBRARY_NUMBER_MOUNT_ABORTED_MONTH

  • TAPE_LIBRARY_NUMBER_MOUNT_MONTH

  • TAPE_LIBRARY_NUMBER_READ_MONTH

  • TAPE_LIBRARY_NUMBER_WRITE_MONTH

  • TAPE_LIBRARY_READ_MONTH

  • TAPE_LIBRARY_WRITE_MONTH

  • TRANSCODE_DATA_MONTH

  • TRANSCODE_NUMBER_MONTH

  • TRANSCODE_TIME_MONTH

  • MEDIA_OBJECT_INSTANCE_CREATE_DAY

  • MEDIA_OBJECT_INSTANCE_DELETE_DAY

  • MEDIA_OBJECT_INSTANCE_CREATE

  • MEDIA_OBJECT_INSTANCE_DELETE

  • MEDIA_OBJECT_INSTANCE_CREATE_MONTH

  • MEDIA_OBJECT_INSTANCE_DELETE_MONTH

  • MEDIA_OBJECT_INSTANCE_EXTERN_DATASIZE_DAY

  • MEDIA_OBJECT_INSTANCE_EXTERN_DATASIZE_MONTH

  • MEDIA_OBJECT_INSTANCE_ONLINE_DATASIZE_DAY