"David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> wrote in message
news:Xns993B914062C5Ff99a49ed1d0c49c5bbb2[ at ]127.0.0.1...
[Quoted Text] > "Brad P" <bradp_xx[ at ]hotmail.com> wrote in
> news:4655c7c1$0$4032$9a566e8b[ at ]news.aliant.net:
>
>> I have RepMan managing a few replicas and many partials. One
>> replica is on a network server. This server has 2 different
>> address, ie jm1, and jm-cluster as this server has a mirror.
>>
>> Anywho, RepMan syncs on a schedule with this replica on jm1. For
>> some reason though, when after a few days I open RepMan, there is
>> additional replicas representing the the replica on jm1, but has
>> no sync schedule, ie, has a dotted line. If I let it go for weeks,
>> there could be 50+ duplicated replicas that I have to delete. I
>> can not understand why RepMan is creating multiple instances to
>> the one replica.
>>
>> Any help is appreciated.
>
> When you say that there is a "mirror" of the server, how is that
> mirror populated? By file system replication? If so, then perhaps
> that's what's causing the problem. I've never worked in a replicated
> file system, but it definitly causes problems with Jet, whether
> replicated or not.
>
Its done through a Blade server and it mirrors the server to another hard
drive. As far as I know. this is real time mirroring. But you may be on to
something nonetheless because these multiple instances could be either jm1
or jm-cluster.
This morning I deleted all multiple occurances, and now at 5:00, 2 have
reappeared. One is on jm1, the other on jm-cluster.
|