A vendor-neutral format, supported by DIVArchive, for storing content on various mediums (including tape and disk). It can store many files and directories in a single file (container) much like a ZIP file.
The file system directory where DIVAnet is installed. DIVAnet can be installed in its own directory (recommended), or within the DIVArchive home directory.
An archived object describes digital content in the archive system. A DIVAnet object is a set of archive objects, archived at one or more DIVArchive sites, sharing the same name (object name and category pair). Each object on a particular site can have one or more copies (object instances).
A sitename uniquely identifies a DIVAnet site, which is defined as exactly one DIVArchive installation and one or more DIVAnet services.
The DIVArchive DFM service monitors content that is being written to disk in a folder. It then performs the operation assigned to that folder (Archive, Restore, Copy, and so on) to the content (placed in the folder) into a DIVArchive system after the content has been completely written top the folder location.
An operation that copies content from one DIVA site to another, archiving the content to the target site.
An operation that moves content from one site to another, but does not archive the content to the target site.
A name that represents a set of archive media (disks or tapes) in a DIVA system. There exists one media per copy of an asset.
When an API client is connected to DIVAnet in MultiDiva mode, multiple DIVArchive sites appear to the client as one large archive system.
Contains information necessary to communicate with a connected server or disk. You transfer content to and from DIVArchive through these servers and disks. Examples are Video servers, FTP servers, and disk arrays.
You can configure the Oracle DIVArchive Storage Plan Manager (SPM) service to automatically perform an operation when content arrives at a DIVArchive site (such as restore or copy).