1 |
3 |
4 |
Click the applicable database-cluster node, and select Configure from the context menu. |
5 |
On the Configure Database Cluster dialog box, update the parameters as required. |
• |
You cannot change the Database Cluster Name. |
1 |
3 |
4 |
Click the applicable database-cluster node, and select Remove from the context menu. |
IMPORTANT: The Plug‑in for PostgreSQL node will remain in an Open state even after the last database cluster is removed. To close this node and access the other plug-ins in the selection tree, double-click the plug-in node. |
The plug-in lets you set default options for backup and restore jobs.
1 |
In the Navigation Pane, click Create Backup Job. |
2 |
Next to the Selections list, click Create New. |
3 |
In the selection tree, open the applicable client node and click Plug-in for PostgreSQL. |
4 |
From the context menu, select Configure. |
• |
Allow File Level Data Copy Recovery to Modify postgresql.conf file. Selecting this option gives NetVault Backup permission to automatically copy the contents of the “recovery.signal” file into the “postgresql.conf” file before it begins the recovery. This option applies to Plug‑in for PostgreSQL File Level Data Copy restore and recovery jobs. By default, the option is not selected. To automate File Level Data Copy recovery, select this option. If not selected, then during a recovery, you must manually add the contents of the “recovery.signal” file to the PostgreSQL “postgresql.conf” file. |
1 |
In the Navigation pane, click Change Settings. |
2 |
3 |
4 |
• |
Manually Selected Database Unavailable: This issue occurs when an individual database that was manually selected, that is, explicitly clicked, for inclusion in the backup is unavailable for backup. The database might be unavailable for any reason, such as being dropped since the backup job was defined. |
• |
Manually Selected Table Unavailable: This issue occurs when an individual table that was manually selected, that is, explicitly clicked, for inclusion in the backup is unavailable for backup. The table might be unavailable for any reason, such as being dropped since the backup job was defined. |
• |
Failed to Backup Configuration Files: This issue occurs when a configuration file is not found or cannot be backed up for any other reason. The “pg_hba.conf” file is used for user authentication; if this file is missing during job execution, the backup fails because of login failure, regardless of the action set for the Failed to Backup Configuration Files error condition. |
• |
Allow File Level Data Copy Recovery to Modify postgresql.conf file. Selecting this option gives NetVault Backup permission to automatically copy the contents of “recovery.signal” into the “postgresql.conf” file before it begins the recovery. |
• |
Complete with Warnings — Saveset Retained: The job returns a status of “Backup Completed with warnings” and a backup saveset is created that includes the items that were successfully backed up. |
• |
Complete without Warnings — Saveset Retained: The job completes and returns a status of “Backup Completed.” The errors are logged in the NetVault Backup binary logs and ignored on the Job Status page. A backup saveset is created that includes the items that were backed up. |
• |
Fail — Saveset Retained: The job returns a status of “Backup Failed.” However, a backup saveset is generated that includes the items that were successfully backed up. |
• |
Fail — No Saveset Retained: The job returns a status of “Backup Failed” and no saveset of backed-up objects is kept. That is, even if some of the objects were successfully backed up, the saveset is discarded. |
6 |
To save the settings, click Apply. |
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center