Renaming a database during restore
|
1 |
In the Navigation pane, click Create Restore Job. |
.|
3 |
|
4 |
On the Create Selection Set page, click the database that you want to rename, and select Rename from the context menu. |
|
5 |
|
IMPORTANT: If the cluster is configured to use UTF-8 encoding at initdb, you cannot use a name that contains non-ASCII characters. |
|
6 |
Click OK. |
|
7 |
Restoring data to a different database cluster
Before initiating this type of restore, verify that the following prerequisites are met:
|
• |
Same version of PostgreSQL installed: The PostgreSQL version must be same as the version running on the existing database server. |
|
• |
Database cluster exists on the PostgreSQL Server: A database cluster must exist on the PostgreSQL Server and this cluster must be added to the plug-in. To add the cluster, see Adding a database cluster. |
|
1 |
|
2 |
Set the Restore Options by following the instructions outlined in Setting restore options and completing the following parameter: |
|
3 |
Restoring to a database cluster on an alternate server
|
• |
Same OS: The OS running on the target system must be same as the source system. |
|
• |
Same version of PostgreSQL installed: The PostgreSQL version must be same as the version running on the existing database server. |
|
• |
NetVault software and Plug‑in for PostgreSQL installed: The same version of NetVault software and the plug-in must be installed and configured on the new restore target. |
|
• |
Client added to the NetVault Server: The target machine must be added to the NetVault Server through the NetVault WebUI. |
|
• |
Database cluster exists on the new restore target: A database cluster must exist on the new restore target and the cluster must be added to the plug-in. To add the cluster, see Adding a database cluster. |
|
1 |
|
2 |
|
3 |
|
4 |
In Job Name, specify a name for the job if you do not want to use the default setting. |
|
IMPORTANT: Do not use special characters that are not supported in a filename on the target OS. For example, do not use the characters /,\,*, or @ on Windows. This requirement is because Plug‑in for PostgreSQL tries to create a folder with the same name as the job title for restoring data temporarily. |
|
5 |
In the Target Client list, select the new restore target. |
|
TIP: You can also click Choose, and then locate and select the applicable client in the Choose the Target Client dialog box. |
|
6 |
|
7 |
Troubleshooting
|
Password Authentication Failed for the User <username>. |
The superuser password set in the Configure dialog box is invalid. Update the password in the plug-in by following the instructions in Reconfiguring an added database cluster. | |||||||
|
The “pg_hba.conf” file is not available for user authentication. If the “pg_hba.conf” file contains entries for both IPv4 and IPv6, configure the same authentication for each. For example, use TRUST authentication for both IPv4 and IPv6 connections. | ||||||||
| ||||||||
|
Backup in TAR Archive File format fails with the following message: |
Check the pg_dump command with the TAR Archive format from a command prompt or terminal session. If the following error is displayed, “pg_dump: [tar archiver] actual file length <xxxx> does not match expected <xxxx>,” you cannot use the TAR Archive File backup format on the current installation. Use the Custom Archive File format instead. | |||||||
|
On Windows, the backup fails with the following message: Database was found, but failed to backup <locale_name> database. |
Check the pg_dump command from the command prompt. If the following error is displayed, “pg_dump: Cannot access “??-UTF8-C” [database to be dumped]: FATAL: database “??-UTF8-C” does not exist pg_dump: *** Stopped by error,” the problem is in the character-set encoding configured for the database cluster. | |||||||
|
Ensure that the password provided in the Add Database Cluster/Configure Database Cluster dialog box of the plug-in is correct. If the cluster is configured to use TRUST authentication for HOST connection while PASSWORD authentication for LOCAL connection, the backups fail if the password is incorrect or blank. If the “pg_hba.conf” file contains entries for both IPv4 and IPv6, configure the same authentication for each. For example, use TRUST authentication for both IPv4 and IPv6 connections. Quest recommends the following in this scenario:
| ||||||||
|
Without this index information, the data cannot be properly restored. |
Access the Manage Devices page of the NetVault WebUI, and perform a scan of the media targeted by the job. NetVault stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. Performing this scan adds the index information to the NetVault Database. To verify that the information was added, open the Create Restore Job — Choose Saveset page and locate the specific job. If you can browse it and set up a restore job, the scan process has corrected the problem. | |||||||
| ||||||||
|
Restore job failed and PostgreSQL log lists the following message: |
Your PostgreSQL database uses foreign keys to maintain the integrity of the data. To drop the table manually from PostgreSQL, use the DROP TABLE command with the CASCADE parameter. DROP TABLE removes the table from the database, and CASCADE ensures that any objects that depend on the table are also dropped. For more information, see your PostgreSQL documentation. |