Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

December 01, 1996 12:00 AM

How NT Protects Its Hives

Windows IT Pro
InstantDoc ID #2869
Rating: (0)

Windows NT has some built-in methods for protecting system hive files. First, in the NT system32\config directory, several files have no extension (the hive files) and an equal number have the same prefix and a . log extension. Open a .log file with Notepad, and you see garbage. What is it?

This "garbage" is Windows NT's way of protecting itself from failed updates to hive files. When a hive file is being changed (for example, when you edit the Registry), the . log files ensure an unfinished write operation does not corrupt the hive. Such corruption can occur when the system fails. Here's how the fault-tolerance process works:

  1. Changes to the hive are written to the hive's . log file with information about where in the hive the changes will occur, and these changes are flushed (i.e., immediately sent, not cached) to the disk.
  2. The system marks the hive file to signal that the file is in transition.
  3. NT enters the new data into the hive file.
  4. The hive file is marked to show that the change is complete.

If the system fails between steps 2 and 4, the information in the . log file is sufficient to restore the hive file to its previous condition. Thus, the . log file isn't a complete backup­it's a recovery tool in case of accidents.

. log files aren't the only fault-tolerance measure NT provides. The preceding procedure applies to all hive files except for system, which is required to boot the computer. For system, NT uses a . log file and, each time the system is booted, also backs up system to system.alt. You can't delete, move, or rename the system or system.alt files in system32\config. If the original system hive file is unavailable or doesn't work, NT can still boot the system. The .alt file becomes the system hive file, and a backup of it becomes system.alt.

NT's automatic fault-tolerance features work well most of the time. But when these protection measures can't help, (such as after reinstallation or when you make a change to the Registry that disables your system), you must rely on your own hive backups to restore system information.

Related Content:

ARTICLE TOOLS

Comments
  • nlouis4
    9 years ago
    Dec 18, 2003

    useful information, but specific recovery actions are not specified.

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.