The old IPM data is cleaned up at the very end of the data migration process. However, there appears to be a bug with this. The code is looking for something like /backups/0/ipm/IPMDB.db. However, I believe the actual structure is /backups/0/ipm/database/IPMDB.db. However, I have no idea how a copy of IPMDB.db could end up in /.
This sounds rather similar to my previous issue where restorebackup.pl was looking for ani.db in /backups/0/campus/database/, but wrapper.pl had it in /backups/0/cmf/ani.db, because of messed-up /opt/CSCOpx/backup/manifest/cmf/database/cmf.txt and /opt/CSCOpx/backup/manifest/campus/database/ani.txt.
Here's the source LMS(2.6)'s /opt/CSCOpx/backup/manifest/ipm/database/ipm.txt
"ipm.txt" 2 lines, 44 characters
This is right. A problem with the manifest file would also not explain how a copy winds up in /. But as I said, I believe there is a bug in which the old IPM database will not be cleaned up after migration.
No, and the more I look at the code, I don't think this fix is really needed. It certainly wouldn't clean up an IPMDB.db in /. Can you identify where exactly in the migration process this /IPMDB.db gets created?