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

September 22, 2006 Aurora Browse Installation and Configuration Guide 93
Archive stage
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 or Open SAN system, 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.
• 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 machine with high-res online material.
• If the DIVA server is rebooted, the Thomson DIVA MDI service must be restarted.
Refer to “Accessing services” on page 50 .
Network connectivity - all archive types
To test network connectivity, ping all machines from all machines.
If archiving to/from K2 Storage or AuroraShare NAS, ping these machines on the
GigaBit network:
• MediaFrame server
• Archive MDI host
• News MDI host
• The machine hosting the Aurora FTP service
• Archive machine
• The K2 storage or AuroraShare NAS system
If archiving to/from Profile XP/Open SAN systems, ping these machines on the
GigaBit network:
• MediaFrame server
• Archive MDI host
• Profile MDI host (MDI server)
• Archive machine
• All Profile XP or Open SAN systems from/to which media is archived/restored
If archiving to/from Profile XP/Open SAN systems, also use Fibre Channel IP
addresses and ping these machines:
• Archive server