NDS Migrator Data Migration flow and Data Migration Performance Enhancing Tips
Below are some tips and information for NDS Migrator Data Migration flow and Data Migration Performance Enhancing.
There are five main points in a Data Migration using NDS Migrator, and they are:
1. NDS Migrator Console (s) or CopyEngine.exe. 2. SQL Server Location 3. Source Data Server (NDS Server) 4. Target Data Server (Windows 2000/2003, 2008,NAS, etc with NTFS) 5. NDS Tree
Data Migration flow for NDS Migrator is:
1. Data Migration Project is setup to run from a NDS Migrator Console or using the CopyEngine.exe with appropriate Source and Target Data Migration Servers and associated file Migration options.
2. The copy process starts. Files / Folders are copied using the CopyFileEx function called from where the Data Migration project is started. This flow can happen two ways:
A. Using the NDS Migrator Console. The Migration project is started at the console and then a request is sent to the Source NDS Server to start copying files. The Copy then moves the file from Source Server to the Console and then to the Target Server (NTFS file structure).
B. Using the NDS Migrator CopyEngine. The scheduled NDS Data Migration project is started the Computer specified during the CopyEngine configuration and then a request is sent to the Source NDS Server to start copying files. The Copy then moves the file from Source Server to the Console and then to the Target Server (NTFS file structure).
Source NDS Server > Migration Console OR Machine where CopyEngine is installed > Target Windows Server
3. During this copy and Data Migration flow, there is additional permission translation lookups and setting being preformed. These additional Steps are:
A. Source Data (File / Folder) is queried to get the Novell ID from the file System. B. NDS Tree is then queried to translate the File System ID to the "Plain Text" Object Name. C. NDS Migrator Database on SQL is then queried to translate the Novell Object to the AD Object based off the mappings. D. Once the AD Objects ID (SID) is known, then the permissions are set the on the Windows file system.
The main problem areas that are seen in regards to Data Migration speed is going to be these 5 in the order of most precedence:
1. Bandwidth - On a Production Network there is always traffic with a certain load, try to limit the Bandwidth used by other process during the Data Migration period using NDS Migrator. Suggest running Data Migrations during after hours (low bandwidth use hours) and ensure that your over the Network back-up schedule is taken into account.
2. Disk Reads - Generally the Source Server has lower spec and older hardware and the requests for Data coming from the Disks could be a bottleneck. Suggest monitoring the Source Server Disk reads for this condition.
3. LAN / WAN Configuration - Ideally the above 5 points of contact would be on the same Local Network (Subnet would even be best) and there would be no network issues at all. Suggest monitoring the network for a baseline, and to do a test on the Network by performing a Copy of a large set of Data from the Source server to the Target Server suing Windows Explorer from the Migration Console. This will simulate the raw copy of files and rough estimates for Data Migration timings can then be preformed.
4. Virus Detection scanning software. Some Virus scanning configurations can cause slowness due to checking every file and folder access which will slow down the copy process and security setting that needs to be performed. It is recommended that active virus scanning is disabled during the data migration and re-enabled post data migration.
5. Disk Writes - Least of our worries generally, as usually the New Hardware is more that capable of handling the requests to write information to the disks during a NDS Data Migration. Suggest monitoring with PERFMON or Spotlight on Windows to ensure that this is not a hindering facto in the Data Migration.