VirtualFull e client availability...

I use virtual full backup to 'consolidate' backups on weekend; AFAI've
understood,  virtual full backups are a 'sd only' things.

But if client is not abailable (common for that client, on weekend),
also a virtualfull backup fail:

05-Dec 15:33 lnfbacula-dir JobId 31268: Rescheduled Job FVG-PP-HFA3-1.2024-12-05_15.33.41_23 at 05-Dec-2024 15:33 to re-run in 1800 seconds (05-Dec-2024 16:03).
05-Dec 15:33 lnfbacula-dir JobId 31268: Cancelling duplicate JobId=31257.
05-Dec 15:33 lnfbacula-dir JobId 31268: Error: bsockcore.c:285 gethostbyname() for host "850-16268.dyn.pp.lnf.it" failed: ERR=Name or service not known
05-Dec 15:33 lnfbacula-dir JobId 31268: Failed to connect to File daemon.
05-Dec 15:33 lnfbacula-dir JobId 31268: 3904 Job FVG-PP-HFA3-1.2024-12-05_08.00.00_31 not found.
05-Dec 15:33 lnfbacula-dir JobId 31268: Error: bsockcore.c:285 gethostbyname() for host "850-16268.dyn.pp.lnf.it" failed: ERR=Name or service not known
05-Dec 15:33 lnfbacula-dir JobId 31268: Failed to connect to File daemon.
05-Dec 15:33 lnfbacula-dir JobId 31268: 3904 Job FVG-PP-HFA3-1.2024-12-05_08.00.00_31 not found.
05-Dec 15:33 lnfbacula-dir JobId 31268: Error: Bacula lnfbacula-dir 9.4.2 (04Feb19):
  Build OS:               x86_64-pc-linux-gnu debian 10.5
  JobId:                  31268
  Job:                    FVG-PP-HFA3-1.2024-12-05_15.33.41_23
  Backup Level:           Virtual Full
  Client:                 "fvg-pp-hfa3-1-fd" 7.4.4 (28Sep16) Microsoft  (build 9200), 64-bit,Cross-compile,Win64
  FileSet:                "HFA3Std" 2022-09-30 08:00:00
  Pool:                   "FVG-PP-HFA3-1FilePool" (From Job Pool's NextPool resource)
  Catalog:                "BaculaLNF" (From Client resource)
  Storage:                "PPPVE3FileMulti" (From Job resource)
  Scheduled time:         05-Dec-2024 15:33:40
  Start time:             05-Dec-2024 15:33:44
  End time:               05-Dec-2024 15:33:44
  Elapsed time:           1 sec
  Priority:               10
  SD Files Written:       0
  SD Bytes Written:       0 (0 B)
  Rate:                   0.0 KB/s
  Volume name(s):         
  Volume Session Id:      0
  Volume Session Time:    0
  Last Volume Bytes:      0 (0 B)
  SD Errors:              0
  SD termination status:  
  Termination:            *** Backup Error ***


Seems that hapens on client that areon dynamic DNS, so effectively client
does not exist in DNS, not 'does not ping'.


Apart putting clients on static addresses to they exist, there's something i
can do?


Thanks.

--