Thanks Bruno. Sounds good.
On Wednesday, December 21, 2022 at 1:33:03 PM UTC+1 Bruno Friedmann wrote:
> Never forget that Bareos try to be the most conservative as possible with
> data. which can translate to up to the start of the job, it will not expire
> and recycle a volume. That let you a possibility to still restore from it
> up to the last minute.
>
> if you want to know if a next volume is already available you can play the
> the `list nextvol` bconsole command.
>
> On Tuesday, December 20, 2022 at 1:56:16 PM UTC+1 Łukasz Szczepanik wrote:
>
>> Hi guys,
>>
>> Anyone could explain me why Volume information is *unknown* when I
>> execute 'status dir' command:
>>
>> *status dir
>> bareos-director Version: 21.0.0 (21 December 2021)
>> Scheduled Jobs:
>> Level Type Pri Scheduled Name Volume
>>
>> ===================================================================================
>> Incremental Backup 10 20-Dec-22 19:00 server1 *unknown*
>> Incremental Backup 10 20-Dec-22 19:00 server2 *unknown*
>>
>> The job config is:
>>
>> *show job=server1-job
>> Job {
>> Name = "server1-job"
>> Type = Backup
>> Messages = "Standard"
>> Storage = "s3storage"
>> Pool = "server1-full-pool"
>> FullBackupPool = "server1-full-pool"
>> VirtualFullBackupPool = ""
>> IncrementalBackupPool = "server1-inc-pool"
>> DifferentialBackupPool = ""
>> NextPool = ""
>> Client = "server1"
>> FileSet = "server1"
>> Schedule = "CycleSchedule-1"
>> JobToVerify = ""
>> Catalog = ""
>> JobDefs = ""
>> RerunFailedLevels = Yes
>> }
>>
>> When job runs it choose volume from proper pool but somehow 'status dir'
>> is not able to check it.
>>
>> Thank tou
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/003cc53c-797e-4446-ac0a-48d1c1ed1e2dn%40googlegroups.com.
