Running the Server Consolidation Utility

The Server Consolidation Utility is a Windows program that is launched from the Start menu.

To launch the utility, click Start > Programs > Novell Server Consolidation Utility > Novell Server Consolidation Utility. Then complete the following tasks:

1. Create a Project File .
2. Select a Source and Destination Tree .
3. Select Volumes, Directories, and Printer Agents .
4. Perform Pre-Copy Verifications .
5. Resolve Errors .
6. Start the Consolidation .
7. Schedule a Consolidation Project .
8. Consolidate to or from a NetWare 5.1 Cluster .

The Server Consolidation Utility has a helpful interface that guides you through each step of the process.

Consolidation Issues

There are certain rules that you should be aware of when copying files or moving Printer Agents.

• Open files cannot be copied.

  There is one exception to this rule. NSS has a feature called File Copy on Write. This permits a file that is being changed to be accessed in the same state as it was in when it was last closed by all processes.

  This feature is enabled on an NSS volume either by using ConsoleOne^® or entering

  nss /filecopyonwrite=volname

  at the server console to change the volume attributes. For example, nss /filecopyonwrite=vol1 would enable File Copy on Write for the vol1: volume. The effect is immediate, but it affects only files that are currently closed and then opened later.

• If you run a Server Consolidation Utility project involving a NetWare^® cluster and the cluster fails over during the consolidation, the file copy will stop. The Server Consolidation Utility project must be run again.
• Printer Agents can be moved, print queues cannot.
• Printer Agents that are moved still use the same Print Broker.
• You can move Printer Agents back after initially moving them.
• Printer Agents can be consolidated only within the same tree. They cannot be moved between different trees.
• Print Services Managers must be operational.
• After moving Printer Agents from the source to the destination server, unload the source Print Services Manager so the migrated Printer Agents can establish a connection to the destination Print Services Manager.

  HINT:  After unloading the source Print Services Manager, send a test print job to the printer that was moved. This ensures that communication with the destination Print Services Manager is established. After that communication has been established, the source Print Services Manager can be brought back up.

• You might need to manually load or reload the appropriate tsa.nlm or smdr.nlm.