Install using the same version you are running on the old server. (If you are moving from 32-bit to 64-bit, this is a different msi, but use the same package version.) If you are planning to update to a newer version of FSF, make the move first at the same version, and the do an in-place upgrade on the new server.
Use the same proxy objects that you currently do for FSF. This will save you the trouble of having to set all new share permissions for the proxy rights group.
Allow events to process and have an empty pending event queue, or at least only have deferred delete pending events.
Steps for moving to FSFEngine to a new server
- Start by running a runtime-config report. This will give you a record of your current state, where your event and agents are, and listing of all your policies. (You will need to reconfigure your agents to get them to communicate with the new engine server once the new engine is in place.)
- Stop the FSF engine service and disable it.
- Install the same version of FSF on the new server.
- Run FSFAdmin, pointing it at the new server. (You can install FSFAdmin on the new server as well, if you like.)
- Go through the setup wizard in FSFAdmin. Your existing license will work for this step. Use the existing objects for the proxy user and the proxy rights group, and for the FSFAdmins group.
- Stop the engine service on the new server.
- Copy with overwrite all the contents of C:\ProgramData\Condrey Corporation\File System Factory \Engine\data on the old server to C:\ProgramData\Condrey Corporation\File System Factory\Engine\data on the new server
- Restart the engine service.
- If the engine service does not start (or starts and stops), open a command promt window, and go to C:\Program Files\Condrey Corporation\File System Factory\engine and run “fsfengine-ad -–force-proxy-reset” and then try to start the engine service again.
- If you are not moving FSFEvent to a new server, run the FSFEvent-config utility on your server running event, and change the Engine address to point to the new server. (See separate procedure to move Event to a different server.)
11. Run FSFAgent-config on all agent servers to change the engine address to the new server.
12. Check in FSFAdmin to see that event and agents are heartbeating in correctly and show authorized.
13. Uninstall FSFEngine from the old server.