Once the database has been repaired, it’s rinse and repeat, with a twist.
By this point you know how the repair works: export → autofix → review → validate → import. Well, its the same process for the rest with one additonal step.
Introducing CrossRef…
Chances are, that if a file used to be somewhere else, then it will likely be at that old location in your folders, playlists and histories. This is where /stage:crossref comes in handy. Before you run an Autofix or manually update, CrossRef will look at all the imported rows in the database worksheet and fill in the matches for your current repair, marked CrossRef and ready to validate.
These are rock solid fixes, because you’ve already fixed them in the database. This is why you need to keep every worksheet updated until all repairs are complete.
So from here on its export → crossref → autofix → review → validate → import. Taking (most of) the guess work out of the remaining repairs.
And that should complete your first complete repair.
But what happens if your first repair turns out to be the mother of all repairs. The final blog in this series look at handling those large repairs.