Hi.
I'm wondering default storage definition when restoreing.
My restore setting in bacula-dir.conf is below.
Job {
Name = RestoreFiles
Type = Restore
Client = ..jp-fd
FileSet=Full Set
Storage = StorageA
^^^
Messages = Standard
Where =
On Tue, Sep 21, 2010 at 08:19:21AM +1000, James Harper wrote:
Hello,
I am testing backups of an Exchange 2003 server, with the plugin. I
have a
schedule of incrementals with occasional virtualfulls.
The idea being that, after the first real full, doing a full backup is
no
longer
On Tue, 21 Sep 2010 08:24:14 +1200, Craig Miskell said:
Martin Simmons wrote:
I recently had to bscan a tape. The job was in the database (the Job
Retention
period hadn't yet passed), but the file/path records were not (the File
Retention period *had* passed).
For this
On Thu, 16 Sep 2010 10:33:47 -0700, Syn, Joonho said:
for the bacula-bat srpm i tried using
$ rpmbuild --rebuild --define build_centos5 1 --define build_mysql 1
bacula-bat-5.0.3-1.src.rpm
and the package would build correctly but when i installed it with
$ rpm-ivh package name
i
Hi all,
I am running a backup strategy with one Full backup once a week and
Incremental backups on all the other days.
Now there is a special file in the corresponding FileSet. I want this
file to be backed up only when the Full backup runs. The file changes
very often, but the Incremental
On 09/21/10 13:47, Stefan Palme wrote:
Hi all,
I am running a backup strategy with one Full backup once a week and
Incremental backups on all the other days.
Now there is a special file in the corresponding FileSet. I want this
file to be backed up only when the Full backup runs. The file
Thanks I actually ended up figuring this out myself. Turns out there is
also a bug in the bacula-mtx spec file. That one is missing
%storage-daemon-user bacula
On 9/21/10 6:28 AM, Martin Simmons mar...@lispworks.com wrote:
On Thu, 16 Sep 2010 10:33:47 -0700, Syn, Joonho said:
for the
Hi,
On Tue, 2010-09-21 at 14:16 -0400, Phil Stracchino wrote:
The short answer is, you can't. All levels of a given job must use the
same Fileset. To do otherwise ... well, let's just say that That Way
Lies Madness, and leave it at that.
I've already guessed this would be the answer :-)
On 09/21/10 14:35, Stefan Palme wrote:
As far as I understood the main problem is that ONE Job can have only
ONE FileSet. So I could just define a second Job with its own FileSet
(that contains only the special file), and this Job will run only once a
week. The obvious disadvantage of this
