Hi Jonathan,
Thanks for getting back so quickly, I thought you might have some idea!
Exactly correct, once moved from the primary server the dbXXXX folders are not recreated, only the walarchive is propagating on primary. Only on the standby the dbXXXX are continually created.
Neither of the servers have a promote.dat within the db folder.
One thing I'm not sure of is whether the standby machine is successfully acting as the standby server, even though it seems to be reporting as so in portaladmin :
With both reporting as:
I am seeing the following error on the standby machine in the portal logs:
The pgsql.log list only the following:
And on closer inspection there are no postgres.exe services running on the standby which makes it seem it's not "recovered" properly.
I can see in the nodes.properties file in the shared HA configuration directory that the standby machine is not listed:
On the primary server I see this in the DB folder:
and on the standby in the DB folder:
I can see the postmaster files appear to be missing, and they are present in the database backup folders that get copied into the primary db folder.
I have tried replacing the primary db with the backup db from the primary server, but this doesn't resolve I'm afraid.
It seems the key would be to get postgres up and running on the standby server.
I'm guessing it will be something fairly simple as you've specified above related to deleting a status file in the configuration somewhere.
Probably an important point to note is that the now standby machine had its HDD filled due to the WAL archives, and similar things have happened where portal is unable to write or complete writing to a failover configuration file, so is possibly related to this.
Thanks,
Dean