Grass Valley Aurora Browse v.6.5 Installation - Manual (Page 87)

November 1, 2008 Aurora Browse Installation and Configuration Guide 87
Verify archive preparations
4. Fill in the following information needed:
a. Source name – any name (must correspond to the name specified in Transfer
Server)
b. IP Address – can be IP address or host name accessible from DIVA archive
server (must be a reachable News, K2, M-Series or Profile server registered as
the Transfer Server in the News, K2, M-Series or Profile MDI)
c. Source Type – choose the appropriate type of server. News FTP and K2 use
FTP_STANDARD and M-Series, and Profile use PDR
d. Production System – choose the correct system
e. Site – choose the site
f. Connect Options – additional options for connection to source server, that is, a
different login name. For example, for News FTP with a user name vmfmovie ,
put in -login vmfmovie ; for K2 put in -login movie
g. Root Path – If you’re archiving from a News server, leave this blank. If you’re
archiving from a K2, M-Series, or Profile server, type in the root path, for
example
/explodedFile/V:/default
h. Max Throughput (Mb/s) – max throughput
i. Max Accesses – total number of access possible (default 10 )
j. Max Read Accesses – total number of access for reading (default 10 )
k. Max Write Accesses – total number of access for writing (default 10 )
5. Restart the DIVArchive Manager Service to enable the new settings.
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
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 Thomson DIVA MDI service must be restarted.
Refer to “Accessing services” on page 48 .