I want the volume to be overwritten after a specified retention period, 
deleting older jobs. I thought this would work with this pool 
configuration, but overwriting the existing volume doesn't happen even 
though its retention period has already expired. Please tell me how to fix 
this

вторник, 28 ноября 2023 г. в 17:23:44 UTC+6, Ramil: 

> Hello!
> Why is the volume not overwritten with this pool configuration?
> I'm using Bareos v.22.1.2 
>
> Pool {
>   Name = Inc-vl-elma01
>   Pool Type = Backup
>   Recycle = yes
>   AutoPrune = yes
>   Volume Retention = 10d
>   Action On Purge = Truncate
>   Maximum Volumes = 3
>   Maximum Volume Jobs = 500
>   Label Format = "${Pool}"
> }
>
> 28-Nov 16:47 bareos-dir JobId 0: Fatal error: Authorization key rejected 
> by ::.
> 28-Nov 16:47 bareos-dir: ERROR in dird/authenticate_console.cc:352 Unable 
> to authenticate console "admin" at client:::1:9101.
> 28-Nov 16:47 bareos-dir JobId 2681: Start Backup JobId 2681, 
> Job=vl-elma01-job.2023-11-28_16.47.39_14
> 28-Nov 16:47 bareos-dir JobId 2681: Connected Storage daemon at 
> 10.64.118.172:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 28-Nov 16:47 bareos-dir JobId 2681:  Encryption: 
> TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> 28-Nov 16:47 bareos-dir JobId 2681: Probing client protocol... (result 
> will be saved until config reload)
> 28-Nov 16:47 bareos-dir JobId 2681: Connected Client: bareos-fd at 
> localhost:9102, encryption: None
> 28-Nov 16:47 bareos-dir JobId 2681:    Handshake: Cleartext
> 28-Nov 16:47 bareos-dir JobId 2681:  Encryption: None
> 28-Nov 16:47 bareos-dir JobId 2681: *Volume "Inc-vl-elma01" has Volume 
> Retention of 864000 sec. and has 3 jobs that will be pruned*
> 28-Nov 16:47 bareos-dir JobId 2681: Purging the following 3 JobIds: 
> 1126,1133,1140
> 28-Nov 16:47 bareos-dir JobId 2681: Error: cats/sql_create.cc:404 Volume 
> "Inc-vl-elma01" already exists.
> 28-Nov 16:47 bareos-dir JobId 2681: Using Device "Elma" to write.
> 28-Nov 16:47 ct-bareos01-fd JobId 2681:  Encryption: None
> 28-Nov 16:47 ct-bareos01-fd JobId 2681: Connected Storage daemon at 
> 10.64.118.172:9103, encryption: None
> 28-Nov 16:47 bareos-dir JobId 2681: Error: cats/sql_create.cc:404 Volume 
> "Inc-vl-elma01" already exists.
> 28-Nov 16:47 bareos-dir JobId 2681: Error: cats/sql_create.cc:404 Volume 
> "Inc-vl-elma01" already exists.
> 28-Nov 16:47 bareos-sd JobId 2681: Job 
> vl-elma01-job.2023-11-28_16.47.39_14 is waiting. Cannot find any appendable 
> volumes.
> Please use the "label" command to create a new Volume for:
>     Storage:      "Elma" (/mnt/backups/vmware/elma/elma)
>     Pool:         Inc-vl-elma01
>     Media type:   File
> 28-Nov 16:47 ct-bareos01-fd JobId 2681: Extended attribute support is 
> enabled
> 28-Nov 16:47 ct-bareos01-fd JobId 2681: ACL support is enabled
> 28-Nov 16:48 bareos-dir JobId 2681: Fatal error: Network error with FD 
> during Backup: ERR=No data available
> 28-Nov 16:48 bareos-sd JobId 2681: Error: lib/bsock_tcp.cc:461 Socket is 
> terminated=1 on call to client:10.64.116.173:9103
> 28-Nov 16:48 bareos-sd JobId 2681: Job 
> vl-elma01-job.2023-11-28_16.47.39_14 canceled while waiting for mount on 
> Storage Device ""Elma" (/mnt/backups/vmware/elma/elma)".
> 28-Nov 16:48 bareos-dir JobId 2681: Fatal error: No Job status returned 
> from FD.
> 28-Nov 16:48 bareos-dir JobId 2681: Bareos bareos-dir 
> 22.1.2~pre4.c37b33136 (06Nov23):
>   ......................
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/ab183b40-d11d-4114-b3a9-f5d28cc10768n%40googlegroups.com.

Reply via email to