It's almost obvious if you look at possible medium states but to give you a verbose answer - the media can be read from any point but can only be appended at the end.
So if any job is being pruned/purged/deleted, it's just being "forgotten" by the database but is still present on the media where it originally was.
Oversimplifying a bit - a media life cycle is:
Purged -> Recycled -> Append -> Used/Full -> Purged again.
So, as you can see, there is no (de)fragmentation. A volume is getting appended to, then it's getting recycled. Simple as that.
With disk-based storage it's getting a bit more complicated with
dynamicaly created volumes, single-job volumes and auto-truncate
on purge.
--
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 on the web visit https://groups.google.com/d/msgid/bareos-users/b5b7f195-056e-4391-99f0-6de9b0b87129n%40googlegroups.com.
On Dec 26, 2020, at 12:32 PM, Spadajspadaj <spadaj...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/55470d56-be2b-8a22-496a-c0120426c902%40gmail.com.