Hello,
On 12.10.2005 21:00, Christian Reiss wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kern Sibbald wrote:
Problem 2:
Restoring. Even tho every backup process writes a bootstrap, and the
restore jobs have bootstraps parameters, every restore command takes
/var/db/bacuda/restore.bsr as bootstrap. I dont particularly mind
that, but what if two client restore at the same time? Wont they
overwrite each others bootstraps?
Yes. However, that problem is fixed in 1.37.x
Which opens up a nice question.. Do I need bootstraps for file-only
operations? Can't i comment them all out?
Sure. You can do that, even with tapes. The point is that bootstrap
files make simple restoring possible when you lose your catalog
database. If you can live without that function, good. I'd recommend to
keep at least the bootstrap records for your catalog database, if you
put these into bacula.
Problem 3:
Regardless of my "Storage" instruction in the BackupJob definitions,
every restore takes "StoragePDA" as default storage.
Either add "storage=xxx" to the restore command line, or use the mod option to
modify it before starting the restore job.
Mhh. Yes. But shouldnt a setting in the config (for the backup jobs)
already imply that? Why is that setting ignored?
Because the restore job is different from the backup job?
No, seriously, that's a design decision, I think. Currently, bacula only
supports one restore job definition wich is only used as a template for
the interactive selection. That's just the way it is now. Of course,
that might change in the future, although I guess getting the graphical
restore front-end working perfectly is more important.
Question 1:
If I understand it correctly, all backup files on hdd are deleted after
60 days - in order to free up space?
Bacula never deletes Volumes it wrote.
So, after months, how do I gt rid of it, the bacula way?
You either set up your volumes and pools to reuse existing volume files
(retention - automatic recycling - probably limiting number of volumes,
volume use duration, or jobs per volume). This is discussed on the list
quite often, so you will find lots of interesting suggestions in the
archive. And in the manual, of course ;-)
Or, manually delete volumes you don't need anymore:
use the delete command from the console, and delete the corresponding
files from the shell. I wouldn't do this, though - after all, Bacula is
best for automatic backup solutions.
Thanks for your replies,
much appreciated,
Christian.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
