Table of contentsNo headers
In some cases, an archive on a single tape may be accidentally tagged as a multi-tape archive. This results in the application prompt to insert a second tape when there is no need for it.
To fix this problem, use the following environment variables to identify archives that are not tagged correctly, and then to force the archive to register as a single tape:
To identify archives mistakenly tagged as multi-tape:
- In a command shell, type .
- Launch Flame from the shell.
- Open an archive from the Archive menu.
- Examine the feedback in the shell: scroll down past the list of segments and look for “volume=<# of volumes for archive>”.
The number of volumes indicates how many tapes the application registers as being used for the archive. If the number of volumes is more than one and the archive is on a single tape (the line would read “volume=2”) proceed with the following steps.
To force an archive to a specific number of tapes:
- If necessary, quit Flame.
- In command shell, type the following to force the archive to a single tape:
- Relaunch Flame from the same shell and proceed to restore the archive from tape.
Mistakenly changing the number of tapes for an archive results in corrupted clips. It can happen, for example, if the archive is spread over two tapes and you force it to one tape. However, the source material on the tape is not corrupted. If you have corrupted clips, try starting another session of Flame without using the DL_ARCH_FORCED_NB_VOLUMES environment variable.