Running Chkdsk on a Stand-alone server

What Are My Options

• 
  Run a Full Chkdsk
  This option repairs all file system data and restores all user data that can be recovered by means of an automated process. The drawback to this option is that a full Chkdsk can require several hours of downtime for a mission-critical server at an inopportune time. However, in terms of data recovery, this is the recommended course of action.
  
• 
  Run an Abbreviated Chkdsk
  By using some combination of the /c and /i command-line switches, you can repair the severe kinds of corruption that can grow into bigger problems in much less time than a full Chkdsk requires. However, this option does not repair all the corruption that might exist. A full Chkdsk is still required at some future time to guarantee that all the data that can be recovered will be recovered.
  
• 
  Do Nothing
  For a mission-critical server that is expected to be online 24 hours a day, this is frequently the necessary choice. The drawback to this option is that relatively minor corruption can grow into major corruption if it is not repaired as soon after it is detected as possible. Therefore, consider this option only when keeping a system up is more important that the integrity of the data that is stored on the corrupted volume. Keep in mind that all data on the corrupted volume is “at risk” until Chkdsk is run.
  
• 
  Format the Partition and Restore from Tape
  When Chkdsk is run against a volume, Chkdsk may not correctly recover 100 percent of the data if there is extreme corruption. If you have a high-speed tape backup solution and a known last-good backup, it may be just as fast or faster to reformat the partition and then restore the data from tape. This is a rare scenario. Use this option only in extreme situations with careful consideration.