Leftover files after migartion

[gchampoux]

I just completed my first full migaration test from Intralink 3.4 M030 to Intralink 9.1 M060 (PreCopy).
The migration report indicated that all files were transferred (~350,000).

However, nearly 800 files were leftover in the precopy folders.
Prior to migration, I confirmed that there were no orphan files.

Should I be concered?

Gerry

[MikeFoster]

Hi Jerry,

Same here, 1,300 leftover out of 210,000 transferred. And our report also said all objects successfully migrated. No apparent ill effects in the almost two months we've been in production.

Mike Foster
ATK

[MikeLockwood]

Attached may be of interest. All laboriously collected from various logs.
Brings back memories...

[ShawnLothrop]

These files are probably 0 byte files or orphaned files. You can safe remove 0 byte and orphaned files from your PreCopy folder. You can run the orphaned file report from Intralink, <dataserver path=">\intralink\tools\bin\tclsh ilink_extra_object_report.bat, to generate a list of orphaned files.


-- Shawn

[kbrault1]

I have discovered that the Orphaned Files report does not include duplicated
files (Files or folders copied from one place to another via the OS). The
duplications get left being in the migration.

Look at your "fileMap..." file from WCMig and compare it to your "ALL
OBJECTS" report from 3.4. If they match then you are good.

Kevin