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

Monday, July 18, 2016

News from the Lab - System Database Optimization - So easy with DDO!

We often see customers with bloated System databases that never seem to get compacted/maintained (you know the ones.... log.nsf, etc) because.....well it's just a hassle for many admins to shut down and manually do it. As a result, because these databases are missing out on some much needed maintenance, can get pretty huge and often respond sluggishly when they do need to be opened and with many GB of disk space trapped inside are just wasting disk space too, it all adds up costing time and money. Our new Domino Database Optimizer makes it so easy to apply best practice maintenance, get these back to a manageable size and give Domino a nice scheduled "Health Restart".

DDO makes this as simple as ticking a few boxes, set and forget, and If this is scheduled once a week the difference it makes to Domino is quite amazing.

During this phase of scheduled maintenance DDO integrates with Domino's own maintenance processes by using Compact Replication on the System Databases (and other databases you might want to add) with the Domino server up and running and therefore minimizing down-time, a -Restart is then initiated to complete the rename process.





We see below the system databases are compacted and upon restart the rename process is completed:





Friday, June 24, 2016

Arriving soon.. The Domino Database Optimizer.

For the last six months we've been working on our next Domino product, The Domino Database Optimizer.

The DDO (Domino Database Optimizer) is a database-oriented utility that automates and greatly simplifies the optimization of Domino databases and their maintenance. All activities are done through an integrated control panel where tasks can be done either manually or scheduled for overnight processing.

The primary focus of the DDO is maximising the performance of your databases and the Domino server by minimising I/O. With each new release of Domino and the ODS (On-Disk Structure) upgrades to databases, IBM continues to place great emphasis on working to reduce I/O and with good reason as reducing I/O leads to improved performance for the entire system. This has a “more than the sum of it’s parts” ripple effect that manifests through the entire system in many ways, a more responsive server and improved end user experience while interacting with applications and replicas, right through to faster backup times and back-end storage efficiencies.

The Domino Database Optimizer is designed to give you less of the following, so you get ->  More performance and value:
  • Server I/O = Less
  • Compacting = Less
  • DBIID Changes = Less
  • Fragmentation = Less
  • Backup requirements = Less
  • Backup times = Less
  • Server restart time when TXN Log or Consistency Checking required = Less
  • View Rebuild times = Less
  • To-Do List items for the Administrator = Less
The Domino Database Optimizer will empower you to very easily manage, configure and continuously perform extensive best-practice database and server maintenance automatically, so you can focus on the other duties you need to attend to - just set and forget!



It's almost here...... but until it arrives please try our other optimization product that is itself integrated in the DDO.

Monday, May 16, 2016

The Domino Database Optimizer. Our new product is on its way - Preliminary testing on SSD

Our new product is undergoing preliminary testing in our lab and is showing some great performance gains even with Domino attached to the latest SSD storage technology. We are using lightning-fast SSD storage here and seeing these results.

It's further proof that even though a super-fast storage/back end will help it is not a complete performance solution and in fact true optimal performance results from acknowledging and tuning each individual component of a system. To not apply that basic principal is akin to bolting a TurboCharger onto an engine with a clogged Air Filter, you will gain some power but will still leave plenty on the table untapped.

In this test case there is a dramatic I/O reduction during non-cached operations against the same database and after optimization the task also completes in roughly half the time.

I/O Before Domino Database Optimization


I/O After Domino Database Optimization


Result: Less I/O, less stress on the I/O subsystem, this translates directly to improved performance and resource availability for every task Domino performs.


Thursday, February 4, 2016

Notes/Domino futures from Connect 2016

Here are some slides from Connect that talk about Notes and Domino plans. Naturally anything could change.