Specifically, without using ASR, you can perform a Bare Metal Restore BMR to freshly formatted boot volumes and system volumes on the same server that the original backup was taken from. In this case, the volume layouts and identifiers are identical to those used during the backup of the original computer. Additionally, you can perform a BMR that uses ASR to a computer that has different hardware than the original computer. Note BMRs can be performed only when the system is offline.
You cannot mix the two in a BMR scenario. In this scenario, BMR is supported to different hardware. Server malfunction scenario bootable or roll back of server roles In this scenario, you can protect the server by performing a System State Backup or a BMR backup.
You would then recover the server by performing a System State Recovery from the started operating system. System State Recovery after a new installation of Windows Server or Windows Server R2 on new hardware or the same hardware This kind of recovery is not supported.
Windows Server Backup does not block recovery on a newly-installed operating system. Instead, it warns that this operation is not supported.
This feature is used only as a last-ditch support effort to reclaim data from a failed server and is not a supported backup feature.
System State Recovery is only supported on the same operating system instance. It is not supported on a reinstalled operating system on the same or different hardware. Follow the guidelines in the following sections to help make sure that the restore operation succeeds. There is one exception to this rule. For example, if the source computer has a single processor and is using the ACPI uniprocessor HAL, you can restore a backup from that computer to a multiprocessor destination computer.
To determine the computer HAL type that you are using on each computer, follow these steps:. On the Hardware tab, click Device Manager , and then expand the Computer branch. The source and destination computers must use identical operating system versions and identical Windows stock-keeping units SKUs.
For example, you can't back up Windows Server and then restore it on a computer that is running Windows Advanced Server. Also, the source and destination computers should both use retail versions of Windows or the same OEM version of Windows. The best practice is to install Windows on the destination computer by using the same installation media that you used to install Windows on the source computer.
Uninstall third-party filter drivers on the source computer before you perform the backup. These kinds of drivers can cause problems when the backup is restored to a different computer. For domain controllers, the locations of the Active Directory directory service database, Active Directory log files, FRS database, and FRS log files must also be identical for the source and destination computers.
If you remove any hardware on the destination computer that is not required to complete the restore process, you increase the probability of a successful restore operation. For example, physically remove or disable all except one network adapter. Install or enable the additional adapters after you restart the operating system after the restore operation.
For Windows computers, hotfix or Windows Service Pack 4 must be installed on the source computer before you back up data.
These items must also be installed on the destination computer before you restore the backup. Windows Server and Windows XP have no hotfix or service pack level requirements for this kind of restore operation.
A user does not have to bring the destination computer up to the same service pack and hotfix level for Windows Server or for Windows XP.
If you do not do this, you will receive the following error message:. For more information about the error message that you receive when you restore a Windows Server Service Pack 1-based backup on a Windows Server based computer, click the following article number to view the article in the Microsoft Knowledge Base:. For client and member server computers, follow these steps to back up the Windows Vista or Windows Server installation and restore it to a different computer.
Note A member server is any server that is not a domain controller. Note The following requirements must be met to move Windows Vista or Windows Server to a different computer. Startup hard disk capacity should be larger or the same size.
Even if it is smaller by a single byte, BMR will be blocked. You can make the backup on one kind of hard disk and recover on another kind of hard disk. You should make sure that your RAID setup on the destination computer does not interfere with the boot order of the hard disks. The operating system architecture and processor architecture must match. The three architectures, x86, x64, and IA, support the following scenarios:.
Backup of an x86 operating system version: This backup can be restored to an x86 processor computer or to an x64 processor computer. Backup of an x64 operating system version: This backup can be restored only to an x64 processor computer.
Additionally, the architecture of WinRE or the Setup CD should match the architecture of the operating system that is being recovered. For example, you would use an x86 version WinRE CD to restore an x86 operating system on an x86 computer. You can treat AMD or Intel processors as being the same if they follow the same architecture.
The backup of AMD x64 computer's operating system can be recovered on to an Intel x64 computer, or vice a versa. Recovery to Startup disk only: The recovery process will restore the backup to the first hard disk in the BIOS boot order.
You cannot change to another hard disk to restore the operating system. On the source computer, log on by using the administrator account, and then stop all noncritical services and services that you typically stop before you perform a backup.
This may include any service that puts locks on files. This includes antivirus, disk scanning, and indexing services. This value is located in the following registry subkey:. On the source computer, create a complete backup of the computer. Note If you back up the computer to a hard disk, you will have to either move that disk to the destination server, or you will have to share that hard disk over the network if it is possible to do so. In the Which file types do you want to backup window, select all the check boxes, and then click Next.
You must use an installation disc that contains Windows Vista Service Pack 1 because the release version of Windows Vista does not support this scenario.
Select the operating system that you want to repair. If you are restoring to a blank hard disk, no operating systems are listed. Restart the computer, and then verify that it is functioning correctly. You can use System State backup as a super-powered server version of the System Restore Point feature. System State covers most OS-critical files and configurations, which allows you to include additional folders in the same backup.
Try out MSP Backup to get even better flexibility. It allows you to create a System State backup in local or cloud storage, as well as implement bare metal recovery.
Blog Articles. CloudBerry Backup for Windows Server. Recommended for you Guide to System State Backup. Every week we deliver quality content about cloud storage, backups and security.
Leave your email to get weekly and monthly digests. Please specify your contact email. Please enter valid email address. Something wrong. Please try again. What Is System Restore Point? But there are a few peculiarities you should know about: System Restore Point is not a backup - this mechanism allows you to temporarily save a point-in-time Windows state. This state includes the system registry and crucial system folders necessary for proper work.
This feature, for example, will not help to recover deleted user files. If you have uninstalled some software and then decided to retrieve it - using System Restore Point is not the solution, since it may not contain all program files your software used.
Select a backup to perform system state recovery and click Next. All the available backups will be shown in bold, you can select one of them. Step 4. Step 6. Click Recover to start the recovery process. System state backup only contains boot files, active directory, cluster database, the registry and other system files, thus it will be useful if you just want to restore Windows Server R2 to previous date. But if your computer is unbootable, it will not work.
In this case, you can only use a full server backup to repair Windows Server R2. Note that this process requires a repair disk or installation disc and needs to be performed in the recovery environment. Moreover, it's also helpful when you want to restore Windows Server backup to different computer having dissimilar hardware.
All the steps are almost the same, and the only difference is that you need to restore system image in the recovery environment if the server computer is unbootable. Well then, follow the steps below and learn how to restore Windows Server R2 to previous date easily and quickly. Also, you can use the same steps to restore Windows Server R2 to previous date. Then, click Restore and Select Task to find the image file.
Select the backup image you want to restore and click Next.
0コメント