File Based Incremental Conversions fail with the error "An entry with the same key already exists"

  • 7921033
  • 06-Feb-2008
  • 27-Apr-2012

Environment

PlateSpin Migrate, Protect, and Forge 

Situation

This article discusses an issue which may occur when trying to perform a File-based incremental synchronization. When running a file based conversion the job will fail at "Source Machine Ready to Send Files" with the error "An entry with the same key already exists"

 

During a file based incremental conversion you may receive the above error when Microsoft Windows Services for UNIX or Subsystem for UNIX-based Application (SUA) is installed by using the "Change the default behavior to case sensitive" option. When this option is enabled, the installation creates a "pod" symbolic link under the same directory as the Pod directory. PlateSpin cannot identify case-sensitive file names on windows based systems.

 

 

On every volume on the source system, there is a file called PlateSpinCatalog.dat. Open this file using a text editor, and search for "SFU\usr\local\lib\perl5\5.6.1\Pod". You will find something similar to what is listed below.

 

SFU\usr\local\lib\perl5\5.6.1\Pod

SFU\usr\local\lib\perl5\5.6.1\pod

Resolution

 

1. Click Start on the source server, go to Programs, then Windows Services for UNIX, and then click C Shell.

2. Type the following command to delete the pod symbolic link rm /usr/local/lib/perl5/5.6.1/pod