On Wed, 2 Oct 2024 at 12:10, Romain Delmas <
romain...@5group.fr> wrote:
>
> Hello Marcin,
>
> Sorry for the delay.
>
> I was asking about MediaType because of its registration in the bacula database to associate volume/storage.
> If i want to restore a backup, the MediaType on pool must match with the volume entry...
> However, in order to be able to parallelize jobs and retrieve the right files in the event of a problem, now i have as many MediaType as I have devices, and therefore as many pools.
> So, if i move a volume from the ancient pool to the new one, and MediaType between volume and pool do not match, this could pose a problem.
> That is why i wondered if i could change the MediaType of a volume to reassociate the path (in the event that I physically change the backups location ofc).
Hello Romain,
Thanks for the response and for describing us how you see the media
type. Now I see why you wanted to have a media type in the 'update'
command. Let me try to share with you how I understand it.
You wrote:
"If i want to restore a backup, the MediaType on pool must match with
the volume entry..."
I think in this sentence are three wrong assumptions:
1) Media type is not a pool property. It is assigned to volumes as a
volume property.
2) We can have volumes with different media types in the same pool and
it is supported. This media type has been introduced to Bacula exactly
for this purpose, so that when the storage wants to use a volume it
checks if its media type is the same as a volume media type. This way
the storage takes in the pool only volumes that it is able to use and
work with.
3) Pools do not have meaning in restore. It is useful for backup,
copy, migration for groupping volumes in sets of volumes for a given
purpose, but for restore pools are not used. In the restore job
resource we have a pool defined but it is because the Job resource
requires it but it is not used in the restore process.
Please let me know what you think about it? Thanks for your opinions.