Re: VirtualFull e client availability...

Mandi! Bill Arlofski via Bacula-users
  In chel di` si favelave...

Sorry for the late answer.

In the meantime i've done some other checks, and seems that things are a bit
complex then that.

For example, another client configured exactly on the same way works as
expected; eg, fail incremental if not available:

 13-Dec 11:05 lnfbacula-dir JobId 31743: Start Backup JobId 31743, Job=FVG-SV-Hinata.2024-12-13_08.00.00_37
 13-Dec 11:05 lnfbacula-dir JobId 31743: Error: bsockcore.c:285 gethostbyname() for host "hinata.dyn.sv.lnf.it" failed: ERR=Name or service not known
   Job:                    FVG-SV-Hinata.2024-12-13_08.00.00_37
   Client:                 "fvg-sv-hinata-fd" 7.4.4 (28Sep16) Microsoft Professional (build 9200), 64-bit,Cross-compile,Win64
   Pool:                   "FVG-SV-HinataFilePool" (From Job resource)
 13-Dec 11:05 lnfbacula-dir JobId 31743: Rescheduled Job FVG-SV-Hinata.2024-12-13_08.00.00_37 at 13-Dec-2024 11:05 to re-run in 1800 seconds (13-Dec-2024 11:35).
 13-Dec 11:05 lnfbacula-dir JobId 31743: Job FVG-SV-Hinata.2024-12-13_08.00.00_37 waiting 1800 seconds for scheduled start time.
 13-Dec 11:35 lnfbacula-dir JobId 31743: Start Backup JobId 31743, Job=FVG-SV-Hinata.2024-12-13_08.00.00_37
   Job:          t connect to Client: fvg-sv-hinata-fd on hinata.dyn.sv.lnf.it:9102. ERR=Connection timed out
 13-Dec 11:40 lnfbacula-dir JobId 31743: Fatal error: bsockcore.c:209 Unable to connect to Client: fvg-sv-hinata-fd on hinata.dyn.sv.lnf.it:9102. ERR=Interrupted system call
   Job:                    FVG-SV-Hinata.2024-12-13_08.00.00_37
   Client:                 "fvg-sv-hinata-fd" 7.4.4 (28Sep16) Microsoft Professional (build 9200), 64-bit,Cross-compile,Win64
   Pool:                   "FVG-SV-HinataFilePool" (From Job resource)
 13-Dec 11:41 lnfbacula-dir JobId 31743: Rescheduled Job FVG-SV-Hinata.2024-12-13_08.00.00_37 at 13-Dec-2024 11:41 to re-run in 1800 seconds (13-Dec-2024 12:11).
 13-Dec 11:41 lnfbacula-dir JobId 31743: Job FVG-SV-Hinata.2024-12-13_08.00.00_37 waiting 1800 seconds for scheduled start time.
 13-Dec 12:11 lnfbacula-dir JobId 31743: Start Backup JobId 31743, Job=FVG-SV-Hinata.2024-12-13_08.00.00_37
 13-Dec 12:11 lnfbacula-dir JobId 31743: Error: bsockcore.c:285 gethostbyname() for host "hinata.dyn.sv.lnf.it" failed: ERR=Name or service not known
  Job:                    FVG-SV-Hinata.2024-12-13_08.00.00_37
  Client:                 "fvg-sv-hinata-fd" 7.4.4 (28Sep16) Microsoft Professional (build 9200), 64-bit,Cross-compile,Win64
  Pool:                   "FVG-SV-HinataFilePool" (From Job resource)

but work virtualfull:

 15-Dec 12:17 lnfbacula-dir JobId 31840: Start Virtual Backup JobId 31840, Job=FVG-SV-Hinata.2024-12-15_08.00.00_49
 15-Dec 12:17 svpve3-sd JobId 31840: Ready to read from volume "Hinata_0017" on File device "MultiFileStorage1" (/rpool-backup/bacula).
 15-Dec 12:17 svpve3-sd JobId 31840: Recycled volume "Hinata_0002" on File device "MultiFileStorage2" (/rpool-backup/bacula), all previous data lost.
 15-Dec 12:17 lnfbacula-dir JobId 31840: Max Volume jobs=1 exceeded. Marking Volume "Hinata_0002" as Used.
 15-Dec 12:17 svpve3-sd JobId 31840: Forward spacing Volume "Hinata_0017" to addr=235
 15-Dec 12:17 svpve3-sd JobId 31840: End of Volume "Hinata_0017" at addr=1015020 on device "MultiFileStorage1" (/rpool-backup/bacula).
   Job:                    FVG-SV-Hinata.2024-12-15_08.00.00_49
   Client:                 "fvg-sv-hinata-fd" 7.4.4 (28Sep16) Microsoft Professional (build 9200), 64-bit,Cross-compile,Win64
   Pool:                   "FVG-SV-HinataFilePool" (From Pool's NextPool resource)
   Volume name(s):         Hinata_0002
 15-Dec 12:17 lnfbacula-dir JobId 31840: shell command: run AfterJob "/etc/bacula/scripts/deleteFailedJobs SVPVE3FileMulti FVG-SV-HinataFilePool fvg-sv-hinata-fd "Virtual Full" 31840"
 15-Dec 12:17 lnfbacula-dir JobId 31840: AfterJob: DEBUG: Truncate Volume Hinata_0017


So seems it is not an 'dynamic ip' trouble.


Configuration is:

Client {
        Name = fvg-sv-hinata-fd
        Description = "Hinata Bacula File Daemon"
        Address = hinata.dyn.sv.lnf.it
        FDPort = 9102
        Password = "Unknown ;-)"
        Catalog = BaculaLNF
        Maximum Concurrent Jobs = 1
        File Retention = 50 years
        Job Retention = 50 years
}

Pool {
        Name = FVG-SV-HinataFilePool
        Description = "Hinata File Pool"
        Pool Type = Backup
        NextPool = FVG-SV-HinataFilePool
        Storage = SVPVE3FileMulti
        Maximum Volume Jobs = 1
        Recycle = yes
        AutoPrune = yes
        Action On Purge = Truncate
}

Job {
        Name = FVG-SV-Hinata
        Description = "Backup del client Hinata"
        JobDefs = DefaultJob
        Storage = SVPVE3FileMulti
        Pool = FVG-SV-HinataFilePool
        Messages = StandardClient
        Schedule = WeeklyClient
        Reschedule On Error = yes
        Reschedule Interval = 30 minutes
        Reschedule Times = 8
        Max Run Sched Time = 8 hours
        Accurate = yes
        Backups To Keep = 10
        Delete Consolidated Jobs = yes
        Run After Job = "/etc/bacula/scripts/deleteFailedJobs %w %p %c \"%l\" %i"
        Client = fvg-sv-hinata-fd
        FileSet = CyberSabotsStd
        Write Bootstrap = "/var/lib/bacula/FVG-SV-Hinata.bsr"
}

'FVG-SV-HinataFilePool' is a file pool with 20 volumes; every mon-fri i do
an incremental; on sunday i do a VirtualFull that 'pack' incrementals
and keep 10 backups.

The script '/etc/bacula/scripts/deleteFailedJobs' simply cleanup failed jobs
and volumes, to prevent exausting them.


Thanks.

--