This chapter describes the Oracle DIVArchive 7.5 release, and includes the following information:
The DIVArchive architecture enables integration of many different types of servers and technologies, for example Broadcast Video Servers, Storage Area Networks, and Enterprise Tape Libraries. The DIVArchive installation varies from site to site, therefore the exact configuration of your specific DIVArchive platform is not described in this book. Refer to your DIVArchive Site Configuration document for details on your specific DIVArchive system installation and configuration.
The Site Configuration is a document prepared by Oracle (or an affiliated system integrator) after installation at your site. It is a complete record of the configuration of the DIVArchive sub-systems and third party interfaces, site details and contacts, user names and passwords, and remote access codes.
The Site Configuration (for your site) is referenced at various points in this document, such as when user names and passwords are required for access to the DIVArchive software utilities.
Note:
The File System Interface is not released with DIVArchive 7.x and is only supported by special request.See Appendix A for DIVArchive options and licensing.
The following table lists the standard ports used by the DIVArchive system. If you need assistance contact Oracle Support.
Table 1-1 DIVArchive Port Utilization
| Service | Port Number | Description and Notes |
|---|---|---|
|
FTP |
|
Port depends on configuration |
|
Telnet |
|
Solaris hosts only |
|
SSH |
|
Solaris hosts only |
|
HTTP |
|
DIVAdirector |
|
Oracle SQLNet |
|
Manager database access |
|
RDP (Microsoft Terminal Services) |
|
Remote Desktop access |
|
VNC |
|
Used only when AMC is installed to access the Avid servers. |
|
Oracle DIVArchive Robot Manager |
|
Robot Manager |
|
Oracle DIVArchive Manager |
|
Manager |
|
Oracle DIVArchive Actor |
|
Actor |
|
Flip Factory |
|
Flip Factory |
|
DIVArchive AMC |
|
Avid AMC |
|
Oracle DIVAnet |
|
DIVAnet |
The following sections describe new and enhanced features and functionality included in this DIVArchive release.
This following list describes general DIVArchive new and enhanced features and functionality included in this release:
All core DIVArchive components now support for Oracle Linux 7 x86_64 and later.
If you require a Linux environment in a language other than English, create a user and identify the desired language in the user profile. Oracle Linux 7 x86_64 and later has support for a variety of languages (other than English) and you select the language during Linux installation.
Windows installations must use the English language, and Oracle only supports English-based Windows environments.
See the Oracle DIVArchive Supported Environments Guide in the Oracle DIVArchive 7.5 Core documentation Library for information about certain limitations when running in the Linux environment.
Archive and restore operations of symbolic links are now supported in Linux.
Shortcuts created using the Windows operating system are not represented as symbolic links because they are treated as files. Only symbolic links created on the UNIX platform are archived and represented as symbolic links in DIVArchive.
The Java and C++ APIs file list returned from a getFilesAndFolders call includes symbolic links.
The export and import operations type attribute can now contain the letter S to represent a symbolic link.
DIVArchive 7.5 supports configuring Oracle Archive Cloud accounts for use.
Any disks added to a cloud array are considered cloud disks.
See Configuring Oracle Archive Cloud for DIVArchive for detailed information on using Oracle Archive Cloud accounts with DIVArchive.
Visit the following links for information on the Oracle Storage Cloud:
For information regarding metered and non-metered accounts:
http://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/csgsg/
For up to date cloud information:
For further assistance:
http://docs.oracle.com/cloud/latest/storagecs_common/index.html
The DIVArchive Control GUI contains the following enhancements:
A new column is available in the Disks View. The Consumed Size column represents the space (in kilobytes) consumed by content on disk. The new column is especially useful for cloud accounts with unlimited disk space because it provides visibility into the amount of content stored in the cloud.
The cloud storage class associated with the array is also displayed in this view. Non-cloud disks have a storage class of NONE. Cloud disks have a storage class of Standard (immediately available for download from the cloud) or Archive (requires at least 4 hours to download from the cloud).
To view the storage class associated with a particular cloud instance, the Object Properties View contains a new column called Cloud Storage Class.
Database password encryption has been enhanced for additional security. See the Oracle DIVArchive Database User's Guide in the Oracle DIVArchive 7.5 Core documentation library for detailed information.
DIVArchive 7.5 in a Windows environment only supports DIVArchive Oracle database package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_OEL7_ Windows_64-bit.zip.
DIVArchive 7.5 in a Linux environment only supports DIVArchive Oracle database package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_OEL7_x86_64.sh.
The Control GUI password hash has been enhanced for additional security.
LTO-7 drives are now supported.
DIVArchive operations now include the total tape size.
For some specific tape drives (Oracle T10K and IBM LTO drives) the Actor now returns the true remaining size on the tape, and the last written position on tape to the Manager during a transfer of content to tape. The remaining size is given in number of bytes of uncompressed data.
The Manager uses the remaining size and last written position to obtain the true total and remaining size on the tape.
The Manager uses the true total and remaining size on tape in all tape based operations instead of relying on the size of the tape type.
Export and Import operations now include the total tape size.
DIVArchive 7.5 supports a new type of ODA drive from Sony. The details of these drives are as follows:
Sony released a new generation of ODA drives; ODS-280F and ODS-280U. DIVArchive has only been tested with the Fibre Channel type. These drives are twice as fast as the Gen1 drives. The ODS-280U has not been qualified for use with DIVArchive 7.5.
A new type cartridge is available for this drive; ODC3300R. This is a WORM drive with a 3.3 TB capacity.
Gen2 drives can read content written on Gen1 media with Gen1 drives. DIVArchive does not support the read only media-drive compatibility. Oracle recommends isolating Gen1 media from Gen2 media in the configuration (there is no cross-generation compatibility) and there must be at least one Gen1 drive in a library containing Gen1 cartridges.
DataExpedition release 1.17 is now supported.
The JDBC Thin Driver enables replacing the Oracle SID setting with the Oracle Service Name.
MPEG2 Transport Stream enhancements for Oracle DIVArchive Partial File Restore operations. This feature now supports HD MPEG video essences with AES3 audio tracks.
Linux-based Actors only support Telestream Vantage for transcoding operations.
Promedia Carbon (formerly Rhozet) is now supported. This is a new transcoder supported in DIVArchive 7.5. You can now select the transcoder type tre from the Configuration Utility. Both the Name and GUID are supported as options for Presets and Profiles format types.
Archive and Restore of empty files and folders are now supported.
Empty files and folders are only supported by AXF. When Legacy format is in use, DIVArchive reports an error if an empty file or folder is discovered during the transfer.
Empty files are displayed in the Elements list on the Instances tab in the Object Properties dialog box.
Folders are not displayed in the Elements list because they are only metadata and have no physical presence on the tape.
All files and folders are displayed on the Components tab of the Object Properties dialog box.
Long path names are now supported in both Windows and Linux environments.
Absolute path names are supported on both Windows and Linux up to a maximum of 4000 characters.
Relative path names are limited to 256 characters on Windows systems (only).
The Control GUI displays the fully qualified path to a file, and the fully qualified path to an empty folder, in the Components list on the Properties tab of the Object Properties dialog box.
UNC paths are supported for SMB Source/Destinations and Managed disks if the UNC path is mounted directly on the Windows Actors.
Linux-based Actors support Telestream Vantage for transcoding operations.
Linux-based Actors cannot use CIFS, and a new path is required to enable Linux-based Actors to transfer content to and from SMB network shares (transcoder cache).
Caution:
The sequence of theactor, actorPath, and transcoder settings is important. The parameter sequence must be actor, then actorPath, and then transcoder.The path is specified as the value of the actorPath parameter in a delimited list as follows:
[actor:actor_name,actorPath:actor_path,transcoder:trancoder_ip_address],cifs://username:password@\\transcoder_cache_ip_address\transcoder_cache
You do not need to change an existing CIFS path for use with a pre-existing Vantage transcoder configuration if you are switching from a Windows Actor to a Linux Actor. The CIFS path is only used by Vantage to access the cache. The only thing that changes is adding the actorPath to the working directory of the transcoder. For example:
[actor:actor1,actorPath:/tmp/vantagecache,transcoder:100.100.100.100],cifs://Administrator:password@\\100.100.100.100\VantageStore
The actorPath represents the path the Linux Actor uses to transfer content to and from the SMB network share (transcoder cache) on a Linux system.
Migration service jobs now have events associated with them. All job events are displayed under the Job Events tab in Job Properties dialog box. By default, events are loaded in descending order by time and event id. The Events table in the Job Events tab highlights events with different colors based on severity. Red indicates an Error, yellow indicates a Warning, and white indicates Information. You click Refresh to refresh the entire Job Properties dialog box display.
You must use a migration job to change a tape format from Legacy to AXF. Repacking a tape will not change the tape format. Repacking of existing Legacy format objects retains the format of the tape even if the tape group format was updated in the configuration from Legacy to AXF.
You can now change the status of SPM Failed Actions to Completed by right clicking the action and selecting Mark Action Completed from the context menu.
Normally, SPM will retry a completed Copy action if the Once Only option is set to NO, and a user manually (or accidentally) deletes the instance that SPM copied before the Storage Slot expires. Also, SPM will normally retry a completed Delete action if a user manually (or accidentally) copies an instance to the Storage Slot medium after SPM deleted it. Actions marked as complete by a user will never be retried by SPM. However, you can reschedule a user completed action by right clicking it and selecting Reschedule Action from the context menu. The Mark Action Completed (by a user) option is only available using the administrator profile. See Appendix A for Oracle DIVArchive options and licensing information.
DIVAnet version 2.x is available for 64-bit Windows platforms, and 64-bit Oracle Linux. The DIVAnet 2.2 release is compatible with DIVArchive releases 7.3.1 and later. Currently, DIVAnet 2.2 requires that all sites in the DIVAnet network run DIVAnet release 2.2.
New and enhanced features and functionality in DIVAnet 2.x (and later) includes the following:
New architecture supports more sites, requests, connections and objects.
More configurable, manageable, flexible, and improved error handling.
New DIVAnet UI (User Interface) has more powerful request monitoring, asset search capabilities, and a simple, more flexible reconciliation, copy, and delete process.
API functionality has been enhanced.
Support for Oracle Linux 7 x86_64 and later.
Refer to the Oracle DIVAnet Installation, Configuration, and Operations Guide in the Oracle DIVAnet documentation library for more information on the new DIVAnet releases.
This section describes events and metrics processed by DIVAprotect.
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 are removed from the predefined DIVAprotect events.
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.5. If you already had any user-defined metrics, they are automatically assigned a new Metric ID starting with 1001.
The following pre-defined metrics have been remove. 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.5 release. This only affects new installations of DIVArchive 7.5 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
The following new predefined metrics have been added in this release. See Metrics 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
Changes have been made to the configuration files included with DIVArchive for release 7.5. The changes coincide with the new and enhanced functionality. The following is a brief overview of the changes; you can find more details in the sections specific to each component.
The new Manager ABORT_ARCHIVES_ON_EMPTY_FILES configuration setting terminates Archive requests that contain empty files or folders. The default setting is disabled; allowing the archiving of empty files or folders.
The new Manager DIVAMANAGER_DBSERVICENAME configuration setting is the Oracle ServiceName setting. This is set during database installation. The recommended setting is lib5.world. This value or the DIVAMANAGER_DBSID must be set. If both are set, the Service Name takes precedence over the Oracle SID.
This section describe the media storage formats available in this DIVArchive release.
AXF (Archive eXchange Format) is an open format that supports interoperability among disparate content storage systems and ensures the content's long-term availability no matter how storage or file system technology evolves.
An AXF object is an IT-centric file container that can encapsulate any number, and any type, of files in a fully self-contained and self-describing package. The encapsulated package contains its own internal file system, which shields data from the underlying operating system and storage technology. It's like a file system within a file that can store any type of data on any type of storage media.
Tape groups or disk arrays used by complex object requests must be in an AXF format, because complex objects cannot be stored in Legacy format. Because all complex objects are written in the AXF format, any instance of a complex object will also be in the AXF format.
In DIVArchive, a Tape Group or Disk Array has a media format parameter that indicates which storage media format to use when creating Archived objects. You can set the media format to either DIVArchive Legacy Format or the AXF Format. This setting can be changed at any time and does not influence content already stored. It is possible to have more than one storage media format within tape groups and disk arrays.
A DIVArchive object instance is only written in one media format. Therefore, if an object spans tapes, each tape used as part of an object instance will be written in the same media format. An object can contain multiple instances, each of which can be stored in either Legacy or AXF format.
Although a tape group can contain more than one storage format, an individual tape has at most one storage media format. The format of a tape instance is the format of the tape on which the instance resides. All instances on a tape must have the same format.
The media format for an empty tape is assigned when the first object on that tape is written. The tape is assigned the format of the tape group that appears in the request. After the media format for a tape is assigned, you cannot change it unless all objects on the tape are deleted. After deletion of all objects from a tape, the tape's format becomes unassigned until content is again written to the tape. If the tape was in use, the tape format cannot change unless it is empty and cleared.
Both Legacy and AXF formatted tapes can exist in the same group. Nevertheless, objects in AXF format will only be written to AXF formatted tapes, and objects in Legacy format will only be written to Legacy formatted tapes, even though they are in the same tape group.
Note:
A Repack request will always write the destination tape in the same media format as the source tape.Similarly, tape spanning operations will always use the same format across all tapes storing spanned objects. If an instance spans across multiple tapes, then all tapes used to span the content will have the same format.
Unlike tapes, disks do not have a format. DIVArchive allows storing objects in different media formats on the same disk. If a disk contains objects in Legacy format, and that disk is then assigned to an AXF formatted array, it will still contain objects in Legacy format. However, new objects written to the disk will be in AXF format.
If a disk instance is non-complex and permanent (not a cache instance), it is stored in the format of the destination array. If a cache instance is non-complex, it is stored in the format of the group specified in the request.
You can use the Copy To Group, or Copy As New requests to migrate objects from Legacy media format to AXF media format (or back). However some AXF objects cannot be copied to the Legacy format; copying objects from Legacy format to AXF format does not present any issues. In DIVArchive the only limitation on copying an object instance from AXF format to Legacy format is the complex object feature.
Complex objects have significantly expanded the object component boundaries, allowing up to one million files and ten thousand folders per object.
Complex objects maintain information about files and folders in the archive. They store subtotals for each folder, including the total number of files and subfolders within the folder, and the total size of all files within the folder and within any subfolders.
DIVArchive uses the configurable Complex Object Threshold parameter during archival to determine whether a new object should be complex based on the number of components. This value is set in the manager.conf configuration file. If the number of components is greater than the Complex Object Threshold, the object becomes a complex object. After an object is identified as a complex object it will always be complex; even if it is copied using the Copy As command, or imported using the Export/Import Utility.
Oracle recommends that the threshold remain at the default value (1,000 components) unless there is a specific reason to adjust the value. Contact Oracle Support for assistance as required.
A complex object differs from a non-complex object in several key ways. For example, the file and folder metadata information of a complex object is stored in a file, not in the Oracle Database. The file contains the file names, folder names, checksums, and files sizes. The files are located in the Metadata Database root directory. Complex objects must be stored in AXF format whether on tape or on disk.
Complex objects can contain hundreds of thousands of files. However, some DIVArchive API commands (for example, GetObjectInfo) will not return the entire set of files. Instead, these commands return a single placeholder file which prevents downstream applications from being overwhelmed by file and folder information. Also, the entire set of files on a tape are not displayed in the Control GUI Object Properties and Tapes screens, only a single placeholder file is shown. The DIVArchive API includes a command to return all of the files and folders within a complex object. See the appropriate Oracle DIVArchive API documentation in the Oracle DIVArchive documentation libraries for details.
Oracle DIVAnet does not currently support replication of complex objects.
The following features do not support complex objects:
Delete on Source option
Verify on Restore (VFR) checksum feature
Verify on Archive (VFA) checksum feature
deleteFile API call
getObjectListbyFileName API call
GetByFilename API call (for Avid connectivity)
DeleteByFilename API call (for Avid connectivity)
When archiving complex objects using the FTP protocol, and an FTP Client with default settings (FileZilla is recommended), the transfer will typically fail when archiving any object with more than approximately 3,900 files.
Occasionally, during the directory scan, the Actor connection times out before the size of the object can be computed. More often, a request terminates in the middle of the transfer because the FTP server is consuming all of the available sockets.
You can add the following parameters in the Source/Destination Command Options or in the Options of the command itself to resolve timeout issues:
-transfer_timeout 1200 -list_timeout 600
See Appendix C for detailed parameter information.
Use the following procedure to include the parameters in the Source/Destination frame in the Configuration Utility:
Open the DIVArchive Configuration Utility.
Navigate to the System tab.
Double-click the desired Source/Destination in the Sources and Destinations frame to open the edit dialog box.
Add the two parameters (-transfer_timeout 1200 and -list_timeout 600) in the Connect Options field.
Click OK to save the changes.
Notify the Manager of the changes using the Control+N key combination.
Oracle recommends setting the following corresponding parameters in the FileZilla server under General Settings:
Connections Timeout = 600
No Transfer Timeout = 1200
Open the FileZilla server interface.
Click the Server Options icon on the tool bar.
Adjust the settings in the General Settings area.
If requests terminate unexpectedly during transfers, adjust the Windows Registry parameters as follows:
Open regedit.
Modify (or create) the following values under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters:
TcpTimedWaitDelay = 10 MaxUserPort = 90000
If the desired registry parameter does not exist, right-click and create a new double word (DWORD) value.
If the parameter does exist, double-click it and enter the values.
Restart the computer to enable the new registry values.
DIVArchive includes the core software components discussed in the following subsections.
Long path names are now supported on both Windows and Linux. Absolute path names are supported on both Windows and Linux to a maximum of 4000 characters. Relative path names are limited to 256 characters on Windows systems (only).
All Windows batch files (.bat) have corresponding shell scripts (.sh) in Linux. You must substitute Windows paths with Linux paths when operating on Linux. For example, the Windows path C:\DIVA\Program equates to /home/diva/DIVA/Program in the Linux environment.
Note:
Linux commands, paths, and file names are case-sensitive.The following features require Windows-based Actors:
Oracle DIVArchive Avid Connectivity
Transcoder integration
Tape Reading Utility
You must use standard commands. For example DD and MT.
Linux Actors support QuickTime, GXF, and TeleStream wrappers for Oracle DIVArchive Partial File Restore (video). See Appendix A for Oracle DIVArchive options and licensing information.
Due to degraded performance, Windows IIS and FileZilla FTP sources and destinations cannot be used for complex objects. Oracle only supports Linux-based FTP servers when operating in a Linux environment. The Windows IIS and FTP servers cannot accommodate large numbers of files.
The DIVArchive Manager is the main component in a DIVArchive system. All archive operations are controlled and handled by the DIVArchive Manager. Operation requests are sent by initiator applications through the DIVArchive Client API. DIVArchive supports Main and Backup DIVArchive Managers (see Appendix A for Oracle DIVArchive options and licensing information).
The DIVArchive Actor is the data mover between devices in your production system. Actor supports interfacing and data transfer between many different types of devices.
All Actor operations are initiated and coordinated by the DIVArchive Manager through the TCP/IP networking protocol. Key benefits of the distributed design of the DIVArchive Actors are:
You can expand the archive subsystem to increase the overall bandwidth by adding more Actors to the system. See Appendix A for Oracle DIVArchive options and licensing information.
You can share SAN based disk and tape drive resources among multiple Actors.
In combination with the DIVArchive Manager, multiple Actors provide scalability, load balancing, redundancy, and failover. You can take individual Actors offline for maintenance without shutting down the DIVArchive system.
Note:
UNC paths are supported for SMB Source/Destinations and managed disks if the UNC path is mounted directly on Windows Actors.The DIVArchive Client APIs are a set of functions enabling external applications, acting as clients, to use the services offered by the DIVArchive system.
A library of client functions is provided with the selected API and must be linked to each DIVArchive client application. These functions encapsulate client commands into DIVArchive request messages sent over a TCP/IP connection to the DIVArchive Manager.
Currently available APIs are C++, Java, and Web Services (Oracle DIVA Enterprise Connect). Refer to the appropriate Oracle DIVArchive API documentation in the Oracle DIVArchive Additional Features documentation library, and the Oracle DIVA Enterprise Connect documentation library for more information.
The DIVArchive software is bundled with an Oracle database installation. The database stores all information relating to the DIVArchive system including its configuration. SQL queries used by the Manager are optimized to support configurations with up to 58 million components.
When installing DIVArchive in a 64-bit environment, the latest 64-bit DIVArchive Oracle release must be installed to use 64-bit support.
DIVArchive 7.5 in a Windows environment only supports DIVArchive Oracle database package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_OEL7_ Windows_64-bit.zip and later.
DIVArchive 7.5 in a Linux environment only supports DIVArchive Oracle database package OracleDivaDB_3-0-0_12_1_0_2_0_SE2_OEL7_x86_64.sh.
The Oracle database is not intended to be modified directly by customers, but rather by using Oracle utilities. Direct modification of this database by customers through Oracle utilities is not supported by Oracle.
DIVArchive stores object metadata separately from the Oracle database in the DIVArchive Metadata Database. The metadata database contains files stored in a file system local to the DIVArchive Manager. The files are located in the Metadata Database root folder. This storage method enables DIVArchive to effectively operate with large volumes of files, folders and other metadata.
The metadata database is very high performance, and has almost unlimited scalability. You must treat the metadata database with the same caution as the Oracle database, and it must be backed up at regular intervals through the DIVArchive Backup Service.
The DIVArchive Control GUI connects to both the DIVArchive Manager and the DIVArchive database. You use it to monitor, control, and supervise operations in DIVArchive. you can operate multiple Control GUI instances simultaneously from any computer that has TCP/IP connectivity to both the DIVArchive Manager and the DIVArchive database.
The Control GUI is not intended for the intensive archive operations of a DIVArchive system. Archive operations are typically initiated to DIVArchive from a Broadcast Automation or MAM (Media Asset Management) system.
See the Oracle DIVArchive Operations Guide in the Oracle DIVArchive Core documentation library for more information on using the interface.
The refresh rate for the Control GUI is set in the Manager Setting tab of the Configuration Utility in the GUI: Dashboard Refresh Delay field.
Additional modules are available to expand your DIVArchive system capabilities. Most of these options are currently covered in separate documents, but are briefly described here for completeness. See Appendix A for DIVArchive options and licensing information.
You can use DIVArchive to only manage disk storage, but storage capacity can be further expanded by adding one or more tape libraries. In these cases, the DIVArchive Robot Manager module provides an intermediate software layer for the DIVArchive Manager to interact with many different types of tape libraries. It is connected to the DIVArchive Manager through TCP/IP. See Appendix A for DIVArchive options and licensing information.
This distributed architecture provides substantial flexibility including:
Libraries controlled using a SCSI interface are limited by the cable length. Because the connection to the DIVArchive Robot Manager from the DIVArchive Manager is over TCP/IP, the library does not need to be colocated near the DIVArchive Manager host computer.
Enabling installation of multiple, or dissimilar, libraries by configuring additional DIVArchive Robot Manager modules.
Enabling rapid development to support new types or models of libraries.
You can restart the robotics interface without needing to restart the DIVArchive Manager.
The DIVArchive Robot Manager interfaces with the library using either a direct interface to the library itself (through native SCSI, or SCSI over Fibre Channel), or through an intermediate Ethernet connection to the manufacturer's own library control software.
VACP (Video Archive Communications Protocol) is developed by Harris Automation Solutions and used by some automation systems for interfacing to an archive system. DIVArchive has its own API for communicating with the DIVArchive Manager, which is not compatible with VACP.
To provide interoperability without the need to redevelop the archive interface at the automation level, this module is provided to act as an interface to convert VACP commands from the attached automation system to DIVArchive API commands on computers that have TCP/IP connectivity to DIVArchive.
The SPM (Oracle DIVArchive Storage Plan Manager) provides automatic migration and life cycling of material within the archive, based on the rules and policies defined in the SPM configuration. The DIVArchive DSM (Disk Space Monitor) works with SPM to delete material from SPM managed arrays (based on disk space watermarks).
The DIVArchive SNMP (Simple Network Management Protocol) interface supports status and activity monitoring of different DIVArchive components. DIVArchive MIB (Management Information Base) is provided to third party SNMP monitoring applications. The SNMP Agent uses the Windows SNMP Service and has not been ported to the Linux environment.
The DIVArchive Access Gateway provides DIVArchive client authentication and authorization. It can act as an intermediate gateway between DIVArchive components (for example the VACP converter) or third party applications and the DIVArchive Manager, and can restrict that component or application from access to the DIVArchive system.
Oracle DIVAnet is a powerful feature that allows multiple DIVArchive platforms to exchange archive resources and content, whether the archive systems are local to each other or remote.
The Access Gateway is used in DIVAnet installations and is the portal for multiple DIVArchive systems to communicate with each other. See the Oracle DIVAnet Installation, Configuration, and Operations Guide in the Oracle DIVAnet 2.2 documentation library for more information.
The DIVArchive DFM (Drop Folder Monitor) provides automatic monitoring of newly created files in multiple local directories or FTP folders (or combinations thereof). One file, or multiple files, per DIVArchive object are supported. When a new file is identified, DFM issues an archive request automatically to DIVArchive to archive the new file. After the files are successfully archived, they are then automatically deleted from the source. Refer to the Oracle DIVArchive Drop Folder Monitor (DFM) User's Guide in the Oracle DIVArchive 7.5 Additional Features documentation library for more information.
When DFM is used in a Linux environment to monitor an FTP folder, you must configure it as in the following example:
diva
/ifs
/ifs/folder1
A correct DFM configuration with these parameters is:
ftp://diva:password@host_ip/folder1
An incorrect DFM configuration with these parameters is:
ftp://diva:password@host_ip/ifs/folder1
The DIVArchive Actor can integrate with a transcoder engine to provide real time transcoding of material as it is archived or restored, or to create objects from already existing content within the archive. Currently, integration to Bitscream products, and Telestream Flip Factory, and Telestream Vantage are supported. However, multiple transcoders are only supported for Vantage.
Note:
DIVArchive 7.5 ends Oracle support for Telestream Flip Factory. Oracle will provide best efforts to assist customers to transition to other transcoding solutions.Linux-based Actors only support Telestream Vantage for transcoding operations.
DIVArchive assumes a local transcoder address of 127.0.0.1 if a transcoder address is not specified in the transcoder's working directory.
The Promedia Carbon (formerly Rhozet) transcoder is supported in DIVArchive. You select the transcoder type tre from the Configuration Utility to use this transcoder. Both the Name and GUID are supported as options for Presets and Profiles format types.
The following sections describe general Avid connectivity with DIVArchive.
See the Oracle DIVArchive Avid Connectivity User's Guide in the Oracle DIVArchive Additional Features documentation library for more information. Also see Appendix A for DIVArchive options and licensing information.
The Avid DHM (Data Handler Module) interface support in DIVArchive enables finished content to be shared between post-production Avid environments and On Air Video servers. This eliminates the need for tape based content exchange. Timecode based Partial File Restores of content to On Air environments, and finished Avid Sequence submissions to On Air servers are key to the DHM functionality offered within DIVArchive. DHM support is implemented in DIVArchive TMC (Transfer Manager Communicator).
The Avid DET (Dynamically Extensible Transfer) interface support in DIVArchive allows storage expansion of Avid Unity infrastructures and enables editors to move native Avid content in and out of the DIVArchive storage system. Partially edited content stored within DIVArchive through the Avid DET interface can be later restored to Unity, and an editor can then resume editing at the point where they stopped. DIVArchive stores these files in native Avid format. DET support is implemented in DIVArchive TMC (Transfer Manager Communicator).
An interaction between the Avid Archive Manager solution and DIVArchive is implemented in a separate service called AMC (Archive Manager Communicator). AMC handles Archive, Restore, Partial File Restore, and Delete commands from the Avid Archive Manager using DIVArchive to store Avid content in its native MXF OP1 Atom format.
The DIVAprotect option is a utility that collects operational statistics from the DIVArchive system to monitor and maintain the archive's subcomponents (servers, media, drives, tapes, and so on). Analysis of these statistics allows both proactive and reactive maintenance of the DIVArchive system. See the Oracle DIVArchive DIVAprotect User's Guide in the Oracle DIVArchive Additional Features documentation library for more information.
The OTU (Object Transfer Utility) is an optional feature of the Control GUI providing a drag and drop interface to archive and restore content between DIVArchive and a (supported) source or destination server. See Appendix A for DIVArchive options and licensing information.
The following sections describe utilities available in the DIVArchive system
You use the DIVArchive Configuration Utility to configure the DIVArchive system. It connects directly to the DIVArchive database, and can be run on any computer with TCP/IP connectivity to the host running the DIVArchive database.
During configuration and troubleshooting of the library and its tape drives, DIVArchive provides both a command-line interface and GUI utility to send commands directly to the tape library through the Robot Manager. These utilities are not (and must not be) used while the DIVArchive Manager is running because this can adversely affect archive operations. See Appendix A for DIVArchive options and licensing information.
The DIVArchive Backup Service ensures reliability and monitoring of both the Oracle Database and Metadata Database backups.
The DIVArchive Backup Service component is installed as an integral part of the standard DIVArchive system installation. The component is typically installed on the same server as the DIVArchive Manager and Oracle Database. The DIVArchive Backup Service enables configuration of scheduled backups through its configuration file. The DIVArchive Backup Service manages and monitors the entire backup process.
See the Oracle DIVArchive Database User's Guide in the Oracle DIVArchive Core documentation library for more information.
This utility is provided on both Windows and Linux platforms. It assists in obtaining detailed device information such as serial numbers, firmware releases, and SCSI information from tape libraries or tape drives for use in the DIVArchive configuration.
Caution:
This utility must not be used while the DIVArchive Manager is running.This utility is provided on both Windows and Linux platforms and is primarily used with the Robot Manager Client utilities to send manual Eject commands to a tape drive connected to an Actor. This utility also provides advanced tape based operations, such as tape formatting, but should only be used under guidance from Oracle Support.
The Tape Reading Utility is only supported by Windows-based Actors. You must use standard commands, for example, DD and MT when operating in a Linux environment.
This utility allows DIVArchive C++ API commands to be executed using UNIX or DOS based scripts. It is designed to run automated tasks for testing rather than for any intensive uses. There is no Linux-based DIVAscript release.
The DIVArchive RDTU (Recover Damaged Tape Utility) is designed to recover object instances contained on a damaged tape. The utility can recover instances that have valid copies on other available media (that is, internal tape, or a connected disk or array) within a local or remote DIVArchive system.