Hi all,
I wanted to follow up and share my
experience with this subject, and ask for any input about problems I can expect.
I seem to have gotten my 2.4.4 director and
catalog upgraded to 3.0.2 by doing the following:
- Installed
Bacula 3.0.2 on CentOS 5.4;
- Created
the empty sqlite DB;
- Copied
bacula.db from production machine (fedora 11) to new machine;
- Ran
“update_bacula_tables” on the copied DB;
- Test
to make sure director will start;
- Copied
appropriate .conf files (after backing up default ones);
- Modified
paths in .conf files as needed;
- Disable
production director and shut down server;
- Gave
new machine the IP of the production machine;
- Restart
director;
- Use
bconsole to verify that the catalog is complete;
- Run
a job;
Anything I am overlooking?
Thanks!
From: Paul Binkley
[mailto:paul.binkley AT ois DOT com]
Sent: Monday, January 11, 2010
11:49 AM
To:
'bacula-users AT lists.sourceforge DOT net'
Subject:
Hi list,
I have been using Bacula 2.4.4 in production for several
months now, so I have a robust set of backup volumes. I now have a new machine
(CentOS 5.4) up and running with Bacula 3.0.2 installed. Besides fixing up the
conf files, how do I make the new installation work with the existing data? I
don’t want to lose access to the 5TB of backed up data.
Is there a way to upgrade the existing database and plug it
in to the new installation while retaining all the important information that
Bacula needs to continue using/recycling volumes or accessing existing volumes
for restore?
Thanks much!
