Chatee ahora con Soporte
Chat con el soporte

NetVault 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

Finalizing and submitting the job

The final steps include setting additional options on the Schedule, Source Options, and Advanced Options pages, submitting the job, and monitoring the progress through the Job Status and View Logs pages. These pages and options are common to all NetVault Backup Plug-ins. For more information, see the Quest NetVault Backup Administrator’s Guide.

1
To save the settings, click Ok, and then click Next.
2
In Job Name, specify a name for the job if you do not want to use the default setting.
Assign a descriptive name that lets you easily identify the job when monitoring its progress. The job name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Linux, the name can have a maximum of 200 characters. On Windows, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.
3
In the Target Client list, select the machine on which you want to restore the data.
 
* 
TIP: You can also click Choose, and then locate and select the applicable client in the Choose the Target Client dialog box.
4
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options.
5
Click Save or Save & Submit, whichever is applicable.
You can monitor progress on the Job Status page and view the logs on the View Logs page. For more information, see the Quest NetVault Backup Administrator’s Guide.
6
If you restored a file-level data copy as a part of a recovery procedure intended to build or rebuild the database cluster Data directory, complete the following steps to ensure that recovery is completed.
a
Restart the PostgreSQL service.
b
After the PostgreSQL service has restarted, run the following command:
select pg_wal_replay_resume();
If the recovery has completed, a recovery is not in progress message is displayed. Otherwise, recovery is completed.
For more information, see the example in Example of restoring an archived-based backup sequence
Example of restoring an archived-based backup sequence

In the standard recovery scenario, you restore the Base Backup to the original location, and then restore the sequence of Incremental Backups to the staging directory for WAL files. The next step is to generate a Recovery Command file, “recovery.conf,” and place it in the database cluster Data directory. For the final step, you start the PostgreSQL Server, which then reads the Recovery Command file and applies the recovery.

 
* 
NOTE: PostgreSQL Server might replay additional transactions beyond the selected stop time. If you prefer that the recovery only has access to the WAL file transactions that were included in the sequence of Base and Incremental Backups, before you start the recovery process, delete the contents of the PostgreSQL Database Cluster pg_wal or pg_xlog directory and the contents of the staging directory for WAL files. Transactions committed after the last Base or Incremental Backup of the restore sequence are not replayed.

If you prefer to achieve a rollforward up to the latest available consecutive transaction, in addition to excluding a stop time, keep the existing contents in the pg_wal or pg_xlog directory and in the staging directory for WAL files.

The following outlines the steps involved in restoring the Base and Incremental Backups for a file-based Base Backup and associated Incremental Backups.

1
Make sure that all PostgreSQL Server services are stopped.
2
Generate an offline backup to savage the contents of the database cluster Data directory and the contents of the WAL files directory.
When creating the offline backup job, select the Perform Offline Backup option on the PostgreSQL Backup Options tab. For more information, see Setting backup options for a File Level Data Copy.
3
Create a restore job, and select the applicable Base File Level Data Copy saveset to restore.
If the files in the database cluster Data directory are damaged, or you intend to replace them, restore the Base Backup to the original location. To do so, on the Restore Options tab, clear the Relocate all restored files to the directory option. On the Base Data Files tab, select the Include Backup Label File with Restore option.
For more information, see Selecting data for a restore and Setting restore options for a File-Level Data Copy.
 
* 

If the pg_wal or pg_xlog directory is empty and you want to store the current WAL files in a separate filesystem, you can modify pg_wal or pg_xlog to be a symbolic link to the location of your choice. To do so, delete pg_wal or pg_xlog and replace it with a symbolic link.

Examples of creating the link:

Linux or UNIX: ln -s /pg_wal_desired_location /opt/postgres/11/data/pg_wal

Windows: mklink /J "C:\Program Files\PostgreSQL\11\data\pg_wal" "Q:\pg_wal_desired_location"

4
Create a restore job, and select the first Incremental File Level Data Copy saveset to restore to the staging directory.
5
Repeat the previous step for each Incremental File Level Data Copy saveset to restore.
6
For the last Incremental File Level Data Copy saveset that you restore, select the Include Recover Command File with Restore option, and any other applicable options, on the Point in Time Recovery tab.
7
Restart the PostgreSQL service.
8
After the PostgreSQL service has restarted, use the PostgreSQL psql tool to run the following command and complete the recovery:
select pg_wal_replay_resume();
Example:
bash$ psql
postgres=# select pg_wal_replay_resume();
pg_wal_replay_resume
----------------------
(1 row)
postgres=#

Performing advanced restore procedures

You can complete the following advanced procedures:

•
Restoring Global Objects
•
Restoring configuration files
•
Renaming a database during restore
•
Restoring data to a different database cluster
•
Restoring to a database cluster on an alternate server

Restoring Global Objects

You can restore Global Objects from a Plain-Text SQL Script File version of a Full Database Cluster or Global Objects Only backup.

1
Select the Global Objects node from the backup saveset by following the instructions outlined in Selecting data for a restore.
2
Set the Restore Options by following the instructions outlined in Setting restore options and completing the following parameters:
•
Stop on Error: Select this option if you want the restore to stop immediately when an error occurs.
•
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.
•
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.”
 
* 
IMPORTANT: PostgreSQL does not allow detailed restores of individual Global Objects, nor does it allow you to delete global objects before restoring. Therefore, when restoring Global Objects, all the Global Objects are restored. As a result, you encounter error messages about duplicate items during restore. Quest recommends that you restore Global Objects to an empty database cluster during disaster recovery or use the Continue Restore with Warnings option. If the Global Objects are being restored to recover dropped roles or users and the Continue Restore With Warnings option has been selected, warnings are logged in the NetVault Backup binary logs for roles or users that exist.
3
Continue with the restore procedure as explained in Finalizing and submitting the job.

To restore Global Objects from a TAR Archive File or Custom Archive File backup, no additional Restore Options are available. Perform Step 1 and Step 3 to restore Global Objects from these backup formats.

For restoring the data to a different database cluster, see Restoring data to a different database cluster.

Restoring configuration files

When restoring configuration files, you do not have to set any restore options — unless you are restoring to a different cluster or server; for more information, see Restoring data to a different database cluster. The plug-in does not let you select individual configuration files for restoration.

1
Select the Configuration Files node from the backup saveset by following the instructions outlined in Selecting data for a restore.
2
Set the Restore Options by following the instructions outlined in Setting restore options.
3
Continue with the restore procedure as explained in Finalizing and submitting the job.
4
After restoring the configuration files, restart the PostgreSQL Server to apply the settings.
 
* 
IMPORTANT: You can restore configuration files when the database server is not running. However, do not include database, table, and Global Objects in the same job. If you attempt to restore any of these items together with the configuration files when the database server is not running, the restore job fails as a result of login failure.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación