Hello, PAM actually has a Management Console, but from your description what you refer to as the management console seems to be just the PAM user interface (UI). Is that correct? The problem description and proposed action don't make much sense as is. Also, what is the "Log Reduction" procedure you are referring to? PAM is a closed appliance, you cannot delete files to reduce disk usage. Given that you have nodes with different disk size, I assume these are virtual appliances, in which case you would be able to increase the disk size. If a 2-node cluster goes out of sync, normally the only way to recover is to stop and start the cluster, assuming the cause of the problem was something temporary, and not a new condition that prevents communication between the two nodes now. Even in a situation where one node is rebooted and recovers, it would get the database from the other node, there would be no inconsistency afterwards. Mysql database replication protects against split-brain scenarios, where both nodes make changes independently, it is very unlikely that you would have to be concerned about losing information found on server 1 only. 2-node cluster are not recommended, see e.g. documentation page Primary Site Fault Tolerance.
In general this looks like something that a case should be opened for with PAM Support to investigate the cause of the problem.