Hello all, We are upgrading Essbase from 184.108.40.206 to 220.127.116.11. As a part of the migration as you all know one is supposed to copy the app directory over to the new server(target server). My question is does the source server have to be down when this app directory is getting copied over to the target server?On our dev server the copy took 12 hrs. So we are looking at ways to reduce the downtime on production. The essbase staging tool shuts off the source essbase server as a part of the migration and then one of the succeeding steps is to copy over the app directory. Now once the copy has been started can the essbase server be started(to reduce down time) while the copy is in progress or is it a must that the source must be down. Thanks for your suggestions.
I would say either keep Essbase down or have the apps in read only mode as you don't want locks on the files while trying to copy, alternatively if you have an issue with the time it copies to your target could you not do it in two stages copy the app directory local to its existing location which should be quick then copy the directory to the target, this way at least you can bring Essbase back up though you may get some hit on performance while copying the files.
Thanks for the suggestion John, I will take the two step approach. Just one more question though, So When you say "hit on performance while copying the files" does it imply that the source can be up and running when copying locally? Thanks again.
Ok, just understood what you were saying, copy the app directly locally( after shutting of essbase on source) . Once the local copy is complete, bring the application back up, and then copy the local copy to target( and it is during this copy that there could be an impact on performance).
Message was edited by: Teddd