If you are performing a Disk Delivery disaster recovery, Data Protector first tries to
connect to the original client where the backup device was attached (Media Agent
client) in order to use the same device for restore. However, when you are performing
Disk Delivery disaster recovery of the affected Media Agent client where the backup
has been made, Data Protector will not be able to connect to it and will proceed
with offline restore and search for a local device for the restore. If there is no local
device attached, Data Protector will issue a notification that there is no local device
attached and will abort the disaster recovery.
Action
There are tow methods to avoid this:
• Move the media to another pool. This way you assign the media to the new
device. Then proceed with Disk Delivery disaster recovery.
• The second method involves preparation prior to the disaster. If you have two
Media Agent clients in the cell, you can back up of the first Media Agent client
to another and vice versa before the disaster to avoid problems when performing
Disk Delivery disaster recovery of a Media Agent client.
Enhanced automated disaster recovery and one
button disaster recovery
Problem
Automatic DR information could not be collected
When using EADR or OBDR, it is possible that you will receive the following error:
Automatic DR information could not be collected. Aborting the
collecting of system recovery data
Action
• Check if all storage devices are configured correctly. If Device Manager reports
a device as “Unknown Device”, install the proper device drivers before you
can perform EADR/OBDR.
• There must be enough registry space available. It is recommended to set the
maximum registry size to at least twice that of the current registry size. If there is
not enough registry space available, a similar entry would appear in the
autodr.log:
ERROR registry 'Exception while saving registry'
Troubleshooting disaster recovery142
To Next Page
Loading...
Need help?
General