Try reading the Restore chapter rather than the rescue chapter: http://www.bacula.org/dev-manual/Bacula_Consol_Restor_Comman.html#SECTION0002111000000000000000
it may help, but probably not. On Wednesday 19 October 2005 21:44, Doug Sampson wrote: > > Take a look at the end of the Restore chapter in the > > development manual. I > > have started a list of things you should do and how to > > recover from various > > situations -- note the word "started" above, which means > > there is still much > > more documentation to add. If you have any comments or > > suggestions, they are > > welcome. > > 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. > > > > I'm looking at this section (Here's the link > > > > (http://bacula.org/rel-manual/Disast_Recove_Using_Bacula.html# > > SECTION000361 > > > > >2 000000000000000) as follows: > > > > > > "If you have a valid saved Bootstrap file as created for > > > > your damaged > > > > > machine with WriteBootstrap, use it to restore the files to > > > > the damaged > > > > > machine, where you have loaded a static Bacula File daemon > > > > using the Bacula > > > > > Rescue disk). This is done by using the restore command and at the > > > yes/mod/no prompt, selecting mod then specifying the path > > > > to the bootstrap > > > > > file." > > > > > > It seems that I am to restore a valid saved bootstrap file > > > > for the damaged > > > > > machine. I am unsure to which machine the bootstrap file is > > > > to go. Is it to > > > > > the damaged server or to the new machine? If I interpret it > > > > correctly, the > > > > > bootstrap file should be restored to the new server. I then > > > > need to run the > > > > > static bacula-fd on the damaged machine to be recovered. The static > > > bacula-fd then will restore data from either an attached > > > > tape drive or an > > > > > external HD on the new server using the catalog on the new > > > > bacula server. > > > > > Once the damaged machine has restored its files, it can be > > > > rebooted and > > > > > then be its old self (assuming the necessary files have > > > > been properly > > > > > backed up and restored). > > > > > > Am I on the right track as far as restoring a Bacula server > > > > is concerned? > > 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. > > Also do I have to rebuild the partition(s) on the "new" server the same way > as the "damaged" machine? 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? > > 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? > > > > In the above particular case, the bootstrap file is the > > > > BackupCatalog.bsr? > > > > > Not the bootstrap file for the client (i.e. Aries.bsr)? > > This also hasn't been answered. I'm led to believe that it's the > BackupCatalog.bsr that contains the Bacula catalog. Relevant BackupCatalog > job/fileset in bacula-dir.conf as follows: > > <..snip..> > > # Backup the catalog database (after the nightly save) > Job { > Name = "BackupCatalog" > JobDefs = "DefaultJob" > Level = Full > FileSet="Catalog" > Schedule = "WeeklyCycleAfterBackup" > # This creates an ASCII copy of the catalog > RunBeforeJob = "/usr/local/share/bacula/make_catalog_backup bacula > bacula" # This deletes the copy of the catalog > RunAfterJob = "/usr/local/share/bacula/delete_catalog_backup" > Storage = FileStorage > Messages = Standard > Write Bootstrap = "/var/db/bacula/BackupCatalog.bsr" > Priority = 13 # run after verify main backup > > <..snip..> > > # This is the backup of the catalog > FileSet { > Name = "Catalog" > Include { > Options { > signature = MD5 > } > File = /var/db/bacula/bacula.sql > } > } > > <..snip..> > > I just need someone to pat me on my back and say "yes, son, your bootstrap > file contains the catalog!" :) > > 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 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
