Bogus Backup Filename in Validation Log Entry

I've run into the following apparent bug in the log entries made by ATIH 2012 (build 6154) during backup validation. I've created my backup files (I do full backups only; each is to a file on an external hard drive) with a naming convention as follows: P19_FULL_@date@_@exec@. (The @exec@ is the task run number.)

The log entries associated with the filename during BACKUP are fine. For example, for a backup I made on April 3, the log contains the message: "The following backups have been successfully created: "E:\P19_FULL_2012-04-03_9.tib"".

However, if I then run a VALIDATION on the backup in question, the log entry is wrong. It should show the name of the backup file being verified. But instead of showing this, it shows a bogus backup name. The date portion of the filename (@date@) is replaced by the CURRENT date. And the task run number (@exec@) is replaced by a zero.

For example, in the case of the backup file mentioned above, I ran a validation on April 4. The log entry associated with the validation was as follows: "Validate Backup Archive Location: "E:\P19_FULL_2012-04-04_0.tib"".

I've created multiple backup configurations; all appear to exhibit this behavior during validation.

Thanks.