cms failover in portal using filesystem

[henderson_mk]

Hi,
We're having some issues with the supplied cms on portal 2.7.2. In a clustered environment with the cms configured to use the filesystem storage method the failover from one node to the other doesn't seem to work.

The behaviour observed is when the master node goes down, any content that had previously been uploaded is not available on the node that takes up the master role. Just the default content is available.
Is this how this is supposed to behave? If so, is there a way to make the master node transfer the contents of its cms to the node that is taking up the master role?

Using the db as storage for the cms seems to have correct behaviour, but is un-useable as it doesn't work correctly with oracle and concurrent uploads seem to break the cms.

Hope you can give some clarification.

[soshah]

You will need to use a shared file system like NFS in a clustered environment. Thats the only way the data stored on the file system will be in sync.

without the synchronization, on fail over when a new node takes over as master, it will just read data from its local file system which does not have any changes reflected

Using the db as storage for the cms seems to have correct behaviour, but is un-useable as it doesn't work correctly with oracle and concurrent uploads seem to break the cms.

This should not be the case. The cms is certified to work on oracle, so for this there can be several environmental factors at play such as. database version, database driver, network latency, transaction timeout, etc etc

Thanks