Chat now with support
지원 담당자와 채팅

NetVault Backup Plug-in for PostgreSQL 12.3 - User Guide

Introducing NetVault Backup Plug-in for PostgreSQL Installing and removing the plug-in Configuring the plug-in Backing up data Restoring data Troubleshooting

Defining a backup strategy

Before commencing with database backups, ensure that you have a backup strategy that safeguards data against media failure, data corruption, user error, and loss of the database server. The following topics provide information that helps you devise a backup strategy for use with Plug‑in for PostgreSQL.

Reviewing the available backup methods

The plug-in offers the following backup methods:

SQL Logical Data Dump: Selecting this method performs logical data dumps composed of SQL commands that are used to reconstruct the PostgreSQL data. The PostgreSQL Server utilities pg_dump and pg_dumpall are used to perform SQL Logical Data Dump Backups. This option supports database-cluster backups and individual database and table backups in different backup formats.
File Level Data Copy: If you are using PostgreSQL Server 9.6 or later, this option supports archive-based backups and restores of the complete PostgreSQL database cluster. This option performs a physical backup of the PostgreSQL Server data files and works in combination with the pg_start_backup and pg_stop_backup utilities.

Supported backup formats for the SQL Logical Data Dump backup method

The plug-in supports backups in Plain-text SQL Script File, TAR Archive, and Custom Archive backup formats, which can be used to back up an entire database cluster or individual databases and tables.

Plain-text SQL Script File: This format generates a plain-text file that contains the SQL commands required to reconstruct the database to the state it was in at the time of backup.
TAR Archive File: This format generates a tape archive (TAR) file that is not compressed.
Custom Archive File: This format generates an archive file that is compressed by default. It lets you select the compression level and can be used for tables that are larger than the maximum file size supported by the OS.
The custom archive format requires the zlib compression library and can be used only on PostgreSQL installations built with this library. This library is included by default during PostgreSQL installation unless you use the ‑‑without‑zlib option to disable support for Custom Archive.

While similar backup options are available with all three formats, there are minor differences. All three formats let you restore only what is needed and restore data to a different cluster or server.

Available backup types for the SQL Logical Data Dump backup method

The plug-in provides the following backup types:

Full Database Cluster: This option backs up all the databases within the cluster in the selected backup format. It also includes a backup of Global Objects, which are in the form of a Plain-text Script file, regardless of the backup format specified. The plug-in automatically includes the configuration files when the database cluster is selected; however, you can exclude it from the backup if applicable.
Individual Database/Table: This option backs up selected databases or tables in the selected backup format. You can use it to back up databases that are updated more frequently than others or use it as a source when creating test environments. This option does not include Global Objects when the databases or tables are backed up individually.
Global Objects Only: This option backs up only the Global Objects, which you can use to back up the updates made to the database users, groups, and access permissions.
Configuration Files Backup: You can back up the configuration files with any of the preceding backup types, or separately. The following files are included when you select this option:
postgresql.conf: This file is the primary server configuration file that contains all the parameter settings and directives.
pg_hba.conf: This file is the host-based authentication (HBA) or client authentication file.
pg_ident.conf: This file stores ident maps, excluding sameuser, and is used for ident-based authentication.
관련 문서