On Tue, 12 Jul 2011 22:24:15 +, Joseph L Casale said:
I have a director with several sd's and one with an extensive set of data and
file based
volumes needs to be migrated away to another completely distinct director.
What if any is my least painful way of retaining the catalog data
You could make a clone of the whole catalog (outside of bacula) and then use
the bconsole delete volume command to remove unwanted volumes from each
catalog.
Martin,
That's simple enough, what is the correct way to remove extraneous clients and
jobs
etc out of the db?
Thanks for the idea.
jlc
On Wed, 13 Jul 2011 11:24:01 +, Joseph L Casale said:
Accept-Language: en-US
Content-Language: en-US
You could make a clone of the whole catalog (outside of bacula) and then use
the bconsole delete volume command to remove unwanted volumes from each
catalog.
Martin,
That's simple
The delete volume command will delete the job records as well. After that,
you can delete orphaned clients with Bacula's dbcheck utility.
Got it, a quick test shows this to be more trivial than I expected.
Thanks a lot, much appreciated!
jlc
I have a director with several sd's and one with an extensive set of data and
file based
volumes needs to be migrated away to another completely distinct director.
What if any is my least painful way of retaining the catalog data for the
volumes in
question?
Thanks,
jlc
On Jul 12, 2011, at 6:24 PM, Joseph L. Casale wrote:
I have a director with several sd's and one with an extensive set of data and
file based
volumes needs to be migrated away to another completely distinct director.
What if any is my least painful way of retaining the catalog data for the
These questions will help others answer you:
* Are you keeping the old Dir active? If you are abandoning the old Dir, you
can make the new Dir use the existing Catalog
Yes, they will both remain active.
* If you are keeping the old Dir, will you be using anything from the Catalog
on that
