Hi Kern,
llist volume=saturn-fd-Full-01 gave the following.
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
MediaId: 220
VolumeName: saturn-fd-Full-01
Slot: 0
PoolId: 27
MediaType: saturnFile
MediaTypeId: 0
FirstWrit
Hello Martin,
I think this is indeed the root of the problem.
The problem is that the Director has modified the value of VolCatStatus
while the SD
knows that it could have changed this value. It is a sort of "race"
condition where
the variable can change on both (SD and DIR) sides.
I'll nee
Hello Aldolf,
Can you do an "llist volume=saturn-fd-Full-01" command in bconsole?
Note: it is really "ll" (two els).
Best regards,
Kern
On 10/02/2018 03:15 PM, Adolf Belka
wrote:
Hi Kern,
I also get those messages
Dear Bacula Users,
Just FYI.
* Zimbra Network Edition Backup with Bacula
http://bacula.us/zimbra-network-edition-backup-with-bacula/
* Bacula Community 9.x Official Packages Installation Script
http://bacula.us/script-installation-bacula-community-9-x-official-packages/
* Cart
My guess is that the SD is repeated sending Update_media with the status set
to Append, even though the Director has set it to Full in has_volume_expired.
Maybe line 511 of src/stored/askdir.c is copying in the wrong direction?
bstrncpy(dcr->VolCatInfo.VolCatStatus, dev->VolCatInfo.VolCa
Hello,
FWIW, I see the same behavior, with what I believe is a very similar
config, when running a virtual full job. The attached log excerpt is
from a virtual full job that ran as the only active job, although there
were other jobs waiting for higher priority jobs. (This job was the one
they
Hi Kern,
I also get those messages. I have just been living with them. Below are
the outputs from a Full job. The Full has something like 184 messages
with 183.7GB backed up. In the past I have also seen Differential jobs
with size around 2 to 3 GB giving around 3 messages so it seems to
scal
Hello,
Hmm. 107 messages and and the volumes are 107... long. Strange
coincidence. Could you provide a copy of your bacula-sd.conf as
well as the full output including other jobs running at the time of
the 107 messages. As far as I know, there is nothing that wou
Hello,
Bacula should do a better job of printing an error message, but from
what you show, it looks to me like your SQL instance ran out of storage
space. With the size of your backup, you really should be running
PostgreSQL rather than MySQL. It will probably be 20-30% faster
(possibly mo
Hello,
I suspect that what Martin has said in the second to last paragraph is
correct. At the same time, Bacula really should print a reason why the
label command did not work.
Have you already posted your complete bacula-sd.conf file? If not,
please do so.
Best regards,
Kern
On 09/28/2
Hello,
wt., 2 paź 2018 o 02:25 Phil Stracchino napisał(a):
>
> So, let me see if I understand this right.
>
>
If I understand it correctly then:
> (...) you're migrating the jobs one at a time to
> tape, and then ... what, recycling the disk volumes?
He is recycling tempDisk-pool in 5 days,
Hi,
Running that sql command confirmed the temp directory is /tmp
I looked at the mysqld log and couldn't see anything recent. There were space
issues, but they were more than a year ago.
I will look into increasing the logging level, but my concern would be that it
would use more resources w
12 matches
Mail list logo
