Importing legacy backup-to-disk folders with Backup Exec 2012
- 1. BE 2012 supports Exchange 2003 SP1. Do you know whether the source Exchange 2003 is SP1 2. Although this may not be the cause of your problem, what is the version of Exchange that you are trying to restore to? You would not be able to restore Exchange 2003 mailboxes to newer versions of Exchange
...it should be able too. The BE 2012 SCL should state this.
However, if you can't catalog the BE 10.1 data correctly, then this won't work anyway.
Do you have the option to load BE 12.5 on another server and restore using that instead?
Thanks!
Maybe this is happening due to the fact, GRT wasn't available in BE 10 and the indvidual mailboxes were backed up in a different manner (and separately) from the Information Store backup.
As well as:
Backup 10.x not providing GRT backups so Exchange was protected either with Brick Level or Information Store only backup jobs (or both for best practice) - this basically means no restore to PST or GRT to Exchange server possible and you may have to build an Exchange 2003 recovery server to restore for an Information Store backup (if you have one)
If you did do a brick level backup originally then you will have to use an older vsion of Backup Exec to do the restore (where version of BE will need to be the last to support Brick Level backups) as when we released BE 2012 we could not maintain the restore capability for older unsupported configurations and I suspect Brick level may well be caught by this limitation.
I also have a concern that:
The way you have imported the disk backup sets created on one sever into a completely different server might have caused a conflict of media naming and be confusing the catalogs. Basically for this kind of copy between servers you may need to copy to a media server that has never run any backups to disk so that then you avoid any media identity conflicts. As such if the server you had copied to is a production media server running other jobs this may be affecting you.
