Understanding the difference in expected space utilization between source and destination drives on Windows XP

A difference in expected space utilization and also file and folder counts between the source and destination drives can be caused by a number of things, including the Windows swap file, hibernation file, and other temporary and instance specific files.

Casper actually excludes the Windows swap file (pagefile.sys) and hibernation file (hiberfil.sys) as an optimization when cloning a drive on which Windows is running. The swap file is a temporary file used by Windows to manage virtual memory and is created on demand when needed. Likewise, the hibernation file is also a temporary file used by Windows to hibernate the computer and is created on demand when needed. Depending on the amount of RAM installed in the computer, both of these files can be extremely large. The size of a hibernation file is typically equal to the amount of RAM installed. The size of a swap file is typically much greater than the amount of RAM installed (2 or 3 times the size is not atypical).

In addition, Casper will exclude the GoBack history file if Symantec’s GoBack is in use, as well as certain files within the Windows System Volume Information and Prefetch folders when necessary. Primarily these files represent system restore points and data specific to the original disk configuration which should not be included. These files can represent a considerable amount of space – e.g., anywhere from several megabytes to many gigabytes.

Other observable differences may include possibly new or changed files in the logged-in user Temp folder and Windows temp folder. Depending on your system setup, services and utilities running under Windows may be changing, creating, and removing temporary or state files so it may be impossible to find an exact byte utilization match on an active system drive -- i.e. it's a moving target in that respect. When cloning a drive, Casper actually begins by taking a snapshot or "picture" of the drive and then clones the snapshot. This ensures a stable, point-in-time image of the drive is cloned.

If Casper has any trouble during the cloning process, it will log the problem as well as any affected files and/or directories in the Exceptions section of the Activity Report that is generated at the completion of the cloning process. Casper will also alert you to these exceptions at the completion of the Copy Drive wizard. To review a report generated by Casper, follow this procedure:
  1. Start Casper
  2. Click Explore
  3. Click the History button (or from the View menu, click Explorer Bar -> History)
  4. In the History bar, expand the folder representing the day in which the copy was performed
  5. Display the Activity Report created by the Copy Drive Wizard by clicking on its date/time. (This report will be entitled "Casper Activity Report".)
  • Windows XP

Add Feedback