On Sun, Nov 16, 2008 at 3:25 PM, Dan Langille <[EMAIL PROTECTED]> wrote:
>
> On Nov 15, 2008, at 3:07 PM, John Drescher wrote:
>
>>> I have a similar problem with postgres; the catalog database is now so
>>> large that restoring it from a pg_dump backup takes 3-4 hours. This is
>>> before you acco
On Nov 15, 2008, at 3:07 PM, John Drescher wrote:
>> I have a similar problem with postgres; the catalog database is now
>> so
>> large that restoring it from a pg_dump backup takes 3-4 hours.
>> This is
>> before you account for the length of time taken to read it from the
>> tape.
Talki
> I have a similar problem with postgres; the catalog database is now so
> large that restoring it from a pg_dump backup takes 3-4 hours. This is
> before you account for the length of time taken to read it from the tape.
>
How big is your database? pg_dump of my 21GB database takes less than
5 mi
junior.listas wrote:
> 1) mysql tables became huge ( each backup adds a million and six
> hundred thousand lines ), so i split the configuration into 2 daemons
> with 2 different bases, one for mon,tue,wed and other for thu,fri( and
> one 3th for monthly bkps ) ; because between a backup starts
Hi all;
I'm using bacula for a long time, but I always use the same
configuration on all of my costumers: Full diary backups.
..and here my problems start...
first of all, my diary backup take a long time, almost 8 hours, and it
generates a very huge load in the servers... this "default costume
