OK, this is how it works.
A catalog backup consists of x4 jobs
Parent
NBDB staging
Backup of NBDB staging area = backupid_1
Backup of /usr/openv/netbackup/db/images and other config files = backupid_2
Although there are two seperate backup jobs (which could be on different media) there is only one DR file/ email. The DR file will have the name of the catalog policy and the ctime of the last backup job, that being the backup of the ... db/images area.
There is no need to import catalog tapes for a recovery, the DR file acts as the 'catalog' - this is a mistake often made, though it makes no difference if you import the tapes, it won't cause any harm.
The basic steps are to make sure you have the correct DR file, the media is in the library and an inventory has been run (so on a blank system you have to configure the devices). The barcodes / media ID config rules should be such that they match the original system so that everything matches up. NBU versions need to be exactly the same, and install paths the same. It gets more complex if the NBDB location has been moved, but I'm presuming that hasn't happened here.
It should then just be a case of running the recovery wizard and specifing the location/ name of the DR file.
The image files referred to in the email are the two backups that I mentioned above. IF you look at the two ctimes, they are just 90 seconds apart, the one ending 212_FULL is the NBDB backup, the other ending 292_FULL is the /db/images backup.