Chapter 3 Using Your Tape Drive
FTP File Transfer Troubleshooting
SDLT 600A Product Manual
44
drive), these modifications will not be saved in the eMAM when a user
ejects the tape or disconnects its FTP client.
MXF Troubleshooting
3
Two MXF Files with Same UMID
3
It is possible that two MXF files have the same UMID when the MXF
header metadata file is reingested into the SDLT 600A. On a partial
restore operation, the FTP server searches for the file according to the
UMID. This way it can find the good file and bad file if there are two (the
header metadatafile).
Cannot Display MXF Properties
3
When storing MXF files, MXF metadata are extracted. MXF files are
converted to regular files if MXF metadata cannot be retrieved (but are
not renamed).
This solves issues such as the following:
• Creating a partial file without MXF metadata
• Restarting the transfer of an MXF file after an abort
• Listing MXF information (SITE MXFNFO) from aborted MXF files
MXF Interoperability with Avid Files
3
Storing Avid native files may cause an error message (
bad mxf file format
)
if not compliant to the MXF standard.
Network Drive Limitation
3
When the SDLT 600A is mapped as a network drive using ftp://root@Ip,
Windows XP/2000 opens two connections. However, it closes only one
connection when the File Explorer window is closed. After three
connections, there are three root users (maximum allowed) pending on
the FTP server side. To avoid this issue, the network drive must be
mapped using ftp://root:password@Ip. The drawback is that the
password can be read from the network drive properties.
