3 Hardware and Software Requirements

This chapter describes the minimum hardware and software requirements to install and operate the DIVArchive 7.3 software. Refer to "General Storage Requirements" for detailed disk configuration information.

DIVArchive Architecture

A DIVArchive system uses a combination of software modules which can run on a single computer, or can be distributed across different systems.

The main DIVArchive components are as follows:

Oracle DIVArchive Manager

The core component of the archive also hosting the archive system database.

DIVArchive Manager Cluster

Based on Microsoft Cluster.

Oracle DIVArchive Actor

Responsible for all data transfers (Archive, Restore, Copy, Repack, and so on).

DIVArchive Actor and Manager (Single Computer)

Systems running both Actor and Manager functions on a single computer. You should try to avoid this configuration for performance reasons. This is only usable for entry level configurations.

DIVArchive Actor and Transcoder (Single Computer)

Systems running both Actor and Transcoder functions on a single computer.

Oracle DIVAnet (Access Gateway or DIVAnet 2.0)

Used in DIVAnet configuration for unified access. DIVAnet 2.0 is not a drop-in replacement for the legacy Access Gateway.

Oracle DIVAdirector

A web-based application to search and browse the archive.

DIVArchive Control GUI and Configuration GUI

Used for configuring, monitoring and managing the DIVArchive system.

The following figure represents a DIVArchive configuration with the main DIVArchive software components installed on different servers. The DIVArchive Access Gateway (legacy DIVAnet) used to access multiple DIVArchive systems is not represented and is generally installed on a dedicated server.

Typical DIVArchive Configuration

System Component Interconnectivity

On the data path, a DIVArchive solution is connected on the storage side to the tape library and (or) the shared disks. On the source and destination side it is connected to the video servers, NLE, or file servers.

Storage Connection

Storage Area Networks (SAN), Network Attached Storage (NAS) or Direct Attached technologies can be used. Different types of interfaces are required on the servers to support the different types of storage devices as follows:

  • Fiber Channel Host Based Adapter (HBA) for SAN

  • SCSI Bus or HBA for Direct Attach

  • 10 Gigabit Ethernet (GbE) for NAS

Video Server Connections

Connections to video servers generally uses standard GbE or 10 GbE LAN technologies. Grass Valley legacy profile video servers come with two types of interfaces

  • Universal Interface Module (UIM) uses GbE

  • The legacy profile with direct Fiber attachment is now End of Life for Grass Valley and no longer supported by Oracle.

Intel and Microsoft Windows

Oracle can deliver x86 architecture servers matching or exceeding the recommendations provided in the following sections (except the Windows license to be purchased). Partners can also purchase servers from other vendors if the minimum requirements are met. Oracle does not qualify or recommend specific models from other vendors.

Caution:

The operating system installed on all computers must be installed in the English language. Oracle cannot support DIVArchive computers that have the operating system installed in other languages.

DIVArchive Operating System Compatibility

When upgrading your DIVArchive installation to release 7.3, use the following table to confirm that you have the proper operating system installed for each computer.

Component DIVArchive Release Operating System Compatibility (for upgrades only)
Manager 7.3 Windows Server 2008 R2 (64-bit)

Windows Server 2012 R2 (64-bit)
Manager 7.2 Windows Server 2008 R2 (64-bit)

Windows Server 2012 R2 (64-bit)
Actor 7.3 Windows Server 2008 R2 (64-bit only)

Windows Server 2012 R2 (64-bit only)
Actor 7.2 Windows Server 2008 R2 (64-bit)

Windows Server 2012 R2 (64-bit)

Windows Server 2008 Standard (32-bit)

Windows Server 2003 (32-bit)
DIVAnet Legacy Windows Server 2008 R2 (64-bit)

Windows Server 2012 R2 (64-bit)
DIVAnet 2.0 Windows Server 2008 R2 (64-bit)

Windows 2012 R2 (64-bit)
DIVAnet Clients 64-bit Windows 7 and later is required.

DIVArchive Manager

The following server platform is the minimum requirement recommended for the installation of the DIVArchive Manager software:

  • Rack mount chassis

  • One Xeon E5-2420 CPU (six cores, 1.9 GHz)

  • 16 GB RAM

  • Two 300 GB HDD 10,000 RPM (configured in RAID 1) system disks

    Note:

    If you use DIVArchive to archive complex objects like DPX, it is advisable to ask for a specific recommendation based on the estimated traffic (in terms of size and number of objects to be archived per day). In general, if complex objects need to be archived, Oracle recommends using a minimum of two 900 GB HDD with 10,000 RPM. This recommendation is also valid for the Backup Manager or an Actor if an Actor server is used for the Backup Manager.

  • Redundant power supply and fans

  • Two onboard GbE interfaces (copper RJ45 interfaces)

  • One Fiber Channel Host Bus Adapter (HBA) for tape library control

    Note:

    A Fiber Channel HBA is not required with SONY Petasite libraries (controlled through the PCS software and a network API) or with Oracle StorageTek libraries if the ACSLS software is used in the configuration.

  • Windows Server 2012 R2

Important: If ACSLS virtual libraries are used, an HBA will be required (consult with Oracle for more information).

DIVArchive Manager Cluster

The following server platform (two identical servers) is the minimum requirement recommended for the installation of the DIVArchive Manager software in a cluster environment:

  • Rack mount chassis

  • One Xeon E5-2420 CPU (six cores, 1.9 GHz)

  • 16 GB RAM

  • Two 300 GB HDD 10,000 RPM (configured in RAID 1) system disks

    Note:

    If you use DIVArchive to archive complex objects like DPX, it is advisable to ask for a specific recommendation based on the estimated traffic (in terms of size and number of objects to be archived per day). In general, if complex objects need to be archived, Oracle recommends using a minimum of two 900 GB HDD with 10,000 RPM. This recommendation is also valid for the Backup Manager or an Actor if an Actor server is used for the Backup Manager.

  • Redundant power supply and fans

  • Two onboard GbE interfaces (copper RJ45 interfaces)

  • One SAS or FC HBA (for the shared disk bay connection)

    Note:

    A shared disk bay with dual RAID controller (SAS or FC Interface) and seven 300 GB SAS disks connected to both servers to accommodate the Oracle database.

  • One Fiber Channel HBA for tape library control

    Note:

    A Fiber Channel HBA is not required with SONY Petasite libraries (controlled through the PCS software and a network API) or with Oracle StorageTek libraries if the ACSLS software is used in the configuration.

  • Windows Server 2012 R2

DIVArchive Actor

The following is the minimum server configuration recommended for the installation of the DIVArchive Actor software:

  • Rack mount chassis

  • One Xeon E5-2420 CPU (six cores, 1.9 GHz)

  • 16 GB RAM

  • Two 300 GB HDD 10,000 RPM (configured in RAID 1) system disks

  • RAID5 disk space for cache, at least four 1TB disks

  • Optional RAID5 disk space for Nearline storage (DIVAgrid Architecture)

    Note:

    The DIVAgrid Architecture consists of aggregating direct-attached disks from multiple DIVArchive Actors into one single DIVArchive Array. The DIVArchive Manager distributes content it needs to store on this array across the different Actors composing the array. This provides a cost effective, high performance solution for Nearline disk storage and is ideal in workflows requiring temporary disk storage to enable the creation of multiple object instances and transcoding.

  • Redundant power supply and fans

  • Two onboard GbE interfaces (copper RJ45 interfaces)

  • One 10 GbE interface (optional)

  • One Fiber Channel HBA for the connection to an external shared disk (optional)

  • One Fiber Channel HBA for the connection to the tape drives

  • Windows Server 2012 R2

DIVArchive Actor and Manager (Single Computer)

The following is the minimum server configuration recommended for the installation of the DIVArchive Actor and DIVArchive Manager software on a single computer. This configuration should be limited to entry level systems for performances reasons:

  • Rack mount chassis

  • One Xeon E5-2420 CPU (six cores, 1.9 GHz)

  • 16 GB RAM

  • Two 300 GB HDD 10,000 RPM (configured in RAID 1) system disks

    Note:

    If you use DIVArchive to archive complex objects like DPX, it is advisable to ask for a specific recommendation based on the estimated traffic (in terms of size and number of objects to be archived per day). In general, if complex objects need to be archived, Oracle recommends using a minimum of two 900 GB HDD with 10,000 RPM. This recommendation is also valid for the Backup Manager or an Actor if an Actor server is used for the Backup Manager.

  • RAID5 disk space for cache - at least four 1 TB disks

  • Optional RAID5 disk space for Nearline storage (DIVAgrid Architecture)

    Note:

    The DIVAgrid Architecture consists of aggregating direct-attached disks from multiple DIVArchive Actors into one single DIVArchive Array. The DIVArchive Manager distributes content it needs to store on this array across the different Actors composing the array. This provides a cost effective, high performance solution for Nearline disk storage and is ideal in workflows requiring temporary disk storage to enable the creation of multiple object instances and transcoding.

  • Redundant power supply and fans

  • Two GbE interfaces

  • One 10 GbE interface (optional)

  • One Fiber Channel HBA for the connection to an external shared disk (optional)

  • One Fiber Channel HBA for the connection to the tape drives

    Note:

    An additional port maybe required for the tape library control.

  • Windows Server 2012 R2

DIVArchive Actor and Transcoder (Single Computer)

The following is the minimum server configuration recommended for the installation of the DIVArchive Actor software and Transcoder on a single computer:

  • Rack mount chassis

  • Two Xeon E5-2440 CPUs (six cores, 2.4 GHz, 15 MB cache)

  • 16 GB RAM

  • Two 300 GB HDD 10,000 (configured in RAID 1) system disks

  • RAID5 disk space for cache and transcoding, at least five 1 TB disks

    Note:

    The local disk is used as a temporary working disk for the transcoder. The recommended size is equal to MaxClipSize x 4. For example, 2 hours in D10 format requires 50 GB of storage per clip. Therefore, the transcoder local disk size must be 200 GB. A separate storage disk space is recommended for the archiving of the clips before or after transcoding.

  • Optional RAID5 disk space for Nearline Storage (DIVAgrid Architecture)

    Note:

    The DIVAgrid Architecture consists of aggregating direct-attached disks from multiple DIVArchive Actors into one single DIVArchive Array. The DIVArchive Manager distributes content it needs to store on this array across the different Actors composing the array. This provides a cost effective, high performance solution for Nearline disk storage and is ideal in workflows requiring temporary disk storage to enable the creation of multiple object instances and transcoding.

  • Redundant power supply and fans

  • Two onboard Gigabit Ethernet interfaces

  • One 10 GbE interface (optional)

  • One Fiber Channel HBA for the connection to an external shared disk (optional)

  • One Fiber Channel HBA for the connection to the tape drives

  • Windows Server 2012 R2

DIVAnet (DIVArchive Access Gateway)

The DIVArchive Access Gateway is used in a DIVAnet configuration to provide a consolidated view of a distributed archive system. The following is the minimum server configuration recommended for the installation of the DIVArchive Access Gateway (legacy DIVAnet):

  • Rack mount chassis

  • One Xeon E5-2420 CPU (six cores, 1.9 GHz)

  • 16 GB RAM

  • Two 300 GB HDD 10,000 (configured in RAID 1) system disks

  • One 10 GbE interfaces (optional)

  • Windows Server 2012 R2

Oracle DIVAdirector

DIVAdirector is Oracle's archive content management application providing a user friendly web-based window into assets stored in the DIVArchive system. DIVAdirector can play proxy versions of the archived clips, and can store the proxy files on local disks, SAN, or NAS disk storage. The following is the minimum server configuration recommended for the installation of DIVAdirector:

  • Rack mount chassis

  • Two Xeon E5-2440 CPUs (six cores, 2.4 GHz, 15 MB cache)

  • 16 GB RAM

  • Two 300 GB HDD (configured in RAID 1) system disks

  • Redundant power supply and fans

  • RAID5 disk space proxy storage five 3 TB (if stored locally)

  • Two onboard GbE interfaces

  • One 10 GbE interface (optional)

  • Fiber Channel HBA for the connection to an external shared disk for proxy storage (optional)

  • Windows Server 2012 R2

General Storage Requirements

The following table describes the main storage characteristics of the various components:

Server CPU System Disks Cache and Defragment Disks Data Disks
Manager Cluster 1 RAID1 No No
Manager 1 RAID1 No No
Actor 1 RAID1 RAID5 Nearline (optional)
Actor and Manager 1 RAID1 RAID5 Nearline (optional)
Actor and Transcoder 2 RAID1 RAID5 Transcoding area plus optional Nearline disk.
Access Gateway 1 RAID1 No No
DIVAdirector 2 RAID1 No RAID5 if no proxy external storage is attached.

DIVArchive Manager Partitions

The following are the minimum partition sizes for the Manager computer. These minimum sizes are also valid for Actor and Manager Backup configuration.

300 GB RAID1 requires the following:

  • Primary Partition: 60 GB minimum for Windows operating system

  • Extended Partition: 285 GB minimum for the database, and including the following logical drives for backup:

    • E: 20 GB minimum

      • 8KB cluster size

    • F: 5 GB (exact size, not larger)

      • 4KB cluster size

    • G: 100 GB of free space if not used on another volume

    • H: 130 GB minimum

      • 64KB cluster size

DIVArchive Actor Partitions with Database Backup Synchronization

The following partition sizes are the minimum recommended sizes for the Actor computer and includes database backup synchronization.

300 GB RAID1 requires the following:

  • Primary Partition: 60 GB minimum for Windows operating system

  • H: 130 GB (Primary Partition)

  • G: 155 GB of free disk space if not used on another volume

RAID5 disk space is required for the following:

  • K: Cache space

  • S: Nearline storage space

  • X: Transcoding area if transcoder is hosted on the Actor computer

DIVArchive Actor Partitions without Database Backup Synchronization

The following partition sizes are the minimum recommended sizes for the Actor computer without database backup synchronization:

300 GB RAID1 requires the following:

  • Primary Partition: 60 GB minimum for Windows operating system

  • G: 255 GB of free disk space if not used on another volume

RAID5 disk space is required for the following:

  • K: Cache space

  • S: Nearline storage space

  • X: Transcoding area if transcoder is hosted on the Actor computer