Arthur Emerson III wrote:
> I'm having a hard time visualizing how this can be
> done within the current Bacula architecture. Where do
> you run the File Daemon? Not everyone has a Windows-based
> vSphere management server.
The FD could run on any server you had available - a vSphere server, a
b
The dmesg looks great, and the autochanger has a permanent cleaning tape, so I
am good there.
I ran the following and btape reported an error. Any suggestions?
--begin paste--
storage:/etc/bacula# btape -v -c bacula-sd.conf /dev/nst0
Tape block granularity is 1024 bytes.
btape: butil.c:272 Usi
John Drescher wrote:
> I think you can update slots with the single drive running jobs. You
> can not label barcodes however.
I can confirm this, as I did this a couple of days ago, although watch
out for the size of the emailed job report, which for me was just under
4MB and contained thousand
> Yes, if you only have one drive, you need to have no jobs running in order to
> do 'update slots' or 'label barcodes'.
>
I think you can update slots with the single drive running jobs. You
can not label barcodes however.
John
--
On Mon, 15 Mar 2010 13:37:48 +1100
Norberto Meijome wrote:
> >
> >
> > Any time you add/remove tapes from the tape library, you need to do
> > 'update slots' and 'label barcodes' in bacula.
> >
> > Does that not behave as you expect?
> >
> > --
> > Alex Chekholko ch...@pcbi.upenn.edu
> >
>
>
Hi All;
I have Bacula 3.0.2-1 installed on a RHEL 5.4 and it works well without any
issues, but every day I get the following message from my log file watch
program:
sudo:
Authentication Failures:
(0) -> bacula: 1 Time(s)
Had a look with visudo, bacula is not present there, shou
On 03/18/2010 10:37 AM, Phil Stracchino wrote:
> On 03/18/10 10:03, Jeronimo Zucco wrote:
>> On 03/16/2010 03:40 PM, Phil Stracchino wrote:
>>> Doing this portably is actually a rather difficult problem because there
>>> are so many different partitioning schemes and partition table formats
>>> out
Craig Holyoak wrote:
>
> Given VMware's recent announcement to end support for
> VCB in favour of the new vStorage APIs (specifically,
> VADP), does anyone have any plans for integrating Bacula
> with these APIs? Integration could either be a drop in
> replacement program to do the same work as v
Sean Carolan wrote:
>> maybe change VolumeRetention to 5 days and do an "update volumes from
>> resource" (only changing *.conf won't do the trick).
>>
>> Also change "Use volume once" to "Maximum Volume Jobs = 1 "
>
> Here's what I have in my bacula-sd.conf:
>
> Device {
> Name = d2d4112
> D
On 03/18/10 10:03, Jeronimo Zucco wrote:
> On 03/16/2010 03:40 PM, Phil Stracchino wrote:
>> Doing this portably is actually a rather difficult problem because there
>> are so many different partitioning schemes and partition table formats
>> out there. It's a mess.
>
> Or we can used partimage b
Hi,
I am using Bacula 3.0.2 on Ubuntu 9.04.
I use disk staging backups, first to disk, and then on to tape.
The only part i seem to be having a problem with is the recyclepool.
It is set to Scratch, but volumes are never moved there, even if
status is recycle, full, or used.
The technicians remo
On 03/16/2010 03:40 PM, Phil Stracchino wrote:
> On 03/16/10 14:15, Gavin McCullagh wrote:
>
>> On Tue, 16 Mar 2010, Bob Cousins wrote:
>>
>>> - Explicit capturing of boot and partitioning information for easier
>>> bare metal restores. (Bare metal restores should be easy and fast for
>>>
I updated my Bacula to version 5.0.1 and set my job and file retention to 25
days, but in bconsole the show schedules command show the following
information to all schedules:
*"JobRetention=0 secs FileRetention=6 years 8 months 15 days 15 hours 28
mins 40 secs"*
File Retention = 25 days
Job Rete
"Juergen Koch" kirjoitti
viestissä:4ba20268.2050...@unister-gmbh.de...
> Hi Timo,
>
> Thank you, this work fine!
>
> But I've a another problem:
>
> I use the aotoprun-funktion in the Client-config. With 5.0.0 I receive
> the message:
>
> "Begin pruning Jobs older than 40 years 1 month 26 days 1
Hi Timo,
Thank you, this work fine!
But I've a another problem:
I use the aotoprun-funktion in the Client-config. With 5.0.0 I receive
the message:
"Begin pruning Jobs older than 40 years 1 month 26 days 1 hour 6 mins 46
secs."
I think, this is the time since UNIX-time. But I configure
F
15 matches
Mail list logo