Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
home:crameleon:branches:home:lrupp
postgresql-backupscript
postgresql-backupscript.sysconfig
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File postgresql-backupscript.sysconfig of Package postgresql-backupscript
## Path: System/Backup ## Description: ## Type: yesno ## Default: yes # # Start backup script. # START_BACKUP="yes" ## Type: yesno ## Default: no # # If set to "yes", the script will fail immediately on dump or compression errors. # If set to "no", it will record errors, but continue processing and only fail at the end. # ABORT_ON_ERROR="no" ## Type: string ## Default: /root/backup/db # # Place where the database backup files should be # stored. The path will be created if it doesn't # exist. # BACKUPDIR="/root/backup/postgresql" ## Type: string ## Default: /usr/bin/xz # # Which executable should be used to compress the SQL dump files? # The executable should accept a filename as option on the command # line - like /usr/bin/bzip2 or /usr/bin/xz # # Please check that the executable exists before changing anything # here. If the file is not executable, the script will still run, # but not compress the SQL dump files at all. # COMPRESS_EXE='/usr/bin/xz' ## Type: yesno ## Default: yes # # When should the sql backup files be compressed? # Normal behavior: run backups first and compress later. # Alternative (no): compress each sql file once it was created. # # The alternative might use less space on disk, but has the # backtrack that the database can not really be unlocked and # start to resync immediately once the backup files are created. # Choose your poison. # COMPRESS_AFTER_UNLOCK="yes" ## Type: string ## Default: '' # # Special options for the COMPRESS_EXE. # You might want to define another compression level or # other options of your favorite compression tool. # COMPRESS_OPTS='' ## Type: yesno ## Default: yes # # Use Email to send messages from the backup script. # This is enabled by default. # USE_EMAIL='yes' ## Type: string ## Default: root@localhost # # Email address to send errors. # EMAIL="root@localhost" ## Type: string ## Default: /var/log/mysql-backup.log # # Logfile # LOGFILE="/var/log/postgresql-backup.log" ## Type: integer ## Default: 14 # # Retention period for storing old backup files. # Files older than this value in $BACKUPDIR will # be deleted. # Set to '0' if you want to store all backups. # RETENTION=14 ## Type: string ## Default: pg_hba.conf pg_ident.conf postgresql.auto.conf postgresql.conf # # Which configuration files should be included in the backup. # Please not that the backup script expects them inside the DATADIR directory # (where postgres is able to find them as well). # The DATADIR will be automatically detected, you should need to provide the # correct filenames here. Symlinks will be dereferenced. # CONFIG_FILES="pg_hba.conf pg_ident.conf postgresql.auto.conf postgresql.conf" ## Type: string ## Default: 'template0' # # You might want to exclude one or more database from the backup, please # enter the database names here (separated by whitespace). # The 'template0' database is per default excluded here and should stay, # unless you know what you are doing. # (Just note that other template DBs are per default backed up.) # EXCLUDE_DB='template0' ## Type: yesno ## Default: no # # Use NSCA to send messages from the backup to your monitoring. # Please check/configure the other NSCA values here as well in # case you want to use it. # USE_NSCA='no' ## Type: string ## Default: '/etc/send_nsca.cfg' # # The path to the nsca configuration file. # SEND_NSCA_CONFIG='/etc/send_nsca.cfg' ## Type: string ## Default: '/usr/bin/send_nsca' # # The path to the nsca binary. # SEND_NSCA_BIN='/usr/bin/send_nsca' ## Type: string ## Default: '' # # The hostname used in the NSCA messages. # This name needs to be the same as configured in your # monitoring server for this machine. # Fallback is the output of the: 'hostname -s' command. # SEND_NSCA_HOSTNAME=$(hostname -s) ## Type: string ## Default: 'localhost' # # The hostname of your monitoring server. # You can use any resolvable name or IP address here. # NSCA will try to send messages to this address. # NAGIOSHOST='localhost' ## Type: string ## Default: 'PostgreSQL backup' # # The name of the service, configured on your monitoring server. # Please make sure that the server name configured here is the same # as the one your monitoring server shows in the WebUI. # If any of 'SEND_NSCA_HOSTNAME' or 'NAGIOS_SERVICE_NAME' are not # identical on both systems, the messages from NSCA will be ignored. # NAGIOS_SERVICE_NAME='PostgreSQL backup' ## Type: string ## Default: '' # # Additional options added to each psql* and pg_dump* pg_isready calls. # Options given here should be recognized by all the above binaries. # Could be used to define the host, user and password to log-in. # PGSQL_OPTS='' ## Type: string ## Default: '' # # If you need to run extra commands before the real backup starts, # please add the full path to your script here. # # There should be example scripts in # /usr/share/doc/packages/postgresql-backupscript/examples/ # which can be used to stop a classical slave during a backup # or allow a cluster node to get temporary out of sync with the # rest of the cluster - so the backup can be faster and consistent. # PGSQL_SCRIPT_BEFORE_DUMP="" ## Type: string ## Default: '' # # If you need to run extra commands after the real backup finished, # please add the full path to your script here. # # There are some example scripts in # /usr/share/doc/packages/postgresql-backupscript/examples/ # which can be used to start a classical slave during a backup # or allow a cluster node to get synced again with the rest of the # cluster. # PGSQL_SCRIPT_AFTER_DUMP="" ## Type: string ## Default: '' # # If you want to run extra scripts after all compression finished, # please add the full path to your script here. # Think about copying the final backup directory to a backup server # or something similar. # PGSQL_SCRIPT_AFTER_COMPRESSION=""
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor