Performance profiling of VOB DBs, VOB DB filesystems, and live load balancing

VOBs DB's have files like, database, journal, and lock files. Misc files.

Hundreds of VOB may share the same filesystem.
Many VOB processes may try to write at the same time and possibly send the DB file system into write throttling.

The create and management VOBs tools don't allow for distribution of loads to multiple filesystems.

Write throttling is not an easy situation for a ClearCase admin to detect.

*ClearCase should have methods to determine if it is not writing as fast as it should and report it. Possibly a method to slow itself down, i.e. Know that it's sharing a file systems with other VOBs and report the set are all affected.
* Methods to profile a target file system and proactively recommend different storage be used for different files in a VOB DB.
* When a VOB is created ClearCase needs to be able to separate out the DB into different file systems. Allow a site configuration to be establish for storage.
* Allow for a HA and safe backup and restore.
* Allow for Live reconfiguration of VOB DB if a particular filesystem is overtaxed.

For example if locks are taking a while for ClearCase to acquire perhaps the ALMD files should be moved to a different file system that is not write contending with the DB or Journal files. This is currently only supported if ClearCase is shutdown. A live migration method is requested for the ability to move an ALMD file. Minimal would be able to do this with the VOB locked. For example to schedule the move for the next time the VOB is locked for snapshot backup. Lock, snapshot, relocate, unlock.
Similar situation for Journal files.