Pausing it during backups/defrags forces it to hold onto as much of the relevant info from daily use as possible. I don't ever clear the cache unless I think there's corruption of data inside it. Due to it's ability to do multiple drives at once, it only takes as long as a single drive would take. Typically I'll find a good day for the array to be offline for several hours, then manually kick off an analyze and then a full (free space) defrag on the volumes I think need it the most.
Do you schedule it using the defrag software or do you use the windows scheduler? I dont have the paid for version of Auslogic Disk Defrag Pro at the moment so I cannot see the options available for sceduling defrags, so I dont know if it supports pre/post scripts to be run when the defrag job kicks off. I'm currently evaluating the Auslogics Disk Defrag Pro software, I might try to do a similar schedule as yourself whereby you disable the cache, defrag and then re-enable the cache. I use a batch file for that purpose with command line options for Primocache.ĭo you only pause the cache while defragging or do you pause *and* reset primocache cache? Also, with Auslogics Disk Defrag do you kick it off using the cli or are you using the pro version's scheduling option? Pausing Primocache, running defrag, then resuming it seems to be the best course of action for my needs. Once a month or two I'll take my Drive pool offline and do individual defragmentation. I don't really do set-it-and-forget it defragmentation, since it can mess with Primocache's content and hit rates when clusters are constantly being moved around and the cache is running.
0 kommentar(er)
