I agree with Corey Wilson's comment on this.
Because of the GRT feature, we opted for the upgraded from 10d. What a disaster.
Instead of spending just one day to upgrade and test, it's been about a month and half now since the upgrade and troubleshooting. At time of this writing, I am *STILL* monitoring the situation with BE 11d.
11d have so many problems relating to data throughput and corruption in backup and restore.
1.) In a Weekly Full Backup, the job logs gets corrupted and cannot be displayed towards the end. How do we know whether the job was successful or not?
2.) Backup to Disk to a Storage Area Network on a dedicated and private IP is painstakingly slow and our network is on Gigalan. Ironically, backup to tape is fast, but I doubt it's integrity.
3.) When you modify an existing backup selection and then modify a backup job, the schedule is inadvertently rescheduled.
4.) When you backup just the MS Exchange Information Store, not everyone's mailbox show up in the restore when you drill down to a mailbox. You would have to use the legacy option to backup up the individual mailbox in order for restore to show the mailboxes. Then you wonder, what's the point in upgrading to 11d anyways??? It's a waste of money to upgrade.
All of these points are critical and merit the same priority. These are real world situation and Symantec should have done QA thoroughly on Backup Exec 11d before releasing it.
We're already thinking of returning the Backup Exec 11d and go back to Backup Exec 9 or 10d where it is more stable.