On Thursday 17 November 2005 22:30, David Boyes wrote: > > > Item 1: "spool-only" backup > > > Origin: Frank Volf ([EMAIL PROTECTED]) > > > Date: 17 november 2005 > > > Status: > > This is another variation of the pool-to-pool migration idea. If a disk > pool were available as the first pool in the migratino chain, then this > feature request would be satisfied (assuming sufficient space was available > in the disk pool, which would be the case for spooling as well).
The only problem for the moment (unless I am mistaken) is that the SD does not release or send an OK status to the FD until the job terminates, which means the attributes have been sent to the Director. There are several things that can possibly be done: 1. As soon as the SD has all the info from the FD, it could "release" it. In the original implementation, the Dir relied only on the FD to say that all was completed OK, so the confirmation from the SD to the FD was important, but in the current implement (since quite a few releases), the SD reports back its status to the Dir as well, so this SD->FD notification is not critical. 2. The Director could be made to spool the attributes before committing them to the Catalog. This would allow a much earlier release of the SD as well. All these ideas need to be submitted as Feature Requests ... > > > > Item 2: Calling home feature > > > Origin: Frank Volf ([EMAIL PROTECTED]) > > > Date: 17 november 2005 > > > Status: > > Does the recently posted 'set ip' command allow/circumvent this? > > Interesting. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
