On 7/10/2011 11:14 AM, Mike Hobbs wrote:
> I've had concurrent backups working fine for the past few days, this
> morning I login to check my server and I noticed that bacula/vchanger is
> only using 2 of my 4 virtual drives. I don't understand why, could you
> point me in the right direction to f
-Original Message-
>I suggest running smaller jobs. I don't mean to sound trite, but thatreally is
>the solution. Given that the alternative is non-trivial, thesensible choice
>is, I'm afraid, cancel the job.
I'm already kicking off 20+ jobs for a single system already. This does not
Resending, with additional information.
On Jul 10, 2011, at 3:18 PM, Steve Costaras wrote:
>
> -Original Message-
> From: Dan Langille [mailto:d...@langille.org]
> Sent: Sunday, July 10, 2011 12:58 PM
> To: stev...@chaven.com
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacu
On Jul 10, 2011, at 3:18 PM, Steve Costaras wrote:
>
> -Original Message-
> From: Dan Langille [mailto:d...@langille.org]
> Sent: Sunday, July 10, 2011 12:58 PM
> To: stev...@chaven.com
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Catastrophic error. Cannot wri
> Just had a quick look... the "read-only" message is this in stored/block.c:
>
> if (!dev->can_append()) {
> dev->dev_errno = EIO;
> Jmsg1(jcr, M_FATAL, 0, _("Attempt to write on read-only Volume. dev=%s\n"),
> dev->print_name());
> return false;
> }
>
>And can_append() is:
>
>int can_append()
>
> no idea, if we can find out what triggered the original message. Without
> doing anything physical, I did an umount storage=LTO4 from bacula and then
> went and did a full btape rawfill without a single problem on the volume:
>
> *status
> Bacula status: file=0 block=1
> Device status:
no idea, if we can find out what triggered the original message. Without doing
anything physical, I did an umount storage=LTO4 from bacula and then went and
did a full btape rawfill without a single problem on the volume:
*status
Bacula status: file=0 block=1
Device status: ONLINE IM_REP_EN f
Excerpts from Mike Hobbs's message of Fri Jul 08 15:23:47 -0400 2011:
Hi Mike,
> Due to the amount of data and machines I'll be backing up, I can see
> that when the first of the month comes around, running all my level
> 0 (Full) backups is going to take a week or more. I'm concerned
> because
>
> 3000 OK label. VolBytes=1024 DVD=0 Volume="FA0016" Device="LTO4" (/dev/nst0)
> Requesting to mount LTO4 ...
> 3905 Bizarre wait state 7
> Do not forget to mount the drive!!!
> 2011-07-10 03SD-loki JobId 6: Wrote label to prelabeled Volume "FA0016" on
> device "LTO4" (/dev/nst0)
> 2011-07-1
Daniel,
You need to verify that you have the proper SDKs. To do this look in the
/Developer/SDKs/ directory and you should see MacOSX10.4u.sdk, MacOSX10.5.sdk
and MacOSX10.6.sdk if you don't see all three SDKs then grab a Snow Leopard DVD
and open the 'Optional Installs' folder and double click
I'm new to Bacula and am having trouble getting backups of two Mac OS X clients
to work. I think the problem is with my configuration and hope someone can
correct my errors. Here are the conf files:
Mac1 bacula-fd.conf
Director {
Name = dracula-dir
Password = "blah"
}
Director {
Name = dra
-Original Message-
From: Dan Langille [mailto:d...@langille.org]
Sent: Sunday, July 10, 2011 12:58 PM
To: stev...@chaven.com
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Catastrophic error. Cannot write overflow block to
device "LTO4"
>>
>> 2) since everything is sp
schrieb Harald Schmalzbauer am 10.07.2011 16:28 (localtime):
> schrieb Adrian Reyer am 10.07.2011 15:58 (localtime):
> ...
>> I found using Spool Data for copy jobs to be faster for my setup. I have
>> fast local disks for spooling, but some of my disk storage is accessed
>> vie iSCSI on 1-GBit/s-l
On Jul 10, 2011, at 8:17 AM, Steve Costaras wrote:
>
>
> I am trying a full backup/multi-job to a single client and all was going well
> until this morning when I received the error below. All other jobs were
> also canceled.
>
> My question is two fold:
>
> 1) What the heck is this err
On 6/29/2011 5:05 PM, Josh Fisher wrote:
> By default, Bacula will select a volume that is already in a drive in
> preference to a volume not in a drive. For concurrent jobs writing to
> the same pool, this means they will always select the same volume. Thus
> if you set MaximumConcurrentJobs=1 in
schrieb Adrian Reyer am 10.07.2011 15:58 (localtime):
...
> I found using Spool Data for copy jobs to be faster for my setup. I have
> fast local disks for spooling, but some of my disk storage is accessed
> vie iSCSI on 1-GBit/s-links.
> However, I am currently running a few copy jobs and the limi
Hi Harry,
On Sun, Jul 10, 2011 at 03:39:36PM +0200, Harald Schmalzbauer wrote:
> The server is at remote site, so I can't hear any mechanicals, but I
> guess "at rest" means stop, thus my worries about extensive repositioning.
Sorry, I am no expert on drives and only use bacula my very self for 6
schrieb Adrian Reyer am 10.07.2011 14:43 (localtime):
> Hi Harry,
>
> On Sun, Jul 10, 2011 at 01:38:52PM +0200, Harald Schmalzbauer wrote:
>> of a average transfer rate of 65MB/s makes me worrying about massive
>> repositioning.
>
> AFAIK LTO-Drives have adaptive speeds compared to older technolo
Hi Harry,
On Sun, Jul 10, 2011 at 01:38:52PM +0200, Harald Schmalzbauer wrote:
> of a average transfer rate of 65MB/s makes me worrying about massive
> repositioning.
AFAIK LTO-Drives have adaptive speeds compared to older technologies. If
the data comes in slower, the drive will just run slower
I am trying a full backup/multi-job to a single client and all was going well
until this morning when I received the error below. All other jobs were also
canceled.
My question is two fold:
1) What the heck is this error? I can unmount the drive, issue a rawfill to
the tape w/ btape an
Dear bacula insiders,
I got a replacement for my old DDS5 - a LTO4.
Setup is D2D2T.
The problem is not the setup, but the tape drive utilization.
The disk-storage can provide well over 300MByte/s, and using tar with -b
126 or dump or dd, I see 78-160MB/s moving to the drive. So the problem
is prob
21 matches
Mail list logo
