On 06/02/15 21:01, Doug Sampson wrote:
> Recently FreeBSD announced that its default Perl version is now 5.20 and
> urged all users to upgrade to that version. I did so. Now
> make_catalog_backup.pl doesn’t run. The first indication was as follows:
Hello.
I've had some troubles with 5.20, but I'm
Hi Ana,
Does this mean that Bacula prefers to create new volumes over recycling
old ones?
Here's the output, Vol-0001 for example isn't used by any backup jobs
looking at the bacula database, as are 15 others:
*list media
Pool: File
+-++---+-+---
Hello Marc,
Could you post a "list media" output? Bacula will just recycle a volume
when there is no one available for append and it is not possible to create
a new one (and you have automatic labeling configured).
Best regards,
Ana
On Tue, Jun 2, 2015 at 5:04 PM, Marc van Houtum
wrote:
> I do
I don't have any jobs with long retention times. Both file and job
retention are set at 14 days for every client, while the LastWritten
date on the oldest volume is May 10th. The catalog is showing the oldest
backup to be from May 19th and according to the JobMedia table in the
bacula database
On 06/02/2015 02:01 PM, Doug Sampson wrote:
> I'm not sure what needs to be done next in order to avoid the error
from occurring. Can someone shed light on what I need to do next?
Running Bacula 7.0.5 on FreeBSD 9.3.
I have in my BackupCatalog job
> RunBeforeJob = "/usr/bin/pg_dump -c -U bacula
Recently FreeBSD announced that its default Perl version is now 5.20 and urged
all users to upgrade to that version. I did so. Now make_catalog_backup.pl
doesn't run. The first indication was as follows:
30-May 09:05 pisces-dir JobId 15770: shell command: run BeforeJob
"/usr/local/share/bacula
On 06/01/2015 01:18 PM, Ana Emília M. Arruda wrote:
>>> I have this working here. With automatic labeling. When you submit the
>>> jobs, which messeges do you see for the jobs in the "status dir" command
A-ha, it says one job is running and 10 "is waiting on max Storage jobs".
>>> Just for check
|
| ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot
of drive "t:\" failed.
|
| ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot
of drive "u:\" failed.
|
| ctptstwin04-fd JobId 1569: Fatal error: Generate VSS snapshot
of drive "v:\
Am 02.06.2015 um 20:35 schrieb More, Ankush:
Hi Fabio,
Most of windows client are Virtual machine (Hyper-V).
Don’t run any command before job.
Thank you,
Ankush
*From:*"Fábio R. Medeiros" [mailto:fab...@unicamp.br]
*Sent:* 02 June 2015 20:05
*To:* bacula-users@lists.sourceforge.net
*Subject
Hi Fabio,
Most of windows client are Virtual machine (Hyper-V).
Don’t run any command before job.
Thank you,
Ankush
From: "Fábio R. Medeiros" [mailto:fab...@unicamp.br]
Sent: 02 June 2015 20:05
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Windows client backup error
Hi Anku
> I particularly do not like the idea of having separate volumes of the same
> media
> type into two different mount points, but I know people that are configuring
> this way. So I decided to do some tests and see what really was happening. No
> issues. Instead I prefer the LVM solution.
The point
I particularly do not like the idea of having separate volumes of the same
media type into two different mount points, but I know people that are
configuring this way. So I decided to do some tests and see what really was
happening. No issues. Instead I prefer the LVM solution.
On Tue, Jun 2, 2015
Do you have some specific reason to need to have these two volumes separate?
You might be best off using LVM to create a single logical drive. That
would certainly be a more flexible solution long term.
Bryn
On 2015-05-20 09:32 AM, SPQR wrote:
> I would like to set up bacula - well, my first st
Hello Josh,
On Tue, Jun 2, 2015 at 8:12 AM, Josh Fisher wrote:
>
> On 6/1/2015 5:21 PM, Ana Emília M. Arruda wrote:
>
> Hello,
>
> Maybe you could use the "virtual autochanger" resource:
>
>
> This will not work as expected. If the ArchiveDevice in the two Device
> resources specifies differen
Hi Ankush,
Is this Windows a virtual machine? Most virt. technologies requires
special drivers and/or agents.
Are you running any command before the job?
Regards,
Fábio
On 02-06-2015 10:57, More, Ankush wrote:
>
> Hi Heitor/Ana
>
>
>
> Few windows client backup successfully with same file
Chances are that one or more jobs on those full volumes has a long
retention time, causing them to not be recycled. If only one job is
configured with the wrong retention time, then only the volumes that
job's data gets written to ceases to recycle, making it appear to be
random volumes.
On 6/
> Few windows client backup successfully with same fileset.
> So I don’t think wrong in fileset.
Hello Ankush: can you output a estimate listing for this job?
Do this volumes really exist at this Windows Server?
If your FileSet is right it maybe indicate a VSS Windows service problem. You
can
Hi Heitor/Ana
Few windows client backup successfully with same fileset.
So I don’t think wrong in fileset.
Thank you,
Ankush
From: Heitor Faria [mailto:hei...@bacula.com.br]
Sent: 01 June 2015 17:23
To: More, Ankush; Ana Emília M. Arruda
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula
On 2-6-2015 14:43, Marc van Houtum wrote:
> If i compare the resultst to the volume files on the filesystem, I can
> see that there are currently 16 volume files not in use at the moment.
> Does anyone have any idea as to why these aren't being recycled? I've
> attached my bacula-dir.conf.
Forg
Hello,
We seem to be having an issue with our Bacula enviroment where some
volumes are not being recycled properly. This is causing our disk based
storage to fill up with unused volume files. Some volumes are being
recycled though which is why I'm having a hard time wrapping my head
around th
On 6/1/2015 5:21 PM, Ana Emília M. Arruda wrote:
Hello,
Maybe you could use the "virtual autochanger" resource:
This will not work as expected. If the ArchiveDevice in the two Device
resources specifies different directories (mountpoints), then the two
Device resources cannot have the same
21 matches
Mail list logo
