I just ran a single tape fill and it failed:
Wrote block=30, file,blk=19,985 VolBytes=18,062,392,320 rate=5.475 MB/s
Wrote block=305000, file,blk=19,5985 VolBytes=18,384,952,320 rate=5.478 MB/s
10:14:27 Flush block, write EOF
01-Jan 10:14 btape JobId 0: Error: block.c:573 Write error at 19:748
Ok, thanks. I have had no problems with changing tapes without a change to
the script.
Regards,
David Koski
dko...@sutinen.com
On Tuesday 02 March 2010, Brian Debelius wrote:
> vxa_packetloader is not related to the delay. That changes the string that
> is parsed to determine what tapes are lo
vxa_packetloader is not related to the delay. That changes the string that is
parsed to determine what tapes are loaded in the changer.
On 3/2/2010 3:26 PM, David Koski wrote:
> I have not but it is probably a good idea as Packetloaders can delay for a
> very long time if they detect an error a
I have not but it is probably a good idea as Packetloaders can delay for a
very long time if they detect an error and need to take corrective measures
automatically.
Regards,
David Koski
da...@kosmosisland.com
On Tuesday 02 March 2010, Brian Debelius wrote:
> This is unrelated. I am just curio
This is unrelated. I am just curious. Have you enabled the
vxa_packetloader in mtx-changer.conf? I am just trying to figure out if
anyone actually uses this.
On 3/2/2010 2:15 PM, David Koski wrote:
> I think the 172/320 should work the same as VXA-2. I have done some single
> tape backups an
I was just curious if the single tape worked, as it might provide
direction in troubleshooting.
On 3/2/2010 2:15 PM, David Koski wrote:
> I think the 172/320 should work the same as VXA-2. I have done some single
> tape backups and restores with success but did not try btape with single
> tapes.
I think the 172/320 should work the same as VXA-2. I have done some single
tape backups and restores with success but did not try btape with single
tapes. The multitape backup is the big issue. I am using bacula because BRU
would not work and BackupExec is not supported on this unit as it is
I just realized that I have a VXA-172/320 not a VXA-2.
How well does a single tape test work?
On 3/2/2010 1:14 PM, David Koski wrote:
> Thank you Brian. That is almost what I have with the following differences:
>
> AutomaticMount not set, default not defined in doc for version 2.4.
> Drive Ind
Thank you Brian. That is almost what I have with the following differences:
AutomaticMount not set, default not defined in doc for version 2.4.
Drive Index not set but default works correctly.
AutoSelect not set but default is same as yours.
Maxmimum Changer Wait is higher on mine (30 minutes)
I
Sorry that I cannot post the whole files, I have to type this. Watch
for typos.
Bacual-sd.conf
Autochanger {
Name = Packetloader
Device= VXA_Tape
Changer Command = "/opt/bacula/bin/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg7
}
Device {
Name = VXA_Tape
Drive Index 0
On Mon, Mar 1, 2010 at 12:01 PM, David Koski wrote:
> Thank you Brian. I have not had success in finding the configuration form
> archives. I would appreciate if you would send it to me.
>
I found it in my mail. Google search for
"bacula Fwd: Here you go!!"
John
-
Thank you Brian. I have not had success in finding the configuration form
archives. I would appreciate if you would send it to me.
Regards,
David Koski
dko...@sutinen.com
On Monday 01 March 2010, Brian Debelius wrote:
> Hi,
>
> Search the archives. I have posted working configurations. I'd e
Hi,
Search the archives. I have posted working configurations. I'd email
them to you now but I do not have them at the moment. If you can't find
them, let me know and I will get them to you. There are mtx-changer
modifications as well.
brian-
On 2/27/2010 2:53 AM, David Koski wrote:
> I'
I'm looking for storage daemon configuration for an Exabyte Packetloader
(Storageloader) VXA-2. Currently my Device resource looks like this:
Device {
Name = "Exabyte_VXA-2"
Media Type = "VXA-2"
Archive Device = /dev/nst0
Device Type = Tape
Autochanger = yes # if yes, mu
14 matches
Mail list logo
