On 02/09/11 12:27, Jeremiah D. Jester wrote:
> Is it possible to 'pause' a job and then resume at a later time?
Well ...... *sort of*.
If the job is waiting on a media request, you can hold off on changing
the media more or less as long as you want, within reason. (Though if
you have your job "on hold" for a long time, it may cause other later
jobs to fail - if you nave duplicate jobs disallowed, for example.) And
as long as the same Director session is running and the client hasn't
disconnected, you could swap the media later and let the job resume
execution.
But "snapshot" the job, suspend it, go away and do other stuff, restart
any of the Bacula daemons involved, and come back at another time and
pick up where you left off? No. Once a given instance of a job has
*stopped* and its buffers are no longer in memory, it's either complete
or it's failed, kaput, gone, adios, finito Benito. "It is no more. It
has ceased to be! It's expired and gone to meet its maker! It's a
stiff! Bereft of life, it rests in peace! ..."
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
