On Thu, Nov 08, 2012 at 12:53:38PM +0100, Adrian Reyer wrote:
> On Wed, Nov 07, 2012 at 12:53:43PM +0100, Uwe Schuerkamp wrote:
> > to reasonable levels (dumping the db through a gzip --fast would take
> > five hours or so while an rsync takes only roughly 30 minutes,
> > including lzop compression
On Tue, Nov 06, 2012 at 04:15:18PM +0100, lst_ho...@kwsoft.de wrote:
>
> from my knowledge the jobs are created but take on hold as long as
> other jobs with different priority are running. So it looks like the
> catalog connections are established as part of the job creation. That
> said yo
Zitat von Uwe Schuerkamp :
> Hi folks,
>
> I'm having a problem understanding job priorities. We don't allow
> mixed jobs to run concurrently, so based on that I've set up my
> catalog backup at the lowest priority (25) while regular backups run
> at 10, some at prio 15 to assure the catalog back
Hi folks,
I'm having a problem understanding job priorities. We don't allow
mixed jobs to run concurrently, so based on that I've set up my
catalog backup at the lowest priority (25) while regular backups run
at 10, some at prio 15 to assure the catalog backup won't start before
all regular backup
