On 22 Oct 2006 at 13:33, Ross Boylan wrote:
> On Fri, Oct 20, 2006 at 10:58:15AM -0400, Dan Langille wrote:
> > On 20 Oct 2006 at 7:54, Ross Boylan wrote:
> >
> > > On Fri, Oct 20, 2006 at 10:36:50AM -0400, Dan Langille wrote:
> > > > On 20 Oct 2006 at 7:29, Ross Boylan wrote:
> > > >
> > > > > On Fri, Oct 20, 2006 at 07:24:57AM -0400, Dan Langille wrote:
> > > > > > On 19 Oct 2006 at 22:01, Ross Boylan wrote:
> > > > > >
> > > > > > > I have a new machine where I want to run bacula (that is the
> > > > > > > director, the storage pools, the database), and wonder if
> > > > > > > anyone has any advice on how to move over to it.
> > > > > > >
> > > > > > > For example, would this work?
> > > > > > > 1) install bacula
> > > > > > > 2) copy configuration files (*.conf) from old machine
> > > > > > > 3) migrate my database from the old machine (I'm using
> > > > > > > PostgreSQL). The old machine is using an older version of the
> > > > > > > database, so I'd like to migrate to the newer version at the
> > > > > > > same time. 4) copy the spool directory to which I write disk
> > > > > > > backups to the new machine.
> > > > > >
> > > > > > Copy may not be necessary. Just creating the directories should
> > > > > > be enough. The pool directory should be empty when jobs are not
> > > > > > running.
> > > > >
> > > > > I meant copying the contents of the spool directory.
> > > >
> > > > I meant spool. Not spool.
> > > ?
> > > pool not spool?
> > > I may not know what the pool directory is; I thought it meant the
> > > place bacula writes to disk when using FileStorage. I happen to have
> > > that set to a spool directory: Device {
> > > Name = FileStorage
> > > Media Type = File
> > > Archive Device = /var/spool/bacula
> > > ... in bacula-sd.conf
> > >
> >
> > When you move it over to the new machine, I'd recommend a new name.
> >
> > http://www.bacula.org/dev-manual/Data_Spooling.html
> >
> > Best not to confuse the issue by using a name already in Bacula
> > terminoligy.
> >
>
> The things is that name is also used by the Filesystem Hierarchy
> Standard, which states "/var/spool contains data which is awaiting
> some kind of later processing. Data in /var/spool represents work to
> be done in the future (by a program, user, or administrator); often
> data is deleted after it has been processed. "
If you never use the data in that archive device for anything but
transfering that data to another archive device (i.e. tape), then
fine, it fits the literal definition.
IMHO, you are backing up to disk. Thus, not spooling. It just so
happens that you are later moving that backup to some other medium.
> The way I'm using it fits this definition, and is fact substantively
> very close to bacula's spool facility (that is, the files go to disk
> and ultimately to some other medium).
Bacula's spooling is quite different to what you are doing. If you
were using Bacula's spooling mechanism, then I'd say sure, put the
spooling directory under /var/spool/bacula. Personally, I put it all
under /home/bacula.
--
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
