Helo Heitor,
"Use Volume Once" is an explicitly non-recommended directive by Kern himself.
You should use "Maximum Volume Jobs=1" in the pool resource.
Thank You for the above change,and this means only one job will run in that
pool?.
Another way, if you want different backup jobs to ALWAYS write in different
sets of volumes, is scheduling them to different pools.
so instead of device we should maintain pools for all new backup jobs. Will the
increase in number of pools will not be an another problem, like 50 pools for
50 jobs.
Regards,
Muhasin
From: "Heitor Faria" <hei...@bacula.com.br>
To: muha...@assistanz.com
Cc: "bacula-users" <bacula-users@lists.sourceforge.net>
Sent: Friday, August 18, 2017 5:25:49 PM
Subject: Re: [Bacula-users] Jobs are writing to wrong volumes.
Hi,
Hello, Muhasin,
BQ_BEGIN
I have only one pool for all clients now. I have labelled client with job name,
client name and jobid and for each job running a new volume will be created for
it. I have set "use volume once" in the pool.
BQ_END
"Use Volume Once" is an explicitly non-recommended directive by Kern himself.
You should use "Maximum Volume Jobs=1" in the pool resource.
BQ_BEGIN
In my view bacula should use volume created by a jobid, but here is my problem
starts. I have 10 jobs at a time on the same pool and each jobs created with a
jobid. Each jobid created a volume. But the contents are separated or
distributed in all volumes. For example job with jobid "1" successfully use
"vol1"and stores the data on it. Job id "2" and job id "3" creates "vol2" and
"vol3" respectively but the contents of job id "2" stores in the "vol3" instead
of "vol2".with contents of jobid "3".
BQ_END
BQ_BEGIN
I have tweaked the configuration in different ways, and the only way i could
solve the issue is using a seperate virtual drive for each job. It means if
there is 50 jobs at a time, you should created 50 virtual devices.
How to solve the issue by limiting virtual devices. I need the virtual device
should run multiple jobs in it and each job should only write to its created
volume rather than distributing the contents on one volume.
BQ_END
Another way, if you want different backup jobs to ALWAYS write in different
sets of volumes, is scheduling them to different pools.
BQ_BEGIN
Regards.
BQ_END
Regards,
BQ_BEGIN
--
Muhasin C.M
Systems Engineer R & D
Assistanz Networks Pvt LTD
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
BQ_END
--
===========================================================================
Heitor Medrado de Faria | CEO Bacula do Brasil | Visto EB-1 | LPIC-III | EMC
05-001 | ITIL-F
• Não seja tarifado pelo tamanho dos seus backups, conheça o Bacula Enterprise:
[ http://www.bacula.com.br/enterprise/ | http://www.bacula.com.br/enterprise/ ]
• Ministro treinamento e implementação in-company do Bacula Community: [
http://www.bacula.com.br/in-company/ | http://www.bacula.com.br/in-company/ ]
+55 61 98268-4220 | [ http://www.bacula.com.br/ | www.bacula.com.br ]
============================================================================
Indicamos também as capacitações complementares:
• [ http://www.livrate.com.br/ | Shell básico e Programação em Shell ] com
Julio Neves.
• [ http://www.spinola.net.br/blog | Zabbix ] com Adail Host.
============================================================================
--
Muhasin C.M
Systems Engineer R & D
Assistanz Networks Pvt LTD
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
