Hello,
My thoughts about it below:
2011/8/25 Allan Garcia <allan.gar...@gmail.com>
> (...)
> MY INITIAL BRAINSTORM
>
> 1. the dird have to contact the origin *sd* and command the migration (like
> it's done now)
> 2. the origin *sd* detects if the destination *sd* it's himself or the
> other *sd*
>
I think Director should communicate origin SD that destination is remote
device on the other SD and supply required connection info.
> 3. if the origin *sd* detects other destination, it respond informing that
> to the dird
>
4. the dird have to handle the origin *sd* response informing the
> destination *sd*
>
If you change #2, that above steps won't be required.
> 5. the dird commands the destination *sd* to wait the origin *sd*
> connection
> 6. the dird commands waits the destination *sd* to confirm
> 7. the dird commands origin *sd* to send data to destination *sd*
> 8. when it's done the job are marked as sucess, otherwise fail.
>
> Waiting for any comments...
>
>
You have to design a protocol used for SD to SD communication including
TLS/SSL encryption layer.
Best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
