You’re offline. This is a read only version of the page.
Hi,
I am looking for hardware sizing requirements for High Availability for NAV Server for 100+ users & fast database size growth (about 1 GB database size increase daily). Can we keep one server as stand- by replica for using one the hardware failure of first server?
I believe the standard hardware requirement document from Microsoft doesn't have recommendations for this kind of load.
*This post is locked for comments
I have the same question (0)
We (Microsoft) do not give out specific sizing requirements as you mention, we however do have a Service that a partner could engage us in for doing Architecture Assessments and Performance Reviews. Please have them contact support if you wish to engage into this Service. Just for some genearl information on sizing and High availability, I am adding some information below.
In general with the database size you are going to be looking at quickly in the hundreds of GB in a year, you will want to be on Enterprise Edition of SQL Server which then requires Enterprise Edition of Windows. I say this because you will want to look into using Database Compression and Backup Compression. Do not use generic compression information though, the NAV Blog has some information on Compression as you want to be very specific on what Compression levels are used on different Tables. Here are a couple blog posts on Compression:
blogs.msdn.com/.../sql-server-data-compression-and-microsoft-dynamics.aspx
blogs.msdn.com/.../microsoft-dynamics-nav-and-sql-server-database-compression.aspx
As for the High Availability, you will probably be looking at SQL Failover Cluster in Active/Passive mode since NAV is not specifically Cluster Aware for an Active/Active setup so Failover becomes somewhat of a manual process. Production Database and Logs should be split onto their own RAID 10 drives or SAN with backups being RAID 5 and then Tempdb on its own drive system RAID 1 or 10 as well as the OS on its own RAID 1 drive system. If using the RTC then you will want to make sure to have an additional Service Tier for High Availability for a N+1 setup, again it will not auto roll over, you would need to change the Config Files to point to that new Service Tier, but keep that in mind when setting up. You can use either Windows Network Load Balancing or other Hardware based solutions to help provide high availability. If you are using Terminal Server (Remote Desktop) or Citrix then you would follow the same guideline as having an additional Citrix or RDS for High Availability with Load Balancing of some type in a N+1 setup.
Again, this is very generic but some ideas to look at, we do have Services available to help with this if you are interested. SQL 2012 (Denali) will also give more options using the Always On feature that will be extremely useful for these types of setups. As always, we expect to have some type of announcement within 90 days of the SQL 2012 release on compatability with supported versions of NAV, as of now we have no announcements on that, but something also to take into consideration depending on your time frames for getting this set up.
Sizing part of your question isn't so much based on number of Users, that is a difficult thing to base sizing on, we use many more factors when sizing, such as how many concurrent users in different areas of the application, and what exactly are the users doing such as data lookups, transactions, reports, etc. What modules will they be using and how many in each such as Mfg and Warehouse which require larger sizing then say GL. Also how many are remote users vs on site users, and what does your business processes dictate for having to post during business hours vs after hours or reporting which if these type of things can be done after hours, the sizing also cahnges.There are many questions to look at for sizing, so I cannot direclty answer this part of the question. I am sure there are implementors out there with some generic information but it is always different based on the above questions. SQL Server there are some blogs on just for performance and sizing, here is one:
blogs.msdn.com/.../microsoft-dynamics-nav-sql-server-configuration-recommendations.aspx
For NAV Service Tier, it depends on the type of users, it is still a 32 bit application, so anywhere from 5-40 users per Service Tier depending on what type of users, such as Reporting would be towards bottom end of that number, users just looking up data would be towards high side. NAV 2013 will be a 64 bit Service Tier, so the number of Service Tiers will be reduced due to that fact when NAV 2013 releases, but for now the 5-40 number is a general number of users per Service Tier.
If using RDS or Citrix, normally a rule of thumb would be 10-15 Users per processor core depending on work load and 64MB of memory needed per concurrent user with enough left over for the OS. You then also get into Network requirements, Bandwitch requirements, etc.
I hope this is somewhat helpful though pretty generic I realize though a very complex question with much more information needed to fully answer.
Nick
Nick
Share
Report
All responses (
Answers (
