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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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
3 Tier Install - Points of Failure
matttrax
Member Posts: 2,309
Obviously we can install multiple NST on a single server. That way everyone connects through the same box, but NAV balances the load accordingly (my understanding, please correct me if I am wrong). That produces a single point of failure if that server ever goes down.
For the database tier we can just create a cluster and it will fail-over. Is there a recommendation for a similar practice for the NST. We don't want to create, for example, four different servers and have one set of users log into NST01, one set into NST02, etc. Then have the users go through one by one trying to connect to each one if one doesn't work.
We'd like a single NST server with multiple instances that will fail-over to an identical NST in the event something happens. Is this possible?
For the database tier we can just create a cluster and it will fail-over. Is there a recommendation for a similar practice for the NST. We don't want to create, for example, four different servers and have one set of users log into NST01, one set into NST02, etc. Then have the users go through one by one trying to connect to each one if one doesn't work.
We'd like a single NST server with multiple instances that will fail-over to an identical NST in the event something happens. Is this possible?
0
Comments
2) There is no "automatic" load balancing. RTC client selects which server will use.
3) You can use some own module to do that: you can create own application, which will check which server to connect (somehow), write the settings into the .config file for the RTC and after that will run the RTC. You only needs to have tool how to check how many connections are currently on each NST and which NSTs are available... ;-)
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.