Migrating a custom non-hyrid cube into a hybrid enabled essbase
SummaryForward compatibility of non-hybrid EPBCS custom application
Client has a non-hybrid essbase in PROD. So, the custom EPBCS (does not use the modules) application in PROD is also non-hybrid. We will be taking an LCM backup of the application and upgrading the PROD environment to Hybrid essbase. After that, if by chance restoration of the application of TEST to PROD goes bad, would be able to import that old non-hybrid backup from PROD to the newly hybrid enabled environment in PROD? So, in other words checking the forward compatibility of the old hybrid app.