Hello,
On 25.11.2005 06:22, Harry Putnam wrote:
Christoph Haas <[EMAIL PROTECTED]> writes:
MySQL doesn't accept your username (root) and password (...) for accesses
from the current client (localhost). It's a permissions problem in the
MySQL privilege system you need to fix here.
If you do not know how to accomplish that you may want to read:
http://dev.mysql.com/doc/refman/5.1/en/privilege-system.html
I've gotten a little further along by discovering I could access the
server by giving a username like bacula. Also able to run some of the
bacula scripts in /var/lib/bacula
However a cursory read of the material you pointed out seems to
indicate one needs to be a mysql heavy to run bacula. I was under the
impression that bacula did the heavy lifting there.
Which is right. Usually, you only need a working MySQL on the local
machine, with more or less loose security. In every other case you've
got to modify your MySQL setup so hat either the Bacula install scripts
can work with it, or modify the scripts.
Maybe you can help me decide how to proceed:
I came to learn to use bacula, is it also required to become thoroughly
proficient with mysql? I know nothing about databases, does that rule
me out as a bacula user?
Definitely not.
First, make sure you can use your database from the host bacula-dir is
running on. Easiest _is_ the local machine. Then, if you've already
executed some of the scripts, and things don't work, log into the
database and delete the bacula catalog: 'drop database bacula;' should
be a command to investigate. Revoke baculas permissions: 'revoke all
rights ...' or something might be a starting point - you see, I'm also
not the most experienced MySQL admin :-)
Then, execute the create_bacula_catalog script. If this gives errors,
try setting the right username and password. No need to try all sorts of
things at the same time ;-) After that, create_bacula_tables and
(perhaps - I'm not sure) something like grant...
Review your director configuration - it must contain the correct
authentication information for the database.
More should not be necessary if the prerequisites are met.
If that is the case there are many other choices for backup that do
not require learning some whole other area of expertise other than the
tool in hand.
While this is true, I never found an Open-Source solution similarly
flexible and reliable.
Bacula has already proven to be a huge time sinc with no real kick
back so far. If I were to count the hours I've spent on bacula in the
2 times I started trying to learn it they would top out pretty high
like 20-30 solid hours over weeks.
Well, I guess I spent about 4 hours from first reading about bacula till
my basic setup was finished, not counting waiting time during btape
tests, but until I set up my Bacula installation "correct" I did spend
more time, right. But I did not spend more time than, for example, I
would have had to spend had I used arkeia or Veritas, for example.
I have yet to backup a single file with bacula. Would I be better off
spending my time with something more direct and to the point?
That's your choice. One hint, though: Don't use arkeia, and I've heard
statements about Legato that were similar...
I looked at bacula because of the network capability. I've come to
need a network backup tool since my home network has grown to 5-7
machines and some have at least semi-important data on them.
You could, of course, also pay someone to set up Bacula, or buy a
commercial and perhaps more end-user friendly software... although I
still think that, to setup a useful backup system, you do need a good
understanding of the software and concepts involved. After all, you have
to know how to setup an emergency resore system in case of a disaster.
I've been using rsync/rsnaphot which is fully network capable from my linux
machines and for what I don't get with rsync, I use ghost from the
windows machines, which has some network capability although ghost is
grossly overrated as a network tool. Very primitive in that regard.
And is really only a whole partition/disc backup tool.
Too true, although they claim more in their advertisements. It's getting
better, though.
There are some problems related to running rsync from linux onto
windows shares and again bacula looked promising since it has a client
on the actual architecture and I'm guessing that would solve most of
those kind of problems.
What kind of time frame might I expect to begin to see something
getting backed up... That is, for a novice with databases and bacula
but a fair bit of experience in things linux.
Usually, I'd say about two to three days with some effort. Not whole
working days, but rather some hours a day, after regular work.
I'm not in a terrific hurry and am under no actual time constraint.
Good.
Only how long I can maintain an interest compared to effort required.
Bad :-)
And how long this list will put up with me... : )
Try us :-)
I'm a retiree so have a fair bit of available time.
Just try to purge your MySQL from earlier attempts to setup the catalog
and start again.
I didn't follow this thread very closely, but perhaps you might be
better of using a packaged version of Bacula, as a .rpm should do most
of the setup automatically, I believe.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
