[ale] Looking for backup solution.
Jim
ale_nospam at fayettedigital.com
Fri Jun 9 10:18:16 EDT 2006
Back when I was using tape, I usually made the device 664 and changed
group to tape, if it wasn't already. Then I added uses to the tape
group that needed tape access. However this is writing to a big disk
partition only.
Jim.
James P. Kinney III wrote:
> On Fri, 2006-06-09 at 07:00 -0400, Jim wrote:
>
>> Thanks for all the suggestions. I started to implement an rvm solution
>> but the documentation left me with a lot of questions. I decided to go
>> back to bacula to see if I could figure it out one more time. What
>> finally worked was running bacula-sd as root. For some strange reason
>> running as bacula/tape quit working even though the disk volume that I
>> was writing to was owned by bacula/tape. I even set the directory
>> permissions to 777 but no way would the sd write to it. I suspect I
>> shouldn't be running sd as root, but it works and I'm happy with it.
>>
>
> I'm pretty sure running sd as root is a normal thing. It has to actually
> touch the tape device in the same way that mt does. The only other way
> would be to setup a tape user and make them a member of the disk group.
> The disk group has rw on the actual nst* devices.
>
>> I thought I'd document the problem so someone else might find the
>> solution in the future.
>>
>> Thanks again,
>> Jim.
>>
>> Jim wrote:
>>
>>> I tried bacula because it had everything I needed, however I couldn't
>>> get it to work the first time and then when I tried later it seemed to
>>> work after screwing with it too long. Now all of a sudden it started
>>> failing.
>>>
>>> So I'm going to trash it and try something else.
>>>
>>> What I liked about bacula were the following features.
>>>
>>> * it does either full backups or incremental ones.
>>> * it allows me to include/exclude directories/files.
>>> * it runs from a single machine and dumps files from multiple systems,
>>> including Windows
>>>
>>> Rsync does the second, but unless you write some sort of script to
>>> schedule the target in different places, it won't solve the first and
>>> as far as I know it doesn't do the third for windows. I know you can
>>> run rsync on windows, but you can't schedule it from Linux unless you
>>> install some sort of ssh server on the windows box. I'd rather have a
>>> complete package that runs everwhere if possible.
>>>
>>> I'm dumping to a dedicated 200 Gb drive on one of my Linux boxes. I
>>> dont have a tape drive.
>>>
>>> Dump is pretty quick, but it doesn't let me exclude the crap I really
>>> don't want to be bothered with among other limitations.
>>>
>>> So does anyone know of any reasonable solutions? Something that'll last
>>> more than a couple of months? (bacula)
>>>
>>> Thanks,
>>> Jim.
>>> _______________________________________________
>>> Ale mailing list
>>> Ale at ale.org
>>> http://www.ale.org/mailman/listinfo/ale
>>>
>>>
>>>
>>>
>>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://www.ale.org/mailman/listinfo/ale
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://www.ale.org/mailman/listinfo/ale
More information about the Ale
mailing list