Re: [Bacula-users] Mounting/Label question
Hi Arno,
thanks for your comments. Please find my answers inline.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Arno Lehmann
Sent: Monday, February 26, 2007 8:44 PM
To: 'bacula-users'
Subject: Re: [Bacula-users] Mounting/Label question
Device config:
Device {
Name = Quantum
Changer Device = tape0
Media Type = DLT-V4
Device Type = Tape
Archive Device = Tape0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = no
Alert Command = tapeinfo -f %c | findstr TapeAlert
Spool Directory = V:\\BaculaSpool
Maximum Spool Size = 2 GB
Changer Command = mtx-changer %o %a %S
Maximum Changer Wait = 4d
Offline On Unmount = yes
Label media = yes
}
That configuration looks funny... is that an autochanger or a single
drive? The configuration looks like a 1.36 one - i.e. no separate
autochanger section - but that was not ported to windows.
I don't have an autochanger. The last four lines were added recently to achive
that a tape
is automatically ejected, that a new inserted tape is mounted automatically and
that a new
tape is also automatically labeled. The idea behind was, that a normal user
could change
the tape himself and that no admin is needed to mount the tape etc.. These
lines were
actually taken from this list some days ago(Erich Prinz - Win32
mtx-changer.cmd and
single drive).
Data spooling: 0 active jobs, 0 bytes; 7 total jobs, 2,000,050,371 max
bytes/job.
Attr spooling: 1 active jobs, 9,135,494 bytes; 6 total jobs, 17,783,343 max
bytes.
But there are attributes still spooled... looks like the SD
is currently despooling attributes after a completed job.
Is that possible, i.e. did the Job finish some time after you
wrote your mail?
I looked in the log and the Full Backup showed a Termination:***
Backup Error
***. See below for the whole log entry of that job.
If it did not, I'd like to see the 'sta dir' output, because above you
state that the director is still waiting for a tape but didn't give
any output showing us how it did wait :-)
Arno you're right, that was a mistake on my side. The yesterday evening backup
was
normally executed.
Do you have a clue why the director couldn't get the record for JobId 97?
Thanks
Andreas
Log entry for job:
25-Feb 23:05 srv-dir: Start Backup JobId 97, Job=PTHHSrv.2007-02-25_23.05.00
25-Feb 23:05 srv-dir: Max configured use duration exceeded. Marking Volume
Tape04 as
Used.
25-Feb 23:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 00:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 02:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 06:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 09:37 srv-sd: Wrote label to prelabeled Volume Tape05 on device
Quantum (Tape0)
26-Feb 09:37 srv-sd: Spooling data ...
26-Feb 09:37 srv-fd: Generate VSS snapshots. Driver=VSS Win 2003,
Drive(s)=CDEV
26-Feb 09:40 srv-sd: User specified spool size reached.
26-Feb 09:40 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,371
bytes ...
26-Feb 09:43 srv-sd: Despooling elapsed time = 00:02:07, Transfer rate = 15.74 M
bytes/second
26-Feb 09:43 srv-sd: Spooling data again ...
26-Feb 09:45 srv-sd: User specified spool size reached.
26-Feb 09:45 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,386
bytes ...
26-Feb 09:47 srv-sd: Despooling elapsed time = 00:01:55, Transfer rate = 17.39 M
bytes/second
26-Feb 09:47 srv-sd: Spooling data again ...
26-Feb 09:50 srv-sd: User specified spool size reached.
26-Feb 09:50 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,389
bytes ...
26-Feb 09:52 srv-sd: Despooling elapsed time = 00:01:43, Transfer rate = 19.41 M
bytes/second
26-Feb 09:52 srv-sd: Spooling data again ...
26-Feb 09:53 srv-sd: User specified spool size reached.
26-Feb 09:53 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,350
bytes ...
26-Feb 09:56 srv-sd: Despooling elapsed time = 00:02:18, Transfer rate = 14.49 M
bytes/second
26-Feb 09:56 srv-sd: Spooling data again ...
26-Feb 09:57 srv-sd: User specified spool size reached.
26-Feb 09:57 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,383
bytes ...
26-Feb 09:59 srv-sd: Despooling elapsed time = 00:02:16, Transfer rate = 14.70 M
bytes/second
26-Feb 09:59 srv-sd: Spooling data again ...
26-Feb 10:00 srv-sd: Job write elapsed time = 00:22:02, Transfer rate = 7.759 M
bytes/second
26-Feb 10:00 srv-sd: Committing spooled data to Volume Tape05. Despooling
268,975,553
bytes ...
26-Feb 10:00 srv-sd: Despooling elapsed time = 00:00:20, Transfer rate = 13.44 M
bytes/second
26-Feb 10:00 srv-sd: Alert: cannot
Re: [Bacula-users] Mounting/Label question
Hi,
On 2/27/2007 3:24 PM, Andreas Lüdtke wrote:
Hi Arno,
thanks for your comments. Please find my answers inline.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Arno Lehmann
Sent: Monday, February 26, 2007 8:44 PM
To: 'bacula-users'
Subject: Re: [Bacula-users] Mounting/Label question
Device config:
Device {
Name = Quantum
Changer Device = tape0
Media Type = DLT-V4
Device Type = Tape
Archive Device = Tape0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = no
Alert Command = tapeinfo -f %c | findstr TapeAlert
Spool Directory = V:\\BaculaSpool
Maximum Spool Size = 2 GB
Changer Command = mtx-changer %o %a %S
Maximum Changer Wait = 4d
Offline On Unmount = yes
Label media = yes
}
That configuration looks funny... is that an autochanger or a single
drive? The configuration looks like a 1.36 one - i.e. no separate
autochanger section - but that was not ported to windows.
I don't have an autochanger. The last four lines were added recently to
achive that a tape
is automatically ejected, that a new inserted tape is mounted automatically
and that a new
tape is also automatically labeled. The idea behind was, that a normal user
could change
the tape himself and that no admin is needed to mount the tape etc.. These
lines were
actually taken from this list some days ago(Erich Prinz - Win32
mtx-changer.cmd and
single drive).
Ah, ok. Well, unfortunately I didn't follow that thread, but I think I
get a general understanding of what you set up...
Data spooling: 0 active jobs, 0 bytes; 7 total jobs, 2,000,050,371 max
bytes/job.
Attr spooling: 1 active jobs, 9,135,494 bytes; 6 total jobs, 17,783,343 max
bytes.
But there are attributes still spooled... looks like the SD
is currently despooling attributes after a completed job.
Is that possible, i.e. did the Job finish some time after you
wrote your mail?
I looked in the log and the Full Backup showed a Termination:***
Backup Error
***. See below for the whole log entry of that job.
If it did not, I'd like to see the 'sta dir' output, because above you
state that the director is still waiting for a tape but didn't give
any output showing us how it did wait :-)
Arno you're right, that was a mistake on my side. The yesterday evening
backup was
normally executed.
Good to hear.
Do you have a clue why the director couldn't get the record for JobId 97?
No, that's hard to tell... usually, that would indicate a database
problem. Like when your database was shutdown and immediately restarted,
but then you would normally see more errors.
Anyway, this is hard to analyze whan it was a unique, one-time problem.
If this problem persists, you should closely observer the backups, and
tje database, too.
Thanks
Andreas
Log entry for job:
25-Feb 23:05 srv-dir: Start Backup JobId 97, Job=PTHHSrv.2007-02-25_23.05.00
25-Feb 23:05 srv-dir: Max configured use duration exceeded. Marking Volume
Tape04 as
Used.
25-Feb 23:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 00:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 02:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 06:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0)
for Job Srv.2007-02-25_23.05.00
26-Feb 09:37 srv-sd: Wrote label to prelabeled Volume Tape05 on device
Quantum (Tape0)
26-Feb 09:37 srv-sd: Spooling data ...
26-Feb 09:37 srv-fd: Generate VSS snapshots. Driver=VSS Win 2003,
Drive(s)=CDEV
26-Feb 09:40 srv-sd: User specified spool size reached.
26-Feb 09:40 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,371
bytes ...
26-Feb 09:43 srv-sd: Despooling elapsed time = 00:02:07, Transfer rate =
15.74 M
bytes/second
26-Feb 09:43 srv-sd: Spooling data again ...
26-Feb 09:45 srv-sd: User specified spool size reached.
26-Feb 09:45 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,386
bytes ...
26-Feb 09:47 srv-sd: Despooling elapsed time = 00:01:55, Transfer rate =
17.39 M
bytes/second
26-Feb 09:47 srv-sd: Spooling data again ...
26-Feb 09:50 srv-sd: User specified spool size reached.
26-Feb 09:50 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,389
bytes ...
26-Feb 09:52 srv-sd: Despooling elapsed time = 00:01:43, Transfer rate =
19.41 M
bytes/second
26-Feb 09:52 srv-sd: Spooling data again ...
26-Feb 09:53 srv-sd: User specified spool size reached.
26-Feb 09:53 srv-sd: Writing spooled data to Volume. Despooling 2,000,050,350
bytes ...
26-Feb 09:56 srv-sd: Despooling elapsed time = 00:02:18, Transfer rate =
14.49 M
bytes/second
26-Feb 09:56 srv-sd: Spooling data again ...
26-Feb 09:57 srv-sd: User
Re: [Bacula-users] Mounting/Label question
Hello Arno,
It looks like the retention periods are set incorrectly since the Volume was
pruned while the job was running.
On Tuesday 27 February 2007 16:03, Arno Lehmann wrote:
Hi,
On 2/27/2007 3:24 PM, Andreas Lüdtke wrote:
Hi Arno,
thanks for your comments. Please find my answers inline.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Arno Lehmann
Sent: Monday, February 26, 2007 8:44 PM
To: 'bacula-users'
Subject: Re: [Bacula-users] Mounting/Label question
Device config:
Device {
Name = Quantum
Changer Device = tape0
Media Type = DLT-V4
Device Type = Tape
Archive Device = Tape0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = no
Alert Command = tapeinfo -f %c | findstr TapeAlert
Spool Directory = V:\\BaculaSpool
Maximum Spool Size = 2 GB
Changer Command = mtx-changer %o %a %S
Maximum Changer Wait = 4d
Offline On Unmount = yes
Label media = yes
}
That configuration looks funny... is that an autochanger or a single
drive? The configuration looks like a 1.36 one - i.e. no separate
autochanger section - but that was not ported to windows.
I don't have an autochanger. The last four lines were added recently to
achive that a tape is automatically ejected, that a new inserted tape is
mounted automatically and that a new tape is also automatically labeled.
The idea behind was, that a normal user could change the tape himself and
that no admin is needed to mount the tape etc.. These lines were actually
taken from this list some days ago(Erich Prinz - Win32 mtx-changer.cmd
and single drive).
Ah, ok. Well, unfortunately I didn't follow that thread, but I think I
get a general understanding of what you set up...
Data spooling: 0 active jobs, 0 bytes; 7 total jobs, 2,000,050,371 max
bytes/job. Attr spooling: 1 active jobs, 9,135,494 bytes; 6 total jobs,
17,783,343 max bytes.
But there are attributes still spooled... looks like the SD
is currently despooling attributes after a completed job.
Is that possible, i.e. did the Job finish some time after you
wrote your mail?
I looked in the log and the Full Backup showed a Termination:
*** Backup Error ***. See below for the whole log entry of that job.
If it did not, I'd like to see the 'sta dir' output, because above you
state that the director is still waiting for a tape but didn't give
any output showing us how it did wait :-)
Arno you're right, that was a mistake on my side. The yesterday evening
backup was normally executed.
Good to hear.
Do you have a clue why the director couldn't get the record for JobId 97?
No, that's hard to tell... usually, that would indicate a database
problem. Like when your database was shutdown and immediately restarted,
but then you would normally see more errors.
Anyway, this is hard to analyze whan it was a unique, one-time problem.
If this problem persists, you should closely observer the backups, and
tje database, too.
Thanks
Andreas
Log entry for job:
25-Feb 23:05 srv-dir: Start Backup JobId 97,
Job=PTHHSrv.2007-02-25_23.05.00 25-Feb 23:05 srv-dir: Max configured use
duration exceeded. Marking Volume Tape04 as Used.
25-Feb 23:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 00:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 02:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 06:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 09:37 srv-sd: Wrote label to prelabeled Volume Tape05 on device
Quantum (Tape0) 26-Feb 09:37 srv-sd: Spooling data ...
26-Feb 09:37 srv-fd: Generate VSS snapshots. Driver=VSS Win 2003,
Drive(s)=CDEV 26-Feb 09:40 srv-sd: User specified spool size reached.
26-Feb 09:40 srv-sd: Writing spooled data to Volume. Despooling
2,000,050,371 bytes ... 26-Feb 09:43 srv-sd: Despooling elapsed time =
00:02:07, Transfer rate = 15.74 M bytes/second
26-Feb 09:43 srv-sd: Spooling data again ...
26-Feb 09:45 srv-sd: User specified spool size reached.
26-Feb 09:45 srv-sd: Writing spooled data to Volume. Despooling
2,000,050,386 bytes ... 26-Feb 09:47 srv-sd: Despooling elapsed time =
00:01:55, Transfer rate = 17.39 M bytes/second
26-Feb 09:47 srv-sd: Spooling data again ...
26-Feb 09:50 srv-sd: User specified spool size reached.
26-Feb 09:50 srv-sd: Writing spooled data to Volume. Despooling
2,000,050,389 bytes ... 26-Feb 09:52 srv-sd: Despooling elapsed time =
00:01:43, Transfer rate = 19.41 M bytes/second
26-Feb 09:52 srv-sd: Spooling data again ...
26-Feb 09:53 srv-sd: User specified spool size reached.
26-Feb 09:53 srv-sd: Writing spooled data to Volume
Re: [Bacula-users] Mounting/Label question
Hi,
On 2/27/2007 5:04 PM, Kern Sibbald wrote:
Hello Arno,
It looks like the retention periods are set incorrectly since the Volume was
pruned while the job was running.
Ah, ok... in that case, you should do an 'llist volume=...' (IIRC) with
the volume in question. And,of course, also check your pool and client
settings for their retention times, and also keep in mind that
individual volumes may need to be updated to have their retention times
updated after a pool change...
And, of course, this shows how important it is to report problems with
the right sort of information attached to it :-)
Arno
On Tuesday 27 February 2007 16:03, Arno Lehmann wrote:
Hi,
On 2/27/2007 3:24 PM, Andreas Lüdtke wrote:
Hi Arno,
thanks for your comments. Please find my answers inline.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Arno Lehmann
Sent: Monday, February 26, 2007 8:44 PM
To: 'bacula-users'
Subject: Re: [Bacula-users] Mounting/Label question
Device config:
Device {
Name = Quantum
Changer Device = tape0
Media Type = DLT-V4
Device Type = Tape
Archive Device = Tape0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = no
Alert Command = tapeinfo -f %c | findstr TapeAlert
Spool Directory = V:\\BaculaSpool
Maximum Spool Size = 2 GB
Changer Command = mtx-changer %o %a %S
Maximum Changer Wait = 4d
Offline On Unmount = yes
Label media = yes
}
That configuration looks funny... is that an autochanger or a single
drive? The configuration looks like a 1.36 one - i.e. no separate
autochanger section - but that was not ported to windows.
I don't have an autochanger. The last four lines were added recently to
achive that a tape is automatically ejected, that a new inserted tape is
mounted automatically and that a new tape is also automatically labeled.
The idea behind was, that a normal user could change the tape himself and
that no admin is needed to mount the tape etc.. These lines were actually
taken from this list some days ago(Erich Prinz - Win32 mtx-changer.cmd
and single drive).
Ah, ok. Well, unfortunately I didn't follow that thread, but I think I
get a general understanding of what you set up...
Data spooling: 0 active jobs, 0 bytes; 7 total jobs, 2,000,050,371 max
bytes/job. Attr spooling: 1 active jobs, 9,135,494 bytes; 6 total jobs,
17,783,343 max bytes.
But there are attributes still spooled... looks like the SD
is currently despooling attributes after a completed job.
Is that possible, i.e. did the Job finish some time after you
wrote your mail?
I looked in the log and the Full Backup showed a Termination:
*** Backup Error ***. See below for the whole log entry of that job.
If it did not, I'd like to see the 'sta dir' output, because above you
state that the director is still waiting for a tape but didn't give
any output showing us how it did wait :-)
Arno you're right, that was a mistake on my side. The yesterday evening
backup was normally executed.
Good to hear.
Do you have a clue why the director couldn't get the record for JobId 97?
No, that's hard to tell... usually, that would indicate a database
problem. Like when your database was shutdown and immediately restarted,
but then you would normally see more errors.
Anyway, this is hard to analyze whan it was a unique, one-time problem.
If this problem persists, you should closely observer the backups, and
tje database, too.
Thanks
Andreas
Log entry for job:
25-Feb 23:05 srv-dir: Start Backup JobId 97,
Job=PTHHSrv.2007-02-25_23.05.00 25-Feb 23:05 srv-dir: Max configured use
duration exceeded. Marking Volume Tape04 as Used.
25-Feb 23:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 00:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 02:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 06:06 srv-sd: Please mount Volume FirstTape on Storage Device
Quantum (Tape0) for Job Srv.2007-02-25_23.05.00
26-Feb 09:37 srv-sd: Wrote label to prelabeled Volume Tape05 on device
Quantum (Tape0) 26-Feb 09:37 srv-sd: Spooling data ...
26-Feb 09:37 srv-fd: Generate VSS snapshots. Driver=VSS Win 2003,
Drive(s)=CDEV 26-Feb 09:40 srv-sd: User specified spool size reached.
26-Feb 09:40 srv-sd: Writing spooled data to Volume. Despooling
2,000,050,371 bytes ... 26-Feb 09:43 srv-sd: Despooling elapsed time =
00:02:07, Transfer rate = 15.74 M bytes/second
26-Feb 09:43 srv-sd: Spooling data again ...
26-Feb 09:45 srv-sd: User specified spool size reached.
26-Feb 09:45 srv-sd: Writing spooled data to Volume. Despooling
2,000,050,386 bytes ... 26-Feb 09:47 srv-sd: Despooling elapsed time =
00:01:55, Transfer rate = 17.39 M bytes/second
26-Feb 09:47 srv-sd: Spooling data again ...
26-Feb 09:50 srv-sd: User specified spool size reached.
26-Feb 09:50
Re: [Bacula-users] Mounting/Label question
Hello,
On 2/26/2007 11:27 AM, Andreas Lüdtke wrote:
Hi,
my backup strategy is to use one tape per week and after 5 weeks/tapes I
re-use the first
tape.
Ok.
I do a full backup on Sunday evening and I want to change the tape on Monday
morning
when I'm in the office. I recently changed the config files to automatically
eject the
tape.
I never tried that, but I guess we can be sure it works in principle.
This was the case this Monday morning, but after I inserted an unused tape (I
just
labeled it last week in advance) and mounted it, the director is still
waiting for a tape
(see below). I use Bacula on Windows 2003 server.
Uuu... ask Robert ;-)
I do think that the windows version is not as well tested as the unix
one, and I assume that Robert is only waiting to fix the problems that
come up :-)
I did already a purge jobs volume for the Tape05 but that didn't help.
Now I'm somewhat lost. How do I convince Bacula to use Tape05 ?
More comments below...
Thanks in advance
Andreas
Device config:
Device {
Name = Quantum
Changer Device = tape0
Media Type = DLT-V4
Device Type = Tape
Archive Device = Tape0
AutomaticMount = yes
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = no
Alert Command = tapeinfo -f %c | findstr TapeAlert
Spool Directory = V:\\BaculaSpool
Maximum Spool Size = 2 GB
Changer Command = mtx-changer %o %a %S
Maximum Changer Wait = 4d
Offline On Unmount = yes
Label media = yes
}
That configuration looks funny... is that an autochanger or a single
drive? The configuration looks like a 1.36 one - i.e. no separate
autochanger section - but that was not ported to windows.
status storage
==
==
Daemon started 19-Feb-07 15:48, 12 Jobs run since started.
Heap: bytes=92,775 max_bytes=225,526 bufs=110 max_bufs=119
Running Jobs:
No Jobs running.
No jobs running indicates that the SD at least does not actually wait
for a new tape...
Jobs waiting to reserve a drive:
The same applies here.
Terminated Jobs:
JobId LevelFiles Bytes Status FinishedName
===
87 Incr13379.20 M OK 20-Feb-07 23:06 Srv
88 Full 1 432 OK 21-Feb-07 08:40 BackupCatalog
89 Incr193114.0 M OK 21-Feb-07 23:06 Srv
90 Full 1 432 OK 21-Feb-07 23:10 BackupCatalog
91 Incr14678.13 M OK 22-Feb-07 23:06 Srv
92 Full 1 432 OK 22-Feb-07 23:10 BackupCatalog
93 Incr16897.43 M OK 23-Feb-07 23:06 Srv
94 Full 1 432 OK 23-Feb-07 23:10 BackupCatalog
95 Incr15484.61 M OK 24-Feb-07 23:06 Srv
96 Full 1 432 OK 24-Feb-07 23:10 BackupCatalog
But then, there's no job from today. So I guess we can assume the SD
itself has the drive and tape set up correctly but it's the DIR which
does not know it can continue...
Device status:
Device FileStorage (V:\BaculaTmp) is not open.
Device Quantum (Tape0) is mounted with Volume=Tape05 Pool=Default
Total Bytes Read=129,024 Blocks Read=2 Bytes/block=64,512
Positioned at File=0 Block=0
Hmmm... that looks like a mounted, empty tape to me, too. The SD read
the label off the tape an rewound it. No writes yet.
In Use Volume status:
Tape05 on device Quantum (Tape0)
Data spooling: 0 active jobs, 0 bytes; 7 total jobs, 2,000,050,371 max
bytes/job.
Attr spooling: 1 active jobs, 9,135,494 bytes; 6 total jobs, 17,783,343 max
bytes.
But there are attributes still spooled... looks like the SD is currently
despooling attributes after a completed job.
Is that possible, i.e. did the Job finish some time after you wrote your
mail?
If it did not, I'd like to see the 'sta dir' output, because above you
state that the director is still waiting for a tape but didn't give
any output showing us how it did wait :-)
Arno
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann[EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
