The server on which the NSM Engine in Active Directory is installed must have the Novell Client installed while the migration is being performed. After the migration is complete, the client can be removed. Additionally, the NSM Engine can delegate migration operations to NSM Agents for improved migration performance. If Agents are deployed as a part of a Novell Storage Manager installation, these Agents are individually used for migration if the Novell Client is installed on them. In order for an Agent to participate in a migration, the server that has the Agent installed must also have the Novell Client installed. This determination is made automatically within Novell Storage Manager as a part of Agent/Engine communications and no additional configuration is required in order to use this feature.
The Novell Client installed on the NSM Engine in Active Directory should be properly configured to use SLP (Service Location Protocol) for the Novell eDirectory that serves as the source of a data migration. For information on SLP configuration, see “Setting Client Properties” in the Novell Client 2 SP3 for Windows Administration Guide.
Before you proceed with a Cross-Empire Data Migration, perform the following tasks:
Log in with Administrative access to the Domain.
Install the Novell Storage Manager Engine on the Windows 2008 server.
See Installing the NSM Engine
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
Install the Novell Client with the NMAS installation default option on the NSM Engine server.
The Novell Client can be removed after you have completed your migrations.
Extend the Active Directory schema.
This is required only if you are migrating to a target share managed by a collaborative storage policy.
See Active Directory Schema
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
Install NSMAdmin.
See Installing NSMAdmin
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
(Optional) Install and authorize the Event Monitor.
The Event Monitor is not needed for a Cross-Empire Data Migration, but is needed for managing storage once your data has been migrated to the Microsoft network.
See Installing and Configuring the Event Monitor
and Authorizing the Event Monitor
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
Assign Full Control permission to the NSMProxyRights group for shares that you will be migrating data to on the target devices.
See Setting Rights and Privileges on Managed Storage
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
Install and authorize NSM Agents and configure Proxy Agents for all servers that will be target servers for Cross-Empire Data Migrations.
See Installing and Configuring the Agents
and Authorizing the Agents
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
(Conditional) If you plan to migrate data to a NAS device, make the NSMProxyRights group a member of the Local Administrators group on each NAS device.
See Setting Rights and Privileges on Managed Storage
in the Novell Storage Manager 4.1 for Active Directory Installation Guide.
Install the Novell Client and configure SLP on any NSM Agent servers that will be involved in a Cross-Empire Data Migration.
The Novell Clients can be removed after you have completed your migrations.
Create Novell Storage Manager policies for the migration of storage.
These policies are needed if the Cross-Empire Data Migrations will be driven by Novell Storage Manager for Active Directory policies, which we recommend for migrating user data.
For all objects in eDirectory that have rights assigned to the file system, create matching objects in Active Directory.
To migrate rights assigned to containers, you must create an equivalent Group object in Active Directory for each container object in eDirectory,.