Florian Schnabel wrote:
Juliet Kemp wrote:
How long is it normal for pruning/purging a volume to take? I have
found that it takes several hours, even if only purging 2 or 3 jobs (&
incremental jobs, rather than full ones) - this obviously can delay
backups quite significantly.
pruning sh
We all have such an Index.
>From "make_mysql_tables":
CREATE TABLE File (
FileId INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
FileIndex INTEGER UNSIGNED NOT NULL DEFAULT 0,
JobId INTEGER UNSIGNED NOT NULL REFERENCES Job,
PathId INTEGER UNSIGNED NOT NULL REFERENCES Path,
FilenameId INT
On Wed, 25 Jan 2006, Michael 'buk' Scherer wrote:
I suggest getting a faster box, cause prune/pruge is all about SQL
Statements. DELETE FROM File where JobId='1234';
Did you have a JobID index?
---
This SF.net email is sponsored by: Splunk
On Wed, 25 Jan 2006 - 12:19pm, Florian Schnabel wrote:
> Juliet Kemp wrote:
>> Hi,
>>
>> How long is it normal for pruning/purging a volume to take? I have found
>> that it takes several hours, even if only purging 2 or 3 jobs (& incremental
>> jobs, rather than full ones) - this obviously can d
On 25 Jan 2006 at 11:08, Juliet Kemp wrote:
> Hi,
>
> How long is it normal for pruning/purging a volume to take? I have
> found that it takes several hours, even if only purging 2 or 3 jobs (&
> incremental jobs, rather than full ones) - this obviously can delay
> backups quite significantly
Juliet Kemp wrote:
Hi,
How long is it normal for pruning/purging a volume to take? I have
found that it takes several hours, even if only purging 2 or 3 jobs (&
incremental jobs, rather than full ones) - this obviously can delay
backups quite significantly.
Does the purge/prune actually re
Hi,
How long is it normal for pruning/purging a volume to take? I have
found that it takes several hours, even if only purging 2 or 3 jobs (&
incremental jobs, rather than full ones) - this obviously can delay
backups quite significantly.
Does the purge/prune actually require interaction wi
