The below would work if you want your catalog to be aware of the off-site
If you're just pushing off-site for DR scenario then it's a different
a. Simply use array level replication if using zfs, netapp, or fiber
attached filers to do a diff snapshot copy. No your catalog wouldn't be
aware of the offsite copy but rebuilding this in a DR situation to see the
offsite logically as the original copy, shouldn't be too onerous (Be sure
you test how to do it and thoroughly document the procedures). If you
have a hot-standby at your off-site facility you could even script the
hot-standby to re-import the catalog after each night's snapshot so in the
event of a DR, you're already set to begin restores.
b. The below procedures would work, however you would want to test what
would happen in a DR situation if Bacula suddenly loses an entire storage
device (I can't speak to this, perhaps someone else can) Even some
enterprise level software gets "panicky" when it can't find disk storage
that was previously there.
On 10/7/13 10:10 AM, "Marcin Haba" <ganiuszka@...> wrote:
>On Mon, 2013-10-07 at 16:30 +0000, Steven Hammond wrote:
>> Forgive me if this is the wrong group to ask this question. We¹ve
>> been using Bacula in our production environment for about 6 months.
>> One feature we could use is the ability to COPY/MIGRATE from one SD to
>> another SD offsite. Is this currently possible or is it possibly
>> planned for a future release?
>> Steven Hammond
>> I.T. Manager
>> Technical Chemical Company
>There is a small workaround for your issue. You can temporary move
>device configuration from one SD to another SD, next you can do
>Copy/Migration and at the end revert to original SDs state. Below is
>SD1 includes disk devices A, B, C
>SD2 includes disk and/or tape devices X, Y, Z
>If you wish to run Copy/Migration jobs between SD1 and SD2 e.g. between
>A => Z then you can rewrite storage configuration from SD1(A) to SD2 to
>SD1 includes disk devices B, C
>SD2 includes A, X, Y, Z
>Now you need to mount file volumes resources A device from SD1 to SD2.
>It can be done e.g. by using NFS or SMB (or other more secure).
>In this step you have A and Z devices with their resources available
>locally on SD2 and you should be able to run Copy/Migration job.
>After proper Copy/Migration jobs you need just revert all above changes.
>If you need to automate this, you can write a script that will be
>realize all these actions.
>Please do not forget about update Storage configuration resources in DIR
>October Webinars: Code for Performance
>Free Intel webinars can help you accelerate application performance.
>Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>the latest Intel processors and coprocessors. See abstracts and register >
>Bacula-devel mailing list