Within the technology of both products there is a fundermental difference that can create some unwanted problems when not configured correctly.
The reason this happens is because ShadowProtect will monitor block changes on the drive (Note: This is not a file, a block is a portion of a file). Diskeeper on the other hand looks for files across the disc that are spread in multiple locations.
Because of the Diskeeper invisitasking automation we now face a problem where we backup the newly defragmented files. Therefor increasing the backup size dramatically.
**Diskeeper can still continue to provide you fantastic peformance by reduceing the fragmentation creation. This in turn assures that your read and writes are as fast as possible without having any process overheads. Intelliwrite is known to prevent as much as 85% of file fragmentation.
The best practise method of running these two fantastic applications is as follows.
a. If you want to run Continous incrementals ongoing.
Our recommendations on the use of both products together are as follows.
1. Optimize the disk to remove all fragmentation
2. Turn off InvisiTasking
3. Rely on intelliwrite because all files will then be written without fragmentation as a result
4. Do your incremental backups
b. If you want to run a weekly/monthly full base image.
Our recommendations on the use of both products together are as follows.
1. Optimize the disk to remove all fragmentation
2. Turn off InvisiTasking
3. Rely on intelliwrite because all files will then be written without fragmentation as a result
4. Do your incremental backups.
5. When it is time to do your new base image, stop ShadowProtect, run a full defragmentation of your drives which will then take you back to step 1.
This means that from each time you are creating a base image, your disk is 100% healthy and intelliwrite will have you in the best possible state for the duration of your backups.
The reason we disable invisitasking is to prevent additional file movment on the system.
Therefor addressing the problem block based solutions have.
