When I want to restore from the webui, the clients' backups come out blank!

105 views
Skip to first unread message

Rodrigo Yesi

unread,
Jan 29, 2025, 6:27:58 AMJan 29
to bareos-users
Hello good morning. As you can see in the images, certain backups work. The webui marks them as correct for the backup, but when I want to do a restore. In some clients it does not show them to me, as in the case of MFS. It has 2 backups made and both are left blank. in the case of MANTIS, if you see the image. The back from the 28th works, but the one from the 29th doesn't! I already gave more resources to postgresql-14 and still nothing.
MFS nothing 1.26 tb on data.png
respaldo 28 Mantis OK.png
respaldo 29 Mantis Bad.png

Rodrigo Yesi

unread,
Jan 29, 2025, 10:01:54 PMJan 29
to bareos-users
this is to day, its ok, but dont see in web


29-ene 21:00 bareos-dir JobId 38: Version: 24.0.1~pre27.250812184 (24 January 2025) Red Hat Enterprise Linux release 9.5 (Plow) 29-ene 21:00 bareos-dir JobId 38: Start Backup JobId 38, Job=Backup-AVY.2025-01-29_21.00.00_03

29-ene 21:00 bareos-dir JobId 38: Connected Storage daemon at 192.168.12.27:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 29-ene 21:00 bareos-dir JobId 38:  Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 29-ene 21:00 bareos-dir JobId 38: Probing client protocol... (result will be saved until config reload) 29-ene 21:00 bareos-dir JobId 38: Connected Client: AMB-SVR-AVY-fd at 192.168.6.91:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

29-ene 21:00 bareos-dir JobId 38:    Handshake: Immediate TLS

29-ene 21:00 bareos-dir JobId 38:  Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 29-ene 21:00 bareos-sd JobId 38: Using just in time reservation for job 38 29-ene 21:00 bareos-dir JobId 38: Using Device "JustInTime Device" to write.

29-ene 20:59 amb-svr-avy-fd JobId 38: Created 24 wildcard excludes from FilesNotToBackup Registry key 29-ene 20:59 amb-svr-avy-fd JobId 38: Connected Storage daemon at 192.168.12.27:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 29-ene 20:59 amb-svr-avy-fd JobId 38:  Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 29-ene 21:00 bareos-sd JobId 38: Version: 24.0.1~pre27.250812184 (24 January 2025) Red Hat Enterprise Linux release 9.5 (Plow) 29-ene 21:00 amb-svr-avy-fd JobId 38: Generate VSS snapshots. Driver="Win64 VSS"

29-ene 21:00 amb-svr-avy-fd JobId 38: VolumeMountpoints are not processed as onefs = yes.

29-ene 21:00 amb-svr-avy-fd JobId 38: (C:\)\\?\Volume{2077a78b-2dee-4fbe-b9a2-ab119663189b}\ -> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5

29-ene 21:00 amb-svr-avy-fd JobId 38: Version: 24.0.1~pre27.250812184 (24 January 2025) Microsoft Windows Server 2012 Standard Edition (build 9200), 64-bit 29-ene 21:00 bareos-sd JobId 38: JustInTime Reservation: Finding drive to reserve.

29-ene 21:00 bareos-dir JobId 38: Created new Volume "VolAVY-0041" in catalog.

29-ene 21:00 bareos-sd JobId 38: Using Device "MyDevice2" (/Storage2) to write.

29-ene 21:00 bareos-sd JobId 38: Labeled new Volume "VolAVY-0041" on device "MyDevice2" (/Storage2).

29-ene 21:00 bareos-sd JobId 38: Moving to end of data on volume "VolAVY-0041"

29-ene 21:00 bareos-sd JobId 38: Ready to append to end of Volume "VolAVY-0041" size=221 29-ene 21:00 bareos-dir JobId 38: Max Volume jobs=1 exceeded. Marking Volume "VolAVY-0041" as Used.

29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 amb-svr-avy-fd JobId 38: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) 29-ene 21:52 bareos-sd JobId 38: Releasing device "MyDevice2" (/Storage2).

29-ene 21:52 bareos-sd JobId 38: Elapsed time=00:52:25, Transfer rate=2.321 M Bytes/second 29-ene 21:52 bareos-dir JobId 38: Insert of attributes batch table with 70834 entries start 29-ene 21:52 bareos-dir JobId 38: Insert of attributes batch table done 29-ene 21:52 bareos-dir JobId 38: Bareos bareos-dir 24.0.1~pre27.250812184 (24Jan25):

  Build OS:               Red Hat Enterprise Linux release 9.5 (Plow)

  JobId:                  38

  Job:                    Backup-AVY.2025-01-29_21.00.00_03

  Backup Level:           Full

  Client:                 "AMB-SVR-AVY-fd" 24.0.1~pre27.250812184 (24Jan25) Microsoft Windows Server 2012 Standard Edition (build 9200), 64-bit,Cross-compile

  FileSet:                "MyFileSetAVY" 2025-01-24 09:03:38

  Pool:                   "Pool-AVY" (From Run Pool override)

  Catalog:                "MyCatalog" (From Client resource)

  Storage:                "MyStorage2" (From run override)

  Scheduled time:         29-ene-2025 21:00:00

  Start time:             29-ene-2025 21:00:00

  End time:               29-ene-2025 21:52:25

  Elapsed time:           52 mins 25 secs

  Priority:               10

  Allow Mixed Priority:   no

  FD Files Written:       70,835

  SD Files Written:       70,835

  FD Bytes Written:       7,284,102,133 (7.284 GB)

  SD Bytes Written:       7,300,803,636 (7.300 GB)

  Rate:                   2316.1 KB/s

  Software Compression:   None

  VSS:                    yes

  Encryption:             no

  Accurate:               no

  Volume name(s):         VolAVY-0041

  Volume Session Id:      2

  Volume Session Time:    1738150563

  Last Volume Bytes:      7,303,834,619 (7.303 GB)

  Non-fatal FD errors:    0

  SD Errors:              0

  FD termination status:  OK

  SD termination status:  OK

  Bareos binary info:     Bareos community build (UNSUPPORTED): Get professional support from https://www.bareos.com

  Job triggered by:       Scheduler

  Termination:            Backup OK

 

29-ene 21:52 bareos-dir JobId 38: Begin pruning Jobs older than 3 months .

29-ene 21:52 bareos-dir JobId 38: No jobids found to be purged 29-ene 21:52 bareos-dir JobId 38: Begin pruning Files.

29-ene 21:52 bareos-dir JobId 38: No Files found to prune.

29-ene 21:52 bareos-dir JobId 38: End auto prune.

2025-01-30 00_00_44-.png

Bruno Friedmann (bruno-at-bareos)

unread,
Jan 30, 2025, 4:58:53 AMJan 30
to bareos-users
You might want to cleanup your bvfs_cache and try to regenerate it 

bconsole <<< ".bvfs_clear_cache yes"

then recreate it completely

bconsole <<< ".bvfs_update"

Rodrigo Yesi

unread,
Jan 30, 2025, 9:12:00 AMJan 30
to bareos-users
Jan 30 10:54 bareos-dir JobId 0: Fatal error: cats/bvfs.cc:247 cats/bvfs.cc:247 query INSERT INTO PathVisibility (PathId, JobId) SELECT a.PathId,27 FROM (SELECT DISTINCT h . PPathId AS PathId FROM PathHierarchy AS h JOIN PathVisibili ty AS p ON (h.PathId=p.PathId) WHERE p.JobId=27) AS LEFT JOIN PathVisibility AS b ON (b.JobId=27 AND a.PathId = b .PathId) WHERE b.PathId IS NULL failed : ERROR: canceling the sentence because it was done? the waiting time for sentences Jan 30 10:54 bareos-dir JobId 0: Error: cats/bvfs.cc:251 cats/bvfs.cc:251 update UPDATE Job SET HasCache=1 WHERE Job Id=27 failed: ERROR: transaction aborted, orders will be ignored until the end of the transaction block

Rodrigo Yesi

unread,
Jan 30, 2025, 9:31:22 AMJan 30
to bareos-users
Hello, I increased the timeout time and it completed, but it still shows blank in the web ui.

Bruno Friedmann (bruno-at-bareos)

unread,
Jan 30, 2025, 9:33:57 AMJan 30
to bareos-users
You may do this in bconsole, so there's no timeout when recreating the bvfs cache.

Rodrigo Yesi

unread,
Jan 30, 2025, 1:36:58 PMJan 30
to bareos-users
 
I did it, but it still doesn't show the files for the restore.

Bruno Friedmann (bruno-at-bareos)

unread,
Feb 3, 2025, 3:39:24 AMFeb 3
to bareos-users
Is it able to show the restore files in bconsole ?

Rodrigo Yesi

unread,
Feb 3, 2025, 1:47:34 PMFeb 3
to bareos-users
Yes, from bconsole I see all of them, from all the clients! I'm currently seeing it. I had to give more resources to the DB, I had a timeout originating from the web to the DB. I increased the time, I gave more resources to the DB. and now I see them correctly. I don't know if it influences, but I had old backs from the previous version of the scales that were 18.x.x.x. Will you have wanted to read those backs and bug?

Bruno Friedmann (bruno-at-bareos)

unread,
Feb 4, 2025, 3:30:15 AMFeb 4
to bareos-users
What I know is that you need to carefully size and tune the PostgreSQL database depending of your hardware and of course size of files/jobs in.
it is also often recommended to have 50% of occupied space free for large operation like generating bvfs cache for large jobs.

I've seen numerous people that get transient error because PG has just not enough space to write the temp result, and just drop the query ( then in a microsecond the space used is free again) which make it hard to discover.

Rodrigo Yesi

unread,
Feb 4, 2025, 8:49:04 PMFeb 4
to bareos-users
Excellent, thank you very much. one last question. I need the client for an Ubuntu 14 tls. I tried to compile it from the server but the version is obsolete, I compiled it in another environment (centos 9 stream) to pass it on and it didn't work, something is always missing. My question is through a "donation" can't you give me a single download of the bareos-fd version (client) compatible with my Ubuntu 14 tls?

Rodrigo Yesi

unread,
Feb 4, 2025, 8:50:21 PMFeb 4
to bareos-users
I don't want a subscription, support or anything.
Only download the client for the Ubuntu 14 TLS version

Bruno Friedmann (bruno-at-bareos)

unread,
Feb 5, 2025, 4:02:05 AMFeb 5
to bareos-users
You might want to ask sales at bareos.com for a quote to get access to such binaries

Bruno Friedmann (bruno-at-bareos)

unread,
Feb 5, 2025, 4:04:56 AMFeb 5
to bareos-users
Or you might want to try to build bareos-fd version 18.2 on a xubuntu 14 by yourself.
Any more recent version have great chance to fail.
Unfortunately for you that Ubuntu version is too old (openssl 1.0x) otherwise you would have give a try to the ULC (Universal client) 

Rodrigo Yesi

unread,
Feb 9, 2025, 12:24:00 PMFeb 9
to bareos-users
why happen this??


6
2025-02-09 14:13:27
bareos-sd JobId 95: Elapsed time=00:33:34, Transfer rate=0 Bytes/second

75
2025-02-09 14:13:18
DAA-VSR-MFS-fd JobId 95: Fatal error: filed/backup.cc:1413 Network send error to SD. ERR=Input/output error (errno=5 | win_error=0x00000000)

74
2025-02-09 14:13:18
DAA-VSR-MFS-fd JobId 95: Error: lib/bsock_tcp.cc:469 Wrote 262246 (mlen: 262242) bytes to Storage daemon:192.168.12.27:9103, but only 147456 accepted.

73
2025-02-09 14:13:27
bareos-sd JobId 95: Releasing device "MyDevice3" (/Storage3).

72
2025-02-09 14:13:27
bareos-sd JobId 95: Fatal error: Job 95 canceled.

71
2025-02-09 14:10:18
bareos-sd JobId 95: Warning: stored/mount.cc:246 Open device "MyDevice3" (/Storage3) Volume "VolMFS-0087" failed: ERR=stored/dev.cc:602 Could not open: /Storage3/VolMFS-0087, ERR=No existe el fichero o el directorio


70
2025-02-09 14:10:18
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

69
2025-02-09 14:05:18
bareos-sd JobId 95: Warning: stored/mount.cc:246 Open device "MyDevice3" (/Storage3) Volume "VolMFS-0087" failed: ERR=stored/dev.cc:602 Could not open: /Storage3/VolMFS-0087, ERR=No existe el fichero o el directorio


68
2025-02-09 14:05:18
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

67
2025-02-09 14:00:18
bareos-sd JobId 95: Warning: stored/mount.cc:246 Open device "MyDevice3" (/Storage3) Volume "VolMFS-0087" failed: ERR=stored/dev.cc:602 Could not open: /Storage3/VolMFS-0087, ERR=No existe el fichero o el directorio


66
2025-02-09 14:00:18
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

65
2025-02-09 13:55:18
bareos-sd JobId 95: Warning: stored/mount.cc:246 Open device "MyDevice3" (/Storage3) Volume "VolMFS-0087" failed: ERR=stored/dev.cc:602 Could not open: /Storage3/VolMFS-0087, ERR=No existe el fichero o el directorio


64
2025-02-09 13:55:18
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

63
2025-02-09 13:50:18
bareos-sd JobId 95: Warning: stored/mount.cc:246 Open device "MyDevice3" (/Storage3) Volume "VolMFS-0087" failed: ERR=stored/dev.cc:602 Could not open: /Storage3/VolMFS-0087, ERR=No existe el fichero o el directorio


62
2025-02-09 13:50:18
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

61
2025-02-09 13:45:18
bareos-sd JobId 95: Warning: stored/mount.cc:246 Open device "MyDevice3" (/Storage3) Volume "VolMFS-0087" failed: ERR=stored/dev.cc:602 Could not open: /Storage3/VolMFS-0087, ERR=No existe el fichero o el directorio


60
2025-02-09 13:45:18
bareos-dir JobId 95: Recycled volume "VolMFS-0087"

59
2025-02-09 13:45:18
bareos-dir JobId 95: All records pruned from Volume "VolMFS-0087"; marking it "Purged"

58
2025-02-09 13:45:18
bareos-dir JobId 95: There are no more Jobs associated with Volume "VolMFS-0087". Marking it purged.

57
2025-02-09 13:45:14
bareos-dir JobId 95: Purging the following 1 JobIds: 50

56
2025-02-09 13:45:14
bareos-dir JobId 95: Volume "VolMFS-0087" has Volume Retention of 604800 sec. and has 1 jobs that will be pruned

55
2025-02-09 13:45:14
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

54
2025-02-09 13:40:14
bareos-sd JobId 95: Please mount append Volume "VolMFS-0085" or label a new one for:
Job: Backup-MFS.2025-02-09_13.39.50_07
Storage: "MyDevice3" (/Storage3)
Pool: Pool-MFS
Media type: File

53
2025-02-09 13:40:14
bareos-sd JobId 95: Marking Volume "VolMFS-0085" in Error in Catalog.

52
2025-02-09 13:40:14
bareos-sd JobId 95: Error: Bareos cannot write on disk Volume "VolMFS-0085" because: The sizes do not match! Volume=221 Catalog=222

51
2025-02-09 13:40:14
bareos-sd JobId 95: Moving to end of data on volume "VolMFS-0085"

50
2025-02-09 13:40:14
bareos-sd JobId 95: Labeled new Volume "VolMFS-0085" on device "MyDevice3" (/Storage3).

49
2025-02-09 13:40:14
bareos-dir JobId 95: Recycled volume "VolMFS-0085"

48
2025-02-09 13:40:14
bareos-dir JobId 95: All records pruned from Volume "VolMFS-0085"; marking it "Purged"

47
2025-02-09 13:40:14
bareos-dir JobId 95: There are no more Jobs associated with Volume "VolMFS-0085". Marking it purged.

46
2025-02-09 13:40:14
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

45
2025-02-09 13:40:14
bareos-sd JobId 95: Marking Volume "VolMFS-0084" in Error in Catalog.

44
2025-02-09 13:40:14
bareos-sd JobId 95: Error: Bareos cannot write on disk Volume "VolMFS-0084" because: The sizes do not match! Volume=221 Catalog=222

43
2025-02-09 13:40:14
bareos-sd JobId 95: Moving to end of data on volume "VolMFS-0084"

42
2025-02-09 13:40:14
bareos-sd JobId 95: Labeled new Volume "VolMFS-0084" on device "MyDevice3" (/Storage3).

41
2025-02-09 13:40:14
bareos-dir JobId 95: Recycled volume "VolMFS-0084"

40
2025-02-09 13:40:14
bareos-dir JobId 95: All records pruned from Volume "VolMFS-0084"; marking it "Purged"

39
2025-02-09 13:40:14
bareos-dir JobId 95: There are no more Jobs associated with Volume "VolMFS-0084". Marking it purged.

38
2025-02-09 13:40:13
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

37
2025-02-09 13:40:13
bareos-sd JobId 95: Marking Volume "VolMFS-0083" in Error in Catalog.

36
2025-02-09 13:40:13
bareos-sd JobId 95: Error: Bareos cannot write on disk Volume "VolMFS-0083" because: The sizes do not match! Volume=221 Catalog=222

35
2025-02-09 13:40:13
bareos-sd JobId 95: Moving to end of data on volume "VolMFS-0083"

34
2025-02-09 13:40:13
bareos-sd JobId 95: Labeled new Volume "VolMFS-0083" on device "MyDevice3" (/Storage3).

33
2025-02-09 13:40:13
bareos-dir JobId 95: Recycled volume "VolMFS-0083"

32
2025-02-09 13:40:13
bareos-dir JobId 95: All records pruned from Volume "VolMFS-0083"; marking it "Purged"

31
2025-02-09 13:40:13
bareos-dir JobId 95: There are no more Jobs associated with Volume "VolMFS-0083". Marking it purged.

30
2025-02-09 13:40:13
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

29
2025-02-09 13:40:13
bareos-sd JobId 95: Marking Volume "VolMFS-0006" in Error in Catalog.

28
2025-02-09 13:40:13
bareos-sd JobId 95: Error: Bareos cannot write on disk Volume "VolMFS-0006" because: The sizes do not match! Volume=221 Catalog=443

27
2025-02-09 13:40:13
bareos-sd JobId 95: Moving to end of data on volume "VolMFS-0006"

26
2025-02-09 13:40:13
bareos-sd JobId 95: Labeled new Volume "VolMFS-0006" on device "MyDevice3" (/Storage3).

25
2025-02-09 13:40:13
bareos-sd JobId 95: Error: stored/mount.cc:815 Hey!!!!! WroteVol non-zero !!!!!

24
2025-02-09 13:40:13
bareos-sd JobId 95: Marking Volume "VolMFS-0005" in Error in Catalog.

23
2025-02-09 13:40:13
bareos-sd JobId 95: Error: Bareos cannot write on disk Volume "VolMFS-0005" because: The sizes do not match! Volume=221 Catalog=16987980205

22
2025-02-09 13:40:13
bareos-sd JobId 95: Moving to end of data on volume "VolMFS-0005"

21
2025-02-09 13:40:13
bareos-sd JobId 95: Labeled new Volume "VolMFS-0005" on device "MyDevice3" (/Storage3).

20
2025-02-09 13:40:13
bareos-sd JobId 95: Using Device "MyDevice3" (/Storage3) to write.

19
2025-02-09 13:40:13
bareos-sd JobId 95: JustInTime Reservation: Finding drive to reserve.

18
2025-02-09 13:40:04
DAA-VSR-MFS-fd JobId 95: Version: 24.0.1~pre27.250812184 (24 January 2025) Microsoft Windows Server 2012 Standard Edition (build 9200), 64-bit

17
2025-02-09 13:40:04
DAA-VSR-MFS-fd JobId 95: (E:\)\\?\Volume{51e715ad-34bf-11e9-80b4-000c29a6f8ad}\ -> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy27

16
2025-02-09 13:39:48
DAA-VSR-MFS-fd JobId 95: VolumeMountpoints are not processed as onefs = yes.

15
2025-02-09 13:39:48
DAA-VSR-MFS-fd JobId 95: Generate VSS snapshots. Driver="Win64 VSS"

14
2025-02-09 13:39:53
bareos-sd JobId 95: Version: 24.0.1~pre27.250812184 (24 January 2025) Red Hat Enterprise Linux release 9.5 (Plow)

13
2025-02-09 13:39:43
DAA-VSR-MFS-fd JobId 95: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

12
2025-02-09 13:39:43
DAA-VSR-MFS-fd JobId 95: Connected Storage daemon at 192.168.12.27:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

11
2025-02-09 13:39:43
DAA-VSR-MFS-fd JobId 95: Created 25 wildcard excludes from FilesNotToBackup Registry key

10
2025-02-09 13:39:53
bareos-dir JobId 95: Using Device "JustInTime Device" to write.

9
2025-02-09 13:39:53
bareos-sd JobId 95: Using just in time reservation for job 95

8
2025-02-09 13:39:52
bareos-dir JobId 95: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

7
2025-02-09 13:39:52
bareos-dir JobId 95: Handshake: Immediate TLS

6
2025-02-09 13:39:52
bareos-dir JobId 95: Connected Client: DAA-VSR-MFS-fd at 192.168.12.69:9102, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

5
2025-02-09 13:39:52
bareos-dir JobId 95: Probing client protocol... (result will be saved until config reload)

4
2025-02-09 13:39:52
bareos-dir JobId 95: Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

3
2025-02-09 13:39:52
bareos-dir JobId 95: Connected Storage daemon at 192.168.12.27:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3

2
2025-02-09 13:39:52
bareos-dir JobId 95: Start Backup JobId 95, Job=Backup-MFS.2025-02-09_13.39.50_07

1
2025-02-09 13:39:52
bareos-dir JobId 95: Version: 24.0.1~pre27.250812184 (24 January 2025) Red Hat Enterprise Linux release 9.5 (Plow)




all the time happen with same client.

Sebastian Sura

unread,
Feb 10, 2025, 1:48:30 AMFeb 10
to bareos...@googlegroups.com

Hi Rodrigo,

it looks like a volume that bareos expected to exist was deleted.  You should not manually delete volumes otherwise errors such as these may pop up.
If you need to delete volumes for some reason, do not forget to also delete that volume from the catalog via the `delete` console command, see here:
* https://docs.bareos.org/TasksAndConcepts/BareosConsole.html
* https://docs.bareos.org/TasksAndConcepts/VolumeManagement.html

Kind Regards
Sebastian Sura

09.02.25 um 18:24 schrieb Rodrigo Yesi:

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bareos-users/85308e27-12b3-40f8-9476-e3b30de73bd4n%40googlegroups.com.
-- 
 Sebastian Sura                  sebasti...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-0
 https://www.bareos.com
 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz
Reply all
Reply to author
Forward
0 new messages