On Oct 20, 2014, at 5:14 AM, Anton Gorlov wrote:
> postgresql.conf:
> max_connections = 100
> shared_buffers = 128MB
> temp_buffers = 512MB
> work_mem = 64MB
> maintenance_work_mem = 32MB
> fsync = off
> checkpoint_segments = 90
I’d start by bumping shared_buffers. Here’s how I solved a similar
I'm backuping only linux servers
24.10.2014 12:10, ALI LARAB пишет:
> Hello.I encountered the same problem with a job saving a Windows 2008 server.
> So, I have added and activated, in the bacula-dir.conf, the shadow copy
> option (VSS) to resolve this problem.
> FileSet{ Name = "WinJob_xxx"
Hello.I encountered the same problem with a job saving a Windows 2008 server.
So, I have added and activated, in the bacula-dir.conf, the shadow copy option
(VSS) to resolve this problem.
FileSet{ Name = "WinJob_xxx" Enable VSS = yes #activation of the Volume
Shadow Copy.
Include { Opt
20.10.2014 20:34, Anton Gorlov пишет:
> I change
> wall_buffers to -1 (-1 sets based on shared_buffers)
> shared_buffers = 1536MB
> effective_cache_size = 4608MB
>
> fsync is commented.
> bacula == 5.2.6+dfsg-9 (debian stable)
>
> run a full backup's at night...
+ full vacuum of dataase is help.
I change
wall_buffers to -1 (-1 sets based on shared_buffers)
shared_buffers = 1536MB
effective_cache_size = 4608MB
fsync is commented.
bacula == 5.2.6+dfsg-9 (debian stable)
run a full backup's at night...
20.10.2014 20:06, Eric Bollengier пишет:
> You might want to take some advise on how t
Hello,
Le 20. 10. 14 11:14, Anton Gorlov a écrit :
> The problem is observed recently time.
>
> After database backup "Dir inserting Attributes" job runs more than 5 hours.
> Previously, it takes less time. Size of database changed slightly, current
> size
> - 85Gb.
> the loads of io system: ioto
job with "Different backup" run on another day. Full jobs not ended at
this time. Early full backup is finish before different is run. Maximum
time for inserting attributes == 2-3 hours. At this time over 10 hours
All full backup is running with hour step for all clients.
20.10.2014 19:18, Bryn H
You have a very large number of jobs all trying to do inserts into the
database at once. What you are probably hitting is the limit of the
number of transactions/second that your database server can sustain -
most likely you are I/O bound at the disk level.
All of those 'inserting attribute' j
The problem is observed recently time.
After database backup "Dir inserting Attributes" job runs more than 5 hours.
Previously, it takes less time. Size of database changed slightly, current size
- 85Gb.
the loads of io system: iotop read 5 M/s, write several Kb
LA 1.4-2.2
atop retruns postgres
