As most of us know that has worked with Domino server that are setup for using transaction logging, these servers are very sensitive to (even the smallest) issues with the drive (or filesystem) where the transaction logs are placed.
I sometimes work with IBM DB2 servers and they support setting up both primary and secondary log paths for transaction logging.
IBM DB2 also support setting up Overflow log paths and Mirror log paths.
The overflow log path would be of benefit when using Archived logging and if for some reason the backup of the transaction logs, doesn't run as smoothly as it should. We all know what happens when the log drive runs full!
Mirror log path would as well as providing increased stability also potentialy give a performance gain on servers with a high transaction rate.
Think one or more of these options are getting more and more important as Domino databases can get up 256 GB in size. And who knows, maybe even bigger in the foreseeable future.
This sounds like a lot of work for not much extra benefit.
If the drive has an issue, you have an issue on your machine.
Just adding an extra drive does not really help in most cases.
I am working with many customers leveraging archive style translog and I never heard that request.
Once you add those kind of features, also backup vendors might to need their applications changed. And this would be a blocker for updates!
I asked for a larger size of each translog extend than 64MB which would make backup and restore a lot faster. And also would increase performance for translog.
That's the kind of enhancements that would bring us forward.
[ Daniel Nashed / http://blog.nashcom.de ]