Skip to main content

Hello,

We are running commvault 11.28.52 and currently testing the PostgtreSQL Agent.

 

In our testing environment, we have two PostgreSQL 12 Servers running as a cluster with one Primary active server and one standby server. The servers are Linux-based VMs.

We are performing backups and restores from the primary server. However, every time we restore the DB from the FSBasedBackupSet, the replication between the nodes stops working.

 

What are the Best Practices for FsBased cluster restore and how to perform restore correctly from this backupset?

Hi Tony,

For restore from dumpbased, master should be destination instance (since write to standby does not work) and it will not break replication. 

 

Thank you very much!

Hi Tony,

For restore from dumpbased, master should be destination instance (since write to standby does not work) and it will not break replication. 

 

Hi Tony,

Till sp34, restore to single node is only supported. It will bring up the instance as a regular instance. Replication need to be established manually. Advantage is backup can be offloaded to standby client. 

 

From sp34, restore as cluster is supported. Please see these links for more details.

Creating PostgreSQL Cluster Client (Pseudo-client) (commvault.com)

FSBased In-place Restore Type (commvault.com)

 

 

Thank you for the resposne?

Does the restore from DumpBasedBackupSet also breaks replication?

Hi Tony,

Till sp34, restore to single node is only supported. It will bring up the instance as a regular instance. Replication need to be established manually. Advantage is backup can be offloaded to standby client. 

 

From sp34, restore as cluster is supported. Please see these links for more details.

Creating PostgreSQL Cluster Client (Pseudo-client) (commvault.com)

FSBased In-place Restore Type (commvault.com)

 

 

Reply


Terms & ConditionsCookie settings