This chapter addresses some frequently asked questions received by customers.
The exported XML and FFM files, when generated, can be imported into the release of DIVArchive that they were exported from, and later releases of DIVArchive. DIVArchive enables more than one set of tapes (spanned or not) to be exported to and imported from a single file.
Exported metadata from the DIVArchive 7.6 export function cannot be imported into DIVArchive releases earlier than release 7.0. However, exported metadata created from releases of DIVArchive before 7.6 can be imported into the DIVArchive 7.6 system.
The Media Type ID is a proprietary DIVArchive identifier that represents the type of tape media being exported. DIVArchive exports a mediaTypeId field, which corresponds to the Id column in the Tape Properties table under the Tapes tab in the DIVArchive Configuration Utility. You may need to execute a Synchronize DB call to update the mediaTypeId, and (or) update your hardware to be compatible with a newly imported tape. You should ensure that the block size and total size of the mediaType in the source DIVArchive system matches the mediaType definition in the destination. This becomes especially important if the tape is ever repacked.
The markedAsDeleted is an internal attribute and is not exported or imported through the Export/Import Utility. In addition, the state of checksum verification (verified, partially verified, and so on) is not exported. Linked objects and link information is not exported. Information regarding the request that created each object is not exported - newly imported objects are not associated with a DIVArchive request.