Given that scenario:
Server A has a file called database.nsf
Server B has 2 replicas of server A’s database.nsf:
One replica is at the root and has the same filename as server A's: database.nsf
The other replica is in a sub directory and has a different filename: subdir\otherdatabase.nsf
In the Domino Directory, there is the following replication document set:
Source: Server A
Destination: Server B
Replication Type: Push Only
Filename: database.nsf
Schedule: Every day from 6am to 10pm
Question: Will subdir\otherdatabase.nsf also be updated during that Push? Or do I need a seperate document for it?
I think it will get updated, but I’ve got some colleagues that are argueing with me… so I need an expert’s answer.
Thanks!
Subject: Question about replication and multiple replicas of the same db on a same server.
Sounds like a recipe for disaster. Why on earth would you need 2 replicas of the same database on the same server?
My first thought is that you won’t be able to guarantee which instance will get the changes.
Perhaps if you initiated pull-push replication with server B as the source you might be ok. (one doc for each DB). Not that I’m recommending this, it’s just a thought exercise.
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
Hi,
I know it’s a possible recipe for disaster but i did something similar for a client. It was not with connection documents.
My problem was a DB with 1,5 million documents. I needed 3 databases with 2 views in each dbs.
It was to long to update documents, so we deployed the 3 dbs in 3 separates directories .
Rep1\db1.nsf
Rep2\db1.nsf
Rep3\db1.nsf
In the first db, we made a agent to initiate a replication with the 2 other dbs.
It was not clean but it solved our problems. It’s like that for the last 3 years
JYR
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
Ok, let me explain the actual setup the client needed (and why they did this)…
They needed to export a user list in s special format into a text file for another program to catch and update some sort of Org Chart. The format looks like something Firstname~Lastname~phone number…
So what the ex admins did, was to create a replica of names.nsf using a replication formula to replicate only the person docs. They then disabled the replication of Design changes and Agents and created an agent to do the export…
We recent;y had to dosome cleanup in the NAB cause there was a lot of old connection docs (that environment was a mess when we got it…),and something was changed that caused that special NAB to replicate with the main one, so when we found out what was being done, we frowned quite a bit and told them this will need to change cause it’s too dangerous.
The only reason they gave us when we asked why they did it that was was that they didn’t want to modifythe design of the main directory in case we needed to upgrade the server to another version… Big deal, the modifs they did consist of a custom view, and an agent. Nothing that can be copied back in in a jiffy…
Thanks for the confirmation 
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
That’s my point… a client has that setup for a special NAB, and we told them it’s risky as hell, but they don’t believe us… Trying to prove them wrong.
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
Hi,
Multiple Replicas of a Database on the Same Server Cause Replication/Security Issues
www-1.ibm.com/support/docview.wss?uid=swg21096344
From LooseLeaf (Bob Balaban)
JYR
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
Always the right answer 
Thanks Jean-Yves!
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
We have business reasons to do this and have done it for over 10 years. To correctly replicate, the server where the multiple replicas reside must INITIATE replication to the other server, because then you can include the subfolder plus the filename in the Files to Replicate field. Also, in our case, it is one way replication only.
Rep Server B ==> push (or pull or push/pull) Server A
Files/Directory paths to replicate:
subfolder1\filename1.nsf; subfolder2\filename2.nsf
Subject: RE: Question about replication and multiple replicas of the same db on a same server.
That will work yeah, but it’s still risky… too risky.