Category :Database Health

Posted in : Database Health on by : VitalSigns Comments: 0

The Database Health service has been optimized for one of our big customers.  Now the service is smart about which server it analyzes first, selecting the one with the oldest data first, and working it’s way from oldest to newest until all is up to date. It also starts at midnight and stops at 9..

Posted in : Database Health on by : VitalSigns Comments: 0

To better accommodate one of our larger customers, the icon view on the Overall Health tab has been improved to allow more servers to be shown at once.   There is also a new “condensed view” in the browser version of the VitalStatus database created for the same reason. The Database Health module continues to be..

Posted in : Database Health, Domino Health on by : VitalSigns Comments: 0

I haven’t posted in a while, and I wanted to bring you all up to date. One of our newer customers has 60 servers all over the world, and scanning all those servers sequentially just wasn’t working.    (Some servers took several minutes to respond.)   So we  tweaked and tested our algorithms and now..

Posted in : Database Health, Overall Health on by : VitalSigns Comments: 0

Although Domino is a very stable product, occasionally things go wrong with Notes databases.  They can become corrupt, require a fix up, lose their full-text index, and more.  Usually this is virtually impossible for an administrator to detect before an end-user tries to open the database and discovers that they cannot.  Then your phone rings…

Posted in : Database Health on by : VitalSigns Comments: 0

VitalSigns monitors Lotus Domino server health better than any other product on the market.  VitalSigns watches Overall Health, Cluster Health, Mail Health, Disk Health, and now with release 9, Database Health too. When a user opens a critical Notes database only to wait for a view to be refreshed, to find out it hasn’t replicated,..