06-24-2014 12:09 PM
When I load my Full backup tape from backup exec 12.5 It shows four information store
databases. with only the fourth db corrupted.
I get this error when trying to restore to Ahgserver2
"
How to troubleshoot "Unable to attach to one of the drives" or "unable to attach to a resource" when...
|
The original server name was ahgserver. the new server does not have exchange as I am trying to restore to disk in order to selectively
restore data.
06-24-2014 12:35 PM
Hi,
You need to duplicate to disk...you can't restore Exchange to a server that doesn't have it. Follow my article below on how to do this. Once done, you can selectively restore data into an Exchange server.
https://www-secure.symantec.com/connect/articles/restoring-exchange-or-individual-mailboxesitems-using-backup-exec-howto
While for BE 2010 the process is the same for BE 12.5.
Thanks!
06-25-2014 06:02 AM
Thanks. Only problem is when checking the credentials it is asking for a remote agent.
Why?
The backup to disk job is local.
I don't even know if i have the agent to install it.
How can I get around this?
06-25-2014 06:07 AM
...you cannot do a file-level type restore of Exchange. You either restore to an Exchange server (local or remote) or duplicate the Information Store to disk, and you'd then get the *.edb, *.stm and any log files used for the backup.
If the local server doesn't have Exchange, then you need to follow my article in order to duplicate the IS to disk first. Once on disk, you can then either restore to another Exchange server, or use something like Kernel for Exchange to pull the mails out of the *.edb flat file and into a personal folder.
Thanks!
06-25-2014 08:57 AM
Yes did all that. Now i'm getting. now I am getting media is write protected
when trying to restore. how? this is the hard disk
06-25-2014 01:39 PM
And now my credentials no longer work again
06-25-2014 02:59 PM
Make sure you are meeting all the requirements for backing up and restoring Exchange accordingly, depending on the version of Exchange you are currently using.
Try referring to the links below
http://www.symantec.com/docs/TECH184449