[Bacula-users] Hope usefull script if you know % of progress backup
Hi All!
I hope thi can be usefull
the script return lines like this
JobId= 5257 JOBNAME CLIENT | Now: 58.81% Files=217437
Bytes=224761256596 Bytes/sec=7269592 Errors=3 (on tot.byte= 382146782310)
08:35:18-- duration
JobId= 5226 JOBNAME CLIENT | Now: 73.15% Files=1580436
Bytes=217781667592 Bytes/sec=5045914 Errors=0 (on tot.byte= 297702961761)
11:59:20
Here you are and pls, let me know ;)
Fabio
#!/bin/bash
#
# Script to know the progress of running bck
#using by -u for updating client list/estimate
#
# By CHIECHI Fabio
# (c) 2009
#
chcpath=/filedisk/chc/tmp
bindir=/usr/bin
db_name=${db_name:-bacula}
if [ ! -f $bindir/mysql ]; then
echo -e Sorry, Script for MySQL!\nI can't find MySQL :(
exit 1
fi
case $1 in
-u|update|-update|upd|-upd)
rm -f $chcpath/bacula_estratto_estimate.txt
bconsole END-OF-DATA | grep -v Enter | grep -v 1000 | grep -v client
| sort -u $chcpath/bacula_lista_client.txt
.client
END-OF-DATA
cat $chcpath/bacula_lista_client.txt | while read line
do
echo $line
esito=$(bconsole END-OF-DATA| grep OK estimate
estimate job=$line.j
END-OF-DATA)
echo $esito
echo $line $esito | awk '{print $1bytes = substr($6,7,20)
files = substr($5,7,20)}' | sed s/,//g
$chcpath/bacula_estratto_estimate.txt
done
rm -f $chcpath/bacula_lista_client.txt
;;
*)
if [ ! -f $chcpath/bacula_estratto_estimate.txt ]; then
echo I can't find estimate data.
echo Run the scrpt with -u option!
exit 1
fi
$bindir/mysql -f END-OF-DATA | grep -v JobId | while read line
USE ${db_name};
select JobId,Job,Client.Name from Job inner join Client on Job.ClientId =
Client.ClientId where Job.JobStatus='R';
END-OF-DATA
do
JBID=$(echo $line |awk '{print $1}')
SRV=$(echo $line |awk '{print $3}')
esito=$(bconsole END-OF-DATA| grep Files= | sed s/,//g
status client=$SRV
END-OF-DATA)
battuali=$(echo $esito | awk '{print $2}'|cut -d = -f 2)
btot=$(cat ${chcpath}/bacula_estratto_estimate.txt | grep $SRV |
awk '{print $4}')
if [ $btot == ]; then
echo client doesn't exists in estimate data!
else
perc=$(echo scale=2; $battuali * 100 / $btot | bc)
adata=$(date '+%Y-%m-%d %H:%M:%S')
durata=$($bindir/mysql -f END-OF-DATA | grep -v timediff
USE ${db_name}
select timediff('$adata',Job.StartTime) from Job where JobId='$JBID'
END-OF-DATA)
echo JobId= $line | Now: $perc% $esito (on tot.byte=
$btot) $durata
fi
done
;;
esac
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] BACULA hang: waiting on max Storage jobs
Hi All! I noticed that someone else got this kind of problem. Now i try to describe it. whith status director I have: JobId Level Name Status == 5226 Fullcli101.j.2009-08-13_23.00.00_14 SD despooling Data 5257 Fullcli102.j.2009-08-13_23.00.00_45 SD despooling Data 5264 Fullcli103.j.2009-08-13_23.00.00_52 is waiting on max Storage jobs 5302 Fullcli104.j.2009-08-14_02.00.00_30 is waiting on max Storage jobs 5303 Fullcli105.j.2009-08-14_02.00.00_31 is waiting on max Storage jobs 5304 Fullcli106.j.2009-08-14_02.00.00_32 is waiting on max Storage jobs 5305 Fullcli107.j.2009-08-14_05.00.00_34 is waiting on max Storage jobs 5306 Fullcli108.j.2009-08-14_05.00.00_35 is waiting on max Storage jobs 5307 Fullcli109.j.2009-08-14_05.00.00_36 is waiting on max Storage jobs 5308 Fullcli110.j.2009-08-14_05.00.00_37 is waiting on max Storage jobs 5309 Fullcli111.j.2009-08-14_05.00.00_38 is waiting on max Storage jobs 5310 Fullcli112.j.2009-08-14_05.00.00_39 is waiting on max Storage jobs 5311 Fullcli113.j.2009-08-14_05.00.00_40 is waiting on max Storage jobs 5312 Fullcli114.j.2009-08-14_05.00.00_41 is waiting on max Storage jobs 5313 Fullcli115.j.2009-08-14_05.00.00_42 is waiting on max Storage jobs 5314 Fullcli116.j.2009-08-14_05.00.00_43 is waiting on max Storage jobs 5315 Fullcli117.j.2009-08-14_05.00.00_44 is waiting on max Storage jobs 5316 Fullcli118.j.2009-08-14_05.00.00_45 is waiting on max Storage jobs 5317 Fullcli119.j.2009-08-14_05.00.00_46 is waiting on max Storage jobs 5318 Fullcli120.j.2009-08-14_05.00.00_47 is waiting on max Storage jobs 5319 Fullcli121.j.2009-08-14_05.00.00_48 is waiting on max Storage jobs 5320 Fullcli122.j.2009-08-14_05.00.00_49 is waiting on max Storage jobs 5321 Fullcli123.bootstrap.j.2009-08-14_07.00.00_50 is waiting for higher priority jobs to finish but with status storage there are no waiting job for drive reservation :( Running Jobs: Writing: Full Backup job cli101.j JobId=5226 Volume=B00055L3 pool=PRODPOOL14 device=Drive-13 (/dev/VTLBACP_tape13) spooling=0 despooling=1 despool_wait=0 Files=2,050,055 Bytes=258,044,201,933 Bytes/sec=5,718,050 FDReadSeqNo=15,905,081 in_msg=11875105 out_msg=5 fd=58 Writing: Full Backup job cli102.j JobId=5257 Volume=B00056L3 pool=PRODPOOL1 device=Drive-3 (/dev/VTLBACP_tape3) spooling=0 despooling=1 despool_wait=0 Files=219,645 Bytes=269,743,401,648 Bytes/sec=8,208,618 FDReadSeqNo=5,279,940 in_msg=4884798 out_msg=5 fd=49 Jobs waiting to reserve a drive: any idea? Backups of first second client are going, why others don't? Thx Fabio -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] BACULA hang: waiting on max Storage jobs
Sorry: forgot to say that i can run till 64 concurrent job before now all was ok! Fabio 2009/8/14 Fabio Xarax fxa...@gmail.com Hi All! I noticed that someone else got this kind of problem. Now i try to describe it. whith status director I have: JobId Level Name Status == 5226 Fullcli101.j.2009-08-13_23.00.00_14 SD despooling Data 5257 Fullcli102.j.2009-08-13_23.00.00_45 SD despooling Data 5264 Fullcli103.j.2009-08-13_23.00.00_52 is waiting on max Storage jobs 5302 Fullcli104.j.2009-08-14_02.00.00_30 is waiting on max Storage jobs 5303 Fullcli105.j.2009-08-14_02.00.00_31 is waiting on max Storage jobs 5304 Fullcli106.j.2009-08-14_02.00.00_32 is waiting on max Storage jobs 5305 Fullcli107.j.2009-08-14_05.00.00_34 is waiting on max Storage jobs 5306 Fullcli108.j.2009-08-14_05.00.00_35 is waiting on max Storage jobs 5307 Fullcli109.j.2009-08-14_05.00.00_36 is waiting on max Storage jobs 5308 Fullcli110.j.2009-08-14_05.00.00_37 is waiting on max Storage jobs 5309 Fullcli111.j.2009-08-14_05.00.00_38 is waiting on max Storage jobs 5310 Fullcli112.j.2009-08-14_05.00.00_39 is waiting on max Storage jobs 5311 Fullcli113.j.2009-08-14_05.00.00_40 is waiting on max Storage jobs 5312 Fullcli114.j.2009-08-14_05.00.00_41 is waiting on max Storage jobs 5313 Fullcli115.j.2009-08-14_05.00.00_42 is waiting on max Storage jobs 5314 Fullcli116.j.2009-08-14_05.00.00_43 is waiting on max Storage jobs 5315 Fullcli117.j.2009-08-14_05.00.00_44 is waiting on max Storage jobs 5316 Fullcli118.j.2009-08-14_05.00.00_45 is waiting on max Storage jobs 5317 Fullcli119.j.2009-08-14_05.00.00_46 is waiting on max Storage jobs 5318 Fullcli120.j.2009-08-14_05.00.00_47 is waiting on max Storage jobs 5319 Fullcli121.j.2009-08-14_05.00.00_48 is waiting on max Storage jobs 5320 Fullcli122.j.2009-08-14_05.00.00_49 is waiting on max Storage jobs 5321 Fullcli123.bootstrap.j.2009-08-14_07.00.00_50 is waiting for higher priority jobs to finish but with status storage there are no waiting job for drive reservation :( Running Jobs: Writing: Full Backup job cli101.j JobId=5226 Volume=B00055L3 pool=PRODPOOL14 device=Drive-13 (/dev/VTLBACP_tape13) spooling=0 despooling=1 despool_wait=0 Files=2,050,055 Bytes=258,044,201,933 Bytes/sec=5,718,050 FDReadSeqNo=15,905,081 in_msg=11875105 out_msg=5 fd=58 Writing: Full Backup job cli102.j JobId=5257 Volume=B00056L3 pool=PRODPOOL1 device=Drive-3 (/dev/VTLBACP_tape3) spooling=0 despooling=1 despool_wait=0 Files=219,645 Bytes=269,743,401,648 Bytes/sec=8,208,618 FDReadSeqNo=5,279,940 in_msg=4884798 out_msg=5 fd=49 Jobs waiting to reserve a drive: any idea? Backups of first second client are going, why others don't? Thx Fabio -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] btape fails to see loaded tape
On Thu, 13 Aug 2009, Dan Langille wrote: I think we have a problem: I flagged this a couple of years ago with Overland changers. [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? This happens consistently with tapes loaded out of i/o slots and the only solution I've found is not to put tapes in them. (FWIW Bacula won't load tapes from these slots either, bacula-changer doesn't parse the IMPORT/EXPORT from mtx and drops the line) AB -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] btape fails to see loaded tape
On Fri, August 14, 2009 6:40 am, Alan Brown wrote: On Thu, 13 Aug 2009, Dan Langille wrote: I think we have a problem: I flagged this a couple of years ago with Overland changers. [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? This happens consistently with tapes loaded out of i/o slots and the only solution I've found is not to put tapes in them. All the slots on this machinare are IO slots, except for 1 2. Perhaps this is a configuration issue that I should look into. (FWIW Bacula won't load tapes from these slots either, bacula-changer doesn't parse the IMPORT/EXPORT from mtx and drops the line) It is mtx-changer that doesn't parse that line. This is part of the customization I've been doing for this particular robot. -- Dan Langille -- http://langille.org/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] mtx: Unknown Storage Element Loaded
Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, Aug 14, 2009 at 1:26 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, August 14, 2009 1:26 pm, Dan Langille wrote: On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
Hi, 14.08.2009 19:26, Dan Langille wrote: On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. ... Status now shows: [dlangi...@backup01 bacula]$ sudo /sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM241L4 Storage Element 1:Full :VolumeTag=AAM274L4 Storage Element 2:Full :VolumeTag=AAM275L4 Storage Element 3 IMPORT/EXPORT:Full :VolumeTag=AAM242L4 Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM265L4 Storage Element 5 IMPORT/EXPORT:Empty With the dreaded Unknown. So it's right where you started? :-) I guess you'll have to track the slot numbers yourself, as the library simply doesn't do that for I/O-slots. (Which slots or magazines are used for im/export can probably be configured, but I assume that you want them as import/export slots so your operators can easily swap tapes.) Actually, all the information you need is already in the catalog, you've just got to modify mtx-changer to look the slot numbers up in the catalog, and when doing the listing, you need to ensure the I/O-slots are considered. I'm planning something similar for a customer who probably needs to use all the slots they have soon, but they are not there yet... Cheers, Arno -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück www.its-lehmann.de -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, August 14, 2009 1:43 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 1:26 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, Aug 14, 2009 at 2:28 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 1:43 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 1:26 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. Current problem: I can't see how to get this information from the device. I'll keep working on it: $ sudo /usr/sbin/mtx -f /dev/sg4 inquiry Password: Product Type: Medium Changer Vendor ID: 'QUANTUM ' Product ID: 'PX500 ' Revision: '0033' Attached Changer: No [dlangi...@backup01 bacula]$ I think we have a problem: [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 load 3 [dlangi...@backup01 bacula]$ sudo /usr/sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM240L4 Storage Element 1:Empty Storage Element 2:Empty Storage Element 3 IMPORT/EXPORT:Empty Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM241L4 Should that 'Unknown Storage Element Loaded' be a 3 to indicate the slot it came from? Here is what my mtx output looks like dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage Element 13:Full :VolumeTag=A00048 Storage Element 14:Full :VolumeTag=A00012 Storage Element 15:Full :VolumeTag=A00068 Storage Element 16:Full :VolumeTag=A00069 Storage Element 17:Empty:VolumeTag= Storage Element 18:Full :VolumeTag=A00065 Storage Element 19:Full :VolumeTag=A00066 Storage Element 20:Full :VolumeTag=A00067 Storage Element 21:Full :VolumeTag=A00062 Storage Element 22:Full :VolumeTag=A00063 Storage Element 23:Full :VolumeTag=A00064 Storage Element 24 IMPORT/EXPORT:Full :VolumeTag=A00029 What version of mtx are you using? dev6 ~ # equery l mtx [ Searching for package 'mtx' in all categories among: ] * installed packages [I--] [ ] sys-block/mtx-1.2.18 (0) It looks like I have 1.2.18 John Ahh. If I manually load a tape using controls on the archive I get the same. Bacula will pick this up correctly if I update slots in the console however. dev6 ~ # mtx -f /dev/autochanger1 status Storage Changer /dev/autochanger1:2 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 17 Loaded):VolumeTag = A00036 Data Transfer Element 1:Full (Unknown Storage Element Loaded):VolumeTag = A00029 Storage Element 1:Full :VolumeTag=A00030 Storage Element 2:Empty:VolumeTag= Storage Element 3:Full :VolumeTag=A00058 Storage Element 4:Full :VolumeTag=A00053 Storage Element 5:Full :VolumeTag=A00023 Storage Element 6:Full :VolumeTag=A6 Storage Element 7:Full :VolumeTag=A7 Storage Element 8:Full :VolumeTag=A00052 Storage Element 9:Full :VolumeTag=A00028 Storage Element 10:Full :VolumeTag=A00020 Storage Element 11:Full :VolumeTag=A00054 Storage Element 12:Full :VolumeTag=A00039 Storage
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, August 14, 2009 2:04 pm, Arno Lehmann wrote: Hi, 14.08.2009 19:26, Dan Langille wrote: On Fri, August 14, 2009 12:23 pm, John Drescher wrote: On Fri, Aug 14, 2009 at 12:01 PM, Dan Langilled...@langille.org wrote: On Fri, August 14, 2009 11:39 am, Dan Langille wrote: On Fri, August 14, 2009 11:13 am, Dan Langille wrote: Changing the subject, given the change in subject. :) On Thu, August 13, 2009 3:14 pm, John Drescher wrote: On Thu, Aug 13, 2009 at 3:09 PM, John Drescherdresche...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:45 PM, Dan Langilled...@langille.org wrote: On Thu, August 13, 2009 2:27 pm, Dan Langille wrote: On Thu, August 13, 2009 1:19 pm, Dan Langille wrote: I am setting up a new autochanger / tape drive. I'm trying to run btape. The basic test works, but I see this message when I start btape: Autochanger loaded? drive 0, result: nothing loaded. mtx-changer [and mtx] both disagree with this: $ sudo /etc/bacula/mtx-changer /dev/sg4 loaded 0 /dev/nst0 0 AAM240L4 That is a problem. You don't want the label. You want the slt it came from. See http://www.bacula.org/en/dev-manual/Autochanger_Resource.html#SECTION001713 loaded -- returns number of the slot that is loaded, base 1, in the drive or 0 if the drive is empty. ... Status now shows: [dlangi...@backup01 bacula]$ sudo /sbin/mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 38 Slots ( 36 Import/Export ) Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = AAM241L4 Storage Element 1:Full :VolumeTag=AAM274L4 Storage Element 2:Full :VolumeTag=AAM275L4 Storage Element 3 IMPORT/EXPORT:Full :VolumeTag=AAM242L4 Storage Element 4 IMPORT/EXPORT:Full :VolumeTag=AAM265L4 Storage Element 5 IMPORT/EXPORT:Empty With the dreaded Unknown. So it's right where you started? :-) Oh sorry, I didn't see your post until John tole me you'd said something. Yes, back to square one. I guess you'll have to track the slot numbers yourself, as the library simply doesn't do that for I/O-slots. (Which slots or magazines are used for im/export can probably be configured, but I assume that you want them as import/export slots so your operators can easily swap tapes.) We looked at configuration settings to get more non-IO slots but failed to see how we could do that. 'Quantum Scalar 50' mean anything to you? The unit consists of two magazines, each of which olds 18 tapes, in three columns of 6. Hence, each of these is an IO slot, I'm guessing. Actually, all the information you need is already in the catalog, you've just got to modify mtx-changer to look the slot numbers up in the catalog, and when doing the listing, you need to ensure the I/O-slots are considered. I'm planning something similar for a customer who probably needs to use all the slots they have soon, but they are not there yet... Yes, I think that would be straight forward to alter. Just invoke another script to get the loaded value. I'll do that if it turns out I need it. I'm running the btape two-tape test now. On Monday, we'll do some real backups and see if they run fine. mtx-changer customizations will come as required. thanks you -- Dan Langille -- http://langille.org/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
People, PLEASE trim when quoting!
On Fri, 14 Aug 2009, John Drescher wrote:
I can tell you that my IMPORT/EXPORT slot does work correctly after a
slight modification of the mtx-changer script. Although after I put a
tape in it the first time I run update slots bacula says there are 23
slots instead of 24 so it ignores slot 24. I run update slots a second
time and all is well.
What did your mtx-changer modification do?
dev6 bacula # cat mtx-changer.patch
--- mtx-changer.old 2008-05-15 15:32:59.0 +0200
+++ mtx-changer 2008-05-15 15:13:12.0 +0200
@@ -188,7 +188,7 @@
# ${MTX} -f $ctl inventory
${MTX} -f $ctl status ${TMPFILE}
rtn=$?
- cat ${TMPFILE} | grep Storage Element [0-9]*:.*Full | awk
{print \$3 \$4} | sed s/Full *\(:VolumeTag=\)*//
+ cat ${TMPFILE} | sed s/ IMPORT\/EXPORT// | grep Storage
Element [0-9]*:.*Full | awk {print \$3 \$4} | sed s/Full
*\(:VolumeTag=\)*//
#
# If you have a VXA PacketLoader and the above does not work, try
# turning it off and enabling the following line.
This was added for bacula to recognize the barcode for slots labeled
IMPORT/EXPORT. I kind of doubt that this is your issue.
I think this is quite dangerous and the reasoning is as follows:
If update slots is run while a tape from a I/O slot is loaded into the
drive then the drive will report unknown as the parent slot and from
that point Bacula doesn't know where to unload it - end result is an
effectively wedged drive.
I made a similar tweak to try and use the I/O slots and backed it out
for this reason.
Ideally the script would be tweaked to associate any unknown tapes
in drives with the I/O slots
AB
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, August 14, 2009 3:17 pm, Alan Brown wrote: I made a similar tweak to try and use the I/O slots and backed it out for this reason. Can someone explain what IO slots are? And why I have 36 of them? -- Dan Langille -- http://langille.org/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] mtx: Unknown Storage Element Loaded
On Fri, 14 Aug 2009, Dan Langille wrote: I made a similar tweak to try and use the I/O slots and backed it out for this reason. Can someone explain what IO slots are? And why I have 36 of them? They are traditionally used for (un)loading individual tapes (mailslots) without stopping the robot (opening the main doors) In some larger libraries (bigger scalars for instance), one (or more) magazine is removable without opening the main door and pausing the robot. The idea is that the tapes can then be dispersed to appropriate slots within the robot without interfering with other ongoing operations or having the operator play dodge the high speed mechanism 36 seems a bit extreme if they are your only tape slots, but it makes sense in a large library with ~800 slots. AB -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula backups and restores
On Thu, 13 Aug 2009 06:13:11 -0400, tqz said: --===6257829277651962677== Hello all Lets say in the event that disaster strikes and all data on my server is lost for whatever reason. I have encrypted backups of the data on the server stored on tapes (on and off site) and NAS. After reinstalling my database management system, and then firing up bacula using copies I have of the director, client and storage daemon files how can I then read the catalog from the encrypted tape. Is there any way I can test this without overwriting the bacula database. Also is there a way to read files (the director, storage and daemon) off the encrypted storage and then restoring them using bacula command line tools or non bacula command line tools .or am I not making any sense?! The command line tool bextract can read tapes, but it can't read encrypted backups, so you would need to dump the catalog unencrypted. That may be OK, because all the information within it is stored on the tapes unencrypted anyway (Bacula only encrypts the contents of the files, not the filenames etc). Alternatively, you could use the Write Bootstrap option in the catalog backup job and keep a copy of this file for use with the restore command in bconsole. You need to keep a copy of each backup, since it records the information about the tape. Second thing is that I am noticing that the size of the backups on my different storage devices are different. So for example the first backup occurs on the tape and the size of the backup is 14.09gb, then on my second storage device it will be 14.12gb and my third one is 14.16gb. They are all full backups ??? Any idea why there may be different sizes Maybe encryption is non-deterministic? __Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Some Operational Questions: Backing up lots of stuff
Hi everyone, I have some strategy questions. We've been using Bacula for about 18 months; backing up ~3.5TB/week to DLT-S4 (Quantum SuperLoader). We are still on 2.2.8, but will be upgrading to 3.x this fall. Thanks to everyone on this list, and the Bacula team for an excellent product. We have a Network Applicance filer (previously produced under their StoreVault division), with both CIFS and NFS exports. Backing up NFS mounts on our backup server is kind of slow - 3-5MB/sec. Not having the hardware to put in to mount and back up the CIFS shares, I found that we can get ~20MB/sec by constructing a pipe on the server using rsh and the NetApp dump command. Of course, all we get into Bacula is a dump file, so we need to set up a similar arrangement with the restore command to restore things, but it's fine. I want to start backing up the NFS-native trees this way. However, backing up the whole thing as one backup job is problematic. It takes a long time, it's opaque, and it's the 600 lb (272kg) gorilla in the backup workflow. And a restore is going to be even more painful from a single backup job of the root of the device. I should point out that I have scripts currently to run through a list of CIFS shares, set up the rsh jobs and pipes, and generate a report of what got backed up and when and how. It's still one job, though, even though each share is a separate file in Bacula. It's a problem because these jobs create snapshots when they are submitted, and so there are snapshots sitting around for the entirety of the job, and I'm never sure whether they are going to be cleaned up properly if the job gets canceled. And if it does get canceled, I have to re-run everything again. Painful. This isn't the real question, though I'd love it if someone has something I haven't thought of. The real question is a more general one: I need to figure out a way to dynamically create jobs. I really want one job per filesystem - but what's the consensus of the best way to do this? Should I just write job definitions and fileset definitions to a file that's included in my director's config, then issue a reload? Is there an API that I've missed? Is there something in 3.x that is going to make this better? I want something that is as transparent as possible, and that can be set up so that when a new share/export gets created on the thing the backups get updated. I can run something in cron, or RunBeforeJob, but it just seems wrong. (By the way, it would be cool to have a plugin that would take the output from 'tar' or 'dump', and feed it to Bacula as if it were coming from an FD so Bacula would store the files and metadata... but I digress.) I know I can dynamically define a fileset. But, again, what I need is a more granular way to break down a large *job*. I can figure out how to kludge it - and I've shown the current NetApp backup system to a few people who've considered I should get some therapy - but I'm at the point where I think I need to ask for directions. We also have a few Windows servers that are in a different hemisphere. I have the same kind of problem: I'd love to just backup C:, but find we just can't keep the (session) up for long enough to get through it. I know that we're going to have Accurate backups, which I presume might allow us to restart a job, but again over a long Internet link this is going to be problematic. So, the question here is: is there a better way to plan for a likely inability to back up a large-ish filesystem in one job without resorting to having to enumerate all of the n level directories and break the task up into multiple jobs? I started writing a script to scan a filesystem and emit the necessary directories to break the backup into a certain number of pieces, but of course we only control the top level, and users are going to want to add things that we'll need to back up incrementally. Or, again, is there something I'm missing? I'm happy to discuss things off-list if that would be easier. Many thanks! _KMP -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
