Resolution:
Here are the recommendations.

#1 Do not use FT with BW if RVCM with ledger files is configured.. The reason being there would be locking issues with the ledger files in many sitautions. Please see one example below.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BW1 and BW2 are run in FT mode,

-- BW1 is running on box1, Active
-- BW2 is running on box2, Non-active

There is a network glitch, so that the heartbeat messages can not flow properly between BW1 and BW2. However, box1 is running, and BW1 is still running, therefore, the cmtransport in BW1 is accessing the CM ledger file. But due to the network glitch, the BW2 on box2 try to become
Active, but the cmtransport could have a problem, as the ledger is using by BW1.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

This is a general FT issue when RVCM with ledger files is used ( nothing to do with BW). And the recommendation we are giving is from the experience RV team had dealing with FT over a period of time.

#2 The solution would be :-

--Please note that storing the ledger files on a shared device is still OK. We are only talking about FT engines configured with RVCM & ledger files
---IF the engine has RVCM publishers then use Hawk to monitor the engine process and if it dies, start it on another box accessing the ledger from the shared network device
---IF the engine has RVCM subscribers then use "Distributed queue(DQ)" feature  which internally provides you FT. You have to change the RV/AE plugins to use DQ quality of service and deploy the RVCMQ process starter on multiple boxes.

What are recommendations if FT is used in BW withRVCM.