• 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).
• 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).
0 comments:
Post a Comment