Diva preparations – Grass Valley NewsBrowse Desktop Browsing System Installation v.2.7 User Manual
Page 102

102
NewsBrowse Installation and Configuration Guide
December 16, 2004
Chapter 3 Configuring the NewsBrowse System
“API_MAX_RESTORES”. The following is an example for an eight drive system:
API_MAX_BACKUPS
2
API_MAX_RESTORES
4
This example specifies that two concurrent jobs could be used for automation
ingest into the archive, four concurrent jobs could be allowed for automation
restore of archives, leaving two drives spare for emergency use or another function.
• The FlashNet MDI uses a file cache to support asset functionality. As the FlashNet
device does not have any support for file system updates, the FlashNet MDI
assumes that the MDI is the only gateway to the entire FlashNet file system. Any
changes made outside the scope of the MDI will not be reflected in MDI
immediately.
• Renaming of an asset is not supported in FlashNet.
• A restore operation always defaults to highest “Time Critical” priority and archive
operation defaults to “normal” priority.
DIVA preparations
Check the following on the machine which runs DIVA software:
1. Login to the machine.
2. Verify that you can FTP from the DIVA server to the Profile on the Ethernet IP
address and login as user movie.
Consider the following when preparing to integrate DIVA with NewsBrowse:
• The DIVA MDI does not take any user specified name for the restore. The clips are
restored using the original name (from archive).
• DIVA has no fixed limit for concurrent transfers, so it can be configured to
consume as few or as many streams provided by the Profile XP systems on the
Open SAN.
• DIVA’s setting for concurrent transfers applies to specific source/destination pairs.
With the configuration utility/tool you can specify the concurrency limit on a
server-by-server (Profile-by-Profile) basis. A single Profile XP system provides a
maximum of four streams for concurrent transfers.
• The DIVA MDI makes an the assumption that the MDI is the only gateway to the
entire DIVA file system. Any changes made outside the scope of the MDI will not
be reflected in MDI immediately.
• Renaming of an asset is not supported in DIVA.
• A restore operation always defaults to highest “Time Critical” priority and an
archive operation defaults to “normal” priority.
• The source name specified in the DIVA configuration utility must be the same as
the host table name of the Profile XP system.
• If the DIVA server is rebooted, the Thomson DIVA MDI service must be restarted.
Refer to
“Accessing NewsBrowse services” on page 46
.