Archive Related Operations Initiator
An entity submitting requests to DIVArchive (typically, an automation process).
In DIVArchive, an array designates a collection of disks identified by their name as they are declared in the DIVArchive configuration. A disk name is associated with a mounting point. Archive requests can be submitted with an array as the destination. DIVArchive is responsible for choosing the disk location to write the data to when several disks belong to the same array.
The Archive Exchange Format (AXF), or AXF Media Format, is based on a file and storage media agnostic encapsulation approach which abstracts the underlying file system, operating system, and storage technology making the format truly open and non-proprietary.
Part of the access key to an object. Categories are an approach to linking the object with the user activity field. It must not be confused with a Group, which is a storage concept.
An object is defined as complex when it contains one thousand (this is the default, but the value is configurable) or more components. Complex object handling may differ from non-complex objects as noted throughout this document.
A piece of code that accesses a shared resource (data structure or device) that must not be concurrently accessed by more than one execution thread.
A system that receives restored data in the DIVArchive system (for example, video servers, remote computers, FTP servers, and so on). Destinations can also be used as a Source certain operations.
Digital Moving-Picture Exchange (DPX)
The Digital Moving-Picture Exchange (DPX) format is a high quality video format that consists of one or more files for each frame of video. This format is likely to be used with complex objects.
An object instance is ejected (externalized) when one of the tapes containing the instance's elements is ejected. An object is ejected when all of its instances are ejected. An object is considered inserted when at least one instance of the object is inserted.
A group is a logical notion for characterizing a set of object instances. This concept has a direct influence on the instance's storage policy for tapes. Instances of the same group will be stored on the same tapes. However, objects cannot have multiple instances stored on the same tape.
Groups are based on the DIVArchive Tape Set. Each tape inserted in the system is assigned to a Set. Groups are then associated with a single Set. Multiple groups may be associated with the same set. No group can use the set number 0.
Several kinds of tape can be used in a DIVArchive system. Groups can be defined either by using a Set, in which you assign only tapes of the same type, or by defining the Set in which you can mix tape types. Therefore, the first case specifies the tape type that stores the object instance. See Set (of Tapes) later in this section for more information.
See Archive Related Operations Initiator previously described.
Tapes and disks may be formatted as either Archive Exchange Format (AXF) or Legacy Format. The format is set for tape groups and disk arrays during configuration.
A set of storage resources. Currently DIVArchive provides two types of media: Groups of Tapes and Arrays of Disks. The DIVA_archiveObject() and DIVA_copyToGroup() requests transfer objects to a Medium.
Copying of data from a DIVArchive media to a tape (Archive operation) or from a tape to a DIVArchive media (Restore operation).
Mutual Exclusion (mutex) avoids the simultaneous use of a common resource (that is, mutual exclusion among threads).
Part of the access key to an object. Names (file names) typically identify the object based on the content within the object.
In DIVArchive objects are archive entries. An object is identified by a pair (Name and Category) and contains one or more components. A component is the DIVArchive representation of a file. The components are stored in DIVArchive as an Object Instance. Also see Complex Object.
The mapping of an object's components onto a set of storage resources belonging to the same storage space. Deleting instances cannot result in deleting the related object and therefore the deletion of an instance, when that instance is unique, is not permitted.
Elimination of blank blocks between two objects on a tape (these blocks are caused by the deletion of objects), by moving the objects to a different, empty tape.
A request is an operation running in DIVArchive which progresses though steps (migration, transfer, and so on) and ends as either Completed, Aborted, or Cancelled.
Used to denote the necessary elements involved for processing requests (for example, Actors, Managers, Disks, Drives, and Tapes).
Every tape in a DIVArchive system belongs to one and only one Set. If the tape is not available to DIVArchive, it belongs to Set #0, otherwise it belongs to a set with a strictly positive ID (for example, Set #1). Each Group is associated with a Set. When the group needs an additional tape, it takes it from its associated Set.
A system that produces data to be archived in the DIVArchive system (for example, video servers, browsing servers, remote computers, and so on). Sources can also be used as a Destination for certain operations.
Splitting an object's components onto several tapes (typically two). This can occur when the component size is larger than the remaining size left on the initial tape.
Copying data from a Source to a DIVArchive media (Archive operation) or from a DIVArchive media to a Destination (Restore operation). See Request for more information.
Universally Unique Identifier (UUID)
A Universally Unique Identifier (UUID) uniquely identifies each object created in DIVArchive across all Oracle customer sites. Objects created using the Copy As request are not assigned a UUID. An object created by a Copy As request contains the same UUID as that of the source object.