Alexandre Oliva wrote:
>
> > I don't care if the mechanisms are out of AMANDA's influence - this
> > is a design issue.
>
> Indeed. Amanda is designed to be a backup manager, that knows how to
> use a couple of existing backup tools. If none of them fit your
> needs, well, then you just have to go find some backup program capable
> of backing up stuff you need and plug it into Amanda. See? It's not
> Amanda's fault.
>
I see. I will have to devise something myself to help me out of this. I
admit I had not expect this.
> > If you say that AMANDA can backup SAMBA shares, people will believe it
> > and be happy.
>
> And they can believe it. I do it every day. Many others do it. Just
> because it fails for some unlucky souls, it doesn't mean it doesn't
> work at all. Most likely, it's some detail in these souls' setups
> that can be easily fixed.
>
That "detail" might be writing a wrapper script, computing datestamps,
redesigning the wheel...:-)
> > The case that does not work is when you have a dual boot system
> > (Win/Linux) and the SAMBA shares you are trying to backup with
> > AMANDA (when running Linux) are the vfat partitions of Windows.
>
> Ok, so how about this idea: get Plex86 or VMWare, boot Windows atop
> GNU/Linux, share the disks you want to back up and tell Amanda to back
> them up using Samba. Then, wait for the blue screens :-) :-)
>
I am glad I had the same idea before I read your answer (see my other
posting) ;-) Believe me, I would try it, but for the moment it is out of
the question because of the computing power needed by VMware (the backup
server is a 486DX-133...).
> Except for this
> minor detail people keep forgetting, which is that Amanda just
> *manages* backups, it doesn't *create* them.
>
I will have to make this statement my daily mantra, until I get it.
Thanks for all the input.
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
