EVS IP2Archive User Manual
User Manual
Version 1.2 - October 2012
IP2Archive
Archive Digitization & Exploitation
IP2Archive- User Manual- IP2Archive Version 1.2
Copyright
EVS Broadcast Equipment S.A.– Copyright © 2003-2012. All rights reserved.
Disclaimer
The information in this manual is furnished for informational use only and subject to
change without notice. While every effort has been made to ensure that the information
contained in this user manual is accurate, up-to-date and reliable, EVS Broadcast
Equipment cannot be held responsible for inaccuracies or errors that may appear in this
publication.
Improvement Requests
Your comments will help us improve the quality of the user documentation. Do not
hesitate to send improvement requests, or report any error or inaccuracy on this user
manual by e-mail to doc@evs.tv.
Regional Contacts
The address and phone number of the EVS headquarters are usually mentioned in the
Help > About menu in the user interface.
You will find the full list of addresses and phone numbers of local offices either at the end
of this user manual (for manuals on hardware products) or at the following page on the
EVS website: http://www.evs.tv/contacts.
User Manuals on EVS Website
The latest version of the user manual, if any, and other user manuals on EVS products
can be found on the EVS download center, on the following webpage:
http://www.evs.tv/downloadcenter.
I
EVS BroadcastEquipment S.A. - October 2012 Issue 1.2.D
Table of Contents
INTRODUCTION 1
1.
1.1. About IP2Archive 1
1.2. Requirements 1
1.2.1. Hardware Requirements 1
1.2.2. Software Requirements 1
1.2.3. Workflow Requirements 2
1.3. Hardware Setup 2
1.3.1. Overview Hardware Components 2
1.3.2. Description and Technical Specifications 2
1.4. Software Components 5
1.4.1. Overview Software Components 5
1.4.2. Deep Archive Manager 5
1.4.3. Deep Archive Sync 6
1.4.4. MAD Config 7
1.4.5. Communicator 8
1.4.6. Deep Archive Controller 9
1.4.7. Tape Storage Controller 10
1.4.8. File Transfer Daemon 11
1.4.9. IP2Archive Software Interaction 12
1.5. Workflow 14
ARCHIVING AND RESTORING CLIPS 15
2.
2.1. Archive and Restore Bin Hierarchy 15
2.2. Archiving Clips 15
2.2.1. Before Archiving 15
2.2.2. Archiving Source Clips 16
2.2.3. Archiving Subclips 17
2.3. Restoring Clips 17
2.3.1. Before Restoring 17
2.3.2. Fully Restoring Clips 17
2.3.3. Partially Restoring Clips 19
2.3.4. Offline Files 19
2.4. Tracking the Archive and Restore Process 19
2.4.1. Archive Metadata 19
2.4.2. Archive Status 20
2.4.3. Moving Clips From Bin to Bin 21
CONFIGURING IP2ARCHIVE 22
3.
II
IP2Archive- User Manual- IP2Archive Version 1.2
3.1. Configuring the IPDirector API Connection 22
3.2. Creating an Archive and Restore Bin Hierarchy 23
3.3. Creating User Fields 23
3.4. Configuring IP2Archive Applications 24
III
EVS BroadcastEquipment S.A. - October 2012 Issue 1.2.D
IV
IP2Archive- User Manual- IP2Archive Version 1.2
1. Introduction
1.1. About IP2Archive
IP2Archive is an add-on for IPDirector that facilitates the connectivity between IPDirector
and a third party hierarchical storage management system (HSM) and LTO tape library. It
allows easy archiving and (partial) restoring of video clips and makes it possible to keep
track of the archive and restore progress and status (in cache, online, offline, on tape) of
each video clip.
1.2. Requirements
1.2.1. Hardware Requirements
• A nearline storage should be present.
• An XTAccess server containing XTAccess should be present.
1.2.2. Software Requirements
• At least IPDirector 5.99.30 and 6.07.90 (API version).
• In IPDirector XTAccess must be configured for creation of low-resolution files.
• Remote access to the IP2Archive setup for EVS support and maintenance.
1. Introduction 1
EVS BroadcastEquipment S.A. - October 2012 Issue 1.2.D
1.2.3. Workflow Requirements
• The high-resolution and low-resolution video files should be stored on a nearline
storage.
• The low-resolution video files and their metadata XML file must be available.
However, if deleted by accident, they can be restored using the Deep Archive Sync
application.
• The VarID must be unique for a media asset.
• The VarID of the low-resolution and high-resolution video file must be the same.
1.3. Hardware Setup
1.3.1. Overview Hardware Components
By default, the IP2Archive system consists of the following hardware components:
• Oracle database server
• Application server
• Managment server
• Third party network switch (Cisco)
• Third party Hierarchical Storage Management system (HSM): DIVArchive (DIVA)
from Front Porch Digital and XenData from XenData
• Third party LTO tape library (Spectralogic) We support any hardware here because
this should be supported by the HSM system.
The following hardware components can be added for failover and performance:
• Oracle failover database server
• Additional application servers
1.3.2. Description and Technical Specifications
Oracle Database Server
The Oracle database server has redundant power supplies and redundant memory. The
system drives containing the operating system (Linux 5.4 x64) and Oracle software are
configured in RAID 1 (mirror). The data drives are configured in RAID 5.
2 1. Introduction
IP2Archive- User Manual- IP2Archive Version 1.2
Weight Power BTU
16 kg 675
Watts
2260
BTU/h
# power
sockets
2 IBM System
Hardware CPU RAM Hard Disk
X3650 M3
2x Intel
Xeon
E5620
24GB 2x 73GB
SAS
(RAID1) +
6x 300GB
SAS
(RAID5)
Oracle Failover Database Server
The failover database server runs Oracle Data Guard. Oracle Data Guard ensures high
availability, data protection and disaster recovery and synchronizes with the main Oracle
database server. It has redundant power supplies and redundant memory. The system
drives containing the operating system (Linux 5.4 x64) and Oracle software are configured
in RAID 1 (mirror). The data drives are configured in RAID 5.
Weight Power BTU
16 kg 675
Watts
2260
BTU/h
# power
sockets
2 IBM System
Hardware CPU RAM Hard Disk
X3650 M3
2x Intel
Xeon
E5620
24GB 2x 73GB
SAS
(RAID1) +
6x 300GB
SAS
(RAID5)
Application Server
The application server is the central server containing all the applications necessary to run
the solution. It runs Windows 2008 R2x64. The application server runs all background
applications needed for archiving and restoring. It has redundant power supply and two
drives in RAID 1 (mirror). Multiple application servers can be used for performance
reasons.
Weight Power BTU
11 kg 320
Watts
1093
BTU/h
# power
sockets
2 XT Access
Hardware CPU RAM Hard Disk
I7 HP
2x Intel
Xeon
E5620
4GB 2x 250GB
(RAID1)
Management Server
The management server runs Windows 7. It is the server on which the applications are
running used to manage and monitor the IP2Archive system. This server must allow
remote access for EVS support and maintenance purposes.
1. Introduction 3
EVS BroadcastEquipment S.A. - October 2012 Issue 1.2.D
Weight Power BTU
11 kg 320
Watts
1093
BTU/h
# power
sockets
2 XT Access
Hardware CPU RAM Hard Disk
I7 HP
Intel I7
950
4GB 2x 250GB
(RAID1)
Cisco Catalyst Ethernet Switch
Connects the various network devices. Series: 3750-E or 3750-X.
Weight Power BTU # power sockets
10 kg 212 Watts 1023 BTU/h 2
Third Party HSM System
IP2Archive can be used in combination with the following HSM systems:
• Front Porch Digital DIVArchive
• XenData Digital Archive
See the websites of the manufacturers for the functional and technical specifications.
Third Party LTO Tape Library
If EVS may supply the LTO tape library, then it will be a tape library by Spectralogic. If the
LTO tape library is not supplied by EVS, then only the HSM software is supported. The
following Spectralogic LTO tape libraries are supported:
• T50e
• T120
• T200
T50e
• Technical specifications: see www.spectralogic.com.
• Capacity and throughput
Media Max Drives Max Slots/Tapes Max Capacity Max Throughput
LTO-6 4 50 400 TB 7.5 TB/h
LTO-5 4 50 150 TB 4.0 TB/h
T120
• Technical specifications: see www.spectralogic.com.
• Capacity and throughput
4 1. Introduction
Loading...