Hello,
On 19.10.2005 21:44, Doug Sampson wrote:
...
I looked at the development manual and I can't find what I'm searching for.
I did note that the Bacula CDROM restore is now available for the Solaris
platform but still not for FreeBSD. :( There's no new additions to the
FreeBSD portion of the Restore chapter nor to the "Restore a Server"
portion. Perhaps I am looking in the wrong places. Or you are not yet
complete adding documentation.
Wouldn't that be a great time to take notes of your own experiences to
later put them into some form of FreeBSD emergency recovery of your
Bacula server?
;-)
...
This hasn't been answered. The key question here is whether I should restore
the bootstrap file to the "new" server or to the "damaged" machine.
The most important thing - apart from new or damaged - is, that to
recover your catalog backup, you need the storage volumes (obviously)
and the bootstrap file for the most recent catalog backup.
Usually, starting with a new machine, you will put the bootstrap file to
that same host.
Also do I have to rebuild the partition(s) on the "new" server the same way
as the "damaged" machine?
Unless you want to restore raw disk image you won't. It's a good idea to
make sure your partitions can hold everything you want to restore to
them, though.
I don't think so as long as I can restore the
BackupCatalog.bsr to the "new" server and then restore to the "damaged"
machine from the backed up data on the "new" server. If the backups are
saved to a file which is then saved to an external USB HD that is archived
off-site, I would think that I would need to create a partition on the "new"
server with the same directory name as the damaged machine where the backups
were created. If that is the case, the partition must be large enough to
accomodate data that needs to be restored. Hm?
Somehow, I'm missing what you want to do... do you want a complete
recovery of an older machine, or do you want to quickly set up a working
Bacula server?
The first would require the bootstrap file from that machine's last
backup, the second requires a working OS, catalog database, and Bacula
installation. After that, you recover your catalog using the
corresponding bootstrap file. From then on, you can do all the normal
tasks like restoring to different clients and locations etc.
On the other hand, if the data was backed up to tape, I should not be
concerned with creating a partition large enough to hold the backed up data
on the "new" server. All I need to do is to create a partition large enough
for the OS, the PGSQL install, the bacula install, do the bootstrap restore,
and finally do the client restore to the "damaged" machine via bacula
directly from tape. Right?
Right, I think.
Note that you don't necessarily need the file based volumes in the same
directories as before - you set this all up in the SD's configuration,
and you can also use external disks there.
...
I just need someone to pat me on my back and say "yes, son, your bootstrap
file contains the catalog!" :)
Sorry, can't do that... the bootstrap file doesn't contain the catalog.
It only contains information where to find the files for a certain
backup job.
Arno
Thanks for putting up with me. Bacula is great!
~Doug
-------------------------------------------------------
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
--
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
