You can perform a table restore and a full instance restore to the same host or a different host from PostgreSQL block-level backups.
Note
Create roles and tablespaces in the destination before attempting database or table level restore.
Live browse for block level restore requires a staging folder to store the extents and metadata. By default, the staging folder is in the job results directory. The size of the staging folder must be at least 4 GB. The recommended size of the staging folder is 10% of the restore data, and it can be as large as the restore data. If the size of the staging folder is smaller than the restore data, then the extents are pruned based on the LRU (least recently used) algorithm, for the new extent restores. This might result in decreased performance during the restore operation.
Best Practice: Include the parent tables with all dependent tables so that the reference constraints remain intact.
You can use one of the following methods to restore the PostgreSQL tables and instances:
Restoring PostgreSQL Tables
Restoring PostgreSQL Instances
Restoring Block-Level Volume Backups
Important
At the time of restore operation, the log files are downloaded to the staging directory. Ensure that the staging directory has sufficient space to hold the log files. The size of the staging directory depends on the total application size of the relevant log backups that you run in a cycle. For example, if there are five transaction log backups in a backup cycle, you can add up the application size of all the five log backups to decide on the size of the staging directory that you need.