Using Commvault Backup & RecoverySuggest edits
How to backup and restore an EDB Database using Commvault Backup & Recovery.
Commvault provides two methods of taking the backup from an EDB database and restoring it.
- DumpBasedBackupSet Backup and Restore
- FSBasedBackupSet Backup and Restore
At this time there is a known issue with FSBased Restore that does not allow for proper restoration of the database. See the known issues section of the guide for more information.
Dump based backup uses the
pg_dump Utility to take the backup.
Open Commvault Backup & Recovery's Command Center and from the navigation pane, go to
Protect > Databases.
Click on the required instance.
Backup setssection, click on
Database groupssection, click the database group that you want to back up. In this case it is
Back up now.
Select Backup Levelscreen.
A Job will be created to take the backup.
Once the Backup Job is completed then its status will be changed to
DumpBased backupset can be used to restore the individual databases.
From the navigation pane, go to
Protect > Databases.
Click the instance that you want to restore.
Recovery pointscalendar, select
Select a date from the calendar, and then click
Backup Contentscreen will display the databases to be restored, select the required database to restore or select all of them to restore all.
Restore Optionsscreen, select the
Destination Instanceand click on
A Job will be created to restore the backup.
Once the Restore is completed successfully, login to the EDB database and check that the restore operation recovered the data. In our example below we connected to an EDB Postgres Advanced Server instance.
FSBaseBackupSet Restore has an issue if the default edb directory (for example,
*:\Program files\edb) has been lost or deleted. If this occurs then after a restore is performed, the permissions on the restored directories are not recovered. Instead the directory inherits the permissions from the parent directory which does not allow EDB Postgres Advanced Server services to start on the restored directory. We are working with Commvault to resolve the issue.