I am having the same really slow vxa throughput experience. I don't
have any real numbers to back it up though a job which used to take 4
hours using dump has take 12+ in bacula. I suspect has to do with either
the block size, fast forward space file or compression.
Here is the device description I am using:
Device {
Name = Drive-1 #
Drive Index = 0
Media Type = "VXA Packet Tape"
Archive Device = /dev/nst0
AutomaticMount = yes # when device opened, read it
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = yes
Minimum Block Size = 1024
Maximum Block Size = 1024
Hardware End of Medium = No
Fast Forward Space File = No
Backward Space Record = No
Backward Space File = Yes
Forward Space Record = Yes
Forward Space File = Yes
Offline On Unmount = Yes
Label Media = Yes
}
If you having a vxa drive working well could you please post your Device
{} settings?
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users