Moving from Novell Storage Manager to File System Factory
Update your NSM installation to the same version of FSF that you will be using. This will ensure full database compatibility.
If you want to, you can use the same proxy objects that you currently do for NSM. This will save you the trouble of having to set all new share permissions for the proxy rights group. This is especially the case for the NSMProxy object and the NSMProxyRights group. If you want to make a new group for your admin users, this will not require a lot of setup – just be sure you put the users you need in as members of your new group. If you would rather have differently named objects, you should rename them rather than create new ones – see optional step 3. This will save you the time of having to add all the share rights etc. that you have set up for the existing objects.
Allow events to process and have an empty pending event queue, or at least only have deferred delete pending events.
Steps for moving to FSF from NSM, but not moving engine or event services to new servers:
1. DeAuthorize all agents.
2. Stop the NSM engine and event services, and disable them.
3. (optional) If you want differently named proxy objects, now it the time to rename them. For example you may want to rename NSMProxy to FSFProxy and NSMProxyRights to FSFProxyRights.
4. Install FSF Engine.
5. Install FSFAdmin.
6. Run FSFAdmin to go through the setup wizard. (You will need your new FSF license for this step.) Use the existing proxy objects for the proxy user and the proxy rights group. For the admins group, you can use the existing group, or create a new one. Be sure to add any users you will have running the FSFAdmin tool added as members to this group.
7. Stop the engine service.
8. Copy with overwrite all the contents of /ProgramData/Novell/StorageManager/Engine/Data to /ProgramData/Condrey Corporation/File System Factory/engine/data, except two subdirectories: state and www.
9. Restart the engine service
10. Now install the FSFEvent monitor.
11. Run the event-config, point it at the engine, but DO NOT start the event service.
12. MOVE (don’t copy) the /ProgramData/Novell/Storage Manager/Event/data directory to /ProgramData/Condrey Corperation/File System Factory/Event/data directory. This will keep it from having to rebuild the entire partial replica again, which can be really time-consuming.
13. Start the event service.
14. Uninstall NSMAgents, and install FSFAgents where needed.
15. Authorize Agents and Event
16. You can uninstall NSMEngine and NSMEvent now as well.