Diva preparations – Grass Valley Aurora Transfer v.6.0b User Manual

Page 38

Advertising
background image

38

Aurora Transfer Instruction Manual

September 11, 2006

Chapter 3 Configuring the Aurora Transfer System

• 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 a AuroraShare NAS, verify that you can FTP from the DIVA

server to the AuroraShare NAS on Gigabit Ethernet and login as user vmfmovie.

Consider the following when preparing to integrate DIVA with Aurora Transfer:

• 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 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.

Advertising
This manual is related to the following products: