Grass Valley Aurora Browse v.7.0 Installation - Manual (Page 126)

126 Aurora Browse Installation and Configuration Guide April 6, 2010
Chapter 5 Configuring the system
are restored using the original name (from archive). The DIVA MDI does,
however, allow a user specified name for a partial restore.
• DIVA has no fixed limit for concurrent transfers.
• If archiving from a Profile XP standalone, take the concurrent transfer limit into
consideration. 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 basis.
• 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.
• The MDI will use whatever priority the user chooses.
• The source name must be the same as the host name specified in the Transfer
Server, not the actual machine. Under that name, specify the host name or IP
address of the actual machine in the IP Address field.
• If the DIVA server is rebooted, the DIVA MDI service must be restarted. Refer to
“Accessing services” on page 80 .
FlashNet preparations
To use Flashnet with the Aurora Browse system, make sure that you have installed the
following pre-requisites on the Flashnet MDI server.
• Flashnet Client software (provided by SGL)
• MS Message Queuing, the Common subcomponent (part of the Windows Server
2003 CD)
Check the following on the Flashnet server:
1. Login to the machine.
2. Verify that you can FTP from the FlashNet server to the high-res storage machine.
If archiving from K2 storage or AuroraShare NAS, verify that you can FTP from
the FlashNet server to the K2 storage or AuroraShare NAS on Control FTP and
login as user vmfmovie.