[EMAIL PROTECTED] writes:
> I've had similar failures--due to client problems--in the midst of multi-TB
> backups, and was extremely interested to hear about what might have been a
> solution to resume the backup without starting from the beginning.
I think most backup programs encounter this at
Sorry. While not an excuse...I was not in a good mood this morning
and took yoru sarcasm personally. I myself am very sarcastic. Anyway.
Thanks for the advice, it's appreciated.
-Aaron
On Jan 8, 2007, at 12:19 PM, Kern Sibbald wrote:
> On Monday 08 January 2007 14:22, Aaron Knister wrote:
>>
On Tuesday 09 January 2007 11:54, Alan Brown wrote:
> On Mon, 8 Jan 2007, Kern Sibbald wrote:
>
> > My advice to other users, remains the same: If a Job fails, the File
records
> > will most likely not have been inserted
>
> Or in other words, if spooling data+attributes is enabled, resuming a
On Mon, 8 Jan 2007 [EMAIL PROTECTED] wrote:
> Hmmm I don't know anything about the internal structure of bacula, or much
> about databases, but it seems to me that this is a serious weakness. Would it
> be
> possible for baclula to function more like a journaling filesystems in terms
> of
>
On Mon, 8 Jan 2007, Kern Sibbald wrote:
> My advice to other users, remains the same: If a Job fails, the File records
> will most likely not have been inserted
Or in other words, if spooling data+attributes is enabled, resuming a
failed job is almost guaranteed to result in an unrestorable back
In the message dated: Mon, 08 Jan 2007 18:19:37 +0100,
The pithy ruminations from Kern Sibbald on
were:
=> On Monday 08 January 2007 14:22, Aaron Knister wrote:
=> > Thanks for the sarcasm. NOT. I come here for support, not to be
=> > ridiculed. And i'll have you know that the restore from th
On Monday 08 January 2007 14:22, Aaron Knister wrote:
> Thanks for the sarcasm. NOT. I come here for support, not to be
> ridiculed. And i'll have you know that the restore from that backup
> set did work.
Yes, I was sarcastic, but life is (at least I am) like that.
I certainly didn't mean
On 8 Jan 2007 at 8:22, Aaron Knister wrote:
> On Jan 8, 2007, at 4:29 AM, Kern Sibbald wrote:
>
> > On Sunday 07 January 2007 23:03, Aaron Knister wrote:
> >> I solved this problem myself. I'm not sure how elegant the solution
> >> is, however.
> >>
> >> Using myphpadmin I changed the "JobStatus"
Thanks for the sarcasm. NOT. I come here for support, not to be
ridiculed. And i'll have you know that the restore from that backup
set did work.
On Jan 8, 2007, at 4:29 AM, Kern Sibbald wrote:
> On Sunday 07 January 2007 23:03, Aaron Knister wrote:
>> I solved this problem myself. I'm not s
On Mon, 8 Jan 2007, Silver Salonen wrote:
> To me it sounds very.. um.. important. I've had similar situations, but with
> 20-30 GB, so it hasn't been SO critical (only sufficiently as I do backups
> via WAN).
I've had it happen 700Gb into 1Tb backups.
There's a few good reasons to keep backup s
On Sunday 07 January 2007 23:03, Aaron Knister wrote:
> I solved this problem myself. I'm not sure how elegant the solution
> is, however.
>
> Using myphpadmin I changed the "JobStatus" field in the respective
> jobid's mysql entry from "f" to "T". I then re-ran the job and it
> picked up mo
Hi.
To me it sounds very.. um.. important. I've had similar situations, but with
20-30 GB, so it hasn't been SO critical (only sufficiently as I do backups
via WAN).
Could anybody confirm that it is really possible to "resume" jobs like this?
What are the risks in such case? Should it be possi
I solved this problem myself. I'm not sure how elegant the solution
is, however.
Using myphpadmin I changed the "JobStatus" field in the respective
jobid's mysql entry from "f" to "T". I then re-ran the job and it
picked up more or less where it left off.
-Aaron
On Jan 5, 2007, at 10:29 PM
Hi,
I recently had a backup job fail mid way. It was backing up 5
terabytes of data, and had written 3tb off to tape. The job stopped
because there were no more writable volumes in the particular volume
pool to which the job was assigned. I cleared up a volume however the
job did not resume
14 matches
Mail list logo
