Dell DL4300 Appliance Users Guide - Page 132

About bare metal restore for Windows machines

Page 132 highlights

NOTE: To identify the recovery point, you can also specify a line number in the command instead of the recovery point ID number. In that case, use the agent/machine line number (from the lm output), followed by the recovery point line number and volume letter, followed by the path, such as, r [machine_line_item_number] [recovery_point_line_number] [volume_letter] [path]. In this command, [path] is the file descriptor for the actual volume. For example, if the lm output lists three agent machines, and you enter the lr command for number 2, and you want to roll back the 23 recovery point volume b to the volume that was mounted to the directory /mnt/data, the command is: r2 23 b /mnt/data. NOTE: It is possible to roll back to /, but only when performing a Bare Metal Restore while booted with a Live CD. For more information, see Performing A Bare Metal Restore For A Linux Machine. 7. When prompted to proceed, enter y for Yes. after the rollback proceeds, a series of messages appear that notify you of the status. 8. Upon a successful rollback, the aamount utility automatically mounts and reattach the kernel module to the rolled back volume if the target was previously protected and mounted. If not, mount the rollback volume to the local disk and then verify that the files are restored. For example, you can use the sudo mount command and then the ls command. CAUTION: Do not unmount a protected Linux volume manually. In the event that you need to manually unmount a protected Linux volume, you must execute the following command before unmounting the volume: bsctl -d [path to volume]. In this command, [path to volume] does not refer to the mount point of the volume but instead refers to the file descriptor of the volume; it must be in a form similar to: /dev/sda1. About bare metal restore for Windows machines Servers, when operating as expected, run and perform the tasks they are configured to do. When a catastrophic event occurs, rendering the server inoperable, immediate steps are needed to restore the server to its previous operating condition. The process typically entails reformatting the machine, reinstalling the operating system, recovering data through backups, and reinstalling software applications. AppAssure provides the ability to perform a bare metal restore (BMR) for your Windows machines whether the hardware is similar or dissimilar. This process encompasses creating a boot CD image, burning the image to disk, booting up the target server from disk, connecting to the recovery console instance, mapping volumes, initiating the recovery, and then monitoring the process. After the bare metal restore is complete, you can continue with the task of loading the operating system and the software applications on the restored server, followed by your unique settings and configuration. Other circumstances in which you may choose to perform a bare metal restore include hardware upgrade or server replacement. BMR functionality is also supported for your protected Linux machines using the command-line aamount utility. For more information, see Performing A Bare Metal Restore For A Linux Machine. Prerequisites for performing a bare metal restore for a Windows machine Before you can begin the process of performing a bare metal restore for a Windows machine, you must ensure that the following conditions and criteria exist: • Backups of the server and the functioning Core 132

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176

NOTE:
To identify the recovery point, you can also specify a line number in the command
instead of the recovery point ID number. In that case, use the agent/machine line number (from
the
lm
output), followed by the recovery point line number and volume letter, followed by the
path, such as,
r [machine_line_item_number] [recovery_point_line_number] [volume_letter]
[path]
. In this command, [path] is the file descriptor for the actual volume.
For example, if the
lm
output lists three agent machines, and you enter the
lr
command for
number 2, and you want to roll back the 23 recovery point volume b to the volume that was
mounted to the directory
/mnt/data
, the command is:
r2 23 b /mnt/data
.
NOTE:
It is possible to roll back to /, but only when performing a Bare Metal Restore while
booted with a Live CD. For more information, see
Performing A Bare Metal Restore For A Linux
Machine
.
7.
When prompted to proceed, enter
y
for Yes.
after the rollback proceeds, a series of messages appear that notify you of the status.
8.
Upon a successful rollback, the
aamount
utility automatically mounts and reattach the kernel
module to the rolled back volume if the target was previously protected and mounted. If not, mount
the rollback volume to the local disk and then verify that the files are restored.
For example, you can use the
sudo mount
command and then the
ls
command.
CAUTION: Do not unmount a protected Linux volume manually. In the event that you need
to manually unmount a protected Linux volume, you must execute the following command
before unmounting the volume:
bsctl -d [path to volume]
.
In this command, [path to volume] does not refer to the mount point of the volume but instead
refers to the file descriptor of the volume; it must be in a form similar to:
/dev/sda1
.
About bare metal restore for Windows machines
Servers, when operating as expected, run and perform the tasks they are configured to do. When a
catastrophic event occurs, rendering the server inoperable, immediate steps are needed to restore the
server to its previous operating condition. The process typically entails reformatting the machine,
reinstalling the operating system, recovering data through backups, and reinstalling software applications.
AppAssure provides the ability to perform a bare metal restore (BMR) for your Windows machines
whether the hardware is similar or dissimilar. This process encompasses creating a boot CD image,
burning the image to disk, booting up the target server from disk, connecting to the recovery console
instance, mapping volumes, initiating the recovery, and then monitoring the process. After the bare metal
restore is complete, you can continue with the task of loading the operating system and the software
applications on the restored server, followed by your unique settings and configuration.
Other circumstances in which you may choose to perform a bare metal restore include hardware
upgrade or server replacement.
BMR functionality is also supported for your protected Linux machines using the command-line
aamount
utility. For more information, see
Performing A Bare Metal Restore For A Linux Machine
.
Prerequisites for performing a bare metal restore for a Windows machine
Before you can begin the process of performing a bare metal restore for a Windows machine, you must
ensure that the following conditions and criteria exist:
Backups of the server and the functioning Core
132