Re: [Bacula-users] Demora excessiva no backup

Heitor Faria Mon, 08 Apr 2019 14:08:33 -0700

Hello Marcio,

This list is for English users.

"01-abr 23:55 bkp-dir JobId 1660: No prior Full backup Job record found.

01-abr 23:55 bkp-dir JobId 1660: No prior or suitable Full backup found in catalog. Doing FULL backup.

03-abr 19:27 bkp-dir JobId 1660: Start Backup JobId 1660, Job=BD-BackupDiario.2019-04-01_23.55.00_58"

There is a huge time lapse between backup scheduled time and actual start time. Probably it was waiting different priority jobs execution or limited by any Bacula object Maximum Concurrent jobs.

Regards,

Heitor

Sent from TypeApp

On Apr 8, 2019, at 4:37 PM, Marcio Demetrio Bacci <marcioba...@gmail.com> wrote:

Boa tarde pessoal

Recentemente percebi que o Bacula está demorando muito para concluir um job de 200 GB, o que não é normal, principalmente porque só faço o backup em disco (LUN iSCSI apresentada ao servidor Bacula com conexões de 10Gbps).

O Servidor Bacula é virtual.

Seguem as informações do backup:

04-abr 07:08 bkp-dir JobId 1660: Bacula bkp-dir 9.2.1 (12Aug18):
Build OS: x86_64-pc-linux-gnu debian 9.5
JobId: 1660
Job: BD-BackupDiario.2019-04-01_23.55.00_58
Backup Level: Full (upgraded from Incremental)
Client: "bd-fd" 5.2.6 (21Feb12) x86_64-pc-linux-gnu,debian,jessie/sid
FileSet: "fileset-linux-servers" 2018-12-03 12:49:28
Pool: "PorDia" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 01-abr-2019 23:55:00
Start time: 03-abr-2019 19:27:22
End time: 04-abr-2019 07:08:14
Elapsed time: 11 hours 40 mins 52 secs
Priority: 80
FD Files Written: 3,267
SD Files Written: 3,267
FD Bytes Written: 204,564,923,472 (204.5 GB)
SD Bytes Written: 204,565,308,008 (204.5 GB)
Rate: 4864.6 KB/s
Software Compression: None
Comm Line Compression: None
Snapshot/VSS: no
Encryption: no
Accurate: no
Volume name(s): diario0075|diario0076|diario0077

Recentemente implementei deduplicação com o ZFS e não sei se há algum erro de configuração que possa causar essa lentidão, assim segue o trecho de código relacionado à deduplicação:
...
Device {
Name = FileStorageAligned
Device Type = Aligned
Media Type = File1
Archive Device = /zfs/Backup
LabelMedia = yes;
Random Access = Yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = no;
Maximum Concurrent Jobs = 1 #Não pode ser maior do que 1 para a deduplicacao
Minimum Block Size=0k
Maximum Block Size=128k
File Alignment=128k
Padding Size=512
Minimum Aligned Size=4096
}
...

Outra suspeita, poderia ser o tamanho máximo do volume que configurei nos Pools, conforme a seguir:

Pool {
Name = PorSemana
Pool Type = Backup
LabelFormat = semanal
Recycle = yes
AutoPrune = yes
Purge Oldest Volume = Yes
Volume Retention = 30 days
Maximum Volume Bytes = 100G
}

Pool {
Name = PorDia
Pool Type = Backup
LabelFormat = diario
Recycle = yes
AutoPrune = yes
Purge Oldest Volume = Yes
Volume Retention = 7 days
Maximum Volume Bytes = 100G
}

Pool {
Name = PorMes
Pool Type = Backup
LabelFormat = mensal
Recycle = yes
AutoPrune = yes
Purge Oldest Volume = Yes
Volume Retention = 365 days
Maximum Volume Bytes = 100G
}

# Scratch pool definition
Pool {
Name = Scratch
Pool Type = Backup
}

Por fim, segue um trecho no meu arquivo de log bacula.log

01-abr 23:55 bkp-dir JobId 1660: No prior Full backup Job record found.
01-abr 23:55 bkp-dir JobId 1660: No prior or suitable Full backup found in catalog. Doing FULL backup.
03-abr 19:27 bkp-dir JobId 1660: Start Backup JobId 1660, Job=BD-BackupDiario.2019-04-01_23.55.00_58
03-abr 19:27 bkp-dir JobId 1660: Using Device "FileStorageAligned" to write.
03-abr 19:27 bkp-sd JobId 1660: Volume "diario0075" previously written, moving to end of data.
03-abr 20:09 bkp-sd JobId 1660: User defined maximum volume size 107,374,182,400 will be exceeded on device "FileStorageAligned" (/zfs/Backup).
Marking Volume "diario0075" as Full.
03-abr 20:09 bkp-sd JobId 1660: End of medium on Volume "diario0075" Bytes=107,374,045,373 Blocks=819,199 at 03-abr-2019 20:09.
03-abr 20:09 bkp-dir JobId 1660: Created new Volume="diario0076", Pool="PorDia", MediaType="File1" in catalog.
03-abr 20:09 bkp-sd JobId 1660: Labeled new Volume "diario0076" on Aligned device "FileStorageAligned" (/zfs/Backup).
03-abr 20:09 bkp-sd JobId 1660: Wrote label to prelabeled Volume "diario0076" on Aligned device "FileStorageAligned" (/zfs/Backup)
03-abr 20:09 bkp-sd JobId 1660: New volume "diario0076" mounted on device "FileStorageAligned" (/zfs/Backup) at 03-abr-2019 20:09.
04-abr 02:23 bkp-sd JobId 1660: User defined maximum volume size 107,374,182,400 will be exceeded on device "FileStorageAligned" (/zfs/Backup).
Marking Volume "diario0076" as Full.
04-abr 02:23 bkp-sd JobId 1660: End of medium on Volume "diario0076" Bytes=107,374,162,980 Blocks=819,199 at 04-abr-2019 02:23.
04-abr 02:23 bkp-dir JobId 1660: Created new Volume="diario0077", Pool="PorDia", MediaType="File1" in catalog.
04-abr 02:23 bkp-sd JobId 1660: Labeled new Volume "diario0077" on Aligned device "FileStorageAligned" (/zfs/Backup).
04-abr 02:23 bkp-sd JobId 1660: Wrote label to prelabeled Volume "diario0077" on Aligned device "FileStorageAligned" (/zfs/Backup)
04-abr 02:23 bkp-sd JobId 1660: New volume "diario0077" mounted on device "FileStorageAligned" (/zfs/Backup) at 04-abr-2019 02:23.
04-abr 07:08 BD-fd JobId 1660: Could not stat "/var/backups/.data/etcadm_BD_Diario_190402.tar.gz": ERR=No such file or directory
04-abr 07:08 bkp-sd JobId 1660: Elapsed time=11:40:50, Transfer rate=4.864 M Bytes/second
04-abr 07:08 bkp-sd JobId 1660: Sending spooled attrs to the Director. Despooling 676,718 bytes ...
04-abr 07:08 bkp-dir JobId 1660: Bacula bkp-dir 9.2.1 (12Aug18):

Alguém poderia me dar uma ajuda?

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

Re: [Bacula-users] Demora excessiva no backup

Reply via email to