Stay organized with collections
Save and categorize content based on your preferences.
Restore a PostgreSQL database from a volume-level backup image to the source
This procedure uses physical recovery of the source data area. To recover
back to the source, follow these instructions:
From the App Manager Applications list, right-click the
protected database and select Access. Use the
Managed Backup Plan status filter to show only protected databases.
Select a snapshot image and click Restore.
On the Restore page, select Restore Back to Source.
Target. This is inaccessible when restoring to the source.
(Optional) Enter a descriptive Label to use for this job.
Application Options
If the source application is protected by a snapshot policy that has
enabled database log backups, and logs are available with the image,
you can use them to roll forward to a specific point in time by changing
these options in the Roll Forward Time section:
The date field contains all possible dates that the database can be
rolled forward to through the application of database transaction
logs. Select which date you need the database to be rolled forward to.
The time field contains a slider showing all possible times on the
selected date that the database can be rolled forward to. If you select
the latest possible date and then move the slider to the right most
position, the restore job applies to all available logs. If you select
the earliest possible date and move the slider to the left most position,
the restore job applies no logs.
You can specify to roll forward using either User Time or Host Time.
User Time is relative to the local time of the current user.
Host time is relative to the system that hosts the data to be restored.
PostgreSQL Target Server Port. Enter the target PostgreSQL instance port
number for restore.
PostgreSQL Target OS User Name. Enter the name of the operating system
user on the target server where the PostgreSQL instance is to be restored.
PostgreSQL Target Server Home Directory. Enter the path of the PostgreSQL
installed binary home directory on the target server.
PostgreSQL Target Server Data Directory. Enter the path to the data
directory where the data files for the PostgreSQL database on the target
server are stored, for example, /pgdata_lvm/pgdata.
Advanced Options
POSTGRESQL TARGET DB USER NAME and POSTGRESQL TARGET DB PASSWORD.
(Optional) Enter new credentials for the target PostgreSQL instance that
will be created. If you don't specify anything, the default database
username (postgres) is used with no password. By default, a password is not
required to sign in from the local system.
Click Pre-flight check.
If the pre-flight check fails, fix the issue and resubmit the pre-flight check.
If the pre-flight check is successful, click Submit to submit the restore job.
Restore a PostgreSQL database from a volume-level backup image to a new target
From the App Manager Applications list, right-click the
protected database and select Access. Use the
Managed Backup Plan status filter to show only protected databases.
Select a snapshot image and click Restore.
On the Restore page, select Restore to a New Target.
For all configurations, eligible PostgreSQL nodes will be available to choose
under the Target drop-down list. Select the node for the new target.
(Optional) Enter a descriptive Label to use for this job.
Replace Original Application Identity. This option is only available when
the restore target is a new host on the same backup/recovery appliance where
the backup was originally generated.
Yes. This replaces the original application and it has the same
application ID, jobhistory, backup images and backup plan as the original
application.
No. This does not replace the original application. It creates a new
application that is discovered but not yet protected.
If logs are available, then Rollforward time is available. Choose a date
and time for the most recent logs to apply to the recovered database.
Included Databases: This is pre-populated with the list of PostgreSQL user
databases that will be restored with the PostgreSQL instance restore. It is
immutable.
Application Options
PostgreSQL Target Server Port. Enter the target PostgreSQL instance
port number for restore.
PostgreSQL Target OS User Name. Enter the name of the operating system
user on the target server where the PostgreSQL instance is to be restored.
PostgreSQL Target Server Home Directory. Enter the path of the
PostgreSql installed binary home directory on the target server.
PostgreSQL Target Server Data Directory. Enter the path of the data
directory where the data files for the PostgreSQL database on the target
server are stored, for example, /pgdata_lvm/pgdata.
Advanced Options
POSTGRESQL TARGET DB USER NAME and POSTGRESQL TARGET DB PASSWORD.
(Optional) Enter new credentials for the target PostgreSQL instance that
will be created. If you don't specify anything, the default database
username (postgres) is used with no password. By default, a password is not
required to sign in from the local system.
Click the Pre-Flight Check.
If the pre-flight check fails, fix the issue and resubmit the Pre-Flight
Check.
If the pre-flight check is successful, click Submit to submit the
restore job.
Restore a PostgreSQL database from a full+incremental backup image to the source
From the App Manager Applications list, right-click the
protected database and select Access. Use the
Managed Backup Plan status filter to show only protected databases.
Select a snapshot image and click Restore.
On the Restore page, select Restore Back to Source.
Target. This is inaccessible when restoring to the source.
(Optional) Enter a descriptive Label to use for this job.
Included Databases. This is the list of PostgreSQL databases that will be
restored with PostgreSQL instance restore. Select one or more databases from
the list for restore. By default all databases are selected for restore.
Application Options
PostgreSQL Target OS User Name. Enter the name of the operating system user
on the target server where the new PostgreSQL instance will get created.
PostgreSQL Target Server Home Directory. Enter the path to the
PostgreSQL installed binary home directory on the target server.
PostgreSQL Target Config File Path. Enter the config path for
PostgreSQL instance on the target server.
Advanced Options
POSTGRESQL TARGET DB USER NAME and POSTGRESQL TARGET DB PASSWORD.
(Optional) Enter new credentials for the target PostgreSQL instance that
will be created. If you don't specify anything, the default database
username (postgres) is used with no password. By default, a password is not
required to sign in from the local system.
Click the Pre-Flight Check.
If the pre-flight check fails, fix the issue and resubmit the Pre-Flight
Check.
If the pre-flight check is successful, click Submit to submit the
restore job.
Restore a PostgreSQL database from a full+incremental backup image to a new target
From the App Manager Applications list, right-click the
protected database and select Access. Use the
Managed Backup Plan status filter to show only protected databases.
Select a snapshot image and click Restore.
On the Restore page, select Restore to a New Target.
For all configurations, eligible PostgreSQL nodes are available to choose
under the Target drop-down list. Select the node for the new target.
(Optional) Enter a descriptive Label to use for this job.
Replace Original Application Identity. This option is only available when
the restore target is a new host on the same backup/recovery appliance where
the backup was originally generated.
Yes. This replaces the original application and has the same
application ID, jobhistory, backup images and backup plan as the original
application.
No. This does not replace the original application. It creates a new
application that is discovered but not yet protected.
Included Databases: This is pre-populated with the list of PostgreSQL
databases that will be restored with the PostgreSQL instance restore. It is
immutable.
Application Options
PostgreSQL Target OS User Name. Enter the name of the operating system
user on the target server where the new PostgreSQL instance will get created.
PostgreSQL Target Server Home Directory. Enter the path to the
PostgreSQL installed binary home directory on the target server
PostgreSQL Target Config File Path. Enter the config path of the
PostgreSQL instance on the target server.
Advanced Options
POSTGRESQL TARGET DB USER NAME and POSTGRESQL TARGET DB PASSWORD.
(Optional) Enter new credentials for the target PostgreSQL instance that
will be created. If you don't specify anything, the default database
username (postgres) is used with no password. By default, a password is not
required to sign in from the local system.
Click the Pre-Flight Check.
If the pre-flight check fails, fix the issue and resubmit the Pre-Flight
Check.
If the pre-flight check is successful, click Submit to submit the
restore job.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eThis guide outlines how to restore a PostgreSQL database from a backup image, either back to its original source or to a new target location.\u003c/p\u003e\n"],["\u003cp\u003eYou can choose to restore from either a volume-level backup or a full+incremental backup image, depending on your needs and backup strategy.\u003c/p\u003e\n"],["\u003cp\u003eDuring the restore process, there are optional settings to specify a roll-forward time by using logs to bring the database to a specific point in time, which can be performed in user time or host time.\u003c/p\u003e\n"],["\u003cp\u003eThe guide provides options for setting parameters like the target server port, operating system user, home directory, and data directory, as well as optional custom database credentials.\u003c/p\u003e\n"],["\u003cp\u003eA pre-flight check is a crucial step to validate the configurations before submitting the restore job, and ensures the job is successful.\u003c/p\u003e\n"]]],[],null,["# Restore PostgreSQL databases\n\nRestore a PostgreSQL database from a volume-level backup image to the source\n----------------------------------------------------------------------------\n\nThis procedure uses physical recovery of the source data area. To recover\nback to the source, follow these instructions:\n\n1. From the **App Manager Applications** list, right-click the protected database and select **Access** . Use the **Managed Backup Plan** status filter to show only protected databases.\n2. Select a snapshot image and click **Restore**.\n3. On the **Restore** page, select **Restore Back to Source**.\n4. **Target**. This is inaccessible when restoring to the source.\n5. (Optional) Enter a descriptive **Label** to use for this job.\n6. Application Options\n - If the source application is protected by a snapshot policy that has enabled database log backups, and logs are available with the image, you can use them to roll forward to a specific point in time by changing these options in the **Roll Forward Time** section:\n - The date field contains all possible dates that the database can be rolled forward to through the application of database transaction logs. Select which date you need the database to be rolled forward to.\n - The time field contains a slider showing all possible times on the selected date that the database can be rolled forward to. If you select the latest possible date and then move the slider to the right most position, the restore job applies to all available logs. If you select the earliest possible date and move the slider to the left most position, the restore job applies no logs.\n - You can specify to roll forward using either **User Time** or **Host Time** . **User Time** is relative to the local time of the current user. **Host time** is relative to the system that hosts the data to be restored.\n - **PostgreSQL Target Server Port**. Enter the target PostgreSQL instance port number for restore.\n - **PostgreSQL Target OS User Name**. Enter the name of the operating system user on the target server where the PostgreSQL instance is to be restored.\n - **PostgreSQL Target Server Home Directory**. Enter the path of the PostgreSQL installed binary home directory on the target server.\n - **PostgreSQL Target Server Data Directory** . Enter the path to the data directory where the data files for the PostgreSQL database on the target server are stored, for example, `/pgdata_lvm/pgdata`.\n7. Advanced Options\n - **POSTGRESQL TARGET DB USER NAME** and **POSTGRESQL TARGET DB PASSWORD**. (Optional) Enter new credentials for the target PostgreSQL instance that will be created. If you don't specify anything, the default database username (postgres) is used with no password. By default, a password is not required to sign in from the local system.\n8. Click **Pre-flight check** .\n - If the pre-flight check fails, fix the issue and resubmit the pre-flight check.\n - If the pre-flight check is successful, click **Submit** to submit the restore job.\n\nRestore a PostgreSQL database from a volume-level backup image to a new target\n------------------------------------------------------------------------------\n\n1. From the **App Manager Applications** list, right-click the protected database and select **Access** . Use the **Managed Backup Plan** status filter to show only protected databases.\n2. Select a snapshot image and click **Restore**.\n3. On the Restore page, select **Restore to a New Target**.\n4. For all configurations, eligible PostgreSQL nodes will be available to choose under the **Target** drop-down list. Select the node for the new target.\n5. (Optional) Enter a descriptive **Label** to use for this job.\n6. **Replace Original Application Identity** . This option is only available when the restore target is a new host on the same backup/recovery appliance where the backup was originally generated.\n - **Yes**. This replaces the original application and it has the same application ID, jobhistory, backup images and backup plan as the original application.\n - **No**. This does not replace the original application. It creates a new application that is discovered but not yet protected.\n7. If logs are available, then **Rollforward time** is available. Choose a date and time for the most recent logs to apply to the recovered database.\n8. Included Databases: This is pre-populated with the list of PostgreSQL user databases that will be restored with the PostgreSQL instance restore. It is immutable.\n9. Application Options\n - **PostgreSQL Target Server Port**. Enter the target PostgreSQL instance port number for restore.\n - **PostgreSQL Target OS User Name**. Enter the name of the operating system user on the target server where the PostgreSQL instance is to be restored.\n - **PostgreSQL Target Server Home Directory**. Enter the path of the PostgreSql installed binary home directory on the target server.\n - **PostgreSQL Target Server Data Directory** . Enter the path of the data directory where the data files for the PostgreSQL database on the target server are stored, for example, `/pgdata_lvm/pgdata`.\n10. Advanced Options\n - **POSTGRESQL TARGET DB USER NAME** and **POSTGRESQL TARGET DB PASSWORD**. (Optional) Enter new credentials for the target PostgreSQL instance that will be created. If you don't specify anything, the default database username (postgres) is used with no password. By default, a password is not required to sign in from the local system.\n11. Click the **Pre-Flight Check** .\n - If the pre-flight check fails, fix the issue and resubmit the Pre-Flight Check.\n - If the pre-flight check is successful, click **Submit** to submit the restore job.\n\nRestore a PostgreSQL database from a full+incremental backup image to the source\n--------------------------------------------------------------------------------\n\n1. From the **App Manager Applications** list, right-click the protected database and select **Access** . Use the **Managed Backup Plan** status filter to show only protected databases.\n2. Select a snapshot image and click **Restore**.\n3. On the Restore page, select **Restore Back to Source**.\n4. **Target**. This is inaccessible when restoring to the source.\n5. (Optional) Enter a descriptive **Label** to use for this job.\n6. **Included Databases**. This is the list of PostgreSQL databases that will be restored with PostgreSQL instance restore. Select one or more databases from the list for restore. By default all databases are selected for restore.\n7. Application Options\n - **PostgreSQL Target OS User Name**. Enter the name of the operating system user on the target server where the new PostgreSQL instance will get created.\n - **PostgreSQL Target Server Home Directory**. Enter the path to the PostgreSQL installed binary home directory on the target server.\n - **PostgreSQL Target Config File Path**. Enter the config path for PostgreSQL instance on the target server.\n8. Advanced Options\n - **POSTGRESQL TARGET DB USER NAME** and **POSTGRESQL TARGET DB PASSWORD**. (Optional) Enter new credentials for the target PostgreSQL instance that will be created. If you don't specify anything, the default database username (postgres) is used with no password. By default, a password is not required to sign in from the local system.\n9. Click the **Pre-Flight Check** .\n - If the pre-flight check fails, fix the issue and resubmit the Pre-Flight Check.\n - If the pre-flight check is successful, click **Submit** to submit the restore job.\n\nRestore a PostgreSQL database from a full+incremental backup image to a new target\n----------------------------------------------------------------------------------\n\n1. From the **App Manager Applications** list, right-click the protected database and select **Access** . Use the **Managed Backup Plan** status filter to show only protected databases.\n2. Select a snapshot image and click **Restore**.\n3. On the Restore page, select **Restore to a New Target**.\n4. For all configurations, eligible PostgreSQL nodes are available to choose under the **Target** drop-down list. Select the node for the new target.\n5. (Optional) Enter a descriptive **Label** to use for this job.\n6. **Replace Original Application Identity** . This option is only available when the restore target is a new host on the same backup/recovery appliance where the backup was originally generated.\n - **Yes**. This replaces the original application and has the same application ID, jobhistory, backup images and backup plan as the original application.\n - **No**. This does not replace the original application. It creates a new application that is discovered but not yet protected.\n7. **Included Databases**: This is pre-populated with the list of PostgreSQL databases that will be restored with the PostgreSQL instance restore. It is immutable.\n8. Application Options\n - **PostgreSQL Target OS User Name**. Enter the name of the operating system user on the target server where the new PostgreSQL instance will get created.\n - **PostgreSQL Target Server Home Directory**. Enter the path to the PostgreSQL installed binary home directory on the target server\n - **PostgreSQL Target Config File Path**. Enter the config path of the PostgreSQL instance on the target server.\n9. Advanced Options\n - **POSTGRESQL TARGET DB USER NAME** and **POSTGRESQL TARGET DB PASSWORD**. (Optional) Enter new credentials for the target PostgreSQL instance that will be created. If you don't specify anything, the default database username (postgres) is used with no password. By default, a password is not required to sign in from the local system.\n10. Click the **Pre-Flight Check** .\n - If the pre-flight check fails, fix the issue and resubmit the Pre-Flight Check.\n - If the pre-flight check is successful, click **Submit** to submit the restore job."]]