gpcrondump is a wrapper utility for gp_dump, which can be called directly or from a crontab entry.

Syntax

gpcrondump -x database_name 

[-s schema | -t schema.table | -T schema.table] 

[-w dbid[,...]] [-u backup_directory] 

[-R post_dump_script] [-c | -o] [-z] [-r] [-f free_space_percent]

[-b] [-i] [-j | -k] [-g] [-G] [-C] [-d master_data_directory] 

[-B parallel_processes] [-a] [-q] 

[-y reportfile] [-l logfile_directory] [-D] 

{ [-E encoding] [--inserts | --column-inserts] [--oids]

[--no-owner | --use-set-session-authorization]

[--no-privileges] }

gpcrondump -?

gpcrondump -v

gpcrondump is a wrapper utility for gp_dump. By default, dump files are created in their respective master and segment data directories in a directory named db_dumps/YYYYMMDD. The data dump files are compressed by default using gzip.

gpcrondump allows you to schedule routine backups of a Greenplum database using cron (a scheduling utility for UNIX operating systems). Cron jobs that call gpcrondump should be scheduled on the master host.

To have gpcrondump send out status email notifications, you must place a file named mail_contacts in the home directory of the Greenplum superuser (gpadmin) or in the same directory as the gpcrondump utility ($GPHOME/bin). This file should contain one email address per line. gpcrondump will issue a warning if it cannot locate a mail_contacts file in either location. If both locations have a mail_contacts file, then the one in $HOME takes precedence.

-a (do not prompt)

Do not prompt the user for confirmation.

-b (bypass disk space check)

Bypass disk space check. The default is to check for available disk space.