Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
_exit(2)
terminate the calling process
_nc_free_and_exit(3), %exit_curses(3), %exit_terminfo(3)
check for memory leaks in curses
at_quick_exit(3)
registers a cleanup function to run on quick exit
atexit(3)
register a function to be called on exit
atf-c(3), ATF_CHECK(3), ATF_CHECK_MSG(3), ATF_CHECK_EQ(3), ATF_CHECK_EQ_MSG(3), ATF_CHECK_MATCH(3), ATF_CHECK_MATCH_MSG(3), ATF_CHECK_STREQ(3), ATF_CHECK_STREQ_MSG(3), ATF_CHECK_INTEQ(3), ATF_CHECK_INTEQ_MSG(3), ATF_CHECK_ERRNO(3), ATF_REQUIRE(3), ATF_REQUIRE_MSG(3), ATF_REQUIRE_EQ(3), ATF_REQUIRE_EQ_MSG(3), ATF_REQUIRE_MATCH(3), ATF_REQUIRE_MATCH_MSG(3), ATF_REQUIRE_STREQ(3), ATF_REQUIRE_STREQ_MSG(3), ATF_REQUIRE_INTEQ(3), ATF_REQUIRE_INTEQ_MSG(3), ATF_REQUIRE_ERRNO(3), ATF_TC(3), ATF_TC_BODY(3), ATF_TC_BODY_NAME(3), ATF_TC_CLEANUP(3), ATF_TC_CLEANUP_NAME(3), ATF_TC_HEAD(3), ATF_TC_HEAD_NAME(3), ATF_TC_NAME(3), ATF_TC_WITH_CLEANUP(3), ATF_TC_WITHOUT_HEAD(3), ATF_TP_ADD_TC(3), ATF_TP_ADD_TCS(3), atf_tc_get_config_var(3), atf_tc_get_config_var_wd(3), atf_tc_get_config_var_as_bool(3), atf_tc_get_config_var_as_bool_wd(3), atf_tc_get_config_var_as_long(3), atf_tc_get_config_var_as_long_wd(3), atf_no_error(3), atf_tc_expect_death(3), atf_tc_expect_exit(3), atf_tc_expect_fail(3), atf_tc_expect_pass(3), atf_tc_expect_signal(3), atf_tc_expect_timeout(3), atf_tc_fail(3), atf_tc_fail_nonfatal(3), atf_tc_pass(3), atf_tc_skip(3), atf_utils_cat_file(3), atf_utils_compare_file(3), atf_utils_copy_file(3), atf_utils_create_file(3), atf_utils_file_exists(3), atf_utils_fork(3), atf_utils_free_charpp(3), atf_utils_grep_file(3), atf_utils_grep_string(3), atf_utils_readline(3), atf_utils_redirect(3), atf_utils_wait(3)
C API to write ATF-based test programs
atf_add_test_case(3), atf_check(3), atf_check_equal(3), atf_check_not_equal(3), atf_config_get(3), atf_config_has(3), atf_expect_death(3), atf_expect_exit(3), atf_expect_fail(3), atf_expect_pass(3), atf_expect_signal(3), atf_expect_timeout(3), atf_fail(3), atf_get(3), atf_get_srcdir(3), atf_init_test_cases(3), atf_pass(3), atf_require_prog(3), atf_set(3), atf_skip(3), atf_test_case(3)
POSIX shell API to write ATF-based test programs
au_to_arg32(3), au_to_arg64(3), au_to_arg(3), au_to_attr64(3), au_to_data(3), au_to_exit(3), au_to_groups(3), au_to_newgroups(3), au_to_in_addr(3), au_to_in_addr_ex(3), au_to_ip(3), au_to_ipc(3), au_to_ipc_perm(3), au_to_iport(3), au_to_opaque(3), au_to_file(3), au_to_text(3), au_to_path(3), au_to_process32(3), au_to_process64(3), au_to_process(3), au_to_process32_ex(3), au_to_process64_ex(3), au_to_process_ex(3), au_to_return32(3), au_to_return64(3), au_to_return(3), au_to_seq(3), au_to_sock_inet32(3), au_to_sock_inet128(3), au_to_sock_inet(3), au_to_socket_ex(3), au_to_subject32(3), au_to_subject64(3), au_to_subject(3), au_to_subject32_ex(3), au_to_subject64_ex(3), au_to_subject_ex(3), au_to_me(3), au_to_exec_args(3), au_to_exec_env(3), au_to_header(3), au_to_header32(3), au_to_header64(3), au_to_header_ex(3), au_to_header32_ex(3), au_to_trailer(3), au_to_zonename(3)
routines for generating BSM audit tokens
builtin(1), !(1), %(1), .(1), :(1), @(1), [(1), {(1), }(1), alias(1), alloc(1), bg(1), bind(1), bindkey(1), break(1), breaksw(1), builtins(1), case(1), cd(1), chdir(1), command(1), complete(1), continue(1), default(1), dirs(1), do(1), done(1), echo(1), echotc(1), elif(1), else(1), end(1), endif(1), endsw(1), esac(1), eval(1), exec(1), exit(1), export(1), false(1), fc(1), fg(1), filetest(1), fi(1), for(1), foreach(1), getopts(1), glob(1), goto(1), hash(1), hashstat(1), history(1), hup(1), if(1), jobid(1), jobs(1), kill(1), limit(1), local(1), log(1), login(1), logout(1), ls-F(1), nice(1), nohup(1), notify(1), onintr(1), popd(1), printenv(1), printf(1), pushd(1), pwd(1), read(1), readonly(1), rehash(1), repeat(1), return(1), sched(1), set(1), setenv(1), settc(1), setty(1), setvar(1), shift(1), source(1), stop(1), suspend(1), switch(1), telltc(1), test(1), then(1), time(1), times(1), trap(1), true(1), type(1), ulimit(1), umask(1), unalias(1), uncomplete(1), unhash(1), unlimit(1), unset(1), unsetenv(1), until(1), wait(1), where(1), which(1), while(1)
shell built-in commands
call_once(3), cnd_broadcast(3), cnd_destroy(3), cnd_init(3), cnd_signal(3), cnd_timedwait(3), cnd_wait(3), mtx_destroy(3), mtx_init(3), mtx_lock(3), mtx_timedlock(3), mtx_trylock(3), mtx_unlock(3), thrd_create(3), thrd_current(3), thrd_detach(3), thrd_equal(3), thrd_exit(3), thrd_join(3), thrd_sleep(3), thrd_yield(3), tss_create(3), tss_delete(3), tss_get(3), tss_set(3)
C11 threads interface
cpu_machdep(9), cpu_copy_thread(9), cpu_exec_vmspace_reuse(9), cpu_exit(9), cpu_fetch_syscall_args(9), cpu_fork(9), cpu_fork_kthread_handler(9), cpu_idle(9), cpu_idle_wakeup(9), cpu_procctl(9), cpu_set_syscall_retval(9), cpu_set_upcall(9), cpu_set_user_tls(9), cpu_switch(9), cpu_sync_core(9), cpu_thread_alloc(9), cpu_thread_clean(9), cpu_thread_exit(9), cpu_thread_free(9), cpu_throw(9)
machine-dependent interfaces to handle CPU and thread state
critical_enter(9), critical_exit(9)
enter and exit a critical region
epoch(9), epoch_context(9), epoch_alloc(9), epoch_free(9), epoch_enter(9), epoch_exit(9), epoch_wait(9), epoch_enter_preempt(9), epoch_exit_preempt(9), epoch_wait_preempt(9), epoch_call(9), epoch_drain_callbacks(9), in_epoch(9), in_epoch_verbose(9)
kernel epoch based reclamation
err(3), verr(3), errc(3), verrc(3), errx(3), verrx(3), warn(3), vwarn(3), warnc(3), vwarnc(3), warnx(3), vwarnx(3), err_set_exit(3), err_set_file(3)
formatted error messages
exit(3), _Exit(3)
perform normal program termination
kproc_start(9), kproc_shutdown(9), kproc_create(9), kproc_exit(9), kproc_resume(9), kproc_suspend(9), kproc_suspend_check(9)
kernel processes
kthread_start(9), kthread_shutdown(9), kthread_add(9), kthread_exit(9), kthread_resume(9), kthread_suspend(9), kthread_suspend_check(9)
kernel threads
osd(9), osd_register(9), osd_deregister(9), osd_set(9), osd_reserve(9), osd_set_reserved(9), osd_free_reserved(9), osd_get(9), osd_del(9), osd_call(9), osd_exit(9)
Object Specific Data
pthread_cleanup_push(3)
add a cleanup function for thread exit
pthread_exit(3)
terminate the calling thread
quick_exit(3)
exits a program quickly, running minimal cleanup
signal(9), SIGADDSET(9), SIGDELSET(9), SETEMPTYSET(9), SIGFILLSET(9), SIGISMEMBER(9), SIGISEMPTY(9), SIGNOTEMPTY(9), SIGSETEQ(9), SIGSETNEQ(9), SIGSETOR(9), SIGSETAND(9), SIGSETNAND(9), SIGSETCANTMASK(9), SIG_STOPSIGMASK(9), SIG_CONTSIGMASK(9), SIGPENDING(9), cursig(9), execsigs(9), issignal(9), killproc(9), pgsigio(9), postsig(9), sigexit(9), siginit(9), signotify(9), trapsignal(9)
kernel signal functions
svc_dg_enablecache(3), svc_exit(3), svc_fdset(3), svc_freeargs(3), svc_getargs(3), svc_getreq_common(3), svc_getreq_poll(3), svc_getreqset(3), svc_getrpccaller(3), svc_pollset(3), svc_run(3), svc_sendreply(3)
library routines for RPC servers
sysexits(3)
legacy exit status codes for system programs
thr_exit(2)
terminate current thread
thread_exit(9)
abandon current thread context
OPENSSL_INIT_new(3), OPENSSL_INIT_set_config_filename(3), OPENSSL_INIT_set_config_appname(3), OPENSSL_INIT_set_config_file_flags(3), OPENSSL_INIT_free(3), OPENSSL_init_crypto(3), OPENSSL_cleanup(3), OPENSSL_atexit(3), OPENSSL_thread_stop_ex(3), OPENSSL_thread_stop(3)
OpenSSL initialisation and deinitialisation functions
CURLOPT_QUICK_EXIT(3)
allow to exit quickly
Dpkg::Exit(3perl)
program exit handlers
HPL_grid_exit(3)
Exit process grid
OPENSSL_INIT_new(3), OPENSSL_INIT_set_config_filename(3), OPENSSL_INIT_set_config_appname(3), OPENSSL_INIT_set_config_file_flags(3), OPENSSL_INIT_free(3), OPENSSL_init_crypto(3), OPENSSL_cleanup(3), OPENSSL_atexit(3), OPENSSL_thread_stop(3)
OpenSSL initialisation and deinitialisation functions
OPENSSL_INIT_new(3ossl), OPENSSL_INIT_set_config_filename(3ossl), OPENSSL_INIT_set_config_appname(3ossl), OPENSSL_INIT_set_config_file_flags(3ossl), OPENSSL_INIT_free(3ossl), OPENSSL_init_crypto(3ossl), OPENSSL_cleanup(3ossl), OPENSSL_atexit(3ossl), OPENSSL_thread_stop_ex(3ossl), OPENSSL_thread_stop(3ossl)
OpenSSL initialisation and deinitialisation functions
Tcl_CreateExitHandler.tcl86(3), Tcl_Exit(3), Tcl_Finalize(3), Tcl_CreateExitHandler(3), Tcl_DeleteExitHandler(3), Tcl_ExitThread(3), Tcl_FinalizeThread(3), Tcl_CreateThreadExitHandler(3), Tcl_DeleteThreadExitHandler(3), Tcl_SetExitProc(3)
end the application or thread (and invoke exit handlers)
Tcl_CreateExitHandler.tcl90(3), Tcl_Exit(3), Tcl_Finalize(3), Tcl_CreateExitHandler(3), Tcl_DeleteExitHandler(3), Tcl_ExitThread(3), Tcl_FinalizeThread(3), Tcl_CreateThreadExitHandler(3), Tcl_DeleteThreadExitHandler(3), Tcl_SetExitProc(3)
end the application or thread (and invoke exit handlers)
XSetErrorHandler(3), XGetErrorText(3), XDisplayName(3), XSetIOErrorHandler(3), XSetIOErrorExitHandler(3), XGetErrorDatabaseText(3)
default error handlers
XmtErrorMsg(3), XmtErrorMsg()(3), XmtWarningMsg()(3)
print an error message and exit or print a warning message and return
XtAppSetExitFlag(3), XtAppGetExitFlag(3)
thread support functions
_nc_free_and_exit(3x), %exit_curses(3x), %exit_terminfo(3x)
check for memory leaks in curses
allegro_exit(3)
Closes down the Allegro system
atf-c(3), ATF_CHECK(3), ATF_CHECK_MSG(3), ATF_CHECK_EQ(3), ATF_CHECK_EQ_MSG(3), ATF_CHECK_MATCH(3), ATF_CHECK_MATCH_MSG(3), ATF_CHECK_STREQ(3), ATF_CHECK_STREQ_MSG(3), ATF_CHECK_INTEQ(3), ATF_CHECK_INTEQ_MSG(3), ATF_CHECK_ERRNO(3), ATF_REQUIRE(3), ATF_REQUIRE_MSG(3), ATF_REQUIRE_EQ(3), ATF_REQUIRE_EQ_MSG(3), ATF_REQUIRE_MATCH(3), ATF_REQUIRE_MATCH_MSG(3), ATF_REQUIRE_STREQ(3), ATF_REQUIRE_STREQ_MSG(3), ATF_REQUIRE_INTEQ(3), ATF_REQUIRE_INTEQ_MSG(3), ATF_REQUIRE_ERRNO(3), ATF_TC(3), ATF_TC_BODY(3), ATF_TC_BODY_NAME(3), ATF_TC_CLEANUP(3), ATF_TC_CLEANUP_NAME(3), ATF_TC_HEAD(3), ATF_TC_HEAD_NAME(3), ATF_TC_NAME(3), ATF_TC_WITH_CLEANUP(3), ATF_TC_WITHOUT_HEAD(3), ATF_TP_ADD_TC(3), ATF_TP_ADD_TCS(3), atf_tc_get_config_var(3), atf_tc_get_config_var_wd(3), atf_tc_get_config_var_as_bool(3), atf_tc_get_config_var_as_bool_wd(3), atf_tc_get_config_var_as_long(3), atf_tc_get_config_var_as_long_wd(3), atf_no_error(3), atf_tc_expect_death(3), atf_tc_expect_exit(3), atf_tc_expect_fail(3), atf_tc_expect_pass(3), atf_tc_expect_signal(3), atf_tc_expect_timeout(3), atf_tc_fail(3), atf_tc_fail_nonfatal(3), atf_tc_pass(3), atf_tc_skip(3), atf_utils_cat_file(3), atf_utils_compare_file(3), atf_utils_copy_file(3), atf_utils_create_file(3), atf_utils_file_exists(3), atf_utils_fork(3), atf_utils_free_charpp(3), atf_utils_grep_file(3), atf_utils_grep_string(3), atf_utils_readline(3), atf_utils_redirect(3), atf_utils_wait(3)
C API to write ATF-based test programs
atf-sh(3), atf_add_test_case(3), atf_check(3), atf_check_equal(3), atf_check_not_equal(3), atf_config_get(3), atf_config_has(3), atf_expect_death(3), atf_expect_exit(3), atf_expect_fail(3), atf_expect_pass(3), atf_expect_signal(3), atf_expect_timeout(3), atf_fail(3), atf_get(3), atf_get_srcdir(3), atf_pass(3), atf_require_prog(3), atf_set(3), atf_skip(3), atf_test_case(3)
POSIX shell API to write ATF-based test programs
au_token(3), au_to_arg32(3), au_to_arg64(3), au_to_arg(3), au_to_attr64(3), au_to_data(3), au_to_exit(3), au_to_groups(3), au_to_newgroups(3), au_to_in_addr(3), au_to_in_addr_ex(3), au_to_ip(3), au_to_ipc(3), au_to_ipc_perm(3), au_to_iport(3), au_to_opaque(3), au_to_file(3), au_to_text(3), au_to_path(3), au_to_process32(3), au_to_process64(3), au_to_process(3), au_to_process32_ex(3), au_to_process64_ex(3), au_to_process_ex(3), au_to_return32(3), au_to_return64(3), au_to_return(3), au_to_seq(3), au_to_sock_inet32(3), au_to_sock_inet128(3), au_to_sock_inet(3), au_to_socket_ex(3), au_to_subject32(3), au_to_subject64(3), au_to_subject(3), au_to_subject32_ex(3), au_to_subject64_ex(3), au_to_subject_ex(3), au_to_me(3), au_to_exec_args(3), au_to_exec_env(3), au_to_header(3), au_to_header32(3), au_to_header64(3), au_to_header_ex(3), au_to_header32_ex(3), au_to_trailer(3), au_to_zonename(3)
routines for generating BSM audit tokens
barman-cloud-backup(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ { { -z | --gzip } | { -j | --bzip2 } | --snappy } ] [ { -h | --host } HOST ] [ { -p | --port } PORT ] [ { -U | --user } USER ] [ { -d | --dbname } DBNAME ] [ { -n | --name } BACKUP_NAME ] [ { -J | --jobs } JOBS ] [ { -S | --max-archive-size } MAX_ARCHIVE_SIZE ] [ --immediate-checkpoint ] [ --min-chunk-size MIN_CHUNK_SIZE ] [ --max-bandwidth MAX_BANDWIDTH ] [ --snapshot-instance SNAPSHOT_INSTANCE ] [ --snapshot-disk NAME ] [ --snapshot-zone GCP_ZONE ] [ -snapshot-gcp-project GCP_PROJECT ] [ --tags TAG [ TAG ... ] ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { -e | --encryption } { AES256 | aws:kms } ] [ --sse-kms-key-id SSE_KMS_KEY_ID ] [ --aws-region AWS_REGION ] [ --aws-await-snapshots-timeout AWS_AWAIT_SNAPSHOTS_TIMEOUT ] [ --aws-snapshot-lock-mode { compliance | governance } ] [ --aws-snapshot-lock-duration DAYS ] [ --aws-snapshot-lock-cool-off-period HOURS ] [ --aws-snapshot-lock-expiration-date DATETIME ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --encryption-scope ENCRYPTION_SCOPE ] [ --azure-subscription-id AZURE_SUBSCRIPTION_ID ] [ --azure-resource-group AZURE_RESOURCE_GROUP ] [ --gcp-project GCP_PROJECT ] [ --kms-key-name KMS_KEY_NAME ] [ --gcp-zone GCP_ZONE ] DESTINATION_URL SERVER_NAME Description The barman-cloud-backup script is used to create a local backup of a Postgres server and transfer it to a supported cloud provider, bypassing the Barman server. It can also be utilized as a hook script for copying Barman backups from the Barman server to one of the supported clouds (post_backup_retry_script). This script requires read access to PGDATA and tablespaces, typically run as the postgres user. When used on a Barman server, it requires read access to the directory where Barman backups are stored. If --snapshot- arguments are used and snapshots are supported by the selected cloud provider, the backup will be performed using snapshots of the specified disks (--snapshot-disk). The backup label and metadata will also be uploaded to the cloud. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. IMPORTANT: 0.0 3.5 The cloud upload may fail if any file larger than the configured --max-archive-size is present in the data directory or tablespaces. However, Postgres files up to 1GB are always allowed, regardless of the --max-archive-size setting. Parameters 0.0 SERVER_NAME Name of the server to be backed up. DESTINATION_URL URL of the cloud destination, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -z / --gzip gzip-compress the backup while uploading to the cloud (should not be used with python < 3.2). -j / --bzip2 bzip2-compress the backup while uploading to the cloud (should not be used with python < 3.3). --snappy snappy-compress the backup while uploading to the cloud (requires optional python-snappy library). -h / --host Host or Unix socket for Postgres connection (default: libpq settings). -p / --port Port for Postgres connection (default: libpq settings). -U / --user User name for Postgres connection (default: libpq settings). -d / --dbname Database name or conninfo string for Postgres connection (default: (dqpostgres(dq). -n / --name A name which can be used to reference this backup in commands such as barman-cloud-restore and barman-cloud-backup-delete. -J / --jobs Number of subprocesses to upload data to cloud storage (default: 2). -S / --max-archive-size Maximum size of an archive when uploading to cloud storage (default: 100GB). --immediate-checkpoint Forces the initial checkpoint to be done as quickly as possible. --min-chunk-size Minimum size of an individual chunk when uploading to cloud storage (default: 5MB for aws-s3, 64KB for azure-blob-storage, not applicable for google-cloud-storage). --max-bandwidth The maximum amount of data to be uploaded per second when backing up to object storages (default: 0 - no limit). --snapshot-instance Instance where the disks to be backed up as snapshots are attached. --snapshot-disk Name of a disk from which snapshots should be taken. --tags Tags to be added to all uploaded files in cloud storage, and/or to snapshots created, if snapshots are used. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). -e / --encryption The encryption algorithm used when storing the uploaded data in S3. Allowed options: 7.0 (bu 2 AES256. (bu 2 aws:kms. --sse-kms-key-id The AWS KMS key ID that should be used for encrypting the uploaded data in S3. Can be specified using the key ID on its own or using the full ARN for the key. Only allowed if -e / --encryption is set to aws:kms. --aws-region The name of the AWS region containing the EC2 VM and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. --aws-await-snapshots-timeout The length of time in seconds to wait for snapshots to be created in AWS before timing out (default: 3600 seconds). --aws-snapshot-lock-mode The lock mode for the snapshot. This is only valid if --snapshot-instance and --snapshot-disk are set. Allowed options: 7.0 (bu 2 compliance. (bu 2 governance. --aws-snapshot-lock-duration The lock duration is the period of time (in days) for which the snapshot is to remain locked, ranging from 1 to 36,500. Set either the lock duration or the expiration date (not both). --aws-snapshot-lock-cool-off-period The cooling-off period is an optional period of time (in hours) that you can specify when you lock a snapshot in compliance mode, ranging from 1 to 72. --aws-snapshot-lock-expiration-date The lock duration is determined by an expiration date in the future. It must be at least 1 day after the snapshot creation date and time, using the format YYYY-MM-DDTHH:MM:SS.sssZ. Set either the lock duration or the expiration date (not both). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --encryption-scope The name of an encryption scope defined in the Azure Blob Storage service which is to be used to encrypt the data in Azure. --azure-subscription-id The ID of the Azure subscription which owns the instance and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. --azure-resource-group The name of the Azure resource group to which the compute instance and disks defined by the --snapshot-instance and --snapshot-disk arguments belong. Extra options for GCP cloud provider 0.0 --gcp-project GCP project under which disk snapshots should be stored. --snapshot-gcp-project (deprecated) GCP project under which disk snapshots should be stored - replaced by --gcp-project. --kms-key-name The name of the GCP KMS key which should be used for encrypting the uploaded data in GCS. --gcp-zone Zone of the disks from which snapshots should be taken. --snapshot-zone (deprecated) Zone of the disks from which snapshots should be taken - replaced by --gcp-zone
barman-cloud-backup-delete(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-delete [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -r | --retention-policy } RETENTION_POLICY ] [ { -m | --minimum-redundancy } MINIMUM_REDUNDANCY ] [ { -b | --backup-id } BACKUP_ID] [ --dry-run ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [--batch-size DELETE_BATCH_SIZE] SOURCE_URL SERVER_NAME Description The barman-cloud-backup-delete script is used to delete one or more backups created with the barman-cloud-backup command from cloud storage and to remove the associated WAL files. Backups can be specified for deletion either by their backup ID (as obtained from barman-cloud-backup-list) or by a retention policy. Retention policies mirror those used by the Barman server, deleting all backups that are not required to meet the specified policy. When a backup is deleted, any unused WAL files associated with that backup are also removed. WALs are considered unused if: 0.0 (bu 2 The WALs predate the begin_wal value of the oldest remaining backup. (bu 2 The WALs are not required by any archival backups stored in the cloud. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. IMPORTANT: 0.0 3.5 Each backup deletion involves three separate requests to the cloud provider: one for the backup files, one for the backup.info file, and one for the associated WALs. Deleting by retention policy may result in a high volume of delete requests if a large number of backups are accumulated in cloud storage. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be deleted. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -b / --backup-id ID of the backup to be deleted -m / --minimum-redundancy The minimum number of backups that should always be available. -r / --retention-policy If specified, delete all backups eligible for deletion according to the supplied retention policy. Syntax: REDUNDANCY value | RECOVERY WINDOW OF value { DAYS | WEEKS | MONTHS } --batch-size The maximum number of objects to be deleted in a single request to the cloud provider. If unset then the maximum allowed batch size for the specified cloud provider will be used (1000 for aws-s3, 256 for azure-blob-storage and 100 for google-cloud-storage). --dry-run Find the objects which need to be deleted but do not delete them. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-backup-keep(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-keep [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ { { -r | --release } | { -s | --status } | --target { full | standalone } } ] SOURCE_URL SERVER_NAME BACKUP_ID Description Use this script to designate backups in cloud storage as archival backups, ensuring their indefinite retention regardless of retention policies. This script allows you to mark backups previously created with barman-cloud-backup as archival backups. Once flagged as archival, these backups are preserved indefinitely and are not subject to standard retention policies. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be kept. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. BACKUP_ID The ID of the backup to be kept. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -r / --release If specified, the command will remove the keep annotation and the backup will be eligible for deletion. -s / --status Print the keep status of the backup. --target Specify the recovery target for this backup. Allowed options are: 7.0 (bu 2 full (bu 2 standalone Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-backup-list(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-list [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --format FORMAT ] SOURCE_URL SERVER_NAME Description This script lists backups stored in the cloud that were created using the barman-cloud-backup command. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be listed. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --format Output format (console or json). Default console. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-backup-show(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-backup-show [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --format FORMAT ] SOURCE_URL SERVER_NAME BACKUP_ID Description This script displays detailed information about a specific backup created with the barman-cloud-backup command. The output is similar to the barman show-backup from the %barman show-backup command reference, but it has fewer information. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 BACKUP_ID The ID of the backup. SERVER_NAME Name of the server that holds the backup to be displayed. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --format Output format (console or json). Default console. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-check-wal-archive(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-check-wal-archive [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --timeline TIMELINE ] DESTINATION_URL SERVER_NAME Description Verify that the WAL archive destination for a server is suitable for use with a new Postgres cluster. By default, the check will succeed if the WAL archive is empty or if the target bucket is not found. Any other conditions will result in a failure. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 SERVER_NAME Name of the server that needs to be checked. DESTINATION_URL URL of the cloud destination, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --timeline The earliest timeline whose WALs should cause the check to fail. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
barman-cloud-restore(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-restore [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --snapshot-recovery-instance SNAPSHOT_RECOVERY_INSTANCE ] [ --snapshot-recovery-zone GCP_ZONE ] [ --aws-region AWS_REGION ] [ --gcp-zone GCP_ZONE ] [ --azure-resource-group AZURE_RESOURCE_GROUP ] [ --tablespace NAME:LOCATION [ --tablespace NAME:LOCATION ... ] ] [ --target-lsn LSN ] [ --target-time TIMESTAMP ] [ --target-tli TLI ] SOURCE_URL SERVER_NAME BACKUP_ID RECOVERY_DESTINATION Description Use this script to restore a backup directly from cloud storage that was created with the barman-cloud-backup command. Additionally, this script can prepare for recovery from a snapshot backup by verifying that attached disks were cloned from the correct snapshots and by downloading the backup label from object storage. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 SERVER_NAME Name of the server that holds the backup to be restored. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. BACKUP_ID The ID of the backup to be restored. Use auto to have Barman automatically find the most suitable backup for the restore operation. RECOVERY_DESTINATION The path to a directory for recovery. -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --snapshot-recovery-instance Instance where the disks recovered from the snapshots are attached. --tablespace Tablespace relocation rule. --target-lsn The recovery target lsn, e.g., 3/64000000. --target-time The recovery target timestamp with or without timezone, in the format %Y-%m-%d %H:%M:%S. --target-tli The recovery target timeline. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --aws-region The name of the AWS region containing the EC2 VM and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --azure-resource-group The name of the Azure resource group to which the compute instance and disks defined by the --snapshot-instance and --snapshot-disk arguments belong. Extra options for GCP cloud provider 0.0 --gcp-zone Zone of the disks from which snapshots should be taken. --snapshot-recovery-zone (deprecated) Zone containing the instance and disks for the snapshot recovery - replaced by --gcp-zone
barman-cloud-wal-archive(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-wal-archive [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ { { -z | --gzip } | { -j | --bzip2 } | --xz | --snappy | --zstd | --lz4 } ] [ --tags TAG [ TAG ... ] ] [ --history-tags HISTORY_TAG [ HISTORY_TAG ... ] ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { -e | --encryption } ENCRYPTION ] [ --sse-kms-key-id SSE_KMS_KEY_ID ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --encryption-scope ENCRYPTION_SCOPE ] [ --max-block-size MAX_BLOCK_SIZE ] [ --max-concurrency MAX_CONCURRENCY ] [ --max-single-put-size MAX_SINGLE_PUT_SIZE ] [ --kms-key-name KMS_KEY_NAME ] DESTINATION_URL SERVER_NAME [ WAL_PATH ] Description The barman-cloud-wal-archive command is designed to be used in the archive_command of a Postgres server to directly ship WAL files to cloud storage. NOTE: 0.0 3.5 If you are using Python 2 or unsupported versions of Python 3, avoid using the compression options --gzip or --bzip2. The script cannot restore gzip-compressed WALs on Python < 3.2 or bzip2-compressed WALs on Python < 3.3. This script enables the direct transfer of WAL files to cloud storage, bypassing the Barman server. Additionally, it can be utilized as a hook script for WAL archiving (pre_archive_retry_script). NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 SERVER_NAME Name of the server that will have the WALs archived. DESTINATION_URL URL of the cloud destination, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. WAL_PATH The value of the (aq%p(aq keyword (according to archive_command). -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. -z / --gzip gzip-compress the WAL while uploading to the cloud. -j / --bzip2 bzip2-compress the WAL while uploading to the cloud. --xz xz-compress the WAL while uploading to the cloud. --snappy snappy-compress the WAL while uploading to the cloud (requires optional python-snappy library). --zstd zstd-compress the WAL while uploading to the cloud (requires optional zstandard library). --lz4 lz4-compress the WAL while uploading to the cloud (requires optional lz4 library). --tags Tags to be added to archived WAL files in cloud storage. --history-tags Tags to be added to archived history files in cloud storage. Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). -e / --encryption The encryption algorithm used when storing the uploaded data in S3. Allowed options: 7.0 (bu 2 AES256. (bu 2 aws:kms. --sse-kms-key-id The AWS KMS key ID that should be used for encrypting the uploaded data in S3. Can be specified using the key ID on its own or using the full ARN for the key. Only allowed if -e / --encryption is set to aws:kms. Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --encryption-scope The name of an encryption scope defined in the Azure Blob Storage service which is to be used to encrypt the data in Azure. --max-block-size The chunk size to be used when uploading an object via the concurrent chunk method (default: 4MB). --max-concurrency The maximum number of chunks to be uploaded concurrently (default: 1). --max-single-put-size Maximum size for which the Azure client will upload an object in a single request (default: 64MB). If this is set lower than the Postgres WAL segment size after any applied compression then the concurrent chunk upload method for WAL archiving will be used. Extra options for GCP cloud provider 0.0 --kms-key-name The name of the GCP KMS key which should be used for encrypting the uploaded data in GCS
barman-cloud-wal-restore(1) - Barman-cloud Commands Synopsis 0.0 3.5 barman-cloud-wal-restore [ { -V | --version } ] [ --help ] [ { { -v | --verbose } | { -q | --quiet } } ] [ { -t | --test } ] [ --cloud-provider { aws-s3 | azure-blob-storage | google-cloud-storage } ] [ --endpoint-url ENDPOINT_URL ] [ { -P | --aws-profile } AWS_PROFILE ] [ --profile AWS_PROFILE ] [ --read-timeout READ_TIMEOUT ] [ { --azure-credential | --credential } { azure-cli | managed-identity | default } ] [ --no-partial ] SOURCE_URL SERVER_NAME WAL_NAME WAL_DEST Description The barman-cloud-wal-restore script functions as the restore_command for retrieving WAL files from cloud storage and placing them directly into a Postgres standby server, bypassing the Barman server. This script is used to download WAL files that were previously archived with the barman-cloud-wal-archive command. Disable automatic download of .partial files by calling --no-partial option. IMPORTANT: 0.0 3.5 On the target Postgres node, when pg_wal and the spool directory are on the same filesystem, files are moved via renaming, which is faster than copying and deleting. This speeds up serving WAL files significantly. If the directories are on different filesystems, the process still involves copying and deleting, so there(aqs no performance gain in that case. NOTE: 0.0 3.5 For GCP, only authentication with GOOGLE_APPLICATION_CREDENTIALS env is supported. Parameters 0.0 SERVER_NAME Name of the server that will have WALs restored. SOURCE_URL URL of the cloud source, such as a bucket in AWS S3. For example: s3://bucket/path/to/folder. WAL_NAME The value of the (aq%f(aq keyword (according to restore_command). WAL_DEST The value of the (aq%p(aq keyword (according to restore_command). -V / --version Show version and exit. --help show this help message and exit. -v / --verbose Increase output verbosity (e.g., -vv is more than -v). -q / --quiet Decrease output verbosity (e.g., -qq is less than -q). -t / --test Test cloud connectivity and exit. --cloud-provider The cloud provider to use as a storage backend. Allowed options are: 7.0 (bu 2 aws-s3. (bu 2 azure-blob-storage. (bu 2 google-cloud-storage. --no-partial Do not download partial WAL files Extra options for the AWS cloud provider 0.0 --endpoint-url Override default S3 endpoint URL with the given one. -P / --aws-profile Profile name (e.g. INI section in AWS credentials file). --profile (deprecated) Profile name (e.g. INI section in AWS credentials file)
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
bl_sam_buff_out_of_order(3), bl_sam_buff_out_of_order()(3)
Print sort order message and exit
cdk_objs(3), cleanCdkTitle drawCdkTitle getCdkTitle positionCDKObject setCDKObjectBackgroundColor setCDKObjectPostProcess setCDKObjectPreProcess setCdkExitType setCdkTitle validCDKObject cdk_objs(3)
Cdk object-support functions
cdk_traverse(3), exitCancelCDKScreen exitCancelCDKScreenOf exitOKCDKScreen exitOKCDKScreenOf getCDKFocusCurrent resetCDKScreen resetCDKScreenOf setCDKFocusCurrent setCDKFocusFirst setCDKFocusLast setCDKFocusNext setCDKFocusPrevious traverseCDKOnce traverseCDKScreen cdk_traverse(3)
Cdk functions for keyboard traversal
coap_io(3), coap_io_process(3), coap_io_process_with_fds(3), coap_context_get_coap_fd(3), coap_io_prepare_io(3), coap_io_do_io(3), coap_io_prepare_epoll(3), coap_io_do_epoll(3), coap_io_pending(3), coap_can_exit(3)
Work with CoAP I/O to do the packet send and receives
dbh_sweep(3), dbh_fanout(3), dbh_foreach_sweep(3), dbh_foreach_fanout(3), dbh_exit_sweep(3), dbh_exit_fanout(3)
apply a function to all or part of the DBHashtable
deductionguidesforstd::experimental::scope_exit(3)
deductionguidesforstd::experimental::scope_exit
ecalloc(3), emalloc(3), eread(3), erealloc(3), esetenv(3), estrdup(3), ewrite(3)
exit-on-failure wrapper functions
encapsulate(1)
multiplex several channels over a single socket with sampling of remote process exit status, and provide conversation termination without closing the socket. netpipes 4.2
exit.tcl86(n), exit(n)
End the application
exit.tcl90(n), exit(n)
End the application
explain_exit(3)
print an explanation of exit status before exiting require_index { }
filter_wait(3), filter_wait (3)
wrap waitpid to decode the exitcode and why your filter quit
gcin-exit(1)
send quit message to gcin
grace(1)
command line interface xmgrace - full-featured GUI mode gracebat - batch mode - print and exit
iv_quit(3)
signal ivykis to exit the main loop
jack_wait(1)
JACK toolkit client to check and wait for existence/exit of jackd
home | help