Update: Also, can it be used to restore to a system with a different name and IP? I am suspecting not, as configuration files may refer to the system name?
Update 2: Just found in 5.1 product guide:
"Using the restored ePolicy Orchestrator SQL database server, that includes the Disaster Recovery
Snapshot, you can connect it to:
New McAfee ePO server hardware with a new server name and IP address — This allows you to, for
example, move your server from one domain to another.
This example can provide a temporary network management solution while you rebuild and reinstall
your McAfee ePO server hardware and software back to its original domain."
So from the look of it, we can restore to a new server with a new server name and new IP address, which is good - however could I confirm if this would also support changes to the install directory? What we are looking to do at a high level:
- Old server: Server1, 192.168.1.1. Local SQL Server. Everything resides in C:\
- New server: Server2, 192.168.1.2. Same version of ePO (vanilla build), but installed in D:\. Local SQL Server (same version as old server), but installed in D:\ with data in E:\
- Create DR snapshot from old ePO server
- Backup ePO DB and restore to new ePO server
- Restore from DR snapshot on new ePO server
- Update DNS entry for old ePO server name to point to new ePO server IP address (agents will connect to new ePO server, and pull down new sitelist containing new server name). 'Migration' can also be tested with pilot hosts by updating their local hosts file.
Would anybody see any immediate problems with this?