Assuming that the user would be responsible for the initial partitioning
etc, is there any reason that a generic 'bare metal' restore CD could
not be made? It looks like the catalogs and bootstrap files can be
recreated with the bscan etc tools, so unless I'm missing something, it
should be
On Tuesday 26 December 2006 11:02, James Harper wrote:
Assuming that the user would be responsible for the initial partitioning
etc, is there any reason that a generic 'bare metal' restore CD could
not be made? It looks like the catalogs and bootstrap files can be
recreated with the bscan etc
1. A snapshot of your hard disk configuration.
2. A copy of your current Bacula file daemon that can be run on
a rescue system (i.e. probably statically linked).
3. A bunch of scripts that can be used to do various recovery tasks
(bring up the network, repartition your hard disks as they
On Tuesday 26 December 2006 15:57, David Boyes wrote:
1. A snapshot of your hard disk configuration.
2. A copy of your current Bacula file daemon that can be run on
a rescue system (i.e. probably statically linked).
3. A bunch of scripts that can be used to do various recovery tasks
Yes, I think that is a good idea. First, though, we must create such a
tar
file, which doesn't currently exist as such. If you load and run the
rescue
make, it will exist as a directory.
One other thing that might be an issue is encryption information. I'm not
sure if the current scripts
On Thu, 14 Dec 2006, Kshatriya wrote:
The best solution would be to clone the files which are stored on disk to
tape...
Is really nobody using Cloned Pools and Jobs? :-(
My current try is, to make a Default pool and a Clone pool. The Clone
pool has the type Cloned.
After that I created 2
Kern Sibbald wrote:
On Tuesday 26 December 2006 11:02, James Harper wrote:
Assuming that the user would be responsible for the initial partitioning
etc, is there any reason that a generic 'bare metal' restore CD could
not be made? It looks like the catalogs and bootstrap files can be
On Tuesday 26 December 2006 20:23, Dan Trainor wrote:
Kern Sibbald wrote:
On Tuesday 26 December 2006 11:02, James Harper wrote:
Assuming that the user would be responsible for the initial partitioning
etc, is there any reason that a generic 'bare metal' restore CD could
not be made? It
Well, interestingly enough, I am just today working on the Bacula
rescue
CDROM, and I have just about given up the idea of making a generic
rescue
CDROM for a number of reasons that I'll describe below. First, here
is
what
I consider the Bacula CDROM to be:
1. A snapshot of your hard
On Tue, Dec 26, 2006 at 09:02:12PM +1100, James Harper wrote:
Assuming that the user would be responsible for the initial partitioning
etc, is there any reason that a generic 'bare metal' restore CD could
not be made? It looks like the catalogs and bootstrap files can be
Ignoring the case of
Do any of the configuration files allow an include statement? What about
an include statement to include all files in a directory? Eg
Director {
Name = my-dir
...
}
include /etc/bacula/bacula-dir.d/
My bacula-dir.conf only has a few clients in it and is already huge.
Breaking up the
for an individual file include you can place an @ in front of the
filename.
I dont think that there is a full directory include at this time.
Here is an example of my bacula-dir.conf:
Director {
Name = kninfra01_mycastle-dir
DIRport = 9501
QueryFile =
Yes, but not a dir as far as I know. This is in the manual, and as I recall is
rather obviously explained.
Use an @/path/to/include.conf
-Original Message-
From: James Harper [EMAIL PROTECTED]
Subj: [Bacula-users] include statement in config files?
Date: Wed Dec 27, 2006 12:11 am
[EMAIL PROTECTED] wrote:
for an individual file include you can place an @ in front of the
filename.
I dont think that there is a full directory include at this time.
Here is an example of my bacula-dir.conf:
Director {
Name = kninfra01_mycastle-dir
DIRport = 9501
QueryFile =
14 matches
Mail list logo
