Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
On 04/15/13 15:31, Bill Arlofski wrote: I'll let you know what I come up with. Hi Leon, and everyone. :) Leon, as promised I have spent some time to take a second look at the auto_enable_disable_vols.sh which I had originally hacked together to use Josh Fisher's benablemag script to enable/disable the available/not_available vchanger magazines on a system. I have posted a new, almost completely re-written version which now sends one bconsole sqlquery command per magazine to enable all volumes on it if it is plugged in, or to disable all volumes on any magazines which are not currently plugged in. So, in your case (Leon) instead of calling bconsole 18 * 186 = 3348 times, it would now make only 18 calls to bconsole. New version is here: http://www.revpol.com/node/146 As far as I can tell it is working on our systems, ymmv, not responsible for rising sea levels, all comments welcome, etc. :) -- Bill Arlofski Reverse Polarity, LLC -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
On 04/12/13 04:47, Leon White wrote: That said, I am sticking to manually issuing the commands for now until I at least have a full backup completed. I decided not to use Bill's new script just yet, mainly because it takes a long time to cycle through all the non-mounted drives and disable them, even if they are already disabled. We have around 18 magazines (2TB drives have 2 magazines), each with 186 volumes, so it just took too long watching text scroll on the screen for what should be a quick drive switch operation. Instead, I issue something like 'benablemag 5 0' followed by 'benablemag 6 1', and set all drives to disabled immediately after formatting and adding the UUID to vchanger config. Leon, I only have (9) drives each with 69 volumes on them and I also notice that it takes more time than I would like (and adds many lines to the job output) That script was a quick write-up as kind of a proof-of-concept to automate Josh's benablemag script. My script/implementation works, yes, but [IMHO] it is not optimal - for the reasons you mention. When I have a few mins, I plan on re-visiting that script and maybe use SQL queries to bulk enable/disable volumes instead. Without looking now, I am pretty sure that would entail just a few queries to do the job instead of one bconsole enable or disable command for each volume and will work much much faster. I'll let you know what I come up with. -- Bill Arlofski Reverse Polarity, LLC -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
Hi guys, sorry for the delay in replying. To clarify what I mean by 'without typing anything in the terminal', I was hoping to try out the web interface in the future to see if it can be used to start jobs. If the benablemag and update slots commands could be automated in some way, this would make the system sufficiently user friendly that I could just document the mechanism behind it and move on to other projects. Hopefully a few practice runs would be all someone needs to understand the process of switching the drives. Ideally, a message would pop up in the web UI saying 'drive full, insert next drive' or something similarly user friendly and idiot proof. That said, I am sticking to manually issuing the commands for now until I at least have a full backup completed. I decided not to use Bill's new script just yet, mainly because it takes a long time to cycle through all the non-mounted drives and disable them, even if they are already disabled. We have around 18 magazines (2TB drives have 2 magazines), each with 186 volumes, so it just took too long watching text scroll on the screen for what should be a quick drive switch operation. Instead, I issue something like 'benablemag 5 0' followed by 'benablemag 6 1', and set all drives to disabled immediately after formatting and adding the UUID to vchanger config. This has created a new problem: during the full backup which I have been running over the past days, if a drive sits in the changer for a few hours before the next drive in sequence is loaded, the bconsole messages indicate that bacula is automatically Pruning oldest volume gpea-backup-0010-0001 or something similar. This is obviously because I haven't played with the volume recycling settings yet. Does this mean that the backup set is incomplete? Have the volumes been erased in some way, or just marked as next in line for recycling, but not overwritten? Thanks for the help, this is quite an adventure! Cheers, Leon On Wed, Apr 3, 2013 at 11:00 PM, Bill Arlofski waa-bac...@revpol.comwrote: On 04/03/13 04:59, Leon White wrote: Hi Bill and Josh, I just want to say again how helpful your support and development skills have been, not just for our system here but also helping a relative novice like me get my head around scripting approaches! Happy to help out. :) Bill, your latest script serves to check which magazine is currently inserted and then runs benablemag with the appropriate variable for that magazine, correct? Yes. BUT - more importantly - it also calls Josh's benablemag script to DISABLE all the volumes on any magazines that are not available at the time you run my script. That is important to remember. Our use case here involves very infrequent backups (6 month cycle) of very large amounts of data (30 TB). As such, we don't have much use for timed jobs because we plan to run it manually once the hard drives have been retrieved from safe storage every 6 months. Ahhh. I see. The main issue is the ability for a luddite to be able to switch drives in the autochanger when the light stops flashing without typing anything into any terminal anywhere. Preparing the drives for first use and then disabling all volumes works fine with my clunky scripts, but I wonder how to integrate the benablemag $thismag 1 command with udev so that a newly inserted drive is enabled by the system (rather than a bacula job), followed by bcommand update slots or something similar (as this command currently also fails). This should only occur for drives passing through the /etc/auto.vchanger rule, or whatever the equivalent is in udev (I'm still very fuzzy on this point). Then after the customary 3 minute wait, backup would continue with no user interaction. Rinse and repeat until the job is done. Leon, I am confused as to when or how you intend to start a job. You do mention we plan to run it manually but you also say without typing anything into any terminal anywhere Those two things are somewhat mutually exclusive. Even if it has to be just unplug drive 1, plug in drive 2 and walk away simple, you still need a way to start a job. If someone needs to manually start a job, then I would still say use a RunScript. But instead of my previous recommendation of a scheduled Admin job to update the database of available volumes (using my script and Josh's), and a bconsole update slots command, I would just include those two in the actual backup job as a RunScript. So, then it goes like this: LEDs stop flashing, swap drive(s) out, in bconsole type: run Job=Our_30TB_Job enter Walk away as db gets updated with currently available volumes, update slots is run, and then the job starts backing up data. Leon, in my opinion even that is too simplistic. I mean that just because there are no LEDs flashing, it does not necessarily mean a job is not currently running. Bacula could be moving volumes in/out of a
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
Hi Bill and Josh,
I just want to say again how helpful your support and development skills
have been, not just for our system here but also helping a relative novice
like me get my head around scripting approaches!
I will be implementing a lot of this for our system over the coming days
(another Chinese holiday) and I want to make sure I have a few things
right. Bill, your latest script serves to check which magazine is currently
inserted and then runs benablemag with the appropriate variable for that
magazine, correct?
Our use case here involves very infrequent backups (6 month cycle) of very
large amounts of data (30 TB). As such, we don't have much use for timed
jobs because we plan to run it manually once the hard drives have been
retrieved from safe storage every 6 months. The main issue is the ability
for a luddite to be able to switch drives in the autochanger when the
light stops flashing without typing anything into any terminal anywhere.
Preparing the drives for first use and then disabling all volumes works
fine with my clunky scripts, but I wonder how to integrate the benablemag
$thismag 1 command with udev so that a newly inserted drive is enabled by
the system (rather than a bacula job), followed by bcommand update slots
or something similar (as this command currently also fails). This should
only occur for drives passing through the /etc/auto.vchanger rule, or
whatever the equivalent is in udev (I'm still very fuzzy on this point).
Then after the customary 3 minute wait, backup would continue with no user
interaction. Rinse and repeat until the job is done.
Sorry this is a little long! Takes me a while to think through it all. If
either of you wants to pick this up as a supported job, we do have some
limited funding available :)
Cheers from Beijing,
Leon
On Wed, Apr 3, 2013 at 8:36 AM, Bill Arlofski waa-bac...@revpol.com wrote:
Leon,
After replying to you earlier today, I spent a little time testing Josh's
benablemag script, and thought about my just create a script to run in an
Admin job comment.
Thought that it required a little more information.
So, here is my Admin job called UpdateSlots which runs before all of my
other jobs each night.
--[snip]--
#
# Update Slots Job
#
Job {
Name = UpdateSlots
Client = None
Type = Admin
FileSet = None
Storage = c0
Schedule = WeeklyToOffsiteDisk
Messages = Standard
Priority = 8
SpoolData = no
Pool = Default
RunScript {
RunsWhen = Before
RunsOnClient = no
Fail Job On Error = no
Command =
/etc/bacula/include/mag_and_vol_scripts/auto_enable_disable_vols.sh
Command = /etc/bacula/include/runbefore-updateslots.sh
}
}
--[snip]--
Here is the runbefore-updateslots.sh script that is called:
--[snip]--
#!/bin/bash
#
# waa - 20091110
# --
BC=/usr/sbin/bconsole
CONF=/path/to/bconsole.conf
STORAGE=c0
DRIVE=0
$BC -c $CONF WAAEOF
update slots storage=$STORAGE drive=$DRIVE
quit
WAAEOF
--[snip]--
And here is the auto_enable_disable_vols.sh script I am using starting
today.
http://www.revpol.com/node/146
Hope this helps - someone. :)
--
Bill Arlofski
Reverse Polarity, LLC
--
陆智诚 | Leon White
绿色和平 | Greenpeace East Asia
+86 186 0692 9781 | Skype: strophy
行动，带来改变。 Positive change through action.
--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
On 04/03/13 04:59, Leon White wrote: Hi Bill and Josh, I just want to say again how helpful your support and development skills have been, not just for our system here but also helping a relative novice like me get my head around scripting approaches! Happy to help out. :) Bill, your latest script serves to check which magazine is currently inserted and then runs benablemag with the appropriate variable for that magazine, correct? Yes. BUT - more importantly - it also calls Josh's benablemag script to DISABLE all the volumes on any magazines that are not available at the time you run my script. That is important to remember. Our use case here involves very infrequent backups (6 month cycle) of very large amounts of data (30 TB). As such, we don't have much use for timed jobs because we plan to run it manually once the hard drives have been retrieved from safe storage every 6 months. Ahhh. I see. The main issue is the ability for a luddite to be able to switch drives in the autochanger when the light stops flashing without typing anything into any terminal anywhere. Preparing the drives for first use and then disabling all volumes works fine with my clunky scripts, but I wonder how to integrate the benablemag $thismag 1 command with udev so that a newly inserted drive is enabled by the system (rather than a bacula job), followed by bcommand update slots or something similar (as this command currently also fails). This should only occur for drives passing through the /etc/auto.vchanger rule, or whatever the equivalent is in udev (I'm still very fuzzy on this point). Then after the customary 3 minute wait, backup would continue with no user interaction. Rinse and repeat until the job is done. Leon, I am confused as to when or how you intend to start a job. You do mention we plan to run it manually but you also say without typing anything into any terminal anywhere Those two things are somewhat mutually exclusive. Even if it has to be just unplug drive 1, plug in drive 2 and walk away simple, you still need a way to start a job. If someone needs to manually start a job, then I would still say use a RunScript. But instead of my previous recommendation of a scheduled Admin job to update the database of available volumes (using my script and Josh's), and a bconsole update slots command, I would just include those two in the actual backup job as a RunScript. So, then it goes like this: LEDs stop flashing, swap drive(s) out, in bconsole type: run Job=Our_30TB_Job enter Walk away as db gets updated with currently available volumes, update slots is run, and then the job starts backing up data. Leon, in my opinion even that is too simplistic. I mean that just because there are no LEDs flashing, it does not necessarily mean a job is not currently running. Bacula could be moving volumes in/out of a drive, waiting on some type of operator intervention etc. So, I'd say that no matter what, someone should be running a bare minimum of a few commands at the console before swapping drives out: * messages (to clear the console message log and quickly see if there are any obvious issues) * status dir (to see if all jobs have completed and no jobs are queued/waiting etc, see if drive is blocked etc) * cancel (if necessary clean up and cancel any jobs that have an issue) Otherwise, if a job is just requiring another magazine change, swap out magazine, then run run the Admin job to enable/disable volumes, and update slots. Bacula should continue job after that. If all jobs are done, swap out agazines and: * run Job=Our_30TB_Job (to start the next job) Of course, if you are emailing messages to an admin-type person, then most issues would be pre-known, and possibly solved remotely before the worker is on-site to swap magazines but... you know... Sorry this is a little long! Takes me a while to think through it all. If either of you wants to pick this up as a supported job, we do have some limited funding available :) I might be interested, you may contact me off-list if we can't get you up and running via the list. But I would be happy to help in here if we can get past what I think is just a little confusion - maybe a little on your part and a little on mine. :) -- Bill Arlofski Reverse Polarity, LLC -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
On 04/01/13 05:38, Leon White wrote: I plan to use this script to ensure that all volumes are set to disabled before and after they are used to prevent bacula from trying to use unmounted volumes. Is there any way to trigger this script to run silently as soon as the update slots command is triggered, or is there some other point we could trigger it during the process of swapping drives in the eSATA changer? Perhaps automount could do it and then subsequently use the bcommand script to call update slots in bconsole as well, making the process of changing drives effectively fully automatic and independent from the shell. I won't be operating this system forever, and I want to keep the process as simple as possible for anybody else who has to use it. Hi Leon... You could create a simple job of type Admin with a RunScript that calls a script (or multiple scripts) to enable/disable the appropriate magazines/volumes and run the bconsole update slots command. Then, set the Admin job to run before your nightly jobs by starting at the same time (e.g. use same schedule) but with a higher priority (lower numeric value is higher priority). Also, for operations outside of any schedule, you would just need to manually run the Admin job after a disk (magazine) change before running any other jobs. I am also looking into Josh's scripts currently due to a similar problem I have run into. I just have not had the time to get around to it until this thread came along. :) Good luck Leon. P.S. Thanks for sharing Josh. -- Bill Arlofski Reverse Polarity, LLC -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
Leon,
After replying to you earlier today, I spent a little time testing Josh's
benablemag script, and thought about my just create a script to run in an
Admin job comment.
Thought that it required a little more information.
So, here is my Admin job called UpdateSlots which runs before all of my
other jobs each night.
--[snip]--
#
# Update Slots Job
#
Job {
Name = UpdateSlots
Client = None
Type = Admin
FileSet = None
Storage = c0
Schedule = WeeklyToOffsiteDisk
Messages = Standard
Priority = 8
SpoolData = no
Pool = Default
RunScript {
RunsWhen = Before
RunsOnClient = no
Fail Job On Error = no
Command =
/etc/bacula/include/mag_and_vol_scripts/auto_enable_disable_vols.sh
Command = /etc/bacula/include/runbefore-updateslots.sh
}
}
--[snip]--
Here is the runbefore-updateslots.sh script that is called:
--[snip]--
#!/bin/bash
#
# waa - 20091110
# --
BC=/usr/sbin/bconsole
CONF=/path/to/bconsole.conf
STORAGE=c0
DRIVE=0
$BC -c $CONF WAAEOF
update slots storage=$STORAGE drive=$DRIVE
quit
WAAEOF
--[snip]--
And here is the auto_enable_disable_vols.sh script I am using starting today.
http://www.revpol.com/node/146
Hope this helps - someone. :)
--
Bill Arlofski
Reverse Polarity, LLC
--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
Hi Josh, thanks for taking the time once again to respond to support my bacula/vchanger project! I was able to read, set up and configure the scripts you supplied, the variables are quite clear and anybody who set up their own bacula system should be able to fill them in. Note that it may be necessary to change the #!/bin/sh at the beginning of the files to #!/bin/bash depending on your system (mine is Ubuntu Server 12.10). I plan to use this script to ensure that all volumes are set to disabled before and after they are used to prevent bacula from trying to use unmounted volumes. Is there any way to trigger this script to run silently as soon as the update slots command is triggered, or is there some other point we could trigger it during the process of swapping drives in the eSATA changer? Perhaps automount could do it and then subsequently use the bcommand script to call update slots in bconsole as well, making the process of changing drives effectively fully automatic and independent from the shell. I won't be operating this system forever, and I want to keep the process as simple as possible for anybody else who has to use it. Thanks mate, Leon On Tue, Mar 26, 2013 at 12:13 AM, Josh Fisher jfis...@pvct.com wrote: On 3/22/2013 5:59 AM, Leon White wrote: Hi list! I am using Bacula 5.2.6 with vchanger 0.8.6 to backup a multi-terabyte fileset to a bunch of 1 and 2TB drives in an eSATA virtual autochanger. I have formatted each drive with one or two 2TB partitions with 186x 5GB volume slots, and vchanger switches between 2 magazine bays when necessary for the 2TB drives. My problem is that when bacula hits the last writable volume in the virtual magazine, it attempts to load the next appendable volume from the next available magazine. Obviously, I haven't changed the drive yet, and bacula attempts this in vain 4 more times before pausing the job and requesting that I mount the next magazine. I then switch the drives in the changer, issue 'update slots', and bacula updates all the slot data. I thought it would then continue from the next volume it initially tried to mount, but instead it skips the first five volumes and starts writing the sixth. These volumes are marked as 'error' and not used. It looks like this: http://i.troll.ws/e60e9955.png This is what hitting the end of the magazine looks like (screenshot shows jump to next appendable volume, which happens not to be 0001): http://i.troll.ws/250d9942.png Is there a way to tell bacula to stop and ask for a mount when it uses the last volume identified by update slots, and immediately request the magazine change? Or to step back to the first volume in a magazine after mounting and issuing update slots? The trick is to disable a drive's volumes when it is not attached and enable them when attached. This can be done with the update volume=??? enabled=? command. Bacula will not consider a disabled volume available for use. I use the attached scripts for vchanger autochangers. They allow enabling/disabling all volumes on a magazine drive or only volumes on a magazine that are in a specified pool. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- 陆智诚 | Leon White 绿色和平 | Greenpeace East Asia +86 186 0692 9781 | Skype: strophy 行动，带来改变。 Positive change through action. -- Own the Future-Intelreg; Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
On 4/1/2013 5:38 AM, Leon White wrote: Hi Josh, thanks for taking the time once again to respond to support my bacula/vchanger project! I was able to read, set up and configure the scripts you supplied, the variables are quite clear and anybody who set up their own bacula system should be able to fill them in. Note that it may be necessary to change the #!/bin/sh at the beginning of the files to #!/bin/bash depending on your system (mine is Ubuntu Server 12.10). I plan to use this script to ensure that all volumes are set to disabled before and after they are used to prevent bacula from trying to use unmounted volumes. Is there any way to trigger this script to run silently as soon as the update slots command is triggered, or is there some other point we could trigger it during the process of swapping drives in the eSATA changer? Perhaps automount could do it and then subsequently use the bcommand script to call update slots in bconsole as well, making the process of changing drives effectively fully automatic and independent from the shell. I won't be operating this system forever, and I want to keep the process as simple as possible for anybody else who has to use it. It is possible to construct a udev rule that runs a script when a device is attached/detached. I don't think there is any way to do this with autofs/automount. -- Own the Future-Intelreg; Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
On 3/22/2013 5:59 AM, Leon White wrote: Hi list! I am using Bacula 5.2.6 with vchanger 0.8.6 to backup a multi-terabyte fileset to a bunch of 1 and 2TB drives in an eSATA virtual autochanger. I have formatted each drive with one or two 2TB partitions with 186x 5GB volume slots, and vchanger switches between 2 magazine bays when necessary for the 2TB drives. My problem is that when bacula hits the last writable volume in the virtual magazine, it attempts to load the next appendable volume from the next available magazine. Obviously, I haven't changed the drive yet, and bacula attempts this in vain 4 more times before pausing the job and requesting that I mount the next magazine. I then switch the drives in the changer, issue 'update slots', and bacula updates all the slot data. I thought it would then continue from the next volume it initially tried to mount, but instead it skips the first five volumes and starts writing the sixth. These volumes are marked as 'error' and not used. It looks like this: http://i.troll.ws/e60e9955.png This is what hitting the end of the magazine looks like (screenshot shows jump to next appendable volume, which happens not to be 0001): http://i.troll.ws/250d9942.png Is there a way to tell bacula to stop and ask for a mount when it uses the last volume identified by update slots, and immediately request the magazine change? Or to step back to the first volume in a magazine after mounting and issuing update slots? The trick is to disable a drive's volumes when it is not attached and enable them when attached. This can be done with the update volume=??? enabled=? command. Bacula will not consider a disabled volume available for use. I use the attached scripts for vchanger autochangers. They allow enabling/disabling all volumes on a magazine drive or only volumes on a magazine that are in a specified pool. volume_scripts.tgz Description: application/compressed -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Vchanger attempts to mount 5 volumes before stopping and requesting magazine change
Hi list! I am using Bacula 5.2.6 with vchanger 0.8.6 to backup a multi-terabyte fileset to a bunch of 1 and 2TB drives in an eSATA virtual autochanger. I have formatted each drive with one or two 2TB partitions with 186x 5GB volume slots, and vchanger switches between 2 magazine bays when necessary for the 2TB drives. My problem is that when bacula hits the last writable volume in the virtual magazine, it attempts to load the next appendable volume from the next available magazine. Obviously, I haven't changed the drive yet, and bacula attempts this in vain 4 more times before pausing the job and requesting that I mount the next magazine. I then switch the drives in the changer, issue 'update slots', and bacula updates all the slot data. I thought it would then continue from the next volume it initially tried to mount, but instead it skips the first five volumes and starts writing the sixth. These volumes are marked as 'error' and not used. It looks like this: http://i.troll.ws/e60e9955.png This is what hitting the end of the magazine looks like (screenshot shows jump to next appendable volume, which happens not to be 0001): http://i.troll.ws/250d9942.png Is there a way to tell bacula to stop and ask for a mount when it uses the last volume identified by update slots, and immediately request the magazine change? Or to step back to the first volume in a magazine after mounting and issuing update slots? Thanks! Leon -- 陆智诚 | Leon White 绿色和平 | Greenpeace East Asia +86 186 0692 9781 | Skype: strophy 行动，带来改变。 Positive change through action. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
