I am trying to get bacula up on Solaris 10 using a working set of
config files from the same box when it was on centos 4 linux.
Version: 2.0.3 (06 March 2007) i386-pc-solaris2.8 solaris 5.8
This new bacula seems to behave differently on our long running
backups. We have an LTO3 we are using to backup 3-4TB for a full.
Under the old config I would get an email requesting a volume change
in ever increasing intervals, first after an hour, then two, then
four etc. and I would not have a timeout where it would error the
job. Bacula just waited till I popped in a new volume labeled and
mounted it and then it kept on going.
Now I get the behavior where I get an email every minute:
19-Oct 01:00 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
and then finally after 4 hours or so of this I get an error message
like:
18-Oct 17:13 SERVERNAME-dir: Start Backup JobId 46, Job=JOBNAME.
2007-10-18_17.13.00
18-Oct 17:13 SERVERNAME-dir: Recycled current volume "POOL_B_0001"
18-Oct 17:14 SERVERNAME-sd: Recycled volume "POOL_B_0001" on device
"LTO-Drive-1" (/dev/rmt/0bn), all previous data lost.
19-Oct 00:49 SERVERNAME-sd: End of Volume "POOL_B_0001" at 504:12014
on device "LTO-Drive-1" (/dev/rmt/0bn). Write of 64512 bytes got 0.
19-Oct 00:49 SERVERNAME-sd: Re-read of last block succeeded.
19-Oct 00:49 SERVERNAME-sd: End of medium on Volume "POOL_B_0001"
Bytes=504,742,855,680 Blocks=7,824,014 at 19-Oct-2007 00:49.
19-Oct 00:49 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 00:51 SERVERNAME-sd: JOBNAME.2007-10-18_17.13.00 Warning:
Director wanted Volume "POOL_B_0002".
Current Volume "POOL_B_0001" not acceptable because:
1998 Volume "POOL_B_0001" status is Full, but should be Append,
Purged or Recycle.
19-Oct 00:51 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 00:52 SERVERNAME-sd: JOBNAME.2007-10-18_17.13.00 Warning:
Director wanted Volume "POOL_B_0002".
...
SNIP
...
Current Volume "POOL_B_0001" not acceptable because:
1998 Volume "POOL_B_0001" status is Full, but should be Append,
Purged or Recycle.
19-Oct 04:08 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 04:09 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 04:10 SERVERNAME-sd: JOBNAME.2007-10-18_17.13.00 Warning:
Director wanted Volume "POOL_B_0002".
Current Volume "POOL_B_0001" not acceptable because:
1998 Volume "POOL_B_0001" status is Full, but should be Append,
Purged or Recycle.
19-Oct 04:10 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 04:11 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 04:12 SERVERNAME-sd: JOBNAME.2007-10-18_17.13.00 Warning:
Director wanted Volume "POOL_B_0002".
Current Volume "POOL_B_0001" not acceptable because:
1998 Volume "POOL_B_0001" status is Full, but should be Append,
Purged or Recycle.
19-Oct 04:12 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 04:13 SERVERNAME-sd: Please mount Volume "POOL_B_0002" on
Storage Device "LTO-Drive-1" (/dev/rmt/0bn) for Job JOBNAME.
2007-10-18_17.13.00
19-Oct 04:14 SERVERNAME-sd: JOBNAME.2007-10-18_17.13.00 Fatal error:
Too many tries: Wrong Volume mounted on device "LTO-Drive-1" (/dev/
rmt/0bn): Wanted POOL_B_0002 have POOL_B_0001
19-Oct 04:14 SERVERNAME-sd: Job write elapsed time = 11:00:18,
Transfer rate = 12.73 M bytes/second
19-Oct 04:14 SERVERNAME-sd: JOBNAME.2007-10-18_17.13.00 Fatal error:
askdir.c:320 NULL Volume name. This shouldn't happen!!!
19-Oct 04:14 SERVERNAME-fd: JOBNAME.2007-10-18_17.13.00 Fatal error:
backup.c:873 Network send error to SD. ERR=Broken pipe
19-Oct 04:14 SERVERNAME-dir: JOBNAME.2007-10-18_17.13.00 Error:
Bacula 2.0.3 (06Mar07): 19-Oct-2007 04:14:38
JobId: 46
Job: JOBNAME.2007-10-18_17.13.00
Backup Level: Full
Client: "SERVERNAME-fd" 2.0.3 (06Mar07) i386-pc-
solaris2.8,solaris,5.8
FileSet: "JOB_DATA" 2007-10-18 17:13:00
Pool: "Pool_B" (From Job resource)
Storage: "LTO" (From Job resource)
Scheduled time: 18-Oct-2007 17:12:50
Start time: 18-Oct-2007 17:13:02
End time: 19-Oct-2007 04:14:38
Elapsed time: 11 hours 1 min 36 secs
Priority: 10
FD Files Written: 335,818
SD Files Written: 335,818
FD Bytes Written: 504,290,872,389 (504.2 GB)
SD Bytes Written: 504,358,691,067 (504.3 GB)
Rate: 12703.8 KB/s
Software Compression: None
VSS: no
Encryption: no
Volume name(s): POOL_B_0001
Volume Session Id: 5
Volume Session Time: 1192750442
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: Error
SD termination status: Error
Termination: *** Backup Error ***
It seems as though the drive is not unmounted in the old way?
Thanks in advance for any help you can give.
Asa
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
