Documentation PDF

PROTECT. ACCESS. COMPLY. SHARE

PostgreSQL
The PostgreSQL agent is designed to efficiently manage and protect business critical data in PostgreSQL databases. You can use this agent to backup and restore the
entire PostgreSQL server or individual databases. If necessary, you can also restore individual tables.

Key Features
Block-Level Backups
You can use block-level backup as a faster method to back up data because only the extents (or modified parts of the database) are backed up rather than the entire
PostgreSQL database. You eliminate the need to run a full backup each time the database is changed. For more information, see PostgreSQL Block-Level Backup .

Automatic Discovery of Applications

You can use the Auto discover applications option to automatically find PostgreSQL databases in your environment and install software to back up the PostgreSQL
databases. For more information, see Automatic Discovery of Applications .

A Wide Range of Backup and Restore Operations

The following table describes the backups and restores that can be performed on the PostgreSQL Agent:

Backup More
Feature Uses Backup options Backup set Restore options
type information
Backup of Create a Traditional Full DumpBasedBackupSet Database Cloud Apps
databases consistent level restore
from an dump of
instance databases Schema level
hosted in using restore
cloud pg_dump Table level
using restore
pg_dump Create a
utility table Restore to
objectlist another
during instance on
backup cloud
(optional)
Restore to an
onpremise
instance
Backup of Create a Traditional Full DumpBasedBackupSet Database Creating a
databases consistent level restore PostgreSQL
from an dump of Subclient to
on- databases Schema level Back Up
premise using restore Specific
using pg_dump Table level Databases
pg_dump restore
utility Create a
table Table level
objectlist restore to
during auxiliary
backup database
(optional)
Restore dump
to disk
Cross
instance
restore
Cross
machine
restore
File based Combine file Traditional Full FSBasedBackupSet Full instance Configuration
online system- restore - PostgreSQL
data level backup Incremental iDataAgent
backup of data files logs Point in time
with WAL and WAL restore
files files to Application-
restore Free Restore
1/31/2023 Commvault Systems Page 2 of 35
 restore Free Restore
databases
to a Redirect
consistent restore
level by Cross
replay of instance
logs restore
Perform full Cross
backup of machine
data restore
directory,
tablespace
directories,
config files
and WAL
files
Incremental
backup of
WAL files
Snapshot Create IntelliSnap Full FSBasedBackupSet Full instance Getting
based application restore from Started with
online consistent Incremental snapshot the
data storage logs PostgreSQL
backup snapshots Full instance Agent
with WAL while the restore from
files, database is backup copy
followed in the Revert
by file backup restore
system mode
backup Point in time
copy Copy restore
snapshots
to a disk at Redirect
file level restore
using Instant Clone
multistream Recovery
backup
copy option Cross
instance
Proxy client restore
to mount
snapshot Cross
during machine
backup restore
copy
(optional)
Block level Create Block level Full FSBasedBackupSet Full instance Block-Level
backups application restore from Backups
using consistent Incremental snapshot
snapshot storage data
based snapshots Full instance
Incremental restore from
online while the logs
data database is backup copy
backup in the Synthetic Revert
with WAL backup full restore
files, mode, with
followed efficient Database
by file block level restore
system storage Schema level
backup mechanisms restore
copy to speed up
the backups Table level
restore
Faster
backups, Point in time
quick restore
granular Redirect
restore and restore
1/31/2023 improved Commvault Systems Page 3 of 35
 restore
improved
recovery Cross
points with instance
frequent restore
backup
cycles Cross
machine
Copy restore
snapshots
to a disk at Instant Clone
file level Recovery
using Volume level
multistream multisteam
backup restore
copy option (indexing v2
Proxy client client only)
to mount
snapshot
during
backup
copy
(optional)
Live Sync Continuous Traditional Full FSBasedBackupSet As applicable for Live Sync
replication synchronization traditional backups Replication
of master server Incremental of
to standby server logs FSBasedBackupSet
by restoring logs
from the backups
taken for master
Backup File based Traditional Based on the FSBasedBackupSet Based on the Back Up from
from online backup type backup type Standby
Standby backup of IntelliSnap selected selected Server
Server data and
WAL files
from
standby
server
Offloads
backup
activity from
production
server

1/31/2023 Commvault Systems Page 4 of 35

PostgreSQL Agent: System Requirements
Verify that your environment meets the system requirements for PostgreSQL.

Application
PostgreSQL and EnterpriseDB Version 9.2–14.x

Operating System
AIX
Operating system Processor architecture
AIX 7.1 64-bit PowerPC

FreeBSD
Operating system Processor architecture
FreeBSD 10.x x64
Compatible processors
FreeBSD 9.x x64
Supported for PostgreSQL Version 9.2 only. Compatible processors

Linux
Operating system Processor architecture
Amazon Linux 2 x64
Compatible processors
Debian 11.x x64
Compatible processors
Debian 10.x x64
Compatible processors
Debian 9.x x64
Compatible processors
Debian 8.x x64
Compatible processors
Debian 7.x x64
Compatible processors
Debian 6.x x64
Compatible processors
Debian 5.x x64
Compatible processors
Oracle Linux 8.x with glibc 2.28.x or a more recent version x64
Compatible processors
Red Hat Enterprise Linux 9.x with glibc 2.34.x x64
Compatible processors
Red Hat Enterprise Linux/CentOS 8.x with glibc 2.28.x x64
1/31/2023 Commvault Systems Page 5 of 35
 PowerPC (little endian)
Compatible processors
Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 7.x x64
PowerPC (little endian)
Compatible processors
Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 6.x with glibc 2.12.x Intel Pentium
x64
Power PC (Little endian)
Compatible processors
Red Hat Enterprise Linux/Oracle Linux Enterprise/CentOS 5.x with glibc 2.5.x x86
x64
Compatible processors
Source Mage Linux x64
SuSE Linux 15 SP3 x64
PowerPC (little endian)
Compatible processors
SuSE Linux 12 Initial Release x64
PowerPC (little endian)
Compatible processors
SuSE Linux 11 (Initial Release/SP1 and later SPs) with glibc 2.9.x and higher Intel Pentium
x64
Power PC (Little endian)
Compatible processors
Ubuntu 22.04 LTS x86
x64
Compatible processors
Ubuntu 20.04 LTS x86
x64
Compatible processors
Ubuntu 18.04 LTS x86
x64
Compatible processors
Ubuntu 16.04 LTS x86
x64
Compatible processors
Ubuntu 14.04 LTS x86
x64
Compatible processors
Ubuntu 12.04 LTS x86
x64
Compatible processors

1/31/2023 Commvault Systems Page 6 of 35

Solaris
Operating system Processor architecture
Solaris 11.x x64
Sparc T/M series
Solaris 10 Update 6 or equivalent x64
Sparc T/M series

Windows
Operating system Processor architecture
Microsoft Windows Server 2019 Editions All Windows-compatible processors are supported
All Windows-compatible processors are supported
Microsoft Windows Server 2016 Editions
Server Core installations are not supported.
Microsoft Windows Server 2012 R2 Editions All Windows-compatible processors are supported
Server Core installations are not supported.
Microsoft Windows Server 2012 Editions All Windows-compatible processors are supported
Server Core installations are not supported.
Microsoft Windows Server 2008 R2 Editions All Windows-compatible processors are supported
Server Core installations are not supported.

Hard Drive
Component Space required
Software 1 GB
Job results folder 256 MB
Log folder 256 MB

Memory (RAM)
2 GB or more

Block-Level Backups
Block-level backups are supported only on Linux platforms. For supported Linux kernel version details of PostgreSQL block-level backups, see List of
Supported Kernel Versions .
Block-level backups on Network File System (NFS) are not supported.

Software That Is Automatically Installed

Linux File System Agent
The Linux File System Agent is automatically installed during installation of this software, if it is not already installed. For system requirements and installation
information, see Linux File System: System Requirements .

Microsoft Visual C++ Redistributable 2017

Starting with Service Pack 18, Microsoft Visual C++ Redistributable 2017 (vcredist2017.exe) is automatically installed.
If a computer does not have the most recent Windows updates, the installation of Microsoft Visual C++ Redistributable 2017 will fail in installing Universal C Runtime.
The following Windows updates must be installed to prevent the installation failure. The updates are not required on the most recent Windows operating system
versions, such as Microsoft Windows 10 and Microsoft Windows Server 2016, because these versions have the Universal C Runtime already installed.
KB2919355
1/31/2023 Commvault Systems Page 7 of 35
 KB2939087
KB2975061
KB2999226

DISCLAIMER
Certain third-party software and service releases (together, "Releases") may not be supported by Commvault. You are solely responsible for ensuring Commvault’s
products and services are compatible with any such Releases.

1/31/2023 Commvault Systems Page 8 of 35

Supported Features - PostgreSQL Agent
The following table lists the features that are supported by PostgreSQL iDataAgent.

Feature Sub-Feature Support Comments

Advanced Backup/Archive Options Data tab - Verify Synthetic Full
Job Retry tab
Media tab - Allow other Schedule to
use Media Set
Media tab - Mark Media Full on
Success
Media tab - Reserve Resources
Before Scan
Media tab - Start New Media
Startup tab
Vault Tracking tab
Comments
Advanced File System Agent Automatic File System Multi-
Options Streaming
On-Demand Data Protection
Operation
Restore by Jobs
Restore Data Using a Map File
Comments
Alerts and Monitoring Global Alerts
Job-Based Alerts
Comments
Backup/Archive Options Block-Level Backup Full, incremental and synthetic full
backups are supported on block-level
subclients.
Differential Backup
Full Backup
Incremental Backup Incremental log backups are supported
only on FSBasedBackupSet traditional
subclients.
Synthetic Full Backup
Comments Transaction logs are only supported for
File System backups.
Browse Browse from Copy Precedence
Browse the Latest Data
Browse Using Filters
Exclude Data Before
Find
Full Backup Transparent Browse

1/31/2023 Image Browse Commvault Systems Page 9 of 35

 Image Browse
No Image Browse By default, show deleted items is enabled.
Page Size
Specify Browse Path
Specify Browse Time
Subclient Browse
Use MediaAgent
View All Versions
Comments
Clustering Netware cluster
Unix Cluster
Windows - Microsoft Cluster (MSCS)
Windows - Non-Microsoft Cluster
Comments
Command Line Interface Command Line Interface
Comments
CommCell Migration CommCell Migration
Comments
Content Indexing Offline Content Indexing
Comments
Data Aging Basic Retention Rules
Deleting a Job
Extended Retention Rules
Retaining a Job
Unique Data Aging Rules
Comments
Data Compression Client Compression
Hardware Compression
MediaAgent Compression
Comments
Data Encryption Data Encryption
Third-party Command Line
Encryption Support
Comments
Data Multiplexing Multiplexing
Comments
Deduplication MediaAgent-Side Deduplication
Source-Side Deduplication
Comments
1/31/2023 Commvault Systems Page 10 of 35
 Delete Backup and Archive Data Delete Data Using CommCell
Console
Delete Data Using Web Console
Comments
File System Backup Quota File System Backup Quota
Comments
Global Filters Global Filters
Comments
GRC GRC
Comments
Installing 32-bit Components on a Install 32-bit On x64
Microsoft Windows x64 Platform
Comments
Job Restart - Data Protection Not Restartable
Restarts from the Beginning
Restarts from the Beginning of the
Database
Restarts from the Point-of-Failure
Comments
Job Restart - Data Recovery Not Restartable
Restarts from the Beginning
Restarts from the Beginning of the
Database
Restarts from the Point-of-Failure
Comments
List Media List Media Associated with a
Specific Backup Set or Instance
List Media Associated with Index
List Media Associated with Specific
Files and/or Folders
List Media Associated with Specific
Jobs
Comments
Live Sync Replication
Failover
Failback
Validation
Multi Instancing Multi-Instance Installations
Comments
Optimized Scan Optimized Scan
Comments
1/31/2023 Commvault Systems Page 11 of 35
 Pre/Post Processes Pre/Post Process with Data
Protection and Recovery
Comments
Restore/Recover/Retrieve Cross-Application Restores
Destinations (Different Application version)
Cross-Platform Restores - Different
Operating System
Cross-Platform Restores - Same
Operating System - Different
Version
In-place Restore - Same path/
destination - Same Client
Out-of-place Restore - Different
path/ destination
Out-of-place Restore - Same path/
destination - Different Client
Point-in-Time Restore
Restore Data Using a Map File
Restore to Network Drive /NFS-
Mounted File System
Table-Level Restore
Comments
Restore/Recover/Retrieve Options Automatic Detection of Regular
Expressions
Filter Data From Recover Operations
Rename/ Redirect Files on Restore
Restore Data Using Wildcard
Expressions
Restore Data with Pre/Post
Processes
Restore from Copies
Skip Errors and Continue
Use Exact Index
Use MediaAgent
Comments
Restore/Recover/Retrieve Overwrite Overwrite Files
Options
Overwrite if file in backup is newer
Restore only if target exists
Unconditional Overwrite
Unconditionally overwrite only if
target is a DataArchiver stub
Comments
Schedule Policy Agent Specific Data Protection
Schedule Policy
1/31/2023 Commvault Systems Page 12 of 35
 Schedule Policy
All Agent Types Schedule Policy
Comments
Storage Policies Incremental Storage Policy
Standard Storage Policies
Comments Incremental Storage Policy is supported
only for Log Only backups.
Subclient Policies Subclient Policy
Comments
User Administration and Security Backup Set/Archive Set
Instance
Subclient
Comments
Web Console Support Web Console Interface
Comments

1/31/2023 Commvault Systems Page 13 of 35

License Requirements - PostgreSQL Agent
For information about licensing, see the Commvault Licensing Program Guide .

1/31/2023 Commvault Systems Page 14 of 35

Deployment
For your computer's operating system, review each of the following topics to get started with the installation.

On Windows
Prepare the Installation on Windows Computers
Review general guidelines to prepare for the installation, which include configurations that your computer might need before the installation.
Preinstallation Checklist for the PostgreSQL Agent on Windows
Review agent specific guidelines to prepare for the installation, such as gathering the information that you must provide during the installation.
Installation Methods
Select the installation method that is most appropriate for your environment.

On UNIX
Prepare the Installation on UNIX, Linux, and Macintosh Computers
Review general guidelines to prepare for the installation, which include configurations that your computer might need before the installation.
Preinstallation Checklist for the PostgreSQL Agent on UNIX
Review agent specific guidelines to prepare for the installation, such as gathering the information that you must provide during the installation.
Installation Methods
Select the installation method that is most appropriate for your environment.

1/31/2023 Commvault Systems Page 15 of 35

Configuration
Once you install PostgreSQL iDataAgent, you need to create an instance in order to perform your first backup. This automatically creates the following default backup
sets, each with a default subclient:
DumpBasedBackupSet
FSBasedBackupSet

Before You Begin

If you have not done so already, configure a storage policy .

Procedure
1. From the CommCell Browser, navigate to Client Computers | <Client>.
2. Right-click PostgreSQL, point to All Tasks, and then click New PostgreSQL Instance.
The PostgreSQL Create Instance Dialog dialog box appears.
3. On the General tab, perform the following.
In the Instance Name box, type the name of the instance.
In the PostGres User Name box, type the user name to access the Postgres application.
In the PostGres Account Password box, type the Postgres User Account Password.
In the PostGres Confirm Password box, type the Postgres password to confirm the password.
In the Maintenance DB box, type the name of a system database which is used as Maintenance DB.
In the Binary Directory box, type the path to the Postgres application. Alternatively, click Browse to locate the path.
In the Lib Directory box, type the path to the library directory for the instance. For example, /opt/PostgreSQL/9.2/lib.
In the Archive Log Directory box:
On a UNIX client, type the path to the directory where you want to store the archive log files. For example, /opt/wal. Make sure that this path does
not point to pg_log or log directories and pg_xlog or pg_wal directories.
On a Windows client, type the path to the directory where you want to store the archive log files.
If Archive Log Directory is configured as a UNC path, set the value for bAllowUNCForPostgres to true. If you type a UNC path, click Change to
provide UNC user account credentials.
For instructions on adding the additional setting from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell
Console .

Notes:
Prior to performing the PostgreSQL backup, specify the Archive Log directory path in the postgresql.conf file.
From PostgreSQL 8.3 version onwards, use the following command to turn on the archive_mode. This feature is not supported for
PostgreSQL 8.2 and earlier versions.

archive_mode = on

For more information, see Configuring the Archive Log Directory .

In the Port box, type or select the port to open the communication between PostgreSQL Server and the clients.
In the Log Backup Storage Policy box, select a storage policy to be used for the transaction log backup jobs under Log Backup section.
4. Click OK.

Note: You can use LDAP to authenticate the PostgreSQL Server.

1/31/2023 Commvault Systems Page 16 of 35

Backup
What Gets Backed Up
Dump Based Backup
PostgreSQL system databases
PostgreSQL user databases

File System Based Backup

PostgreSQL databases (data and logs)
Log files

What Does Not Get Backed Up

The following component is not backed up if using DumpBased Backup Set
Roles and Tablespace locations because we use pg_dump utility for DumpBased backup operation. You can back up this information using FSBased backup set.

Use the File System Agent to back up the below mentioned components
PostgreSQL application files
Operating system data.

Note: If TDE or Always Encrypted are enabled, then the following rules apply:
Backups are not affected.
If you have a storage policy that uses deduplication, then the deduplication ratio is low or non-existent.
If the restore destination is a different client or instance, then the database administrator must back up the encryption key, and present it to the destination
instance.

Procedure
1. From the CommCell Browser, navigate to Client Computers |<Client> | PostgreSQL | <Instance> | DumpBasedBackupSet.
Right-click the default subclient and click Backup.

2. Click Full as backup type and then click Immediate.

3. Click OK.

1/31/2023 Commvault Systems Page 17 of 35

 4. You can track the progress of the job from the Job Controller window of the CommCell console.

5. Once the job is complete, view the job details from the Backup History. Right-click the Subclient and select Backup History.

6. Click OK.

1/31/2023 Commvault Systems Page 18 of 35

 7. You can view the following details about the job by right-clicking the job:
Items that failed during the job
Items that succeeded during the job
Details of the job
Events of the job
Log files of the job
Media associated with the job

1/31/2023 Commvault Systems Page 19 of 35

Restore
Restoring your backup data is crucial, therefore you should perform a restore operation immediately after your first full backup so that you understand the process.
Ensure that the following guidelines are met before you start the restore:
You need to stop the PostgreSQL server before performing the File System restore to recover the entire PostgreSQL server.
Make sure to delete or rename the wal and data directories.
Restore the File System backups of same version of PostgreSQL and not from higher to lower or lower to higher.
1. From the CommCell Browser, navigate to Client Computers| <Client> | PostgreSQL.
Right-click the <Instance>, and then click All Tasks | Restore PostgreSQL Server.
2. Select the destination server from the Destination Server list.
Click OK.
Note: If you do not want the PostgreSQL Server to start automatically after the restore operation is complete, clear the Recover Database Server check box.

3. You can monitor the progress of the restore job in the Job Controller.

4. Once the restore job has completed, right-click the agent or <Instance>, point to View and click Restore History.

1/31/2023 Commvault Systems Page 20 of 35

 5. Click OK.

6. You can view the following details about the job by right-clicking the job:
View Restore Items
You can view them as Successful, Failed, Skipped or All.
View Job Details
View Events of the restore job.
View and send Log files of the restore job
Resubmit the restore job

1/31/2023 Commvault Systems Page 21 of 35

 7. Once the database is restored, verify that the restored database and log files are available in the original location.

1/31/2023 Commvault Systems Page 22 of 35

Advanced Options

1/31/2023 Commvault Systems Page 23 of 35

Replication for PostgreSQL
The replication feature synchronizes the master PostgreSQL server to a standby PostgreSQL server by replicating logs from the backup of the master server to a
synced standby server. The replication operation continuously applies log files from the master database backups since the last sync point.

Note: Backup and restore operations for this feature can be performed from PostgreSQL and EnterpriseDB version 9.2 to version 11.

The replication feature performs the following procedures:

Initiates the replication automatically after a backup is completed on the master server.
Minimizes the impact on production systems CPU and I/O by using the backup data for replications. This method avoids the need to read the master server
again for replication.
Copies the backup data to remote disaster recovery (DR) sites with deduplication to minimize the wide area network (WAN) traffic. A replication operation then
runs at the DR site.
Supports the destination database sync in standby mode so that users can schedule workloads on the destination server.
Initiates replication after the auxiliary copy completes, when you use a copy precedence for replication operation.
You can use a replication schedule to initiate replication automatically after the backup operation completes on the master server. If no new backup operations have
run since the last replication, then the scheduled replication operation does not run.
Use the following backup types to replicate PostgreSQL databases:
Traditional backups
Auxiliary copies

1/31/2023 Commvault Systems Page 24 of 35

Back Up from Standby Server
Backup operations can affect the performance on the production server. In a healthy replication setup, standby server has data similar as the production server, at any
time. Commvault PostgreSQL standby backup operation can utilize the standby server for backup operations. This enables you to offload backup activity from the
production (master) server to its standby server. Jobs that you start on the master server are offloaded to be performed on a standby server. Backups are registered
to the master server.
If the replication is found to be broken at any point of time, the backup operations from such a standby server is not useful, as it will not include the latest data. In such a
case, backup operations can be run on the master server itself, until the standby server is repaired. This ensures a continuous backup activity.
The following are the key features of PostgreSQL standby server backup operation:
Offloading the backup operations on master server for improved performance.
Flexibility to utilize the production server for seamless backup activity in the event of a standby server failure.
We support backup operation from a standby server for regular and snap backup operations running on FSBased backup set. We do not support it for block level
backup operations.

Note:
Both the master server and the standby server should be Linux computers.
You can perform backup and restore operations from a single master-standby unit only. You cannot perform backup operation from multiple standby
servers.
Backup and restore operations for a standby server can be performed from PostgreSQL and EnterpriseDB version 9.2 to version 11. For versions 12 and later,
you can run a standby backup for a streaming replication setup.
License of the client whose instance is configured as a standby server in the CommCell Console can be safely released.

1/31/2023 Commvault Systems Page 25 of 35

PostgreSQL Block-Level Backup
Block-level backup analyzes the source volume and backs up the extents (groups of contiguous blocks) for supported databases.
For more information on block-level backup and its benefits, see Block-Level Backups .

Notes:
Block-level backups are supported only on Linux platforms. For more information, see the list of supported kernel versions below.
We do not support block-level backup if your data directory is present in the root volume.
Network File System (NFS) is not supported for PostgreSQL block-level backups.
Some agents and components require additional disk space, see Agents and Components Requiring Additional Disk Space .

 List of Supported Kernel Versions

The following are the requirements for running a block-level backup operation.

Operating Operating System Version Architecture

System
Linux CentOS
CentOS 8.4 with kernel 4.18.0-305 x64
Compatible
processors
CentOS 8.3 with kernel 4.18.0-240 x86
x64
Compatible
processors
CentOS 8.1 with kernel 4.18.0-147 x64
CentOS 8.0 with kernel 4.18.0-80 x64
CentOS 7.9 with kernel 3.10.0-1160 x64
CentOS 7.8 with kernel 3.10.0-1127 x64
CentOS 7.7 with kernel 3.10.0-1062 x64
CentOS 7.6 with kernel 3.10.0-957 x64
CentOS 7.5 with kernel 3.10.0-862 x64
CentOS 7.3 with kernel 3.10.0-514 x64
CentOS 6.5 with kernel 2.6.32-431 x64
Debian
Debian 10.x with kernel 4.19.0-9 x86
x64
Compatible
processors
Debian 10.x with kernel 4.19.0-8 x86
x64
Compatible
processors
Debian 10.x with kernel 4.19.0-6 x86
x64
Compatible
processors
1/31/2023 Commvault Systems Page 26 of 35
 Debian 9.x with kernel 4.9.0-6 x86
x64
Compatible
processors
Debian 8.x with kernel 3.16.0-5 x86
x64
Compatible
processors
Debian 8.x with kernel 3.16.0-4 x86
x64
Compatible
processors
Debian 7 with kernel 3.2.0-4-amd64 x86
x64
Compatible
processors
Oracle Linux
Oracle Linux 8.6 with kernel 5.4.17-2136.310.7.el8uek.x86_64 x64
Oracle Linux 8.5 with kernel 5.4.17-2136.302.6.1.el8uek.x86_64 x64
Oracle Linux 8.x with kernel 4.18.0.x x64
Oracle Linux 7.x with kernel 3.8.13.x x64
Oracle Linux 7.5 with kernel 4.1.12-124.14.2.el7uek.x86_64 x64
Oracle Linux 7.4 with kernel 4.1.12-112.14.1.el7uek.x86_64 x64
Oracle Linux 7.3 with kernel 4.1.12-61.1.18.el7uek.x86_64 x64
Oracle Linux 7.2 with kernel 3.8.13-98.7.1.el7uek.x86_64 x64
Oracle Linux 7.1 with kernel 3.8.13-55.1.6.el7uek.x86_64 x64
Oracle Linux 6.9 with kernel 4.1.12-61.1.28.el6uek.x86_64 x86
x64
Compatible
processors
Oracle Linux 6.8 with kernel 4.1.12-37.3.1.el6uek.x86_64 x86
x64
Compatible
processors
Oracle Linux 6.7 with kernel 3.8.13-68.3.4.el6uek.x86_64 x86
x64
Compatible
processors
Oracle Linux 6.6 with kernel 3.8.13-68.1.3.el6uek.x86_64 x86
x64
Compatible
processors
Oracle Linux 6.4 with kernel 2.6.39-400 x86
x64
1/31/2023 Commvault Systems Page 27 of 35
 Compatible
processors
Red Hat Enterprise Linux
RedHat Enterprise Linux 8.4 with kernel 4.18.0-305 x86
x64
Compatible
processors
Red Hat Enterprise Linux 8.3 with kernel 4.18.0-240 x86
x64
Compatible
processors
Red Hat Enterprise Linux 8.1 Advanced Platform with kernel 4.18.0-147 x64
Red Hat Enterprise Linux 8.0 Advanced Platform with kernel 4.18.0-80 x64
Red Hat Enterprise Linux 7.9 Advanced Platform with kernel 3.10.0-1160 x64
Red Hat Enterprise Linux 7.8 Advanced Platform with kernel 3.10.0-1127 x64
Red Hat Enterprise Linux 7.6 Advanced Platform with kernel 3.10.0-957 x64
Red Hat Enterprise Linux 7.5 Advanced Platform with kernel 3.10.0-862 x64
Red Hat Enterprise Linux 7.4 Advanced Platform with kernel 3.10.0-693 x64
Red Hat Enterprise Linux 7.3 Advanced Platform with kernel 3.10.0-514.10.2.el7 x64
Red Hat Enterprise Linux 7.1 Advanced Platform with kernel 3.10.0-229 x64
Red Hat Enterprise Linux 6.9 Advanced Platform with kernel 2.6.32-696 x64
Red Hat Enterprise Linux 6.7 Advanced Platform with kernel 2.6.32-573 x64
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71 x64
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-279 (Update x64
3)
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-220 (Update x64
2)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-92 (Update x64
2)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-308 (Update x64
8)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-274 (Update x64
7)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update x64
6)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-194 (Update x64
5)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update x64
4)
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-128 (Update x64
3)
SuSE Linux (SLES)
SuSE Linux 15 Enterprise Server with kernel 4.12.14-25.22 x86
x64
1/31/2023 Commvault Systems Compatible Page 28 of 35
 Compatible
processors
SuSE Linux 12 SP3 Enterprise Server with kernel 4.4.82-6.9 x86
x64
Compatible
processors
SuSE Linux 12 SP2 Enterprise Server with kernel 4.4.121-92.92 x86
x64
Compatible
processors
SuSE Linux 12 SP2 Enterprise Server with kernel 4.4.38-93 x86
x64
Compatible
processors
SuSE Linux 12 Enterprise Server with kernel 3.12.49-11-default (Update 1) x86
x64
Compatible
processors
SuSE Linux 11 SP4 Enterprise Server with kernel 3.0.101-63 x86
x64
Compatible
processors
SuSE Linux 11 SP2 Enterprise Server with kernel 3.0.13-0.27-default x86
x64
Compatible
processors
SuSE Linux 11 Enterprise Server with kernel 2.6.32.12-0.7-default x86
x64
Compatible
processors
SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.54.5 (Update 3) x86
x64
Compatible
processors
SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Update 2) x86
x64
Compatible
processors
SuSE Linux 10 Enterprise Server with kernel 2.6.16.46-0.12 (Update 1) x86
x64
Compatible
processors

Related Topics
Configuring a Subclient for PostgreSQL Database Block-Level Backups
Perform a Block-Level Backup for PostgreSQL Databases

1/31/2023 Commvault Systems Page 29 of 35

Restoring PostgreSQL Database Tables and Instances
System Requirements - PostgreSQL Agent

1/31/2023 Commvault Systems Page 30 of 35

Command Line
There are PostgreSQL Agent operations that can be performed using the command line interface (also referred to as CLI), for example, backup and restore operations.
You can also perform some other operations at the agent and subclient levels.

1/31/2023 Commvault Systems Page 31 of 35

Best Practices
Creating Subclients
As a best practice, it is recommended that you create separate subclients to back up data that undergo frequent changes.
For example, if the EXAMPLE and USERS dbspaces undergo frequent changes, you can create a separate subclient for each database.
Example:
User-defined subclient: Test1
Content: EXAMPLE
User-defined subclient: Test2
Content: USERS
Distributing the client data using subclients as recommended above, can help improve backup performance by organizing the workload on the client into logical
groupings.

Subclient Content
As a best practice, it is recommended that you add only a few small databases to each subclient and add larger databases into separate subclients. On a restart
condition, the system will back up all databases in the subclient from the beginning. For this reason, you would not want a large database that has completed its backup
successfully to be backed up again only because a smaller one has caused a restart to occur.

Managing transaction logs for File System based backup

We recommend you to schedule several log only backups between full backups.
If Archive Delete check box is not selected, the Commvault software does not prune the logs. Here, it is useful to have a method to clean up the archive log directory.
If the logs are not pruned from the archive log directory, all the logs will be backed up with full backups. If you do not want to back up the old cycle logs during a newer
full backup cycle, set the value of additional setting nDoNotBackupAllLogs to 1.

Better performance for dumpbased backup

To achieve better performance for dumpbased backups, enable Commvault compression. For more information, see Data Compression .

1/31/2023 Commvault Systems Page 32 of 35

Trademark Acknowledgment
Commvault, Commvault and logo, the "CV" logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified
Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, Quick Snap, QSnap, IntelliSnap, Recovery Director, CommServe,
CommCell, ROMS, Commvault Edge, Simpana OnePass, and CommValue are trademarks or registered trademarks of Commvault Systems, Inc. All other third party
brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners.
All specifications are subject to change without notice.
Products in Germany are not distributed using the "QNet" brand.

For more information about Commvault® software modules and solutions, and for up-to-date system requirements, please contact us: www.commvault.com •
888.746.3849 • get-info@commvault.com
Commvault Worldwide Headquarters
1 Commvault Way • Tinton Falls, NJ 07724 • Phone: 888.746.3849 • Fax: 732.870.4525
Commvault Regional Offices

United States • Europe • Middle East & Africa • Asia-Pacific • Latin America & Caribbean Canada • India • Oceania

1/31/2023 Commvault Systems Page 33 of 35

1/31/2023 Commvault Systems Page 34 of 35