For my current project we are thinking of setting up a dual master replication topology for a geographically separated setup; one db on the us east coast and the other db in
There are several things to consider when replicating databases geographically. If you are doing this for performance reasons, be sure your replication model supports your data being "eventually consistent" as it can take time to bring the replication current in both, or many, locations. If your throughput or response times between locations is not good, active replication may not be the best option.