Quantcast
Channel: Forum CRM Deployment
Viewing all articles
Browse latest Browse all 997

CRM 2013 SQL Report Servers Disk Size & Partition Recommendation (for Production with NLB)

$
0
0

Hi there CRM experts & experienced implementers,

We're building the servers for our Production CRM 2013 On-Prem deployment and I need advise on the SSRS Servers disk size and partition.

Currently, we have 1 (Physical) SSRS Server for Prod (SSRS #1) that’s built & online with the ff. specs (see Table 1). Now, we are load balancing (NLB) the Report Servers due to our heavy reports requirements; so we're now building SSRS #2.

We're planning to put the same specs for SSRS #2 (Green highlights), but I want to make sure, so could you pls. verify and recommend correct disk size and partition for our CRM 2013 SQL Report Servers for Production with NLB.

FYI - we have ample amount of disk storage in our 2 (Physical) SQL DB Servers that are clustered where data files will be stored.

SERVER

PRODUCTION

Server Type

Building Status

  • SSRS #1

1 PhysicalSQL SERVER REPORTING SERVICES SERVER

Specs:

C:\ -- 50GB

D:\ -- 50GB

32 GB per server for Memory

(2) quadcore CPU’s.

Physical

Done & ready.

  • SSRS #2

1 VM SQL SERVER REPORTING SERVICES SERVER

[Please verify and advise on the ff. specs plan]

Specs:

C:\ -- 50GB

D:\ -- 50GB

32 GB per server for Memory

(2) quadcore CPU’s.

VM

Finalizing specs.

Table 1 -  Prod (w/ NLB) CRM 2013 SQL Report Servers Specs plan

Btw, this is a Middle Tier deployment and we're following the Middle Tier server design (see Fig. 1) from the 2.3.5 Architectural Tiers section of the document 'Deployment and Operational Guidance for Hosting Microsoft Dynamics CRM' (Microsoft_Dynamics_CRM_2013_Service_Provider.pdf) official whitepaper from MS Downloads.

And as you can see for the RAM, this meets the recommended RAM requirements (for both Middle & Upper).

Fig. 1 

Thanks!

ProgCRM


Viewing all articles
Browse latest Browse all 997

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>