Dell NetWorker 19.9 Administration Guide

PDF

Additional recovery options

You can specify non-default recovery options on the WinPE command line or in the Additional Options field in the NetWorker Bare Metal Recovery wizard.

The following table describes the additional recovery options that can be used with a Windows BMR operation.

Table 1. Additional recovery options
Entry	Result
`-D x` where `x` is a number from 1 to 9, with 9 providing the most troubleshoot information and 1 providing the least.	Additional troubleshoot information is in the Windows BMR log files.
`-v`	Additional information on the progress of the recovery displays in the wizard’s System Recovery Status window.
`-p`	By default, the Windows BMR recovery skips the formatting of non-critical disks. By using the `-p` option, any existing partitions are deleted and all disks are reformatted on the recovered computer to match the layout of the system image. However, by Microsoft specification, even if the `-p` option is selected, a non-critical volume is not reformatted if the disk signature has not changed since the backup. This option might be useful in situations where a system fails to recover because of disk mismatch errors. In this case, the `-p` option might resolve those errors. The recovery process does not recover non-critical volume data even if the volume is reformatted. Non-critical volumes can be recovered by using the NetWorker User program after the wizard has completed and the host has been restarted.
`recover -s <NetWorker server> -U -N "WINDOWS ROLES AND FEATURES\Cluster Database"`	When the restored data is meant to override the data on other nodes, it should be restored using the authoritative mode. Once this data is restored to one of the nodes, it is propagated to the other nodes and overwrites any newer data on those nodes. Perform Authoritative restore by using the command on the left. While the recovery is in progress, observe that the status of the groups changes from Online to Pending to Offline in the Failover Cluster Management application. Alternatively, check the Event Viewer, under Application and Services Logs > Failover Clustering > Operational on all nodes that the Cluster Service has stopped and restarted. Recover the shared drive data through winworkr on the cluster node with its current active node. Select source client as the virtual client, and destination client as the current active node.