Archiving conveniently removes completed jobs from the job queue. It is a practical means for keeping the job queue organized by reducing clutter. Its advantage over deleting completed jobs is in preserving all the information needed to re-submit the jobs at a later date. You can also restore an archived job simply to examine job details, such as the render nodes that processed it. This can assist in identifying problems—if unexpected or unsatisfactory results occurred, for example. Archiving can also be part of a facility backup strategy, since the archive represents a job history, in compact form. Note, however, that the job archive contains metadata (job details) only—it does not contain source material or rendered frames.
Use the following procedures to archive a job, restore an archived job, or delete a job from the archive. Jobs can be archived automatically, when the manager has been configured to do so. You can also archive jobs directly from the monitor, as explained here. Note that archiving a job has no effect upon the associated media. The job archive contains job metadata only; that is, it contains the information needed to restart a job, but not the source media.
Jobs are archived (and restored) with their original status intact. Suspending the job before archiving it minimizes the impact on the system if the job is restored later.
The job is archived and removed from the Job list. By default, archived jobs are saved to the Network\Archive folder where the Backburner Manager is installed.
The Job Archive page appears, presenting information for all archived jobs.
To restore or delete a job from the archive:
The Job Archive appears, presenting information for all archived jobs.