warlord711, You have few options.
1. Setup and install ePO with new database at new cluster. Register each server and "transfer" your systems/policies/tasks everything.
2. Setup the vm, install same ePO version as physical. When you install, ePO will point to a blank database. But in sql, you can restore the sql database, and configure ePO to the new database. Be sure to use same dns name, ip address and everything for least disruption.
I prefer method 1 where you would need to have both up and running at the same time while you transfer everything seamlessly. THis is the graceful method. Method 2 requires good planning, be prepared to do some troubleshooting. This is the quick/dirty method.
Thanks Moe !
The scenario is that the old system gots ePO 5.1.0 and the customer wants to upgrade to 5.9.
Would you do scenario 1 with the new ePO at 5.9 or would you install 5.1.0 first, transfer systems/policies etc and do an upgrade afterwards ?
Hi there, so if you decided to do scenario 1, it is NOT necessary to install 5.1.0 on the new server. The new server can be 5.9.0. Here's a quick plan of action:
1. Install ePO 5.9.0 on new server
2. Register each other ePO servers (both 5.1.0 and 5.9.0). Exchange security keys.
3. You can now enable system/policy/task sharing and start the transfer process.
4. Monitor progress and continue the migration.
5. When everything (all systems, tasks, policies etc) has been transferred and clients are communicating successfully, you can focus on the new server.
DON'T turn off the old server just yet. Give it a little time to see if there's anything that's still trying to communicate to the old server. Or you may discover something... just leave it running for a little while.
This approach is a little lengthy but works well.