Ah!
Sorry I misunderstood.
On Sep 9, 2010, at 3:38 PM, David Montminy wrote:
> Why have seperate build? What's the advantage of simply having
> seperate configurations in say:
> /etc/amanda/DailySet
> /etc/amanda/WeeklySet
> /etc/amanda/MonthlySet
This is just fine,
My way has no big advantage but, for me personally, I place all of my
important applications and their confs in the same place, so that they can be
backed up and recovered easily. "tar -cf /dev/tape /opt/amanda/day" will get
me everything including the bins at once.
> My "problem" is simply to have an offsite backup, and, after talking
> about it with my boss, we might go with a backup-on-disk + offsite
> mirror, as in
> -backup to disk1
> -bring disk2 on first day of the month
> -copy disk1 to disk2
> -send disk2 offiste
> -bring disk3 on the first of the next month
> -copy disk1 to disk3
If you create a new vtape for each run/increment this will work no probs:
1)You will need to clean old "slots" so as to not fill up the disk
2) You will want changer.conf to have a couple of slots so you dont
overwrite a zero with and increment :).
3) you will still want to have the catalog, just in case :)
NB At runtime the changer will only look at the tape in the "slot" ( aka where
the "data" symlink points to ) so it doesn't care if the other "slots" aren't
there... so long as it doesn't need to access them for amrecover etc.
I hope this was helpful. I am not always the best at explaining things :)
Gluck
Hroth,
> Much simpler and from our perspective it achieves the same result: an
> offsite backup with bare-metal recovery possible.
>
> David Montminy
>
>
> On 09/09/2010 1:13 PM, Hroðgar Skjöldung wrote:
>> Hi,
>> On Sep 8, 2010, at 1:40 PM, David Montminy wrote:
>>> We are already using amanda to backup to Tape,
>> <snip>
>>> -Switch External Harddrive every 4 week to send off-site.
>>>
>>> It is do-able with Amanda? Won't the vtape-changer have problem with the
>>> fact that I'm removing/replacing hard-drives?
>> I think he real question is what your catalog has. The vtapes catalog
>> would be overwritten and amanda and wound't know that you still have that
>> data... So you need to move your catalog along with the data... but that
>> sounds a bit fishy.
>>
>>
>> I personally have a separate build for each amanda backup type. 2
>> daily(24 cycle), 2 monthly(12 cycle) and 2 yearly(archived). In my case I
>> could theoretically just move the build with the vtapes offsite, and then
>> restore both when needed.
>>
>>
>> So, this would work for what you are suggesting, but you'd want to script
>> the build unless you are patient. Once you've made your first build you'd
>> want to script the rest.
>> # eg
>> ./configure --prexif=/opt/amanda0-4 $other_args&& make&& make install
>> ./configure --prexif=/opt/amanda4-8 $other_args&& make&& make install
>> ./configure --prexif=/opt/amanda8-12 $other_args&& make&& make install
>> ...
>> ./configure --prexif=/opt/amanda/48-52 $other_args&& make&& make install
>>
>>
>> **But dont forget to place the amanda builds ('/opt/amanda#') with the
>> drives when you take them away.
>>
>>
>> How does that sound? Anyway you might also ask the amanda mailing
>> list since there may be a better solution.
>>
>> Gangi þér vel!
>> Hro
>> _______________________________________________
>> mlug mailing list
>> [email protected]
>> https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
>
> _______________________________________________
> mlug mailing list
> [email protected]
> https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
_______________________________________________
mlug mailing list
[email protected]
https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
