Hi we are use bacula for our backups. So far I like all of it's features
and how it performs. More research into the "Migrate" function and will not
work the way it's currently implemented (2.2.6)
We currently have a large NAS server which we backup all servers to on a
nightly basis. No tape library is installed. We would like to use the
Migrate function to move data off site via a VPN to another location after a
specific age. At our other data center we also have a large NAS server.
The issue is this which appears in the online docs:
http://www.bacula.org/rel-manual/Migration.html
"Migration is only implemented for a single Storage daemon. You cannot read
on one Storage daemon and write on another."
I tried it and sure enough it doesn't work. All jobs get into a waiting
state.
Since the other storage daemon is on another server located at our other
data center, which means a seperate storage daemon, this then makes
Migration function useless for what we would like to do. FYI to the
developers this "feature" then makes the migrate function very limited. I
would be curious why it was implemented this way.
My question is how then can we implement off site backups via a network
transfer. use rsync to move the existing bacula pool files?? Ideally I
would like to do it directly within bacula. Is there a method to do this
within bacula?
I assume someone else has also had this issue and curious what was your
solution.
Thanks in advance..
-L
--
Larry Ludwig
Empowering Media
1-866-792-0489 x600
Have you visited our customer service blog?
http://www.supportem.com/blog/
-------------------------------------------------------------------------
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
