Hi Manoj,
In this situation you have 2 main options:
1. You could create a database backup dump from the secondary site node and restore it to the primary node. If you choose to do this, make sure you put the secondary site node in maintenance mode first so that there are no additional changes to the database after taking the dump.
2. You could re-configure the cluster so that the secondary site node which has continued running is the new Primary Master node. Then you can turn the cluster back on to get the Secondary nodes data onto the restored Primary node. At this point you could either leave the cluster running with the new configuration or if you prefer you could re-configure the cluster back to its original configuration.
Documentation on DB Backups:
Configuration and Database Backups - CA Privileged Access Manager - 3.1.1 - CA Technologies Documentation
Regards,
Christian Lutz
Support Engineer
CA Technologies