On Tuesday 11 September 2007 19:30, David Boyes wrote: > > Item 1: Implement a Copy job type that will copy the > > job data from one device to another, for example, > > copy from a fiel Tape to a real Tape. > > This function already exists in Bacula. Define a nextpool resource in > the disk pool definition and define a migration job, and schedule it as > normal. The migration code offers a number of selection choices; it does > not yet have automatic triggers -- that's still outstanding -- but the > rest of the function you describe is already there and working.
If I am not mistaken, the problem is that the current code deletes the original job so it is a migrate rather than a copy. Though it may as you indicate be a partial solution, I will implement a Copy job very similar to Migrate that will work more or less identical to the Migrate, except for two things: 1. the original job will not be purged. 2. the new job will be very specially marked a Copy job so that it can be clearly distinguished from the original Backup job. This will allow users to make copies -- the step after that will be to provide some means for the users to be able to indicate they want to use the Copy Volumes during the restore. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
