Replistor with Documentum and Index Server

Replistor is not as such supported with any software as it does not care - it replicate data changes that are written to the disk - the Replistor filter driver sits between the OS and the disk and picks up any changes to the disk and replicates them regardless of where they have came from.

David,

So, what if a database corruption occurs, Replistor replicate the corruption?
Replistor have any Admin console to rollback a data block replication process?

David,

Then no mather what DB engine I use, SQL Server or Oracle Database?

Exist any connector for Databases?

Regards

Thanks a lot.

It does not replicate files - it replicates blocks of data that are written to disk so works independent of how the data is stored. With databases you have to start the Replistor driver prior to the database to ensure its consistency and there may be additional configurational tasks you may need to recover if you are looking to failover an application.

David,

Sorry but I have a new question about this, if a "volume" corruption occurs, what's the behavior on Replistor

Thanks in advance

It would depend whether the corruption occurs within your specification - if you are replicating the whole volume it would replicate that corruption but if you were replicating a particular folder and the corruption was elsewhere then there should be no issue (I am assuming here that "volume" does not hold some specific meaning in Documentum!)