Converse agora com nosso suporte
Chat com o suporte

NetVault Plug-in for PostgreSQL 12.3.1 - 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

Backing up configuration files

You can select configuration files for backup with any of the backup types. Regardless of the format selected, the plug-in performs a file-system backup of the following files:

•
postgresql.conf
•
pg_hba.conf
•
pg_ident.conf

To back up these files separately, complete the following steps.

1
Following the steps outlined in Selecting data for a backup, select the Configuration Files node in the selection tree.
2
Because the Backup Type and Backup Format are not considered, select any of the options in Backup Options when you create the Backup Options Set by following the steps outlined in Setting backup options.
3
Following the steps outlined in Finalizing and submitting the job, complete and submit the job.

Restoring data

•
Selecting data for a restore
•
Setting restore options
•
Finalizing and submitting the job
•
Performing advanced restore procedures

Selecting data for a restore

1
In the Navigation pane, click Create Restore Job.
2
On the Create Restore Job — Choose Saveset page, select Plug‑in for PostgreSQL from the Plugin Type list.
3
To filter the items displayed in the saveset table further, use the Client, Date, and Job ID lists.
The table displays the saveset name (job title and saveset ID), creation date and time, and size. By default, the list is sorted by creation date.
4
In the saveset table, select the applicable saveset to display the database cluster that was the target of the backup.
When you select a saveset, the following details are displayed in the Saveset Information area: Job ID, job title, server name, client name, plug-in name, saveset date and time, retirement setting, Incremental Backup or not, Archive or not, saveset size, and snapshot-based backup or not.
The following table outlines the backup type identifiers:
 
Backup type identifier
Backup type and format

CA FULL FILESYSTEM
•
Base File Level Data Copy

CA INCREMENTAL WAL
•
Incremental File Level Data Copy

SQL FULL DB CLUSTER ARCHIVE
•
Full Database Cluster
•
TAR/Custom Archive File

SQL FULL DB CLUSTER PLAIN
•
Full Database Cluster
•
Plain-text SQL Script File

SQL INDIVIDUAL ARCHIVE
•
Individual Database/Table
•
TAR/Custom Archive File

SQL INDIVIDUAL PLAIN
•
Individual Database/Table
•
Plain-text SQL Script File

SQL GLOBAL OBJECT ONLY
•
Global Objects Only
5
Click Next.
6
On the Create Selection Set page, select the data that you want to restore.
Based on the backup type, opening the database cluster displays the following:
•
Full Database Cluster: The following nodes are displayed for this type:
•
Configuration Files, if included in the backup
•
Global Objects
•
All Databases
•
Individual Database Cluster: The following nodes are displayed for this type:
•
Configuration Files, if included in the backup
•
All Databases
7
To view the databases included in the backup, open All Databases.
8
For next-level selections, drill down further.
9
Select the database cluster, databases, or tables as required.
 
* 
IMPORTANT: BLOBs included in the backup are displayed as a separate node, and not beneath the associated table. Selecting this node restores all BLOBs contained in the saveset and not just objects associated with the selected table. Also note that, to restore BLOBs, this node must be selected explicitly, that is, either this node or the parent database node must be selected. Selecting only the table does not restore the associated BLOBs.

Setting restore options

Select the applicable topic:

•
If you are restoring a SQL Logical Data Dump, skip to Setting restore options for a SQL Logical Data Dump.
•
If you are restoring a File-Level Data Copy, skip to Setting restore options for a File-Level Data Copy.
Setting restore options for a SQL Logical Data Dump
1
On the Create Selection Set page, click Edit Plugin Options, and configure the applicable parameters on the Options tabs.
2
If you are restoring a Plain-Text SQL Script File backup, select the applicable options in the Pre-Restore Options section to specify what actions should be taken before the plug-in begins the restoration of a database:
•
Drop and Recreate Database: Select this option if you want to drop an existing database before restoring it from the backup. The database is created using the template specified in the Configure dialog box, Template Database Used during CREATE Database option. All existing data is discarded if this option is selected.
 
* 
IMPORTANT: Regardless of whether the Drop and Recreate Database option is selected, the plug-in performs this action if you are restoring Template Databases.
•
Create Database Only: Select this option if you want to create a nonexistent database or to write data to the existing database. If the database is not found during restore, a new database is created. If the database is present, tables that are not part of the current restore job are not modified in any manner. If the selected tables are present in the database, the action is based on whether the Include Drop Object Commands option was selected during backup:
•
Include Drop Object Commands was selected: The table is dropped and re-created. The restored table only contains records that were present at the time of backup.
•
Include Drop Object Commands was not selected: For existing tables, you can use the Truncate Table(s) option to truncate existing records before restoring.
If Truncate Table(s) is not enabled, the plug-in attempts to insert all the backed-up records into the existing table. For tables on which the unique or primary keys have been defined, this action might result in constraint errors.
•
Truncate Table(s): Select this option if you want to delete all existing records from the tables and restore the records present in the backup saveset. After restoration, the tables only contain records that were present at the time of backup. Be aware of the following:
•
The database must exist.
•
For existing tables, the “create table” command during psql execution fails. If the Stop on Error option is selected, the restore stops immediately on encountering this error. Select the Continue with Warnings option if the selected tables are present to ignore these errors and continue with table truncation and data restoration.
•
No errors are encountered for tables that do not exist.
3
If you are restoring a Plain-Text SQL Script File backup, select the applicable options in the Restore Options section:
•
Stop on Error: Select this option if you want the restore to stop immediately when an error occurs. Changes made before the error are not rolled back, which leaves the database in an inconsistent state.
The entire restore job is not canceled; only the restoration of the current database stops. Restoration of other databases included in the job continues normally.
If the Disable Triggers option was enabled for backup and the restoration of the database stops in between, the plug-in does not enable triggers defined for the last table that caused the failure.
•
Restore as Single Transaction: Select this option if all commands in the database backup must complete successfully; otherwise, no changes are applied. The changes made are rolled back if an error occurs.
The commit or roll-back action applies to a specific database and not the entire restore job. The databases for which restoration has completed successfully are not affected. Similarly, this process does not affect restoration of remaining databases in the job.
•
Continue Restore with Warnings: Select this option if you want the plug-in to ignore the errors and continue with the restore. The errors encountered during job execution are recorded as warning messages in the NetVault Backup logs and the job status is reported as “Completed with Warnings.”
You can use this option to restore nonexistent or nonduplicate records into existing tables without truncating the existing records.
 
* 
IMPORTANT: If you select this option, review the logs after the job is complete to confirm that they only contain warnings pertaining to the following:

Primary or Unique Key Constraints Database Object (like table, language, user, role, and others) Already Exists

You can ignore these errors. However, if any other type of error message is noted, take corrective action, such as restoring the database again by selecting Drop and Recreate Database or Truncate Table(s).
4
If you are restoring a TAR Archive File or Custom Archive File backup, select the applicable options:
•
Stop on Error: Select this option if you want the restore to stop immediately when an error occurs. Changes made before the error are not rolled back, which leaves the database in an inconsistent state.
The entire restore job is not canceled; only the restoration of the current database stops. Restoration of other databases included in the job continues normally.
 
* 
IMPORTANT: If this option is not selected, the plug-in ignores the errors and continues the job. The errors encountered during job execution are recorded as warning messages in the NetVault Backup logs and the job status is reported as “Completed with Warnings.” Review the logs after the job is complete to confirm that they only contain warnings pertaining to the following:

Primary or Unique Key Constraints Database Object (like table, language, user, role, and others) Already Exists

You can ignore these errors. However, if any other type of error message is noted, take corrective action, such as restoring the database again by selecting Drop and Recreate Database or Do Not Restore Data for Failed Create Table Commands.
•
Drop and Recreate Database: Select this option if you want to drop an existing database before restoring it from the backup. The database is created using the template specified in the Configure dialog box, Template Database Used during CREATE Database option.
You can also use the Exclude Access Privileges option with Create Database Only. To prevent restoration of access privileges, grant and revoke commands, select this option. Without this option selected, the restoration fails if the required users or roles do not exist.
 
* 
IMPORTANT: Regardless of whether the Drop and Recreate Database option is selected, the plug-in performs this action if you are restoring Template Databases.
•
Create Database Only: Select this option if you want to create a nonexistent database or to write data to the existing database. If the database is not found during restore, a new database is created. If the database is present, tables that are not part of the current restore job are not modified in any manner. If the selected tables are present in the database, the action is based on the following options:
•
Drop Database Objects: To drop the existing table and restore it from the backup, select this option. If you select this option, you lose the existing records. The restored table only contains records that were present at the time of backup.
•
Restore Data for Failed Create Table Commands: If you want the plug-in to insert all the backed-up records into the existing table, select this option. For tables on which the unique or primary keys have been defined, this action might result in constraint errors.
•
If Stop on Error option is selected, the restoration of the database stops.
•
Do Not Restore Data for Failed Create Table Commands: With this option enabled, the existing tables are not restored.
You can also use the Exclude Access Privileges option with Create Database Only. To prevent restoration of access privileges, grant and revoke commands, select this option. Without this option selected, the restoration fails if the required users or roles do not exist.
•
Restore Data Only (No Schema Definitions): Select this option if you want to restore only the data from the backup and exclude the schema definitions. The restore fails if the target database or table does not exist.
 
* 
IMPORTANT: Template Databases are not restored if you select this option.
You can also use the Disable Triggers option with Restore Data Only. Select this option if there are referential integrity checks or other triggers on the tables. This option temporarily disables triggers on the target tables during restore. After successful data restoration, the triggers are enabled. If Stop on Error is selected and the restoration of the database stops in between, the plug-in does not enable triggers defined for the last table that caused the failure.
5
Click OK.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação