You can archive and restore material from the command line, using flame_archive, found in/usr/discreet/io/bin.
A possible workflow you might try is to archive a project daily, and then restore a specific clip, as required.
Archive the project:
./flame_archive -f -F /usr/tmp/daily_archive
./flame_archive -l
./flame_archive -a -P ProjectOne -F /usr/tmp/daily_archive
Once the process completes, you have archived the whole project in the daily_archive.
Restore a single clip from the daily_archive:
./flame_archive -l -F /usr/tmp/daily_archive
./flame_archive -r -F /usr/tmp/daily_archive -S '/daily_archive/Archive Session - 2014/12/01 14:54:24/projectOne/Workspace (projectOne)/Libraries/Default Library/newNoise' -E /projects/projectOne/988110ac_547cc27f_0005859a/988110ac_547cc27f_0005859c/988110ac_547cc283_000312c0
You an also pass a text file containing the clips to restore to flame_archive. That text file lists one clip to restore on each line.
The above approach is fine for a manual restore, but for a programmatic approach, try using: ./flame_archive -l -x, where -x outputs the archive contents in XML.
Some additional notes:
USAGE: flame_archive <operation> <modifiers> <options>
flame_archive -h | --help flame_archive -a [-N] [-k] [-p] [-y] [-g] -E <WIRETAP_PATH_SOURCE> -F <PATH_TO_FILE> flame_archive -e [-E <WIRETAP_PATH_SOURCE>] [-F <PATH_TO_FILE] [-m All|MetaData|Video|Audio] flame_archive -f -F <PATH_TO_FILE> [-n <NAME>] [-t <COMMENT>] [-i <SIZE_IN_GB] flame_archive -l [-F <PATH_TO_FILE> [-x] [-S <PATH_IN_ARCHIVE>]] [-E <WIRETAP_PATH>] flame_archive -r -F <PATH_TO_FILE> -S <PATH_TO_ENTRY_IN_ARCHIVE> [-E <TARGET_WIRETAP_PATH>]
Examples:
flame_archive -f -F /usr/tmp/archive1
flame_archive -a -E /projects/TestProject/a38310ac_53a82f6b_0006a1c1/a38310ac_53a82f6b_0006a1c3/a38310ac_53a82f77_000079d7/a38310ac_53a82ff6_000d6100 -F /tmp/arch1
flame_archive -a -P pj1 -F /tmp/arch1
flame_archive -r -F /tmp/arch1 -S '/Archive Session - 2014/03/12 23:43:40/prj1'
flame_archive -l
flame_archive -l -F /usr/tmp/arch1 -x
flame_archive -l -P project1 -E /wksp/Libraries/MyLib/MyFolder
flame_archive -e -P project1
The different flame_archive operation modes:
Archive clips to a file archive. This requires the Wiretap path to the material to archive, and the file path to the archive file. The archive file must already exist, either created from within Flame, or created using flame_archive. The archiving process is recursive: there are no provisions made for excluding material from the archive. If you need to archive specific clips, you must run flame_archive for each individual clip. -F specifies the file to use, -E the material to archive, as a Wiretap path (without a trailing '/').
Estimate the space required to store or restore material to and from an archive. The estimate is recursive.
Format an archive file, default size being 1 GB (1024 MB).
Lists contents of a project or of an archive, depending on the target.
Restore clips from a file archive. Requires the source file archive from which to restore, and the path of the entry to restore. Do not specify a Wiretap path target when restoring a project: flame_archive restores a project so that it is accessible from Flame as a regular project.
Optional modifiers to use with the different flame_archive modes:
With any option: