Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Configuration in multi-installation scenario
JanGD
Member Posts: 12
Hello all,
i am currently working out some general requirements for a multi installation scenario, which we are planning. I tried the search but haven't found anything similar.
We are hosting (going to host) multiple installations from various countries (including Far-East with Doublebyte characterset). We plan on serious hardware, nothing cheap, but reasonable.
Final installation would be about 20 countries with each 20 concurrent users (slowly growing) in some years (5-8).
Now i am thinking about the best hosting solution.
The SQL Solution i think is not so complex to plan.
I am thinking of a machine with 8-16 cores, 48GB RAM with our *sick* SAN connected. Maybe 2 of these machines for fallover.
I thought about setting up 2 Hyper-V win2k8r2 servers with sql2008r2 on that host machine:
One for doublebyte characterset countries (Korea, China, Japan, etc) and another for the "other" countries.
My problem is now the configuration of the up to 20 Service Tiers. (per country/db one ST)
I read somewhere that MS suggests to have a dedicated virtual server per service tier. This would make a total of 20 virtual servers. That can't be hosted if these Hyper-Vs each need 4 cores, 4 GB RAM.
Aside that, if i am not mistaken the Client and Service Tier needs to be on the same timezone to be able to connect. This would split it to "for each timezone" at least. I am not sure if this problem of Dynamics NAV 2009 was resolved in SP1.
The "other" solution would be to consolidate all Service Tiers on a "timezone-basis" with multiple timezone-matching Service Tiers installed on one Hyper-V server. This would require less virtual servers, but as stated earlier, i read somewhere that MS suggest 1 service tier per virtual server.
A Service-Tier hosting server could look like the sql server spec i wrote above.
Suggestions/Ideas are appreciated
Thanks in advance!
~jan
i am currently working out some general requirements for a multi installation scenario, which we are planning. I tried the search but haven't found anything similar.
We are hosting (going to host) multiple installations from various countries (including Far-East with Doublebyte characterset). We plan on serious hardware, nothing cheap, but reasonable.
Final installation would be about 20 countries with each 20 concurrent users (slowly growing) in some years (5-8).
Now i am thinking about the best hosting solution.
The SQL Solution i think is not so complex to plan.
I am thinking of a machine with 8-16 cores, 48GB RAM with our *sick* SAN connected. Maybe 2 of these machines for fallover.
I thought about setting up 2 Hyper-V win2k8r2 servers with sql2008r2 on that host machine:
One for doublebyte characterset countries (Korea, China, Japan, etc) and another for the "other" countries.
My problem is now the configuration of the up to 20 Service Tiers. (per country/db one ST)
I read somewhere that MS suggests to have a dedicated virtual server per service tier. This would make a total of 20 virtual servers. That can't be hosted if these Hyper-Vs each need 4 cores, 4 GB RAM.
Aside that, if i am not mistaken the Client and Service Tier needs to be on the same timezone to be able to connect. This would split it to "for each timezone" at least. I am not sure if this problem of Dynamics NAV 2009 was resolved in SP1.
The "other" solution would be to consolidate all Service Tiers on a "timezone-basis" with multiple timezone-matching Service Tiers installed on one Hyper-V server. This would require less virtual servers, but as stated earlier, i read somewhere that MS suggest 1 service tier per virtual server.
A Service-Tier hosting server could look like the sql server spec i wrote above.
Suggestions/Ideas are appreciated
Thanks in advance!
~jan
0