Re: [Bacula-users] Identify corrupted volume files

[José Queiroz]

Thank you all for the help; "bls -j" (and a lot of shell scripting) done
the job.
Unfortunately, I lost many of my backup volumes. Thanks God, only backup
files were affected.

Em qui, 15 de ago de 2019 às 06:42, Martin Simmons 
escreveu:

> bls -j will do some checks the volume without using the catalog and should
> detect corruption (see
>
> https://www.bacula.org/9.4.x-manuals/en/utility/Volume_Utility_Tools.html#SECTION00251000
> ).
>
> __Martin
>
>
> > On Wed, 14 Aug 2019 16:48:35 -0300, José Queiroz said:
> >
> > Thanks for the response, Pedro and Heitor.
> >
> > Some of these volumes were recent, but most of them were historical, and
> > were purged/pruned from the catalogs.
> > Is there a way to verify them without using the catalogs? In fact, I only
> > need to know if the volumes are consistent/readable.
> >
> > Em seg, 12 de ago de 2019 às 17:20, Pedro Oliveira <
> oliveira...@gmail.com>
> > escreveu:
> >
> > > Hi Jose,
> > >
> > > you can create a new verify job and check the catalog against the disk
> or
> > > create a script and use the bscan and  bls volume utility tools, please
> > > check the following urls:
> > >
> > > *Verify*Run a verify Job. In general, *verify* jobs permit you to
> compare
> > > the contents of the catalog to the file system, or to what was backed
> up.
> > > In addition, to verifying that a tape that was written can be read,
> you can
> > > also use *verify* as a sort of tripwire intrusion detection.
> > >
> > > For a *Verify* Job, the Level may be one of the following:
> > >
> > > *DiskToCatalog*This level causes Bacula to read the files as they
> > > currently are on disk, and to compare the current file attributes with
> the
> > > attributes saved in the catalog from the last backup for the job
> specified
> > > on the *VerifyJob* directive. This level differs from the
> > > *VolumeToCatalog* level described above by the fact that it doesn't
> > > compare against a previous Verify job but against a previous backup.
> When
> > > you run this level, you must supply the verify options on your Include
> > > statements. Those options determine what attribute fields are compared.
> > >
> > > This command can be very useful if you have disk problems because it
> will
> > > compare the current state of your disk against the last successful
> backup,
> > > which may be several jobs.
> > >
> > >
> > >
> https://www.bacula.org/9.4.x-manuals/en/main/New_Features_in_7_4_0.html#SECTION00621000
> > >
> > >
> > >
> https://www.bacula.org/9.4.x-manuals/en/utility/Volume_Utility_Tools.html#SECTION00271000
> > >
> > > Best
> > > Pedro
> > >
> > > José Queiroz  escreveu no dia segunda, 12/08/2019
> à(s)
> > > 19:22:
> > >
> > >> Hi,
> > >>
> > >> I had a massive disk fault that corrupted some of my backup volumes.
> > >> As I'm very short on disk space, I want to find which of the volumes
> were
> > >> affected by the disk fault, to discard them.
> > >> Is there any tool I can use to do that?
> > >>
> > >> Thanks in advance.
> > >> ___
> > >> Bacula-users mailing list
> > >> Bacula-users@lists.sourceforge.net
> > >> https://lists.sourceforge.net/lists/listinfo/bacula-users
> > >>
> > >
> > >
> > > --
> > > --
> > > Cumprimentos,
> > >
> > > Pedro Oliveira
> > >
> > > Rua Antonio Botto | Nº 23 | 1º A | 2950-565 Quinta do Anjo
> > >
> > > tel +351 218 440 100 | mobile +351 916 111 464
> > >
> > > website   |
> > >   
> > > 
> > >
> > >
> > > *Aviso de Confidencialidade:* Esta mensagem é exclusivamente destinada
> ao
> > > seu destinatário, podendo conter informação CONFIDENCIAL, cuja
> divulgação
> > > está expressamente vedada nos termos da lei. Caso tenha recepcionado
> > > indevidamente esta mensagem, solicitamos-lhe que nos comunique esse
> mesmo
> > > facto por esta via ou para o telefone +351 916111464  devendo apagar o
> seu
> > > conteúdo de imediato.
> > >
> > > This message is intended exclusively for its addressee. It may contain
> > > CONFIDENTIAL information protected by law. If this message has been
> > > received by error, please notify us via e-mail or by telephone
> > > +351916111464 and delete it immediately.
> > >
> > >
> > >
> >
>
>
> ___
> 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] Bacula “No prior or suitable Full backup found in catalog”

[Martin Simmons]

"The same Job" means that you need a single Job definition (e.g. call it
ubuntu-hm-srv-1-Backup).  You then vary the level for each run (e.g. via the
schedule) to make Full and Incremental backups of that job.

__Martin



> On Fri, 23 Aug 2019 11:20:18 -0400, Leon K said:
> 
> Hello All,
> 
> Ubuntu 18.04
> Bacula 9.0.6-1build1
> 
> Bacula, for some reasons, fails to find a prior full backup job in its
> catalog, though a full backup job listed in the 'Job' table. Bacula-web
> shows that a full backup job successfully completed/terminated. Email
> notifications (job results) state the same.
> Example:
> 
> JobID:41 Level:Full Status:Success 8/19/2019
> JobID:43 Level:Incremental Status:Success 8/20/2019
> JobID:44 Level:Full Status:Success 8/21/2019
> 
> Email notification/log (JobID 41):
> 
> 19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Start Backup JobId 41, 
> Job=ubuntu-hm-srv-1-Full-Backup.2019-08-19_16.23.00_02
> 19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Created new 
> Volume="ub-hm-srv-1-Full-Bak-0015", Pool="ub-hm-srv-1-Full_Backups", 
> MediaType="Disk-Stor-1" in catalog.
> 19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Using Device "FileChgr1-Dev1" to 
> write.
> 19-Aug 16:23 ubuntu-hm-srv-1-sd JobId 41: Labeled new Volume 
> "ub-hm-srv-1-Full-Bak-0015" on File device "FileChgr1-Dev1" 
> (/mnt/backup/bacula/backup).
> 19-Aug 16:23 ubuntu-hm-srv-1-sd JobId 41: Wrote label to prelabeled Volume 
> "ub-hm-srv-1-Full-Bak-0015" on File device "FileChgr1-Dev1" 
> (/mnt/backup/bacula/backup)
> 19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Volume used once. Marking Volume 
> "ub-hm-srv-1-Full-Bak-0015" as Used.
> 
> 
> Email notification (JobID 45):
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: **No prior Full backup Job record 
> found.**
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: No prior or suitable Full backup 
> found in catalog. Doing FULL backup.
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Start Backup JobId 45, 
> Job=ubuntu-hm-srv-1-Incremental-Backup.2019-08-21_01.30.00_05
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: There are no more Jobs associated 
> with Volume "ub-hm-srv-1-Incr-Bak-0003". Marking it purged.
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: All records pruned from Volume 
> "ub-hm-srv-1-Incr-Bak-0003"; marking it "Purged"
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Recycled volume 
> "ub-hm-srv-1-Incr-Bak-0003"
> 21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Using Device "FileChgr1-Dev1" to 
> write.
> 
> 
> 
> According to this Bacula document
> 
> "I want an Incremental but Bacula runs it as a Full backup. Why?", "...If
> Bacula does not find a successful full backup, it proceeds to do one.
> Perhaps you canceled the full backup, or it terminated in error. In such
> cases, the full backup will not be successful..." It wasn't a case with my
> backups. They were all terminated successfully.
> 
> "...Full backup of the same Job..". What do they mean by the same Job?
> These jobs are all different (incremental, differential and full). If they
> mean the same FileSet, so yes, it wasn't changed and the same for all
> backup jobs in question.
> 
> Why JobID 43 found a prior full job JobID 41, but JobID 44 didn't?
> 
> I can post my configuration files if you wish.
> 
> Any idea?
> 
> Thanks.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Virus-free.
> www.avg.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


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

[Bacula-users] Bacula “No prior or suitable Full backup found in catalog”

[Leon K]

Hello All,

Ubuntu 18.04
Bacula 9.0.6-1build1

Bacula, for some reasons, fails to find a prior full backup job in its
catalog, though a full backup job listed in the 'Job' table. Bacula-web
shows that a full backup job successfully completed/terminated. Email
notifications (job results) state the same.
Example:

JobID:41 Level:Full Status:Success 8/19/2019
JobID:43 Level:Incremental Status:Success 8/20/2019
JobID:44 Level:Full Status:Success 8/21/2019

Email notification/log (JobID 41):

19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Start Backup JobId 41,
Job=ubuntu-hm-srv-1-Full-Backup.2019-08-19_16.23.00_02
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Created new
Volume="ub-hm-srv-1-Full-Bak-0015", Pool="ub-hm-srv-1-Full_Backups",
MediaType="Disk-Stor-1" in catalog.
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Using Device
"FileChgr1-Dev1" to write.
19-Aug 16:23 ubuntu-hm-srv-1-sd JobId 41: Labeled new Volume
"ub-hm-srv-1-Full-Bak-0015" on File device "FileChgr1-Dev1"
(/mnt/backup/bacula/backup).
19-Aug 16:23 ubuntu-hm-srv-1-sd JobId 41: Wrote label to prelabeled
Volume "ub-hm-srv-1-Full-Bak-0015" on File device "FileChgr1-Dev1"
(/mnt/backup/bacula/backup)
19-Aug 16:23 ubuntu-hm-srv-1-dir JobId 41: Volume used once. Marking
Volume "ub-hm-srv-1-Full-Bak-0015" as Used.


Email notification (JobID 45):
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: **No prior Full backup Job
record found.**
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: No prior or suitable Full
backup found in catalog. Doing FULL backup.
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Start Backup JobId 45,
Job=ubuntu-hm-srv-1-Incremental-Backup.2019-08-21_01.30.00_05
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: There are no more Jobs
associated with Volume "ub-hm-srv-1-Incr-Bak-0003". Marking it purged.
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: All records pruned from
Volume "ub-hm-srv-1-Incr-Bak-0003"; marking it "Purged"
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Recycled volume
"ub-hm-srv-1-Incr-Bak-0003"
21-Aug 01:30 ubuntu-hm-srv-1-dir JobId 45: Using Device
"FileChgr1-Dev1" to write.



According to this Bacula document

"I want an Incremental but Bacula runs it as a Full backup. Why?", "...If
Bacula does not find a successful full backup, it proceeds to do one.
Perhaps you canceled the full backup, or it terminated in error. In such
cases, the full backup will not be successful..." It wasn't a case with my
backups. They were all terminated successfully.

"...Full backup of the same Job..". What do they mean by the same Job?
These jobs are all different (incremental, differential and full). If they
mean the same FileSet, so yes, it wasn't changed and the same for all
backup jobs in question.

Why JobID 43 found a prior full job JobID 41, but JobID 44 didn't?

I can post my configuration files if you wish.

Any idea?

Thanks.










Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users