D-Link DNS-1250-04 Acronis Backup Software User Manual for DNS-1250-04 - Page 91

Bootability troubleshooting, About Windows loaders

Get D-Link DNS-1250-04 PDF manuals and user guides View all D-Link DNS-1250-04 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 91 highlights

Mass storage drivers to install anyway To access this option, select the Advanced view check box. If the target hardware has a specific mass storage controller such as RAID (especially NVIDIA RAID) or a fibre channel adapter, specify the appropriate drivers in the Drivers field. The drivers defined here will have priority. They will be installed, with appropriate warnings, even if the program finds a better driver. Use this option only if the automatic drivers search does not help to boot the system. 5.3.10 Bootability troubleshooting If a system was bootable at the time of backup, you expect that it will boot after recovery. However, the information the operating system stores and uses for booting up may become outdated during recovery, especially if you change volume sizes, locations or destination drives. Acronis Backup & Recovery Server OEM automatically updates Windows loaders after recovery. Other loaders might also be fixed, but there are cases when you have to re-activate the loaders. Below is a summary of typical situations that require additional user actions. Why a recovered operating system may be unbootable  The machine BIOS is configured to boot from another HDD. Solution: Configure the BIOS to boot from the HDD where the operating system resides.  The system was recovered on dissimilar hardware and the new hardware is incompatible with the most critical drivers included in the backup Solution for Windows: Recover the volume once again. When configuring recovery, opt for using Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.  Windows was recovered to a dynamic volume that cannot be bootable Solution: Recover Windows to a basic, simple or mirrored volume.  A system volume was recovered to a disk that does not have an MBR When you configure recovery of a system volume to a disk that does not have an MBR, the program prompts whether you want to recover the MBR along with the system volume. Opt for not recovering, only if you do not want the system to be bootable. Solution: Recover the volume once again along with the MBR of the corresponding disk.  The system loader points to the wrong volume This may happen when system or boot volumes are not recovered to their original location. Solution: Modification of the boot.ini or the boot\bcd files fixes this for Windows loaders. Acronis Backup & Recovery Server OEM does this automatically and so you are not likely to experience the problem. 5.3.10.1 About Windows loaders Windows NT/2000/XP/2003 A part of the loader resides in the partition boot sector, the rest is in the files ntldr, boot.ini, ntdetect.com, ntbootdd.sys. boot.ini is a text file that contains the loader configuration. Example:

  • 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
Mass storage drivers to install anyway
To access this option, select the
Advanced view
check box.
If the target hardware has a specific mass storage controller such as RAID (especially NVIDIA
RAID) or a fibre channel adapter, specify the appropriate drivers in the
Drivers
field.
The drivers defined here will have priority. They will be installed, with appropriate warnings,
even if the program finds a better driver.
Use this option only if the automatic drivers search does not help to boot the system.
5.3.10
Bootability troubleshooting
If a system was bootable at the time of backup, you expect that it will boot after recovery. However,
the information the operating system stores and uses for booting up may become outdated during
recovery, especially if you change volume sizes, locations or destination drives. Acronis Backup &
Recovery Server OEM automatically updates Windows loaders after recovery. Other loaders might
also be fixed, but there are cases when you have to re-activate the loaders.
Below is a summary of typical situations that require additional user actions.
Why a recovered operating system may be unbootable
The machine BIOS is configured to boot from another HDD.
Solution
: Configure the BIOS to boot from the HDD where the operating system resides.
The system was recovered on dissimilar hardware and the new hardware is incompatible with
the most critical drivers included in the backup
Solution for Windows
: Recover the volume once again. When configuring recovery, opt for
using Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.
Windows was recovered to a dynamic volume that cannot be bootable
Solution
: Recover Windows to a basic, simple or mirrored volume.
A
system volume was recovered to a disk that does not have an MBR
When you configure recovery of a system volume to a disk that does not have an MBR, the
program prompts whether you want to recover the MBR along with the system volume. Opt
for not recovering, only if you do not want the system to be bootable.
Solution
: Recover the volume once again along with the MBR of the corresponding disk.
The system loader points to the wrong volume
This may happen when system or boot volumes are not recovered to their original location.
Solution
:
Modification of the boot.ini or the boot\bcd files fixes this for Windows loaders. Acronis
Backup & Recovery Server OEM does this automatically and so you are not likely to
experience the problem.
5.3.10.1
About Windows loaders
Windows NT/2000/XP/2003
A part of the loader resides in the partition boot sector, the rest is in the files ntldr, boot.ini,
ntdetect.com, ntbootdd.sys. boot.ini is a text file that contains the loader configuration. Example: