Consolidating Data To Or From A Netware 5.1 Cluster; Consolidating Data To Novell Branch Office - Novell SERVER CONSOLIDATION MIGRATION TOOLKIT 1.1 - ADMINISTRATION GUIDE 12-23-2005 Administration Manual

8 When you are ready to commit the changes, run the consolidation.
9 Upon completion, review both the success and error log files.
6.9 Consolidating Data to or from a NetWare 5.1
Cluster
When a volume is cluster enabled, an object is created in eDirectory with the name of the cluster
followed by an underscore followed by the volume name (for example, cluster1_vol1). For the
Server Consolidation Utility to function properly with a NetWare 5.1 cluster-enabled volume, the
server name followed by an underscore followed by the Volume Name object must be used in the
Project Window instead (for example, server1_vol1).
This substitution can be accomplished by completing the following steps:
1 Start ConsoleOne, and browse to the context where the NCP
2 Right-click the right pane, select New > Volume, then type the name of the new object in the
3 In the second field, browse and select the appropriate server.
4 In the third field, select the volume from the drop-down menu, then click OK.
5 In the Server Consolidation Utility Project Window, refresh the container where the Volume
6 When dragging-and-dropping in the project window, use the newly created Volume object.
7 After the consolidation is complete, you can delete the newly created Volume object.

6.10 Consolidating Data to Novell Branch Office

Novell Branch Office (formerly Nterprise Branch Office) server is a business office management
solution that reduces the costs and challenges of managing and using offices in remote locations.
Novell Branch Office is server software that you can deploy on hardware at remote offices and still
56 Novell Server Consolidation and Migration Toolkit Administration Guide
• If the source or destination location is incorrect, click Cancel and make the appropriate
changes in the Project Window.
At the end of the verification, the results dialog is displayed. To ensure a smooth migration, you
should resolve all errors before proceeding.
See Section 6.7, "Run the Consolidation," on page 53
The log file uses three possible states to identify the success of the migration fo each Printer
Agent:
• Success indicates that the Printer Agent was created on the destination server with all of
its attributes and drivers.
• Partial Success indicates the Printer Agent was created on the destination server but not all
of its attributes and drivers were included, so you should review its configuration.
• Failure indicates that the Printer Agent was not created on the destination server.
first field.
This should be the server name followed by an underscore followed by the volume name.
object is located to make the new object appear.
If you use the clustername_volumename object instead of creating and using the new Volume
object, a critical SMDR error will occur and you won't be able to complete the consolidation
process.
for more information.
Server object resides.
TM