This chapter describes the general concepts of a DIVArchive system 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 installation of DIVArchive varies from site to site, so the exact configuration of your specific DIVArchive platform is not covered in this guide. Refer to your System Administrator and your DIVArchive Site Configuration 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 of DIVArchive at your site. It is a complete record of the configuration of the DIVArchive sub-systems, third party interfaces, site details and contacts, user names and passwords, and remote access codes.
Your Site Configuration is referenced at various points in this guide. Refer to your Site Configuration where applicable.
This section describes new and enhanced features and functionality in Oracle DIVArchive 7.5. Refer to the Oracle DIVArchive Installation and Configuration Guide in the Oracle DIVArchive Core documentation library for specific information on each feature and enhancement. See Appendix A for Oracle DIVArchive options and licensing information.
This section describes general DIVArchive new and enhanced features and functionality.
Oracle Linux 7 x86_64 and later is now supported for all core DIVArchive components.
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.
Linux-based Actors only support Vantage transcoding operations.
When restoring the same file to the same destination twice in parallel, the behavior on Windows and Linux is different. On Windows, the first restore (they cannot arrive exactly at the same time) will lock the file so that the second one will terminate. On Linux, there is no such lock at the file system level. Both restores are executed at the same time, and both will write to the same file. The content of the resultant file is not predictable.
See the Oracle DIVArchive Installation and Configuration Guide, and the Oracle DIVArchive Supported Environments Guide in the Oracle DIVArchive 7.5 Core documentation library for information about running Windows services, Linux services, transcoders, and certain limitations when operating in the Linux environment.
UNC paths are supported for SMB Source/Destinations and managed disks if the UNC path is mounted directly on the Windows Actors.
Oracle DIVArchive Actors in the Linux operating system do not support UNC paths for CIFS sources and destinations. However, you can define a local path to a mounted SMB share.
Because Linux-based Actors cannot use CIFS, a new path is required to enable Linux-based Actors to transfer content to and from SMB network shares (transcoder cache). 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 if you are switching from a Windows Actor to a Linux Actor for use with a pre-existing Vantage transcoder configuration. The CIFS path will only be used by Vantage to access the cache. The only thing that changes is adding the actorPath to the working directory of the transcoder. The actorPath represents the path the Linux Actor will use to transfer content to and from the SMB network share on a Linux system.
Caution:
The order of theactor, actorPath, and transcoder settings is important. The order of the parameters must be actor, followed by actorPath, and then transcoder.Example:
[actor:actor1,actorPath:/tmp/vantagecache,transcoder:100.100.100.100],cifs://Administrator:password@\\100.100.100.100\VantageStore
DIVArchive 7.5 supports configuring Oracle Storage Cloud for use.
Any disks added to a cloud array are considered cloud disks.
See Oracle Storage Cloud Transfers for detailed information on using Storage Cloud accounts with DIVArchive.
Visit http://docs.oracle.com/cd/E60880_01/VLPFN/whatis.htm#BABDADAE for information on Oracle Storage Cloud storage accounts.
The DIVArchive Control GUI includes the following enhancements:
A new column is available in the Disks View. The column titled Consumed Size represents the space in kilobytes consumed by content on disk. This 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 named Cloud Storage Class.
DIVArchive 7.5 Local Delete allows delayed delete mode to perform site deletes that are not based on remaining disk space on an array. See the Oracle DIVArchive 7.5 Local Delete User's Guide in the Oracle DIVArchive 7.5 Additional Features documentation library for detailed information.
LTO7 drives are now supported.
DIVArchive 7.5 enables specifying a QOS value as a Request Option.
You can now specify the Additional Service Delete on Source in Archive requests, and the Additional Services Do not overwrite, Do not check existence, and Delete and Write services in Restore requests as Request Options.
DIVArchive operations now include the total tape size for some specific tape drives (Oracle T10K and IBM LTO drives).
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 (no cross-generation compatibility), and there must be at least one Gen1 drive in a library containing Gen1 cartridges.
DataExpedition release 1.17 is supported.
JDBC Thin Driver enables use of the Oracle Service Name instead of the Oracle SID setting.
MPEG2 Transport Stream enhancements for Oracle DIVArchive Partial File Restore operations. This feature now supports HD MPEG video essences with AES3 audio tracks.
Promedia Carbon (formerly Rhozet) support. 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 supported by AXF only. When Legacy format is in use, DIVArchive will report an error if an empty file or folder is discovered during the transfer (previous behavior is no longer supported). Objects containing empty files or folders archived to Legacy format will succeed, but empty files and folders are ignored. Users who are accustomed to archiving data containing empty files and folders to Legacy media are directed to switch to AXF media.
Empty files are now 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.
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 operation's type attribute can now contain the letter S to represent a symbolic link.
Long path names are 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).
The Control GUI now displays the fully qualified path to a file, and the fully qualified path to an empty folder in the Components list in the Properties tab of the Object Properties dialog box.
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. The new Refresh button refreshes the entire Job Properties dialog box.
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.
Oracle DIVArchive Storage Plan Manager has been ported to use 64-bit operating systems.
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 the Oracle DIVArchive 7.5 Storage Plan Manager User's Guide in the Oracle DIVArchive 7.5 Additional Features documentation library for details.
An Operator and Advanced Operator profile are present in the Control GUI profiles. The difference between the two profiles is Insert and Eject tape commands are included in the Advanced Operator profile. During normal operation you use the Operator profile unless you are inserting or ejecting a tape.
Changes have been made to the DIVArchive 7.5 configuration files that coincide with the new and enhanced functionality. This section gives 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. The default setting is disabled, allowing the archiving of empty files.
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 ServiceName takes precedence over the Oracle SID.
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.
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.
The new DIVArchive Web Services API is called Oracle DIVA Enterprise Connect. This release replaces previous WS API releases. See the Oracle DIVA Enterprise Connect documentation library for details installation, configuration, and operations information on the new release