User guide

156 | Protecting Workstations and Servers
7. When prompted to proceed, enter y for Yes.
Once the rollback proceeds, a series of messages will display to notify you of the
status.
8. Upon a successful rollback, the aamount utility will automatically mount and re-
attach the kernel module to the rolled back volume if the target was previously
protected and mounted. If not, you will need to mount the rollback volume to the
local disk and then should verify that the files are restored. (for example, you can
use the sudo mount command and then the ls command.)
Understanding Bare Metal Restore
Servers, when operating as expected, perform the tasks they are configured to do. It
is only when they fail that things change. When a catastrophic event occurs,
rendering a server inoperable, immediate steps are needed to restore the full
functionality of that machine.
AppAssure 5 provides the ability to perform a bare metal restore (BMR) for your
Windows or Linux machines. BMR is a process that restores the full software
configuration for a specific system. It uses the term “bare metal” because the restore
operation recovers not only the data from the server, but also reformats the hard
drive and reinstalls the operating system and all software applications. To perform a
BMR, you specify a recovery point from a protected machine, and roll back to the
designated physical or virtual machine. Other circumstances in which you may
choose to perform a bare metal restore include hardware upgrade or server
replacement.
Performing a BMR is possible for physical or virtual machines. As an added benefit,
AppAssure 5 allows you to perform a BMR whether the hardware is similar or
dissimilar. Performing a BMR on AppAssure 5 separates the operating system from a
specific platform, providing portability.
Note that you should not unmount a protected Linux volume by hand. In the event you need to
do this, 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 would need to be in a form similar to this
example:
/dev/sda1.
Windows 8, 8.1 and Windows Server 2012, 2012 R2 operating systems that are booted from FAT32
EFI partitions are not available for protection or recovery, nor are Resilient File System (ReFS)
volumes.
Bare metal restore of Storage Spaces disks configuration (a feature of Windows 8.1) is also not
supported in this release.
Only supported Linux operating systems are available for protection or recovery. This includes
Ubuntu, Red Hat Enterprise Linux, CentOS, and SUSE Linux Enterprise Server (SLES). For details, see
the AppAssure 5 Deployment Guide.