subject:"\[Bacula\-users\] How to continue after a Failed job \?"

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-07 Thread Martin Simmons

Yes, that's true, you cannot migrate part of a job.  If you migrated that job,
then you would have unused space on some other volume :-(

__Martin


> On Mon, 6 Sep 2021 11:30:20 +0200, Dan-Gabriel CALUGARU said:
> 
> Thanks very much Martin for your answer. In fact, I had the both cases 
> to manage :
> 
> > If the volume is not needed at all then maybe the "purge volume" command is
> > what you need?  That will forget about all data on a selected volume and 
> > mark
> > it for reuse.
> 
> Indeed, for the volume in this first case, I purged it and I think that 
> it will be no problem to fully reuse it later (for now, Bacula has taken 
> volumes marked Append).
> 
> 
> > If the volume contains other jobs that you want to keep, then there is no 
> > way
> > to reuse the space.  The only way around that would be migrate the jobs to
> > another volume.
> 
> 
> For the volume in this second case, your response confirmed me that I 
> had to console myself with the idea of "losing" the 2 TB (out of 6 TB of 
> its total space).
> 
> And this because I think that it is not possible to migrate only a part 
> of a job, I mean only the remaining 4 TB to another volume, as these 4 
> TB are indeed useful, written by the previously successfully completed 
> job (this job consisted in ~25 TB written in 5 volumes: 3 voumes x6 TB 
> exclusively for this job, and 2 others partially written for this job, 
> including the one under discussion)
> 
> 
> As a remark (who could perhaps make you better understand why I am 
> interested in these questions) : these backups are made for archiving 
> purposes (that's why I wanted to use as much as possible of the volumes 
> capacity and so ideally not to have "lost" spaces, because if they will 
> be some ones, they will be so for a long time...)
> 
> 
> Have a good week,
> 
> Dan
> 
> 
> > __Martin
> >
> >
> >> On Fri, 3 Sep 2021 14:13:34 +0200, Dan-Gabriel CALUGARU said:
> >> Thank you Josh and Radosław for your additional responses.
> >>
> >> But in this case (for a Failed job due to bacula machine crash), restart
> >> is the same as (re)run the job, right ?
> >>
> >> And thus, I come back to my main question (from my initial post): how to
> >> properly free up the space written by the Failed job (more than 3TB) on
> >> the volumes in order to be reused ?
> >> As a reminder, during this writing :
> >> - the first used volume became Full (it already contained data correctly
> >> written by the previous successfully completed job)
> >> - and continued writing on another volume, before the machine crashed
> >> (this volume is now used for the restart job)
> >>
> >> This is why (in a previous try) I did my tests with the purge command
> >> for this jobID (which presumably hadn't purged anything), and delete
> >> command this jobID which worked to remove this jobID informations in the
> >> catalog. But not to free up space written by this jobID on volumes.
> >>
> >> In this case, what is the theoretical difference between purge and delete ?
> >>
> >> I also wanted to use the Action On Purge = Truncate feature for both
> >> volumes before initiating the purge of this jobID, but since purge
> >> doesn't seem to do anything for this jobID, then I'm instead wondering
> >> if this feature (or another equivalent) would also work for the delete
> >> command (which it seemed to work in my previous try)?
> >>
> >> Sorry if my questions are too basic, but I haven't really found a clear
> >> answer in the manuals for these points.
> >>
> >> Have a good day,
> >>
> >> Best regards
> >>
> >> Dan
> >>
> >>
> >> Le 03/09/2021 à 13:13, Radosław Korzeniewski a écrit :
> >>> Hello,
> >>>
> >>> pt., 3 wrz 2021 o 12:36 Josh Fisher  >>> > napisał(a):
> >>>
> >>>   Instead, the Bacula server machine itself crashed, so it cannot
> >>>  determine where to restart and did not retain any cached/spooled 
> >>> data.
> >>>
> >>> Yes, exactly. I did miss this very important information in the
> >>> original post. It changes everything!
> >>>
> >>> But the other statements about (not) purging files and job info are
> >>> still valid.
> >>>
> >>> best regards
> >>> -- 
> >>> Radosław Korzeniewski
> >>> rados...@korzeniewski.net 
> >>>
> >>>
> >>> ___
> >>> Bacula-users mailing list
> >>> Bacula-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> -- 
> Dan-Gabriel CALUGARU
> IR en Calcul Scientifique (CNRS)
> Dr de Mathématiques et Applications
> 
> Laboratoire de Mécanique des Fluides et d'Acoustique
> UMR 5509 CNRS - ECL - UCBL - INSA Lyon - Univ. de Lyon
> 
> Bâtiment I11 - bureau 11098
> ECOLE CENTRALE de LYON
> 36, avenue Guy de Collongue
> 69134 ECULLY
> 
> tel: +33 (0)4 72 18 61 73
> 
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-06 Thread Dan-Gabriel CALUGARU

Thanks very much Martin for your answer. In fact, I had the both cases 
to manage :



If the volume is not needed at all then maybe the "purge volume" command is
what you need?  That will forget about all data on a selected volume and mark
it for reuse.


Indeed, for the volume in this first case, I purged it and I think that 
it will be no problem to fully reuse it later (for now, Bacula has taken 
volumes marked Append).




If the volume contains other jobs that you want to keep, then there is no way
to reuse the space.  The only way around that would be migrate the jobs to
another volume.



For the volume in this second case, your response confirmed me that I 
had to console myself with the idea of "losing" the 2 TB (out of 6 TB of 
its total space).


And this because I think that it is not possible to migrate only a part 
of a job, I mean only the remaining 4 TB to another volume, as these 4 
TB are indeed useful, written by the previously successfully completed 
job (this job consisted in ~25 TB written in 5 volumes: 3 voumes x6 TB 
exclusively for this job, and 2 others partially written for this job, 
including the one under discussion)



As a remark (who could perhaps make you better understand why I am 
interested in these questions) : these backups are made for archiving 
purposes (that's why I wanted to use as much as possible of the volumes 
capacity and so ideally not to have "lost" spaces, because if they will 
be some ones, they will be so for a long time...)



Have a good week,

Dan



__Martin



On Fri, 3 Sep 2021 14:13:34 +0200, Dan-Gabriel CALUGARU said:

Thank you Josh and Radosław for your additional responses.

But in this case (for a Failed job due to bacula machine crash), restart
is the same as (re)run the job, right ?

And thus, I come back to my main question (from my initial post): how to
properly free up the space written by the Failed job (more than 3TB) on
the volumes in order to be reused ?
As a reminder, during this writing :
- the first used volume became Full (it already contained data correctly
written by the previous successfully completed job)
- and continued writing on another volume, before the machine crashed
(this volume is now used for the restart job)

This is why (in a previous try) I did my tests with the purge command
for this jobID (which presumably hadn't purged anything), and delete
command this jobID which worked to remove this jobID informations in the
catalog. But not to free up space written by this jobID on volumes.

In this case, what is the theoretical difference between purge and delete ?

I also wanted to use the Action On Purge = Truncate feature for both
volumes before initiating the purge of this jobID, but since purge
doesn't seem to do anything for this jobID, then I'm instead wondering
if this feature (or another equivalent) would also work for the delete
command (which it seemed to work in my previous try)?

Sorry if my questions are too basic, but I haven't really found a clear
answer in the manuals for these points.

Have a good day,

Best regards

Dan


Le 03/09/2021 à 13:13, Radosław Korzeniewski a écrit :

Hello,

pt., 3 wrz 2021 o 12:36 Josh Fisher mailto:jfis...@jaybus.com>> napisał(a):

  Instead, the Bacula server machine itself crashed, so it cannot
 determine where to restart and did not retain any cached/spooled data.

Yes, exactly. I did miss this very important information in the
original post. It changes everything!

But the other statements about (not) purging files and job info are
still valid.

best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


--
Dan-Gabriel CALUGARU
IR en Calcul Scientifique (CNRS)
Dr de Mathématiques et Applications

Laboratoire de Mécanique des Fluides et d'Acoustique
UMR 5509 CNRS - ECL - UCBL - INSA Lyon - Univ. de Lyon

Bâtiment I11 - bureau 11098
ECOLE CENTRALE de LYON
36, avenue Guy de Collongue
69134 ECULLY

tel: +33 (0)4 72 18 61 73



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-03 Thread Martin Simmons

If the volume is not needed at all then maybe the "purge volume" command is
what you need?  That will forget about all data on a selected volume and mark
it for reuse.

If the volume contains other jobs that you want to keep, then there is no way
to reuse the space.  The only way around that would be migrate the jobs to
another volume.

__Martin


> On Fri, 3 Sep 2021 14:13:34 +0200, Dan-Gabriel CALUGARU said:
> 
> Thank you Josh and Radosław for your additional responses.
> 
> But in this case (for a Failed job due to bacula machine crash), restart 
> is the same as (re)run the job, right ?
> 
> And thus, I come back to my main question (from my initial post): how to 
> properly free up the space written by the Failed job (more than 3TB) on 
> the volumes in order to be reused ?
> As a reminder, during this writing :
> - the first used volume became Full (it already contained data correctly 
> written by the previous successfully completed job)
> - and continued writing on another volume, before the machine crashed 
> (this volume is now used for the restart job)
> 
> This is why (in a previous try) I did my tests with the purge command 
> for this jobID (which presumably hadn't purged anything), and delete 
> command this jobID which worked to remove this jobID informations in the 
> catalog. But not to free up space written by this jobID on volumes.
> 
> In this case, what is the theoretical difference between purge and delete ?
> 
> I also wanted to use the Action On Purge = Truncate feature for both 
> volumes before initiating the purge of this jobID, but since purge 
> doesn't seem to do anything for this jobID, then I'm instead wondering 
> if this feature (or another equivalent) would also work for the delete 
> command (which it seemed to work in my previous try)?
> 
> Sorry if my questions are too basic, but I haven't really found a clear 
> answer in the manuals for these points.
> 
> Have a good day,
> 
> Best regards
> 
> Dan
> 
> 
> Le 03/09/2021 à 13:13, Radosław Korzeniewski a écrit :
> > Hello,
> >
> > pt., 3 wrz 2021 o 12:36 Josh Fisher  > > napisał(a):
> >
> >  Instead, the Bacula server machine itself crashed, so it cannot
> > determine where to restart and did not retain any cached/spooled data.
> >
> > Yes, exactly. I did miss this very important information in the 
> > original post. It changes everything!
> >
> > But the other statements about (not) purging files and job info are 
> > still valid.
> >
> > best regards
> > -- 
> > Radosław Korzeniewski
> > rados...@korzeniewski.net 
> >
> >
> > ___
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 
> -- 
> Dan-Gabriel CALUGARU
> IR en Calcul Scientifique (CNRS)
> Dr de Mathématiques et Applications
> 
> Laboratoire de Mécanique des Fluides et d'Acoustique
> UMR 5509 CNRS - ECL - UCBL - INSA Lyon - Univ. de Lyon
> 
> Bâtiment I11 - bureau 11098
> ECOLE CENTRALE de LYON
> 36, avenue Guy de Collongue
> 69134 ECULLY
> 
> tel: +33 (0)4 72 18 61 73
> 
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-03 Thread Dan-Gabriel CALUGARU


Thank you Josh and Radosław for your additional responses.

But in this case (for a Failed job due to bacula machine crash), restart 
is the same as (re)run the job, right ?


And thus, I come back to my main question (from my initial post): how to 
properly free up the space written by the Failed job (more than 3TB) on 
the volumes in order to be reused ?

As a reminder, during this writing :
- the first used volume became Full (it already contained data correctly 
written by the previous successfully completed job)
- and continued writing on another volume, before the machine crashed 
(this volume is now used for the restart job)


This is why (in a previous try) I did my tests with the purge command 
for this jobID (which presumably hadn't purged anything), and delete 
command this jobID which worked to remove this jobID informations in the 
catalog. But not to free up space written by this jobID on volumes.


In this case, what is the theoretical difference between purge and delete ?

I also wanted to use the Action On Purge = Truncate feature for both 
volumes before initiating the purge of this jobID, but since purge 
doesn't seem to do anything for this jobID, then I'm instead wondering 
if this feature (or another equivalent) would also work for the delete 
command (which it seemed to work in my previous try)?


Sorry if my questions are too basic, but I haven't really found a clear 
answer in the manuals for these points.


Have a good day,

Best regards

Dan


Le 03/09/2021 à 13:13, Radosław Korzeniewski a écrit :

Hello,

pt., 3 wrz 2021 o 12:36 Josh Fisher > napisał(a):


 Instead, the Bacula server machine itself crashed, so it cannot
determine where to restart and did not retain any cached/spooled data.

Yes, exactly. I did miss this very important information in the 
original post. It changes everything!


But the other statements about (not) purging files and job info are 
still valid.


best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users



--
Dan-Gabriel CALUGARU
IR en Calcul Scientifique (CNRS)
Dr de Mathématiques et Applications

Laboratoire de Mécanique des Fluides et d'Acoustique
UMR 5509 CNRS - ECL - UCBL - INSA Lyon - Univ. de Lyon

Bâtiment I11 - bureau 11098
ECOLE CENTRALE de LYON
36, avenue Guy de Collongue
69134 ECULLY

tel: +33 (0)4 72 18 61 73

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-03 Thread Radosław Korzeniewski

Hello,

pt., 3 wrz 2021 o 12:36 Josh Fisher  napisał(a):

>  Instead, the Bacula server machine itself crashed, so it cannot determine
> where to restart and did not retain any cached/spooled data.
>
Yes, exactly. I did miss this very important information in the original
post. It changes everything!

But the other statements about (not) purging files and job info are still
valid.

best regards
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-03 Thread Josh Fisher



On 9/2/21 9:50 AM, Dan-Gabriel CALUGARU wrote:

Hello everybody,

I would like to ask for your help to continue the backup of space of 
around 300 TB.


I'am using Bacula 9.6.7 version.

I was able to divide this work into several jobs of about 15-20 TB 
(one week for each job) to be able to resume more easily if there was 
a problem.
After several such jobs successfully completed (I have already backed 
up nearly 250 TB), the machine hosting the bacula server crashed while 
my last backup job (jobID = 25) was running.

Could you advise me what is the best way to continue in such a case ?



If something happens to the network communications or if the client 
crashes, then a job may be marked Incomplete, rather than Failed. In 
that case, the job can be restarted because the Bacula server knows that 
the files it has received so far are correct and that it can restart 
with the file that was being received when the problem occurred. The 
server still has the cached/spooled data. For your job 25, that is not 
the case. Instead, the Bacula server machine itself crashed, so it 
cannot determine where to restart and did not retain any cached/spooled 
data.





As additional information, I would note that this job appears with 
Failed status and that it had written (before the crash) on 2 volumes 
(which are LTO-7 tape cartridges with a capacity of approximately 6TB):
- about 2TB on the 1st volume "volume41" (which became Full), knowing 
that the previous job (well finished) had already written the first 4TB
- about 1TB on the 2nd volume "volume 42" (which was empty before the 
job, ans allways in Append status)


I have tried so far:

1) purge files jobid=25

but this command seems to have nothing done because jobID=25 was still 
present in the catalog (the outputs of the commands list jobid=25 and 
list joblog jobid=25 have not changed after this command)


then

2) delete jobid=25

who deleted this job from the catalog because I got this message :

/JobId = 25 and associated records deleted from the catalog./

and the outputs of the commands list jobid=25 and list joblog jobid=25 
have changed ("No results to list")


On the other hand, the information on the two volumes has not changed 
and if I restart with restart jobid=25  I have the impression that 
bacula acts as if it is another job, so it continues to write on the 
2nd volume ("volume 42") after the 1TB already written (by the 
previous Failed job). Therefore, the space written by the Failes job 
(jobID = 25) no longer seems to be used and will therefore remain "lost".


Instead, I would like bacula reuse this space (the 2TB on the 1st 
volume "volume41" and the 1TB on the 2nd volume "volume 42").


Indeed, from what I understood, for Failed jobs, we have to start from 
scratch, but I would like to re-use the space it had written by Failed 
job (because unusable).


Do you have a technique for doing this ?

Thank you in advance for any response

Best regards,

Dan


--
Dan-Gabriel CALUGARU
IR en Calcul Scientifique (CNRS)
Dr de Mathématiques et Applications

Laboratoire de Mécanique des Fluides et d'Acoustique
UMR 5509 CNRS - ECL - UCBL - INSA Lyon - Univ. de Lyon

Bâtiment I11 - bureau 11098
ECOLE CENTRALE de LYON
36, avenue Guy de Collongue
69134 ECULLY

tel: +33 (0)4 72 18 61 73


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-02 Thread Dan-Gabriel CALUGARU


Hello,

Thanks a lot Radoslaw for your responses.

You are obviously right that restarting a job cannot work if it has been 
deleted from the catalog.


I'm a little confused that a Failed job could however be considered (in 
some circumstances) as an Incomplete one, and I am wondering how my job 
would be considered.


Therefore, from a backup of the virtual machine, I was able to return to 
the situation just after the crash and the reboot of the machine (with 
my job jobID=25 well recorded in the catalog, in Failed state, since my 
purge/delete tries have not yet been done at this time).


So, I restarted this job (in restart prompt, this job was listed in 
Failed jobs list and not in Incomplet job list) : the new job (which is 
now in Running state with jobId=26) are writing to the last volume 
("volume42" from my initial message) apparently following the jobID=25 
backuped data (in any case, this is suggested by the increase of 
volbytes and volfiles for this media).


Could you tell me please if at this point there is any way to know if it 
is indeed a true restart (from the point of at the time of the crash) or 
if it started from zero? I mean if the jobID=25 was considered an 
Incomplete job or a Failed job ?


As a reminder, the jobID = 25 is always given with jobstatus "f" (I 
guess Failed) by the command list jobid = 25.
And the commands list files jobid=25 and list files jobid=26 does not 
return (for the moment) any filename. Also, the jobfiles field is 0 in 
for both jobs (for the moment).


Thanks again,

Dan


Le 02/09/2021 à 17:53, Radosław Korzeniewski a écrit :

Hello,

czw., 2 wrz 2021 o 16:07 Dan-Gabriel CALUGARU 
> napisał(a):


Hello everybody,

I would like to ask for your help to continue the backup of space
of around 300 TB.

I'am using Bacula 9.6.7 version.

I was able to divide this work into several jobs of about 15-20 TB
(one week for each job) to be able to resume more easily if there
was a problem.
After several such jobs successfully completed (I have already
backed up nearly 250 TB), the machine hosting the bacula server
crashed while my last backup job (jobID = 25) was running.
Could you advise me what is the best way to continue in such a case ?

As additional information, I would note that this job appears with
Failed status and that it had written (before the crash) on 2
volumes (which are LTO-7 tape cartridges with a capacity of
approximately 6TB):
- about 2TB on the 1st volume "volume41" (which became Full),
knowing that the previous job (well finished) had already written
the first 4TB
- about 1TB on the 2nd volume "volume 42" (which was empty before
the job, ans allways in Append status)

I have tried so far:

1) purge files jobid=25

but this command seems to have nothing done because jobID=25 was
still present in the catalog (the outputs of the commands list
jobid=25 and list joblog jobid=25 have not changed after this command)

then

2) delete jobid=25

who deleted this job from the catalog because I got this message :

/JobId = 25 and associated records deleted from the catalog./

and the outputs of the commands list jobid=25 and list joblog
jobid=25 have changed ("No results to list")

On the other hand, the information on the two volumes has not
changed and if I restart with restart jobid=25


To restart the job Bacula requires proper data for the failed job 
available in the catalog to know the restart point, which you just 
simply deleted. It won't work that way.


I have the impression that bacula acts as if it is another job, so
it continues to write on the 2nd volume ("volume 42") after the
1TB already written (by the previous Failed job). Therefore, the
space written by the Failes job (jobID = 25) no longer seems to be
used and will therefore remain "lost".


Yes. When no information about a failed job is available then Bacula 
is unable to restart that job, so it just starts it from scratch. For 
any successful job restart it has to be in an "incomplete" state. Any 
other state restarts a job from the start.



Instead, I would like bacula reuse this space (the 2TB on the 1st
volume "volume41" and the 1TB on the 2nd volume "volume 42").


It is absolutely possible with "incomplete" jobs feature and jobs 
restart. But you should never delete an incomplete job from the 
catalog when you want it to be restartable.


Indeed, from what I understood, for Failed jobs, we have to start
from scratch, but I would like to re-use the space it had written
by Failed job (because unusable).


As I wrote above, you can reuse already available data when your job 
is incomplete and you restart it without deleting. :)



Do you have a technique for doing this ?

Thank you in advance for any response

Just take a look at Bacula manual:

/8.2.12

Re: [Bacula-users] How to continue after a Failed job ?

2021-09-02 Thread Radosław Korzeniewski

Hello,

czw., 2 wrz 2021 o 16:07 Dan-Gabriel CALUGARU <
dan-gabriel.calug...@ec-lyon.fr> napisał(a):

> Hello everybody,
>
> I would like to ask for your help to continue the backup of space of
> around 300 TB.
>
> I'am using Bacula 9.6.7 version.
> I was able to divide this work into several jobs of about 15-20 TB (one
> week for each job) to be able to resume more easily if there was a problem.
> After several such jobs successfully completed (I have already backed up
> nearly 250 TB), the machine hosting the bacula server crashed while my last
> backup job (jobID = 25) was running.
> Could you advise me what is the best way to continue in such a case ?
>
> As additional information, I would note that this job appears with Failed
> status and that it had written (before the crash) on 2 volumes (which are
> LTO-7 tape cartridges with a capacity of approximately 6TB):
> - about 2TB on the 1st volume "volume41" (which became Full), knowing that
> the previous job (well finished) had already written the first 4TB
> - about 1TB on the 2nd volume "volume 42" (which was empty before the job,
> ans allways in Append status)
>
> I have tried so far:
>
> 1) purge files jobid=25
>
> but this command seems to have nothing done because jobID=25 was still
> present in the catalog (the outputs of the commands list jobid=25 and list
> joblog jobid=25 have not changed after this command)
>
> then
>
> 2) delete jobid=25
>
> who deleted this job from the catalog because I got this message :
>
>*JobId = 25 and associated records deleted from the catalog.*
>
> and the outputs of the commands list jobid=25 and list joblog jobid=25
> have changed ("No results to list")
>
> On the other hand, the information on the two volumes has not changed and
> if I restart with  restart jobid=25
>

To restart the job Bacula requires proper data for the failed job available
in the catalog to know the restart point, which you just simply deleted. It
won't work that way.


> I have the impression that bacula acts as if it is another job, so it
> continues to write on the 2nd volume ("volume 42") after the 1TB already
> written (by the previous Failed job). Therefore, the space written by the
> Failes job (jobID = 25) no longer seems to be used and will therefore
> remain "lost".
>

Yes. When no information about a failed job is available then Bacula is
unable to restart that job, so it just starts it from scratch. For any
successful job restart it has to be in an "incomplete" state. Any other
state restarts a job from the start.


>
> Instead, I would like bacula reuse this space (the 2TB on the 1st volume
> "volume41" and the 1TB on the 2nd volume "volume 42").
>
>
It is absolutely possible with "incomplete" jobs feature and jobs restart.
But you should never delete an incomplete job from the catalog when you
want it to be restartable.


> Indeed, from what I understood, for Failed jobs, we have to start from
> scratch, but I would like to re-use the space it had written by Failed job
> (because unusable).
>

As I wrote above, you can reuse already available data when your job is
incomplete and you restart it without deleting. :)


>
> Do you have a technique for doing this ?
>
> Thank you in advance for any response
>
Just take a look at Bacula manual:








*8.2.12 Incomplete JobsDuring a backup, if the Storage daemon experiences
disconnection with the File daemon duringbackup (normally a comm line
problem or possibly an FD failure), under conditions that the SDdetermines
to be safe it will make the failed job as Incomplete rather than failed.
This is doneonly if there is sufficient valid backup data that was written
to the Volume. The advantage ofan Incomplete job is that it can be
restarted by the new bconsole restart command from thepoint where it left
off rather than from the beginning of the jobs as is the case with a
cancel.*

best regrads
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] How to continue after a Failed job ?

2021-09-02 Thread Dan-Gabriel CALUGARU


Hello everybody,

I would like to ask for your help to continue the backup of space of 
around 300 TB.


I'am using Bacula 9.6.7 version.

I was able to divide this work into several jobs of about 15-20 TB (one 
week for each job) to be able to resume more easily if there was a problem.
After several such jobs successfully completed (I have already backed up 
nearly 250 TB), the machine hosting the bacula server crashed while my 
last backup job (jobID = 25) was running.

Could you advise me what is the best way to continue in such a case ?

As additional information, I would note that this job appears with 
Failed status and that it had written (before the crash) on 2 volumes 
(which are LTO-7 tape cartridges with a capacity of approximately 6TB):
- about 2TB on the 1st volume "volume41" (which became Full), knowing 
that the previous job (well finished) had already written the first 4TB
- about 1TB on the 2nd volume "volume 42" (which was empty before the 
job, ans allways in Append status)


I have tried so far:

1) purge files jobid=25

but this command seems to have nothing done because jobID=25 was still 
present in the catalog (the outputs of the commands list jobid=25 and 
list joblog jobid=25 have not changed after this command)


then

2) delete jobid=25

who deleted this job from the catalog because I got this message :

/JobId = 25 and associated records deleted from the catalog./

and the outputs of the commands list jobid=25 and list joblog jobid=25 
have changed ("No results to list")


On the other hand, the information on the two volumes has not changed 
and if I restart with restart jobid=25  I have the impression that 
bacula acts as if it is another job, so it continues to write on the 2nd 
volume ("volume 42") after the 1TB already written (by the previous 
Failed job). Therefore, the space written by the Failes job (jobID = 25) 
no longer seems to be used and will therefore remain "lost".


Instead, I would like bacula reuse this space (the 2TB on the 1st volume 
"volume41" and the 1TB on the 2nd volume "volume 42").


Indeed, from what I understood, for Failed jobs, we have to start from 
scratch, but I would like to re-use the space it had written by Failed 
job (because unusable).


Do you have a technique for doing this ?

Thank you in advance for any response

Best regards,

Dan


--
Dan-Gabriel CALUGARU
IR en Calcul Scientifique (CNRS)
Dr de Mathématiques et Applications

Laboratoire de Mécanique des Fluides et d'Acoustique
UMR 5509 CNRS - ECL - UCBL - INSA Lyon - Univ. de Lyon

Bâtiment I11 - bureau 11098
ECOLE CENTRALE de LYON
36, avenue Guy de Collongue
69134 ECULLY

tel: +33 (0)4 72 18 61 73

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

Re: [Bacula-users] How to continue after a Failed job ?

[Bacula-users] How to continue after a Failed job ?

9 matches

Site Navigation

Mail list logo

Footer information