Topics | How To | Full System Restore | Related Topics
The general procedure for a full system restore is to refer to the hardware vendor's documentation to rebuild or replace the file server. While rebuilding or replacing the NAS file server, consider the issues that follow to successfully complete the full system restore process.
The difference between a normal restore and a full system restore is the severity of the problem. Normally, if data is lost or removed, it is recovered from the archives using the normal restore procedures. However, when a normal restore operation cannot correct a software and/or hardware corruption problem, some additional changes may be required. |
The following describes the issues that need to be resolved in order to recover data for a NAS NDMP file server after it has crashed.
If you are restoring data to the same NAS File Server, the configuration information will be the same as the original server. Otherwise, if restoring data to a new NAS File Server, a new NAS client needs to be configured.
Configuration information for a NAS File Server includes a fully qualified network name, login and password for the NDMP account, etc. If applicable, also consider the hardware and disk shelf configuration of the original server, storage capacity of shares and exports, tape drive type if connected to a library, etc.
Issue |
If Yes.... |
If No... |
Will data be restored to the original NAS File Server? |
|
|
|
||
Will the same host name be used for the NAS client to communicate with the NAS File Server? |
|
|
Will the same account (login/password) be used to access the NAS File Server? |
|
|
If you are restoring data to the same location (e.g., file system/mount path name), an in-place restore will be used to restore the data. Otherwise, if restoring data to a new location, an out-of-place restore is performed.
Issue |
If Yes.... |
If No... |
Will data be restored to the original location?* |
|
|
|
|
|
While rebuilding the file system/mount path name, consider these issues: |
|
* The file system/mount path names will be different for each vendor and are as follows:
Vendor |
File System/Mount Path Example |
Agami | |
BlueArc | |
DinoStor | |
EMC Celerra | |
Hitachi | |
Isilon | |
NetApp | |
OnStor | |
Pillar Data Systems |
* The file system/mount path names will be different for each vendor and are as follows:
** Some in-place restores use the original file system/mount path names and configuration while others use new file system/mount path names and configurations.
If you are restoring data to the same NAS client with the same direct-attached storage, changing the old access paths to new access paths is required. Otherwise, if restoring data to a NAS client other than the original, a new NAS client and new media needs to be configured; then the data from the backed-up data from the old drive pool needs to be migrated to the new drive pool.
Issue |
If Yes.... |
If No... |
Does the new NAS File Server have direct-attached storage? |
|
|
Is the NAS client an existing client? |
|
|
Will the new NAS File Server use the same direct-attached storage? |
|
|
|
|
If you are restoring data to the a NAS File Server with the same type of disk storage (e.g., magnetic library or index cache) attached, an in-place restore will be used to restore the data.
Issue |
If Yes.... |
If No... |
Does the new NAS File Server have the same type of disk storage attached? |
|
|