Grass Valley Aurora Browse v.6.0b Installation - Manual (Page 92)

92 Aurora Browse Installation and Configuration Guide September 22, 2006
Chapter 3 Configuring the system
4. Make sure the “FlashNet Socket Listener” and “FlashNet Automation” services are
up and running.
5. Use the FlashNet “Jukebox” application to test that a drive can be successfully
accessed from FlashNet. Refer to “User Guide for FlashNet running on Windows
NT and Windows 2000 platforms”.
Consider the following when preparing to integrate FlashNet with Aurora Browse:
• The FlashNet MDI does not take any user specified name for a full restore. The
clips are restored using the original clip name (from archive). The FlashNet MDI
does, however, allow a user specified name for a partial restore.
• If archiving from a Profile XP or Open SAN system, take the concurrent transfer
limit into consideration. FlashNet’s setting for concurrent transfers applies
globally to all source/destination pairs. There is no setting on a server-by-server
basis. To make the setting for “maximum number of concurrent transfers”, you use
a file named C:\.dtool_env where you can specify “API_MAX_BACKUPS” and
“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.
• The FlashNet server installation must have the GENERATE UNIQUE NAME
entry set to FALSE. Use Configurator.exe for FlashNet server configuration.
• 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 machine with the high-res
online material:
• If archiving from a Profile XP or Open SAN, verify that you can FTP from the
DIVA server to the Profile on the Ethernet IP address and login as user movie.
• If archiving from K2 storage or AuroraShare NAS, verify that you can FTP from
the DIVA server to the K2 storage or AuroraShare NAS on Gigabit Ethernet and
login as user vmfmovie.
Consider the following when preparing to integrate DIVA with Aurora Browse:
• The DIVA MDI does not take any user specified name for a full restore. The clips