This Good info for anyone looking to integrate RepliStor with non-standard
or legacy apps.  Thanks for the post.


-----Original Message-----
From: Michael Brooks [mailto:michaelb AT SEQUOIAINS DOT COM]
Sent: Thursday, April 17, 2003 12:56 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Looking at RepliStor


we used the replistor product for a few months in our environment and
found it unsatisfactory. we tried using both a "daisy chain" and a one to
many scenario to try and overcome its limitations. to its defense we were
trying to push it to be a near-real-time replication across a t-1
throttled to 1024k. the problem arose as a result of replistor's intercept
method. we have a legacy app accessing an ancient dB and replistor
produced a ton of accesses due to this intercept method. these intercepts
would all be sent into a queue for replication. since we could not pick
and choose which type of intercepts (read, write and access by the way),
replistor would quickly fill up this queue, saturate the link and
eventually kill the server. we had a couple options involving turning off
file information, but could not because of versioning issues. after months
of troubleshooting and having legato engineers on site, we had to scrap
the project and start over (we are currently investigating new replication
products). my two cents.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=