11-10-2013 05:55 PM
11-10-2013 08:16 PM
This might be cosmetic as on the left it does show the correct date and time for the backup set selection. You could try performing a test redirected restore to confirm that you are able to restore the data. If this works you could open a support case and report the issue (cosmetic bug).
11-11-2013 01:08 AM
My guess is this is the same 'cosmetic' problem as this one documented for SQL Backup Sets
http://www.symantec.com/docs/TECH210678
For the time being please rely on the date of the set - the middle pane in your screenshot above and ignore the dates listed in the contents pane.
EDIT: My own test servers show the same issue so it is reproducible. The visible location of the problem is in a slightly different place than it is for the SQL issue, however I think it is the same problem and have internally updated the engineering escalation to make them aware of the AVVI effect.
11-11-2013 04:59 AM
11-11-2013 06:58 AM
My answer and the related TECH article are just indications that we are investigating an issue that appears to directly relate to the problem you have asked about. In no way however are we confirming any plans for a final fix as we are still investigating.
By all means log a support case to get confirmation that it is the same problem and to perhaps get more direct details on any plans for the problem.
Note:
When we confirm plans for fixes we use a different disclaimer in the foot of the TECH article.
11-11-2013 07:28 AM
not only related to VM, have the same problems with actual backup-sets of exchange 2007 (LTO6 & BE1012 & FullBackup).