There are several settings that can be increased in the posgresql.conf file. By default this file in the db/pgsql folder where NetVault Backup is installed.
max_connections
If you do not have enough max_connections configured, it can cause many errors and problems including:
WebUI problems
Fatal error: Could not connect to scheduler database to load job
Job Failed: Owning user 'default' (UID 0) does not have the required permissions for the job
In the PostgreSQL logs it will show the following error message if you exceed max_connections.
sorry, too many clients already
For larger NetVault Backup servers this may need to be increased to 200 or 400.
shared_buffers
For servers with 16GB+ RAM, this can be increased to 1GB.
effective_cache_size
For servers with 16GB+ RAM, this can be increased to 2GB
Note: On some systems the PostgreSQL service will not be able to start after increasing the shared_buffers and effective_cache_size. If so, revert these settings.
effective_io_concurrency
By default this is set to 1. On systems with high performance storage, it can be increased to allow multiple writes simultaneously. Setting this value too high will result in extra CPU overhead. You can use commands like ‘iostat -x 5 5’ or resource monitor while the database is under a heavy load to see if the storage is being well utilized. We don’t recommend setting this over 4.
max_worker_processes
The default is 8. For high performance servers this can be increased to 16.
After making changes to the postgresql.conf file, the PostgreSQL service will need to be restarted.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center