Last night we had a crucial server needing a restore, at the same time when
all of our backups run.  When the restore was initiated, it sat in the
queue.  Finally, we just killed the backup jobs and forced the restore.  It
would be nice if, when one backup job ended, the restore had a high enough
priority that it would kick off.  I searched this mailing list and found the
exact same scenario:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/2001-October/006009.html
However, no answer was found in the thread.
Does anyone know of a way to assign a default priority to restores, or some
other way of forcing restores to run in the midst of a queue of backups?

Thanks,

Jesse Gardner