Another advantage using Defrag.NSF+ and all it's integrated functionality is of course that databases and freespace are also monitored and defragged as required, this also maximises the performance of DBMT by providing contiguous freespace for it to work with.
Golden Rule: If the freespace on a server is scrambled then DBMT pre-allocation is going to produce fragmented files, It can only deliver optimum results if contiguous freespace is available, and that's only going to happen if something is actively defragmenting it.
We just had a customer set up DAOS on a new Domino app server build and use the integrated DBMT+ integrated features including DAOS and ODS upgrade on a couple of attachment rich databases, the results were worth documenting.
First, the databases in question were targeted for DAOS using their template, one of these databases was currently almost 40 GB in size
At 2:30am the maintenance set in the schedule kicks off
By 3:00am the attachments were moved into DAOS and the savings were in the bank, database size was reduced from 38GB down to about 195MB. The ODS was also upgraded to 53 at the same time.
That was too easy, tick a box and enter a template name. Done.
Like to check out what else it can do ? Click here.
We've just completed the deployment of Domino 11.0.1
There was just one thing we needed to do. The upgrade had put Updall in the ServerTasksAt2 line and we didn't want that as DBMT is used on this server (integrated with Defrag.NSF+), luckily the post upgrade Defrag.NSF+ Health Check pointed this out and offered a one-click removal.