NetBackup™ Web UI PostgreSQL Administrator's Guide
- Overview
- Managing PostgreSQL instances and databases
- Managing PostgreSQL environment credentials
- Protecting PostgreSQL instances and databases
- Restoring PostgreSQL Instances and Databases
- Things to know before you restore the PostgreSQL instances and databases
- About the pre-restore check
- Restore PostgreSQL instance and database
- Restore target options
- Pre-restore checks for PostgreSQL
- Steps to perform recovery after restore operation
- Steps to perform after Restore and Recovery for PostgreSQL cluster deployment
- Limitations
- Troubleshooting PostgreSQL operations
- Troubleshooting tips for NetBackup for PostgreSQL
- Error during PostgreSQL credential addition
- Error during the PostgreSQL instances and databases discovery phase
- Error during the PostgreSQL Protection Plan Creation
- Error while subscribing protection plan to PostgreSQL asset
- Error while removing PostgreSQL asset
- Error while backup of PostgreSQL asset
- Error while restoring PostgreSQL asset image
- API for PostgreSQL instances and databases
- Index
Limitations
Cross-platform recovery of individual files is not supported. The restore client must be the same platform as the instances that you want to restore. Windows instances can be restored using Windows operating systems and Linux instances can be restored only using Linux operating systems.
For client platform and file system support and limitations, see https://www.veritas.com/support/en_US/doc/NB_70_80_VE .
If a backup and a restore occur simultaneously on the same database, one or both jobs can have unexpected results.
Note:
If a backup or a restore exits with a non-zero NetBackup status code, one possible cause is simultaneous jobs occurring on the same instance.
Restore job fails, if NetBackup does not have sufficient privileges or if there is insufficient space in the client memory.
NetBackup does not support non-ASCII characters in target client location path.