The following issues in 3.0 have all been fixed in
3.1:
1. A rare (reported by two users) MBR restore
failure issue.
2. MBR/hidden track/disk-signature restore failure
when restoring from
A
split/spanned media set.
3. Crash-proof-incremental on continuous incremental
jobs was not set. This means that new bases were generated rather than
diffgen-created incrementals in cases where the VDIFF map is lost.
4. When network access failed, a new base or a
differential backup may have been attempted when an error should have been
reported and the job aborted.
5. The progress control in ShadowProtectPE.exe
stopped updating after a while when restoring a chain with incrementals.
6. Provide option for Iomega Rev drives (which
report themselves as being removable optical media device) and DVD-RAM such
that the user can instruct ShadowProtect to write to these devices as if they
are fixed drives, rather than using the media burning option.
7. Add ability to sbimageapi.dll and image.exe such
that users can easily (on the command line) resolve image file chain
dependencies such that a command-line mount/restore/verify of any specified
point-in-time can be easily performed.
8. A bug in the disk enumeration code that
occasionally caused the ShadowProtectPE.exe process to crash.
9. Execute missed schedule caused an attempt every
second to execute a missed backup if the destination was not available.
10. VSS incremental flag for continuous jobs was not
persisted in the registry. After
stopping the service, all continuous incrementals were VSM direct.
11. DiffGen image list creation could generate a set
Guid mismatch error if unnecessary files were in the list or files were not
sorted correctly.
12. Write caching advanced option was not being
honored. Modified the default write
caching to be off for all destinations (local or network), which we have found
minimizes I/O errors, but will always honor the user’s setting if they override
this advanced option.
13. If a path contained spaces, a DiffGen backup
would fail because the path was not recognized.
14. ShadowProtect 2.x jobs were not updated to
contain additional info such as current set guid and last incremental file
guid.
15. Scheduled jobs with no incrementals selected
sometimes were not rescheduled after they were run. This is the "Next Run Time:Never"
bug.
16. Scheduled jobs will now fail if an error occurs
on exclusion of free space, pagefile.sys or hiberfil.sys. These errors only occur if the file system is
corrupt and the user needs some kind of warning so that they can repair the
file system rather than just let the automatic backup continue to occur and
backup a corrupt file system. A manual
backup (backup now) will always work, even if the file system cannot return the
run list of the pagefile or hiberfile.
17. Job status was occasionally left in running
state after all tasks were done.
18. Scheduled incrementals will now always try a VSS
snapshot first on XP+ except for continuous incrementals where the user has
specified not to use VSS.
19. ShadowProtect service occasionally hung on
startup during disk enumeration as it was using a SCSI passthru request to
obtain capacity information from CD/DVD drives and there is a bug in the
firmware on some of these drives that will cause such a request to hang, and
worse, will hang any future request made to the device. A workaround was added
which calculates the capacity rather than query for it. In this case it's acceptable for this value
to be calculated as this capacity value is only used for display/information
purposes, and isn't actually used for any operations, so it's not critical for
application functionality.
20. The Recommended (Vista-WinPE) recovery
environment altered the system BIOS clock.
21. The Recommended (Vista-WinPE) recovery
environment could not assign static IP addresses.
22. An interoperability issue with Trend Micro
antivirus which caused a system hang (deadlock).
23. Enhanced Recovery CD boot menu explains the
benefits of each recovery environment.
24. Added Close button to the Map Drivers dialog of
the Network Configuration Utility.
25. When updating to new version, occasionally, the
vsnapvss service would fail to register causing diffgen incrementals to occur
instead of quick incrementals.