SDR restore error - Memory could not be read
|Article:TECH199850|||||Created: 2012-11-16|||||Updated: 2012-11-19|||||Article URL http://www.symantec.com/docs/TECH199850|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
When trying to restore a physical machine using Backup Exec 2012 SDR, the SDR Recovery crashes when trying to connect to the Backup Exec Server.
The error given is from bedrwiz.exe and states:
The instruction at 0x011f1532 references memory at 0x00000000. The memory could not be read.
0x011f1532 - The memory could not be read
At least one SSP enabled backup job has at some point failed on the media server and that failed job leaves an invalid catalog reference behind that causes a problem to remote SDR and crashes BEDRWIZ.exe
When performing a remote SDR, the .DR files created during the backup are not used, instead Backup Exec looks in the catalogs on the media server and generates the required information. When a local SDR is performed, the .DR file is used along with the backup data to recover the system and the catalogs themselves are not used. Hence the workaround in the attached screen shots uses the local SDR process but maps a connection to a share on the remote media server to do it. (the share needs to be where the Disk Storage folder is located which should also have a copy of the correct .DR file)
See attached PDF for pictures and walkthrough
SDR: Bedrwiz crashes while trying to connect to the remote media server for performing remote recovery.
Article URL http://www.symantec.com/docs/TECH199850