On 01/13/11 14:34, Pasi Kärkkäinen wrote:
> http://www.bacula.org/manuals/en/concepts/concepts/Migration_Copy.html
> "Migration is only implemented for a single Storage daemon. You cannot read
> on one Storage daemon and write on another."
>
> - Is this still true also for Copy jobs?
Yes, at this time. Both migration and copy jobs are restricted at this
time to using a single SD for source and destination, because there is
no currently existing protocol in Bacula for one SD to communicate
directly with another.
> - Any plans to implement copy/migration from sd to another sd?
It's on the project list, I believe.
--
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.
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
