First the only place I can think of to get real world multi-site implementation tips is here. The architecture class taught at GU doesn't really address this to an adequate level, although they do propose a simple second site. So here are a few of my rules of thumb that I use when I plan a multisite implementation of Genesys.
First, everything is HA at both sites; that means that for every component at each site, I have a backup app also running. Second, depending on the distance and how reliable the WAN link is between the two sites, I will install a Config Server Proxy at the second site (you have this covered). The second site should also have a local copy of Stat server for CCPulse instances (you also have this covered). I try and put URS as close to the agents as possible, but depending on the distance and reliability of the WAN link, in your case, maybe a self-aware URS would be the better approach.
Where is your management layer? you talk about the DB for logging at the second site; I would put that at the first site along with Message Server, Solution Control Server, SCI, Config Mgr, and license manager.
I tend to put licenses on the same physical server as the TServer, SIP server for you. And don't be afraid to split your licenses. One problem this solves is keeping the licenses local to the site so a TServer or URS doesn't have to reach across the WAN to check out licenses.
Also, since you are running IP you haven't mentioned Stream Manager.
Where is reporting? ICON/Informart or CCA? I don't see that mentioned. I normally put reporting in the data center, since it is heavily database dependent.
I normally put IVR platforms in the data center as well. Your DMARC for the service provider sounds like it is in the first site also; you might want to consider a backup SP DMARC in the second site for DR purposes.
Are the calls delivered to the first site and then transported to the second site? Since your IVR is at the first site, it sounds like the calls go to the first site, then are transported to the second site if an agent is needed. Are you taking emails or chats at the second site? Don't see that mentioned. Be sure to purchase the license for TServer to TServer (ISCC) conversations - this used to be called external routing. but InterServer Call Control is what they call it now.
GAD works best if the GAD application/web servers are local, however, GAD is also database dependent, so you have to understand how GAD really works to get a reasonable performance balance. I've seen web servers local and the application server in the data center - that normally works ok.
Databases...a replicated database in the second site for DR is a nice idea if you have the money; couple that with cold config and management layers for DR as well. Be sure that your config failover works seamlessly.
well, it just a start, but I hope it helps.
Guy
