Change the Barcode of Tape in DPM 2010 Puts on Suspect
A situation is not very common, but that has already happened to me in the past and yesterday again is the placement of the barcode label on a tape after this have already been used.
Note: This topic also applies to DPM 2007, but in this case it is necessary to change the instance name in the command.
After placing a new barcode or removing what already existed the tape appears in the list as "SUSPECT" and receive alerts of malfunctions in the tape drive.
When using a tape that does not have a barcode label DPM generates a number identifier in the tape, called OMID (on-media ID) and logs this in the SQL Server database.
To put or replace the label with the barcode DPM stays with the backup data is duplicate and understand that this is another tape, with the same backups. With this tape is as SUSPECT.
The most obvious is to put the barcodes before using the tapes.
However, if the above run the command below:
osql -E -S localhost\MSDPM2010 -d DPMDB -Q "UPDATE tbl_MM_ArchiveMedia SET IsSuspect = 0"
This command will execute a query in SQL Server reseting the flag "IsSuspect" of all tapes to false, which will generate another State in the DPM console that is "Imported".
After this, performs the complete inventory and DPM will retrieve the information from the tape, but the experiences that I will not be possible to do the restore since the references in the database that the console used was the OMID and not the barcode on occasion. The ideal here is to mark tapes as "free" and execute again the backups.