*********************************************************************
Copyright (c) 2010 StorageCraft Technology Corp. All rights reserved.  

File Name:   README.RTF
Last Update: July 2010

StorageCraft ShadowProtect Desktop Edition Ver. 4.0.1
StorageCraft ShadowProtect Server Edition Ver. 4.0.1
StorageCraft ShadowProtect Small Business Server Edition Ver. 4.0.1
StorageCraft ShadowProtect ImageManager Enterprise Ver. 4
*********************************************************************

GENERAL INFORMATION

This file contains additional information to supplement the manual.  Please read all the sections before you proceed with installation.

TABLE OF CONTENTS

1. System Requirements
2. Installing ShadowProtect
3. Activating ShadowProtect
4. General Usage Notes
5. Features/Enhancements
6. Resolved Issues

1. System Requirements

Minimum System Requirements

• Must meet the minimum operating system requirements
• Must have at least 256 MB of physical RAM (512 MB of RAM is required for the "Recommended" (Windows7-based WinPE) Recovery Environment.
• The VirtualBoot feature requires 1GB of available RAM (in addition to memory required by the OS and other applications).
• 32 MB of free hard disk space for installation files
• CD-ROM or DVD drive

Supported Operating Systems

ShadowProtect supports the following Windows 32-bit or 64-bit (x64, not Itanium) operating systems:

• Windows Server 2008 R2 (32-bit x86 and 64-bit x64)
• Windows Server 2008 (32-bit x86 and 64-bit x64)
• Windows Small Business Server 2008 (32-bit x86 and 64-bit x64)
• Windows EBS Server 2008 (32-bit x86 and 64-bit x64)
• Windows Server 2003 (32-bit x86 and 64-bit x64)
• Windows Small Business Server 2003 (32-bit x86 and 64-bit x64)
• Windows 2000 Server/Advanced Server (SP4 or above) (32-bit x86)
• Windows Small Business Server 2000 (32-bit x86)
• Windows 7 (32-bit x86 and 64-bit x64)
• Windows Vista Home Basic (32-bit x86 and 64-bit x64)
• Windows Vista Home Premium (32-bit x86 and 64-bit x64)
• Windows Vista Ultimate (32-bit x86 and 64-bit x64)
• Windows Vista Enterprise (32-bit x86 and 64-bit x64)
• Windows Vista Business (32-bit x86 and 64-bit x64)
• Windows XP Media Center (32-bit x86 and 64-bit x64)
• Windows XP Professional (SP2 or above) (32-bit x86 and 64-bit x64)
• Windows XP Home (SP2 or above) (32-bit x86 and 64-bit x64)
• Windows 2000 Professional (SP4 or above) (32-bit x86)

NOTE: The ShadowProtect Small Business Server Edition will only install on a Small Business Server (SBS) platform.

Supported File Systems/Disk/Volume Types

ShadowProtect Editions support the following File Systems: FAT16, FAT16X, FAT32, FAT32X, NTFS, MBR Disks, GPT Disks, Basic and Dynamic Volumes and Disks.

Supported Storage Media

ShadowProtect supports the following storage media: Disk drives including network drives, SAN, NAS, iSCSI, SCSI, USB or Firewire, Solid State Disks (SSD), and optical media such as CD/DVD/Blu-Ray.

2. Installing ShadowProtect

** You can install ShadowProtect 4.0.1 over an existing 3.x install.  You do not need to uninstall 3.x before installing 4.0.1. **

** If you have active maintenance on your existing 3.x install, then when you upgrade to 4.x you can simply activate your 4.x install using the Activate menu item and your existing 3.x product key.  If you do not have active maintenance with your 3.x product, and you upgrade from 3.x to 4.0.1, then you will need to activate (within 30 days) your 4.0.1 install using a 4.0.1 product key. **

** When upgrading from 3.x to 4.0.1, your job settings will be preserved. **

To upgrade from exiting 2.x versions. Perform the following steps:

• Record the details of each ShadowProtect job
• If you are under a maintenance contract then obtain your free 4.x license key from your reseller.
• Un-install ShadowProtect 2.x
• Reboot when prompted
• Install the new ShadowProtect release
• Reboot when prompted
• Activate new 4.x product License
• Recreate jobs as previous definition

Before you install ShadowProtect, make sure you have reviewed the system requirements for installing ShadowProtect.

To Install ShadowProtect

• Insert the ShadowProtect CD into the media drive of the computer.  If CD auto-run is enabled then the ShadowProtect installation page will launch automatically.
• If the CD auto-run is not enabled, browse the ShadowProtect CD.  Locate and run the ShadowProtect installation program named INSTALL_SHADOWPROTECT_SERVER_EDITION.CMD.  If you want to install the Small Business Editon, select INSTALL_SHADOWPROTECT_SBS_EDITION.CMD To install the desktop Edition select INSTALL_SHADOWPROTECT_DESKTOP_EDITION.CMD.  
• Click Next on the setup Installation Wizard welcome screen.
• ShadowProtect License Agreement.  You must accept the ShadowProtect License Agreement to install ShadowProtect.  Without accepting the ShadowProtect License Agreement you cannot proceed with the installation.  If you wish to print out the License Agreement, click Print.  If you accept the License Agreement, select the radio button indicating "I accept the license agreement."  Then click Next.  If you do not accept the ShadowProtect License Agreement, click Cancel to abort the installation.
• Select the type of setup.  If you select Complete all components will be installed.  Selecting Custom will allow you choose what components to install.  Click Next
• By default, ShadowProtect will be installed in: C:\Program Files\StorageCraft\ShadowProtect\.  You may change the installation location by clicking the Change button and browsing to the location you wish to install ShadowProtect.
• The installation summary dialog will appear.  If you need to make changes to the installation, click Back and make changes.  Click Install to begin the installation.
• A dialog box will appear indicating ShadowProtect installation is complete.  Click Finish.
• You will be prompted to restart your computer for the configuration changes to take effect.  Click Yes to restart your computer now.  Click No to restart your computer later.  **You must reboot your computer before you use ShadowProtect**
• Remove the ShadowProtect CD from the media drive.

3. Activating ShadowProtect

You will need to activate ShadowProtect before the trial period ends.  Each time you take a backup, the number of days left in your trial period will be displayed in the history.  To activate ShadowProtect click Help -> Product Registration.  You can optionally type in the Customer Name.  Type in the Serial Number, select the Automatic online activation and click the Activate button.  ** If you receive an error indicating that the StorageCraft Activation server  cannot communicate with our system and you access the internet through a firewall,  ensure that the SOAP (Simple Object Access Protocol) is not disabled by your firewall. **

Trial Version

If you are installing the Trial Version of ShadowProtect, you can install all the applications and create backup image files of system and data volumes.  You can also restore data volumes or specific files and folders. You will not be able to restore the system volume, because the StorageCraft Recovery Environment is not made available with the Trial Version. Your Trial Version will expire and cease to operate after the trial period.  However, you can purchase ShadowProtect at any time and upgrade your Trial Version to a Full Version without reinstalling the software.

Evaluation Version

If you are installing the Evaluation Version of ShadowProtect, you can install all the applications and create backup image files of system and data volumes.  You can also restore system volumes, data volumes or specific files and folders.  The Evaluation Version is made available on CD or as an .ISO image.  The StorageCraft Recovery Environment is made available with the Evaluation Version, enabling you to restore the system volumes as well enabling you to create backup image files from the Recovery Environment.

Your Evaluation Version will expire and cease to operate after the evaluation period.  However, you can purchase ShadowProtect at any time and turn your Evaluation Version into the Full Version. 

ShadowProtect Licensing

ShadowProtect licensing is based on the number of operating systems you are protecting using the software.  If you are using ShadowProtect to backup 100 computers, you will require 100 licenses.  Please review the End User License Agreement for further clarification.

4. General Usage Notes

ShadowProtect tracks sector changes when taking incremental backups.  Disable any disk defrag software you may have when incremental backups are taken or scheduled.  Since disk defrag software changes sectors, the incremental backup may be larger than expected especially if the disk is severely fragmented.

** To ensure successful implementation and testing please read the Knowledge base article "ShadowProtect Pre-Requisites Checklist.doc" ** 

Testing the StorageCraft Recovery Environment CD

You should test the StorageCraft Recovery Environment to ensure that it runs properly on your computer.  To do this, boot the StorageCraft Recovery Environment from the ShadowProtect CD.

If the StorageCraft Recovery Environment boots and runs as expected, then you will be prepared to perform ShadowProtect operations from the Recovery Environment in the event the system does not boot or you need to restore a system volume from a backup image file or you wish to create cold state backup images using the Recovery Environment.

If the StorageCraft Recovery Environment does not boot or run as expected, you should investigate the following issues:

• The system you are booting the recovery environment from must be configured to boot from the CD. 
• Try both the Recommended and Legacy boot options.  There are additional drivers in the Legacy boot mode. 
• You do not have the necessary network interface card (NIC) drivers to access the network.  Contact StorageCraft Technical Support by sending an email to support@storagecraft.com so that the necessary NIC drivers can be included in subsequent builds of ShadowProtect.
• You do not have the necessary storage drivers to access a storage device on the computer.  You may need to load storage drivers during boot time.  During the initial boot phase of the Legacy XP/2003 StorageCraft Recovery Environment, you will be prompted to hit F6 to add storage drivers.  You will then be prompted to load the storage driver from diskette.  It is a good idea to keep necessary storage drivers on a diskette that is available in the event you need to boot the ShadowProtect CD to run from the Recovery Environment.  The storage drives must be in the textsetup.oem format for loading into the Legacy Recovery Environment. If you have booted the Recommended boot option(Vista Recovery Environment), you can dynamically load the required storage drivers by providing the directory where the drivers are located.  The driver files for the Recommended Recovery Environment must be Vista drivers in the .inf and .sys format. Contact StorageCraft Technical Support by sending an email to support@storageCraft.com so that the necessary storage drivers can be included in subsequent builds of ShadowProtect.

The ShadowProtect CD, contains the StorageCraft Recovery Environment which is used as a boot disk for restoring a backup image to the system volume.  Be sure to store the CD in a safe place for use in the event that a bare metal recovery of your computer is required.

5. Features/Enhancements

For a complete list of changes, see also section 6 ("Issues Resolved")

ShadowProtect version 4.0.1 (July 2010)

• The Restore Wizard in the Recovery Environment has been enhanced to reduce confusion.
• Several enhancements have been made to VirtualBoot.  VirtualBoot now supports x86/x64 VirtualBox versions 3.1.0 - 3.2.6.  VirtualBoot will now prompt for an automated update of more compatible VirtualBoot plugin files (VBoxHDDXSP.dll, SBImageAPI.dll, and SBImageAPI.dll.conf) in cases where an older, or incompatible, plugin is found installed in the VirtualBox directory.  Such incompatibilities can occur when users upgrade from one supported version of VirtualBox to a newer supported version of VirtualBox (which perhaps requires a different version of these plugin files).  VirtualBoot now creates VMs which use VirtualBox-native .VDI files (written by VirtualBox itself) to store the VM's disk writes, rather than .SPWB files (which were not crash proof).  These .VDI files are much more crash resistant, and hence this reduces or eliminates situations where the VirtualBoot-created VM is unbootable after situations where the host has crashed or the VirtualBoot processes (VirtualBox.exe or VBoxSVC.exe) have crashed.  It is still recommended that users, who are using VirtualBoot for failover scenarios, continue incremental backups within the VM in order to protect any new data.  Also, now that VirtualBoot uses .VDI files to store the VM's disk writes, you will notice that when you power off the VM, VirtualBox gives you the option to "Restore current snapshot to 'VirtualBoot'."  YOU SHOULD *NOT* CHECK THIS BOX!  Checking this box will cause the VM to discard all writes made within the VM since its creation.  If you do intend to revert the VM back to its creation state, then it's okay to check this box.
• The product help links now refer to online help.  For those who wish to have local help, it is still available, and is found on the Recovery Environment CD.

ShadowProtect version 4.0.0 (April 2010)

• HeadStart Restore (HSR) capability has been added to the ShadowProtect Recovery Environment.  HSR makes it possible to begin restoring a backup image chain while new incrementals are still being created on that same backup image file chain.  HSR can apply new incrementals which were *created after* the HSR operation itself was initiated.  HSR in the Recovery Environment supports target volumes with a drive letter.  HSR can recommence where it left off after an interruption.
• There are now two flavors of ImageManager: ImageManager Standard, and ImageManager Enterprise.  ImageManager Standard is included at no additional cost as part of ShadowProtect Desktop/Server/SBS Editions.  ImageManager Enterprise is classified as a new product, with features not found in ImageManager Standard.  Common to these two flavors is a completely new interface, support for managed folders on SMB shares without the need to alter the ImageManager service credentials, policy-based consolidation/collapse of image files, and policy-based periodic reverification of image file data and file dependencies.  Standard ImageManager has the ability to replicate backup image files to local targets.  ImageManager Enterprise supports both local and remote policy-based backup image file replication.  ImageManager Enterprise also supports policy-based HeadStart Restore (HSR), with .VMDK or .VHD target types. 
• The ShadowProtect console interface now includes a management tab in which groups of multiple agents can be managed (and states viewed) simultaneously, within a single view.  This feature also supports silent push installation of the ShadowProtect product to target hosts.
• The ShadowProtect console installation now includes VirtualBoot, a feature which makes it possible to directly boot a ShadowProtect backup image within a Sun VirtualBox VM without the need to restore the image file and without the need to convert the backup image to another file format.  VirtualBoot supports data volumes larger than 2TB in size, and the ShadowProtect backups within the VM can continue generating fast incrementals on the same image file chain, protecting any new data created within the VM.  The combination of HeadStart Restore (HSR) and VirtualBoot make it possible to reduce the downtime windows for failover/failback/upgrade/migration/restore to a few *minutes* rather than *days* when dealing with terabytes of data.
• The Backup Image Tool wizard now supports conversion of ShadowProtect backup image files into .VMDK or .VHD virtual machine disk files.
• The Boot Configuration Tool within the Recovery Environment has been enhanced.  It now supports the assignment of the permanent drive letters which are assigned to any volume for a given operating system.
• Interrupted restore operations can new recommence where they left off.  This applies to regular restore operations, as well as to the enhanced HeadStart Restore operations.

ShadowProtect version 3.5.2 (March 2010)

• The are no enhancements for this release.  See the "Issues Resolved" section below for a description of the various bug fixes in 3.5.2.

ShadowProtect version 3.5.1 (December 2009)

• The are no enhancements for this release.  See the "Issues Resolved" section below for a description of the various bug fixes in 3.5.1.

ShadowProtect version 3.5

• The ShadowProtect tray icon now emits balloon notification messages whenever a task (backup, restore, etc) has completed.  The notification ballon messages are only displayed if the main ShadowProtect window is minimized or if it's not in the foreground or if the selected view isn't Backup Jobs or Backup History.  The notification ballon messages include the task status and source and destination.  Clicking on the notification balloon message makes the main ShadowProtect window active and switches the view to Backup History and opens the corresponding task's detailed log.
• The email notification feature now supports additional authentication methods (Plain, AUTH Login, Cram MD5 and NTLM), as well as SSL with any of these methods (which means you can configure notifications with services such as Google Mail - for Gmail use server smtp.gmail.com, port 465, use SSL, use either Plain or Login authentication, and enter your gmail email SMTP account name (minus the @gmail.com), address (with the @gmail.com), and password).  Users can also specify if they want to append custom text to the email subject (such as a company name in cases where you manage services for clients from many companies) and pre-pended to the body of the email.  The Agent Options dialog now has a "Test Email" button.
• A new Agent Option has been added which enables users to specify, in seconds, am amount of time they want the ShadowProtect Agent (which is the ShadowProtectSvc.exe NT service) to wait before beginning a backup after the service has started.  The intent of this feature is to make it possible for users to prevent backups from beginning immediately after their machine has booted.
• A new Agent Option has been added which enables users to specify the names of VSS writers which should be excluded from VSS-based backups.  The effect of this is that the specified writers will not be quiesced by VSS.  Their data will still be backed up, but it will be captured in an in-use state rather than a quiesced state.  One use for this would be to exclude a non-essential writer from the VSS process, particularly spit writers, thereby reducing the size of the image file.  Essential VSS Writers (such as SQL, Exchange, IIS, NTDS) should, generally, not be excluded.
• A new option to ignore read failures (and continue the backup) now exists in the backup job wizard.  Users whose drives are failing (where the hardware fails to return read requests) can now back up their data.  Backup image files will contain zeroes for those sectors which could not be read.  This option is off, by default, which means that if a backup fails to read, the backup itself will fail.  The intent is that you configure email notification and are notified when your hardware begins to fail.  You then intercede and change this setting (edit your job - check the "ignore read failures" box) and take a backup.  The backup will then succeed.  And, this would be a good time to buy a new hard drive.  If you want to override this and always enable backups despite read failures, then simply create a system environment variable named SP_SBVOL_IGNORE_READ_ERRORS with any value (such as 1) and restart the ShadowProtect Service.
• On successful backup, if the user has specified a post-backup command containing the text $SPFILES then this text $SPFILES will be substitued with the text of the full paths to each of the new backup files created by the backup job, delimited with the | character.  If you use this option, then it is highly recommended that you always enclose this text in quotes "$SPFILES" when you enter it in the post-backup command's edit box.  This text substitution makes it possible for you to pass the list of new image files as a parameter to the command you wish to execute.  Search the StorageCraft forums for posts with the tag PostBackupVerify for a sample script that you can use to verify (and email on failure) any newly-created backups.
• The Boot Configuration tool in the bootable-CD ShadowProtect Recovery Environment has been extended.  This is an advanced tool and generally is only necessary for very complex multi-boot systems.
• The Hardware Independent Restore (HIR) functionality in the bootable-CD ShadowProtect Recovery Environment now has an additional Advanced Option which enables users to add specific .INF files to the list of additional directories and files to be considered by HIR when it attempts to find the best drivers for the hardware.  The old option, to add directories, still exists.  When a directory is added to the HIR Advanced Options list, drivers in that directory will be considered by HIR.  However, if HIR finds another driver (on the target volume itself, for instance) which is a better match for the hardware, then HIR will install the best matching driver.  However, when a specific file is added to the list, it will be given precedence over all other matching drivers found by HIR.  This will make it easier for users, who are certain they have the correct storage miniport driver, to force HIR to install their specific storage driver.  Just point to its specific INF file.
• The Hardware Independent Restore (HIR) functionality in the bootable-CD ShadowProtect Recovery Environment now has an additional Advanced Option which enables users to specify if they want the target volume's Windows Activation to be Deactivated.  It has been found that occasionally after an HIR restore, the user will boot and login and immediately be logged back out, without any prompt or opportunity to reactivate their Windows installation.  By checking this Deactivate box, users in such a situation will be prompted to re-activate their Windows installation.

ShadowProtect version 3.4

• Added ability to import and export nodes in the network view.
• Added ability to generate an MD5 file to allow external file verification.
• Added a new scripting interface for creating/modifying backup jobs.
• Added support for the Portuguese language
• ImageManager has been updated to auto verify and periodically re-verify image files.  This is an ImageManager only component.
• A new tool (ISOTool.exe) which can burn CD-R discs using a source .ISO file is now installed as part of the product.  Although there are no shortcuts to this too, you can simply browse to the ShadowProtect program files directory and execute it directly.  This tool can be used to burn the downloaded ShadowProtect Recovery Environment CD .ISO file to a CD-R disc, thereby creating the bootable recovery CD.

ShadowProtect version 3.3

• Shrink volume (for restoring to smaller volumes)
• Support for additional languages (Supported languages are English,French,German and Japanese)
• ShadowProtect’s recommended recovery environment is now based on Vista SP1

ShadowProtect version 3.2

• 64-bit support
• Enhanced retention policy for removable drives

6. Issues Resolved

For a complete list of changes, see also section 5 ("Features/Enhancements")

ShadowProtect version 4.0.1 (July 2010)

• Resolved a rare crash of the ShadowProtect interface/GUI (ShadowProtect.exe) on startup
• Resolved an issue with the calculated time remining value in the Legacy Recovery Environment
• Fixed the search functionality within the ShadowProtect help
• Fixed an issue where the ShadowProtect backup job email notification showed the same time for both the job start and job end times
• Resolved an issue with VirtualBoot incompatibilities with VirtualBox 3.1.8 and 3.2.0.  The VirtualBoot feature in ShadowProtect 4.0.1 is now compatible with VirtualBox versions 3.1.0, 3.1.2, 3.1.4, 3.1.6, 3.1.8, 3.2.0, 3.2.4, and 3.2.6.
• In ImageManager Enterprise, fixed an issue with activation on OEM versions of Windows
• In ImageManager Standard/Enterprise, resolved and issue where a finalized VHD HeadStart Restore job would not boot
• In ImageManager Standard/Enterprise, resolved and issue where a cancelled HeadStart Restore jobs would show error status
• In ImageManager Standard/Enterprise, resolved an issue where the last applied point-in-time for HeadStart Restore jobs displayed incorrectly
• In ImageManager Standard/Enterprise, trying to finalize a HeadStart Restore job before the base image file has been applied displayed an error message.  It will now display the finalize dialog.
• In ImageManager Standard/Enterprise, file create/delete notifications were occasionally processed for the wrong directory.  This would cause error messages to be logged for nonexistent files.
• In ImageManager Standard/Enterprise, replication status messages were not always updated correctly, such as FTP replication would sometimes show 100% from the time the send began.
• In ImageManager Enterprise, Trial Expired message would display if a user did not have a license and tried a licensed feature.
• In ImageManager Standard/Enterprise, Machine Name was not displayed for image chains whose base was created by ShadowProtect 3.2 or earlier.
• In ImageManager Standard/Enterprise, chains that had not collapsed for over a month would create the -cd and -cm files but not the -cw files prior to the last -cm file.
• In ImageManager Standard/Enterprise, replication will check for files to be sent every time a new file is verified instead of only when files to be sent are verified.  This came about because when only sending collapse files, if a transfer was interrupted it would not retry until the next collapse file was verified, usually a day later.
• In ImageManager Standard/Enterprise, using local replication and swapping the destination drive required the ImageManager service to be restarted to recognize the drive had changed.  Instead of restarting the service, disabling (stop button) and re-enabling (start button) on the Replication tab will re-sync ImageManager with the contents of the new drive.
• In ImageManager Standard/Enterprise, installing an upgrade to ImageManager 4.0 will now retain the previous ImageManager.mdb file to avoid forcing a reverify of all files.
• In ImageManager Standard/Enterprise, fixed HeadStart Restore Job Settings form to roll back changes when creating a new job fails
• In ImageManager Standard/Enterprise, fixed empty agent status bar that sometimes appears on startup
• In ImageManager Standard/Enterprise, fixed licensing issues
• In ImageManager Standard/Enterprise, removed Infragistics DLLs
• In ImageManager Standard/Enterprise, change login page to force password change on first login
• In ImageManager Standard/Enterprise, added password hint to login page
• In ImageManager Standard/Enterprise, fixed HeadStart Restore Finalize dialog to hide ‘Restore latest’ option when no points in time are available
• In ImageManager Standard/Enterprise, changed HeadStart Restore to allow finalizing a job with one unfinalized target and one failed target
• In ImageManager Standard/Enterprise, fixed auto-login to save correct password when password is changed
• In ImageManager Standard/Enterprise, changed client to compare interface versions instead of product versions
• In ImageManager Standard/Enterprise, fixed HeadStart Restore to correctly display deleted images
• In ImageManager Standard/Enterprise, fixed pie chart to handle inconsistent used space sometimes reported by NAS devices
• In ImageManager Standard/Enterprise, updated Technical Support hyperlink on About pages
• In ImageManager Standard/Enterprise, fixed taskbar icon so it always appears
• In ImageManager Standard/Enterprise, updated help file
• In ImageManager Standard/Enterprise, disabled publisher evidence generation to resolve client UI startup hang on some machines
• In ImageManager Standard/Enterprise, added client configuration setting to auto-connect to localhost when run the first time

ShadowProtect version 4.0.0 (April 2010)

• A fix has been made to eliminate some harmless (yet confusing) event log errors (NTFS Warning 57, and NTFS Error 137).

ShadowProtect version 3.5.2 (March 2010)

• A workaround has been added to resolve a system-induced blue screen (BSOD) which occurred on Windows Server 2008R2 with Hyper-V at the start of a ShadowProtect backup.
• A fix has been made to eliminate a system-wide hang/deadlock which could occur on Windows Server 2008 at the start of a ShadowProtect backup.
• A fix has been made to eliminate a hung ShadowProtect backup job which could occur on Windows Server 2008 when at the start of a ShadowProtect backup.
• A fix has been made to resolve rare situations where VDiff (the fast incremental tracking) could not be enabled for some volumes.
• A fix has been made to the ShadowProtect NT service (ShadowProtectSvc.exe) so that when it is automatically woken up from sleep mode it will take the next backup if a scheduled backup was missed while the machine was asleep.  In versions prior to 3.5.2, the missed backup would only be taken if the machine was manually woken up, but not when it was automatically woken up.
• A fix has been made to the installed ShadowProtect components to resolve an issue where a new manual differential image, immediately dependent upon an existing full image file, would not be created with the same compression and encryption settings as the full image file (as it should be).
• A fix has been made to the image.exe .MD5 text file processing code to properly process all possible text file types (ANSI, Unicode little-endian with preamble/BOM, Unicode little-endian without preamble/BOM, Unicode big-endian with preamble/BOM, Unicode big-endian without preamble/BOM, UTF-8 with preamble/BOM, UTF-8 without preamble/BOM).
• A fix has been made to the recovery enviornment post-restore code to preserve the drive letter of a restored OS volume.  In the past this has been (and still is) done automatically as part of the post-restore HIR process.  But in situations where the restore process did not involve HIR, the drive letter of the resored OS volume was not preserved.  Now, regardless whether or not the restore uses HIR, if you are restoring an image of an OS volume then after the restore finishes the proper changes will be made to preserve that OS volume's drive letter when that OS volume is booted.
• A fix has been made to the post-restore BCD patching code to properly deal with hidden recovery partitions (such as the Win7 recovery partition).

ShadowProtect version 3.5.1 (December 2009)

• Fix for a rare bug, primarily, but not necessarily limited to Vista, Windows 7 and Server 2008/R2 was resolved. This bug could result in incrementals which do not include all changes to the file system meta-data since the last backup.  Affected incremental images, when mounted, will contain chkdsk errors.  This issue affects incremental backups only and not full images.  It is recommended that all users apply the 3.5.1 patch, reboot their system and start a new backup image set beginning with a new full image.

ShadowProtect version 3.5

• Fix to an issue which would cause the ShadowProtect.exe GUI to not automatically connect to the last-connected ShadowProtectSvc.exe agent (NT service) after upgrading.  Users had to click on "Network View" and then in the Network View they had to click on the Connect button.  This issue would only occur once, after an upgrade install.
• Fix for a hang in the ShadowProect Service (ShadowProtectSvc.exe) which occurs when the Microsoft Volume Shadowcopy Service (VSS) is in a bad state.  Rather than hanging, the service now continues to perform a snapshot-based backup, just without the involvement of VSS.
• Fix for an issue in sbrun.exe which could cause backups to network shares to fail.
• Fix to post-restore code which patches the volume boot record incorrectly for unrecognized file systems (such as would occur if you backed up an encrypted volume from the WinPE environment and then restored that backup).
• Fix to eliminate NTDS event log errors occurring after 64 snapshots fill up the NTDS VSS writer's status log.  These errors didn't actually cause any problem but they did confuse some users and so we took the steps necessary to eliminate such log entries.
• Fix to stcvsm.sys for blue screens (BSODs) occurring on Win7 RTM.
• Fix to the post-restore BCD patching code.
• Fix to the installer dealing with registration of the VSnapVSS.exe NT service on upgrade.  On some upgrades, users had problems because this service was not registered.
• Fixed an issue which caused KeyFile.exe and KeyFileMaker.exe to crash when run on Windows Server 2008.
• Fixed an issue which occasionally caused ShadowProtect to attempt to use the VSS framework when creating a backup on a Windows 2000 platform.  VSS does not exist on Windows 2000.
• Fixed an issue which sometimes caused the ShadowProtect Service (ShadowProtectSvc.exe) to crash on startup if a mirrored dynamic disk volume was present.
• Fixed an issue in which most of the time the execution completion status of the post-backup job was not logged in the task detail log.
• When editing a job, if the user checked the "Backup Now" box at the end of the wizard, the backup job would make a new full backup even if it was a job which supported incrementals.  This has been fixed such that an incremental will be attempted if at all possible, and if not, then a base will be created.
• Optimized image chain resolution code which could cause image.exe or SBMntWiz.exe to run out of memory in cases where a user attempts to resolve the chain of dependent image files for a specified image file (this happens automatically during a mount operation, for instance) of an image in a large image set in which collapses have been performed yet no files deleted after collapse.

ShadowProtect version 3.4

• Fixed issue where the date display options could be interpreted incorrectly if the system was not set to US English. 
• Fixed a very rare issue where scheduled backups didn’t run properly. 
• Fixed issue where using Pre/Post/Finish backup commands in a backup didn’t properly report to the ShadowProtect log files. 
• Fixed a crash on Vista in Backup/Edit job wizard when closing the Advanced options dialog.
• Fixed an issue where path name with 38 characters would not display image files.
• Fixed an issue where a DiffGen backup would fail with "Set Guid Mismatch" error.  This only occurred for a job with the option "Second and subsequent full backups are differentials" selected which had been edited prior to the attempted DiffGen backup.
• Fixed an issue where retention policy would not remove old files stored on some NAS devices.
• Fixed slow backup speed to an Iomega REV drive.
• Added a retry for files that could not be deleted by the retention policy because they were in use.  Also, included retention policy results in log file.
• Execution of missed backups now applies to service resuming from a suspended state as well as service starting.
• Added a delay of 60 seconds before starting backup jobs when the ShadowProtect service is started or resumed.
• Fixed FAT16/FAT32 mounting issue
• Fixed FAT16/FAT32 snapshot issue on Vista+
• Fixed rare blue screen at shutdown time on Vista
• Fixed Sophos AntiVirus interop issue (resulted in a system hang)

ShadowProtect version 3.3

• Setting the retention policy to remove an old chain on a network destination before creating the next full image did not remove the chain.
• When using the Now option in the Backup Wizard, the radio buttons for Full and Differential could get in a state where both were selected.
• When using the Later option to create a backup job to run once, it could run a second time after the ShadowProtect service was restarted.
• stcvsm.sys in-memory data structures for the fast incremental tracking feature now only takes 1/4th the memory.  It wasn’t taking much memory in the first place but this has been enhanced. 

ShadowProtect version 3.2

• Flush registry keys on write so they will be in the next snapshot.
• Fixed a bug where changing the destination of the backup job would cause the next DiffGen to fail.
• Fixed a bug that could occur under certain circumstances after the ShadowProtect service was restarted.  The next base or VSS incremental was scheduled instead of an incremental backup.
• Fixed hang during backup job caused by interop issues with 3rd party applications.
• Fixed a bug where .spk files were written for some Weekly or Monthly jobs.
• Fixed hang during backup job caused by an empty password apparently from failed registry read.
• Enhanced retention policy to allow delete before backup, remove old files when rotating media in destination.
• Fixed handle leak when flushing registry writes.
• Fixed a bug when service holds the destination object's drive locked thus denying removal of the drive.
• Fixed a bug when mbr and/or first track can't be restored if an image file is password protected.
• Decreased time to discover/enumerate disks and volumes in some cases ( when removable media is not present in the drive )
• Fixed crash when editing monthly schedule
• Added retry for auto activation error
• Custom schedules created using scripts are not displayed.
• Hide Activate button after successful activation
• Added option when right clicking on a job to copy job properties to a file (helpful for troubleshooting)
• Fixed look of the tab control in the advanced backup options dialog.
• Fixed connection issues in Vista.
• Added warning notification on quit if any task is still running.
• Fixed keyboard navigation issues.
• Fixed control's tab order in dialogs.
• Added ability to invoke context menu using keyboard.
• Fixed display of summary information for directories on a network share
• Collapse now works for SAMBA shares
• Added option to keep redundant collapse files for users that only transfer collapse daily files
• Fixed problem where GUI would not connect to a running service (should only fail if service is not running)
• Fixed bug where file renamed from *.spi to *-cd.spi caused orphaned files if *-cd.spi file was later removed.
• Recognize image files transported to remote location that are given a temporary name until transfer completes.
• Fixed client connection failure during service startup while directory entries and database are synchronized.
• Fixed bug where attempting to stop the service during startup would sometimes fail.
• Added cleanup policy for collapse daily (-cd) and collapse weekly (-cw) files.
• Added support for x64.
• Fixed bug where invalid directory names were reported as errors but still added to list of watch directories.
• Added ability to browse network locations.

*********************************************************************
Copyright (c) 2010 StorageCraft Technology Corp. All rights reserved.
This Software and Documentation are copyrighted.  Ownership of the
ShadowProtect Server Edition Software is reserved to StorageCraft
Technology Corporation.  StorageCraft, the StorageCraft logo and the
ShadowProtect Server Edition logo are trademarks of StorageCraft
Technology Corporation.  ShadowProtect Server Edition is a trademark
of StorageCraft Technology Corporation in the United States and else-
where. All other brands and product names are or may be trademarks or
registered trademarks of their respective owners.