« The Sexy Laptop? - Move Over MacBook Air | Main | New Diskeeper 2008 Build (781) »
February 28, 2008
New Diskeeper 2008 Build (12.0.770)
We have a new update of Diskeeper available on our website. You can use the Check for Updates feature in the software or simply pull down the new Diskeeper 2008 trialware and install it over the top of your existing full version of Diskeeper 2008.
Here is a list of main changes in build 12.0.770:
1. Full feature support for Windows Server 2008. Note the previous builds of Diskeeper already installed on Server 2008 but did not include Bootime defragmentation.
2. Changes have been made to improve the logic (the new Smart Defrag of v2008) that determines when Diskeeper should run it's "extreme defrag" engine (low free space or severe fragmentation). Previously the volume had to be really badly fragmented AND extremely low on free space. In other words there was a middle ground where DK might not provide expect results. Now Diskeeper will detect if its other defrag engines aren't doing well enough and then, if needed, run this powerful new engine.
3. Fixed the problem with the Volume Map for volumes larger than 8TB and a cluster size of 4KB. It is now displayed correctly.
4. Fixed the problem with running on clustered servers where Diskeeper would lose volume settings after one of the nodes was shut down.
5. Microsoft Logo Certification for Windows Vista (Diskeeper 2008 Professional) and Windows Server 2008 (Diskeeper 2008 Server).
6. Fixed several other minor bugs.
7. Diskeeper News and Information feature added.
Posted by Michael at February 28, 2008 10:50 PM
Comments
This is great, but why is there no I-FAAST on a VSS enabled drive? This is one of the main selling points of Pro-prem but now I find that it doesn't work with Vista and VSS.
Are you going to fix this in a later release?
Posted by: Seajay at April 8, 2008 07:51 PM
Hi Seejay,
The VSS flaw for which we built this special mode imposes severe restrictions on how we move data. This makes I-FAAST file sequencing difficult to impossible. We are pursuing making the two Diskeeper modes work together, but I do not want to make any promises that this will happen. We are also pushing Microsoft to fix this flaw in VSS, which would be the best solution for you - the customer.
An option is to run Diskeeper in the Recommended-mode. You will likely find that after the first few runs of Diskeeper and I-FAAST that much less data needs to be moved and that extra VSS activity is minimal to non-existant.
That statement does depend on how static your data is over time. If the files on your volumes changes at a high rate, then this may not apply.
I hope this info helps.
Posted by: Michael at April 25, 2008 02:13 AM