Dear Mangesh
topics is discussed often here. You will find lots of threads. MOst of them will have same feedback:
a.) 1. Whats is SAP best Practice to Store Report (SDS, Labels, TREM Cards) if the reports numbers is greater than 1 milion.
=> any type of WWI report or Inboudn report is stored in SAP DMS or an external archive; both options do have pros and cons; An external archive is additional hardware; you have an additional interface (data must be searched for retreived etc.); if you use SAP DMS the (this is indicated in different thread) some tables wil get huge amount of lines; if you use proper index etc. => no risk in daily business
Second: luckily you can "archive" reports outside of SAP and reduce the amount of spave nneded (this i s no the sam as to use archive link); so e.g. from time to time you could archive "historic" reports => once again you need to decide on your own what might be the best approach
Third: you can store the reports in "zipped" format in database; this reduces amount of space needed but decrease the read the performance in reading document
So many options. Any company decide on there own the right one
b.)
2. What should the server numbers ( Individual Hardware Box) for Each of the Servers (SAP Expert Server, SAP Expert Server and SAP Content Server if I am generating more than 10 report per year and shipping 5k Reports Per Year.
Expert Server;: the number of the servers is depending on the need to have "up to date" data. Here the companies are acting different; on the top with EnPack 3 you have additional options which should have positive effects on performance; some additional OSS notes increas the performance as well,
On the top: the number of servers and architecute might be linked as well to thenumber of rule sets (and complexity of them) which you would like to use; the "cost" expensive step (in reragrds of performance) is not the calculation but the read of the data => therefore check corresponing OSS notes for sizing; just try it; any company is using different approach
WWI server: same story. Here the story is "slightly" complexer, If you use EHS BD/EHS SAF only or on the top SAP EHS GLM => dependings on this the number of servers should be different (higher),
You need to differentetiate the "generation" step of WWI report and the "dispatch" part; on the top especially for SDS and similar report there are lots of options in SAP EHS to enhance/adpat/improve the existign load balancing options; for SAP EHS GLM you have no option
Content Server: in most case per system you need only one server (dev, qual, prod)
Honestly: 10 reports per year is a very very very small company; in real world you should assue of 1000 new reports generated per month; the "dispatch" pert (as part of SDS process) depends on the "success" of the company (as more sales then you would have higher need to distribute SDS to customer) Therefore 5k is a very low number (very small company)
In regards to:
1. Whats SAP Best Practice on solution Architecture for Devlopement and Quality Landscape. =>
you can use somthing like 5/3/1 relation (that means prod does have 5 times more WWI server then qual; qual does have 3 times servers than dev) => but this you need to check on your own
In regards to
2. Generally Client Copies Production Data to Quality Server whats factors should be considered in deciding server architecture for Devlopement and Quality Landscape.
Refer to the answers above; most "critical" from technical perspecitive is teh "afterwork"; after the "copy" you need to reestablish WWI farm, content farm etc. If you do not act properly Qual might "crash"
As discussed in lots of threads: EHS sizing depends on the modules you use the amount of transactions in SAP ERP, the amount and ned of data chanegs (legal changes etc.)
So sorry: there is no real answer to your questions or doughts
C.B.