Hi Team,
As part of DR testing we want to see the historical data as well in Pulse. Please let us know the process how to replicate the prod data in DR. Server names between the Prod(2 monitor servers and 1 application server) and DR (2 monitor servers and 1 application server) environment is different.
Pulse can sync your metadata but with the exception of attribute values it doesn’t migrate data. I believe this is a conscious and considered design decision as cube data has the potential to be very large indeed and could significantly impact migration performance.
Most data is loaded from external source systems. The solution here is to execute the same load processes on the target system as what has been run on the source system.
If data is manual input or has been otherwise manipulated in the system post-loading then the easiest way to achieve this is to have standard utility processes to export and import data (bedrock.cube.data.export and bedrock.cube.data.import would already fulfil this purpose). All you need to do is export the needed data to CSV, then place the CSVs in a “migration_import” folder. The only missing piece of the puzzle which you still need (and will still need to write) is a wrapper process which will loop through the contents of the migration import folder and pass each file name to the data import utility process to load. If the wrapper process contains no parameters then it can be included in each migration package and automatically executed at the end of migration.