The Content Server should be considered as a back-end server that hosts the business-specific Docbases. Remember that a Docbase is nothing but a logical set of content files (stored in the host server OS's file system), metadata for content (stored in the underlying RDBMS), and the full-text indexes for objects. No matter which tool one may use to create content, it is stored within a Docbase, which is managed by the Content Server.

There are numerous configurations possible in Documentum distributed architecture that provide a failover mechanism. One could set up multiple servers for a single Docbase or provide object replication from one Docbase to another Docbase, etc.

Documentum's security mechanism obfuscates the actual names of the content files on the underlying host server's OS. So, if you create a content item using Web Publisher for example, the content file that is stored on the OS will not be easily recognizable.