Bare metal technology is used for disaster recovery of protected assets. Use the procedures in this chapter to set up bare metal protection and to recover failed assets. (To recover the Unitrends appliance itself, see Appliance Disaster Recovery.)
See the following topics:
• | Bare metal protection by asset operating system to determine which set up and recovery procedures to use for you asset. |
• | Considerations for testing bare metal recovery for general considerations on testing bare metal recovery. |
• | Bare metal protection and recovery of aliased assets for requirements needed to protect and recover aliased assets. |
Bare metal procedures vary depending on the asset operating system (OS). For some operating systems, you can run a hot bare metal backup while the asset is up and operational. For others, you must shut down the asset and run a cold bare metal backup.
Refer to the table below to determine which type of bare metal protection to use for your asset. The referenced sections provide details on implementing bare metal protection and bare metal recovery procedures.
Note: Bare metal for some older OSs is not supported in the current UI. For these assets, you must use the Legacy UI Instead. Links to the applicable sections in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface are given in the table below.
Asset operating system |
Bare metal procedures |
---|---|
AIX |
See Bare metal for AIX. |
Hyper-V hypervisor |
Protection is based on the operating system of the Hyper-V host. See the applicable procedure in this table. |
Hyper-V virtual machine protected with a Unitrends agent |
Protection is based on the operating system of the virtual machine. See the applicable procedure in this table. |
Linux |
|
Mac OS X |
|
VMware virtual machine protected with a Unitrends agent |
Protection is based on the VM operating system. See the applicable procedure in this table. |
Windows XP, 2003, and later versions listed in the Compatibility and Interoperability Matrix |
|
Windows 2000 |
|
XenServer virtual machine protected with a Unitrends agent |
Protection is based on the VM operating system. See the applicable procedure in this table. |
Xen virtual machine |
|
FreeBSD |
Legacy UI only. See Intel platforms bare metal disaster recovery in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
Novell Netware |
Legacy UI only. See Bare Metal for x86 Platforms in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
Novell OES |
Legacy UI only. See Bare Metal for x86 Platforms in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
SCO OpenServer |
Legacy UI only. See Bare Metal for x86 Platforms in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
UnixWare |
Legacy UI only. See Bare metal for UnixWare in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
Solaris (Intel) |
Legacy UI only. See Bare Metal for x86 Platforms in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
Solaris (SPARC) |
Legacy UI only. See Bare Metal for Solaris SPARC in the Administrator Guide for Recovery Series and Unitrends Backup - Legacy Interface. |
It is recommended that you perform test bare metal recovery procedures for each of your assets. Before performing a test recovery, see the table below for considerations.
Type |
Description |
||||||
---|---|---|---|---|---|---|---|
Network considerations |
Note: These considerations do not apply to Windows integrated bare metal recovery. See Considerations for performing a test unified bare metal recovery instead.) Consider the following before performing the test recovery:
If you edit an asset's hosts file entry, you must update the entry to the original value after the bare metal recovery test is complete. Standard backup and recovery procedures for the asset cannot occur until the entry is edited back. |
||||||
Active Directory considerations |
Assets that are dependent on Active Directory for day-to-day functions may not function properly when recovered to a test network if a domain controller is not recovered into the test network first. If you plan to recover a domain controller with bare metals, it is extremely critical to perform this recovery into a test network. |
In order to recover an asset that you are protecting with aliases, special considerations apply when running backups and performing bare metal recovery.
When protecting an asset that you have broken into multiple aliased assets, you must adhere to these requirements when running backups in order to perform bare metal recovery:
• | When you are backing up an aliased asset, you must decide whether to include or exclude the system state. You must include the system state in backups of only one aliased asset. |
• | Bare metal recovery fails if the system state is NOT included when protecting the OS and system critical volumes. Be sure to include the system state for the alias whose backups include these volumes. |
• | Bare metal recovery fails if the system state IS included when protecting only the non-critical volumes. Be sure to exclude the system state when protecting an aliased asset whose backups exclude the OS and system critical volumes. |
• | For more on aliasing, see Creating aliases for agent-based assets. |
To perform bare metal recovery of an aliased asset:
1 | First, recover the asset that contains the operating system and other critical volumes. You MUST do this before you recover any additional aliased assets. Follow the applicable procedure listed in Bare metal protection by asset operating system for details. |
2 | Next, recover each aliased asset (in any order). Follow the applicable procedure listed in Bare metal protection by asset operating system for details. |