NDS Migrator fails to copy files during a migration, when the source NDS volume files have the same name as an existing 8.3 windows file name, on the Target. In this event, the file is shown as processed in NDS Migrator, but not copied. In the (log) statistics there is a difference between number of files copied and files processed.
As an example, the following discrepancy may be seen in the logs upon a new file migration where there are no current files on the target server:
337686 - [12:00:00:000] Total of 6618 files processed
337687 - [12:00:00:000] Total of 6614 files successfully copied
There is no mention (in the logs) why certain files were not copied.
A source file name conflicts with the 8.3 windows target file name during migration. Current logs will not show the conflict and the files seem to copy, but do not.
The attached 184.108.40.206.zip file will log the 8.3 conflict, so the missing files can be identified.
1. Close NDS Migrator
2. Rename C:\Program Files\Quest Software\NDS Migrator\NDSMigrator.exe to NDSMigrator.old (default location)
3. Download the 220.127.116.11.zip and extract the NDSMigrator.exe to the following location:
C:\Program Files\Quest Software\NDS Migrator\ (default location)
4. Launch NDS Migrator, attempt the migration, then view the new log. See below notes for new log entries.
The following has been added to the logs for 18.104.22.168 and will also appear in Quest NDS Migrator 4.2:
- New Debug level logging
<SourceFileName> skipped because timestamp and size are same as target
<SourceFileName> skipped because newer on target
<SourceFileName> skipped because target is read-only
- New Error level logging
<SourceFileName> skipped because failed to set read-only flag on target
<SourceFileName> matches DOS 8.3 short name of <TargetFileName>
Waiting for fix in Quest NDS Migrator 4.2