Thursday, December 8, 2016

DBMT Optimizations in DDO - real world example

Further to my previous post on "DBMT Optimizations in DDO that can reduce its workload by over 90%"  here is a real world screen shot of what is happening at one of our clients.



Now that's optimization.

Why not try DDO for yourself with a free 30 day trial?

DBMT Optimizations in DDO that can reduce its workload by over 90%

DDO includes three optimizations to DBMT that make a dramatic difference in its workload:



The first and most powerful setting is the “Only Compact when Freespace exceeds” fields on the Optimization Schedule.

By setting this field a database can only become a candidate for DBMT compacting when the freespace within it exceed the amount specified. This avoids potentially processing hundreds of database where little, or no, freespace can be recovered. This dramatically reduces DBMT processing times, prevents fragmenting those databases, and prevents unnecessary DBIID changes, which also reduces backup requirements.

Here is an example where only 12 databases exceed the Freespace exceeds setting:



As a result when DBMT runs all other databases are excluded from the compact sub-task of DBMT



DBMT therefore only compacts 12 of the 280+ databases


You can further fine-tune the databases that are excluded from compact processing by adding them to the “Exclude the following databases from DBMT processing field” or adding the directory to the “Exclude the following directories from DBMT processing field”

The end result is significantly less time “compacting for the sake of compacting” and the benefits from there are substantial.

One final note, the DBMT optimizations discussed here are only available in DDO.

Why not try DDO for yourself with a free 30 day trial?




Friday, December 2, 2016

What are the stages of optimization in DDO?

One of the great features of DDO is how it works through its optimization stages automatically to ensure you get the best 'bang for buck' from your Domino server.

The first stage is ensuring database properties on databases inheriting design from the mail template (or other identified templates) are set correctly. Any databases out of line are quickly put back into line.

Stage two optimization ensures databases that need to have DAOS applied, have it. Any new databases created based on the identified template names, get DAOSified. That night a specially targeted DBMT session is run to make it happen.

Stage three optimization is NSF file defragmentation. This occurs when and if required.

Other stages of optimization are core to the product, they include:
  • only running DBMT on databases with active freespace, no more compacting for the sake of compacting.
  • only running DBMT on databases that haven't had maintenance run for a given period.
  • running DBMT index optimisation on all databases.
  • running maintenance on system databases periodically
DDO can also automatically schedule DAOS synchronization, shutdown the mail router before performing maintenance on the mail journal and will do a full NTFS freespace optimization when required.

All this happens in a single package. If you would like to give it a go, check out our website at https://www.preemptive.com.au/products/domino-database-optimizer/

Thursday, December 1, 2016

New product - The Domino Database Optimizer – DDO.


We are delighted to announce the general availability of our new product - The Domino Database Optimizer – DDO.


The DDO combines the power of DBMT, with the intelligence of an inbuilt configuration tuner while also integrating everything we’ve learned developing Defrag.NSF. We’ve wrapped it in a single application, with a super easy to use user interface and scheduler.

It is designed to work on all types of storage systems from direct attached, SSD, NSA, SAN or virtual. No matter what storage type you have, it will help you minimize your Domino Servers’ I/O.

With DDO you can:

  • Schedule DBMT with a super easy to use UI
  • Automatically enable advanced database properties like design and attachment compression. If settings ‘drift’ from your set standard they are automatically reset back to conform with what is required.
  • Automatically have databases ‘DAOSified’ based on their design template. Just set and forget. Databases that require DAOSification are individually identified and targeted.
  • DDO intelligently selects the databases requiring DBMT operations based on their last compact date and the freespace they contain – no more spending time ‘Compacting for the sake of Compacting’
  • Schedule database optimization of system databases with the click of a radio button – this easily reduces the size of databases like log.nsf and mailjrn.nsf. Smaller databases open faster and require less time to backup.
  • Automatically defragment databases that require it, further reducing backup times while increasing overall system throughput – we built Defrag.NSF into DDO.
DDO is everything you need to maintain your Domino Databases and keep them in tip-top shape. Just ‘Set and Forget’ and let it do the work for you. Your servers will be more responsive, your backups faster.
 
For more information please check out our website at https://www.preemptive.com.au/products/domino-database-optimizer/ and while you are there request a free 30 day trial.

System requirements:

Domino 9.01+
Windows Operating System

Thursday, July 21, 2016

Fully automate DAOS - set and forget, save diskspace, time and money

If you have a DAOS enabled server with mail files or other databases like Document Libraries containing attachments on your servers that may have slipped through the administration cracks and not been enabled for DAOS participation, even though they should have been, (possibly as an administrative oversight?), this functionality in DDO will automatically DAOS enable those databases and get those attachments into DAOS, it will also automatically pick up any new databases created in the future without the administrator having to think about it, or chase it up.


An example of this DDO processing at work.
In this example (see below) we'll target a couple of databases that make decent candidates for DAOS participation, like most Document Libraries these are full of attachments, so these types of databases make great "low hanging fruit" for DAOS.


We can see below these database are currently not enabled for DAOS participation. Note the DAOS State and DAOS Count indicating this.



Tick the box to “DAOS enable all databases using the following templates” and enter the template name, you can enter multiple template names, mail templates, etc. If there are databases based on this template type that you don’t want DAOS’d enter the name(s) in the “Never DAOSify the following databases” field.


When the automatic maintenance schedule runs, DDO will enable DAOS participation in the targeted databases and the attachments will be moved out of the databases and into the DAOS store as part of the automated DDO maintenance.

Below, we see the results after the schedule ran, the same databases are now enabled for DAOS participation, the attachments have been moved out and as a result the space savings are significant.


Below, we can also see the DAOS State has changed to "Read/Write" and the DAOS count increased.





LZ1 Compression and Data Compression have also been enabled for the databases.

The databases have also been automatically compacted and defragged as part of the DDO workflow.




If you enable the “Automatically monitor DAOS synchronization” box DDO will automatically monitor the synchronization state of the DAOS catalog and as needed a DAOS resync operation can be automatically performed to re-count all the references to NLO files. If required DDO, will initiate a resyc of the DAOS catalog at 12:15AM. If a resync is not required the operation detects that there is no work to do, and will exit immediately.

Note: IBM best practice recommends that if the catalog state changes, a DAOS resync should be performed but, unless Daoscat.nsf has been damaged somehow, there is no immediate need to do a resync. All DAOS functions will continue to operate normally except for the 2AM prune operations, which will be postponed until the DAOS catalog state is SYNCHRONIZED again.

Additional Information about DAOS maintenance: Here

DDO makes this easier, working for you to automate, and improve Domino performance, I/O and backups (and your performance as a Domino Admin), it's all easier and automated.


Stay tuned, DDO will be available shortly and will be a free update to all Defrag.NSF customers

Fully automate DAOS enabling database - set and forget, save diskspace, time and money

If you have a DAOS enabled server with mail files or other databases like Document Libraries containing attachments on your servers that may have slipped through the administration cracks and not been enabled for DAOS participation, even though they should have been, (possibly as an administrative oversight?), this functionality in DDO will automatically DAOS enable those databases and get those attachments into DAOS, it will also automatically pick up any new databases created in the future without the administrator having to think about it, or chase it up.


An example of this DDO processing at work.
In this example (see below) we'll target a couple of databases that make decent candidates for DAOS participation, like most Document Libraries these are full of attachments, so these types of databases make great "low hanging fruit" for DAOS.


We can see below these database are currently not enabled for DAOS participation. Note the DAOS State and DAOS Count indicating this.



Tick the box to “DAOS enable all databases using the following templates” and enter the template name, you can enter multiple template names, mail templates, etc. If there are databases based on this template type that you don’t want DAOS’d enter the name(s) in the “Never DAOSify the following databases” field.


When the automatic maintenance schedule runs, DDO will enable DAOS participation in the targeted databases and the attachments will be moved out of the databases and into the DAOS store as part of the automated DDO maintenance.

Below, we see the results after the schedule ran, the same databases are now enabled for DAOS participation, the attachments have been moved out and as a result the space savings are significant.


Below, we can also see the DAOS State has changed to "Read/Write" and the DAOS count increased.





LZ1 Compression and Data Compression have also been enabled for the databases.

The databases have also been automatically compacted and defragged as part of the DDO workflow.




If you enable the “Automatically monitor DAOS synchronization” box DDO will automatically monitor the synchronization state of the DAOS catalog and as needed a DAOS resync operation can be automatically performed to re-count all the references to NLO files. If required DDO, will initiate a resyc of the DAOS catalog at 12:15AM. If a resync is not required the operation detects that there is no work to do, and will exit immediately.

Note: IBM best practice recommends that if the catalog state changes, a DAOS resync should be performed but, unless Daoscat.nsf has been damaged somehow, there is no immediate need to do a resync. All DAOS functions will continue to operate normally except for the 2AM prune operations, which will be postponed until the DAOS catalog state is SYNCHRONIZED again.

Additional Information about DAOS maintenance: Here

DDO makes this easier, working for you to automate, and improve Domino performance, I/O and backups (and your performance as a Domino Admin), it's all easier and automated.


Stay tuned, DDO will be available shortly and is a free update to all Defrag.NSF customers