Hardware requirements
As businesses continue to grow using BMC Remedy applications — for example, the full BMC Remedy IT Service Management stack including BMC Remedy AR System and BMC Atrium Core — it is critical to provide realistic hardware requirements to run these applications successfully in enterprise settings.
This topic includes:
Environment sizing
| Environment | BMC Remedy ITSM (concurrent users) | BMC Remedy Smart Reporting (concurrent users) | Number of managed devices# |
|---|---|---|---|
Proof of concept (POC) | 50 | 5 | 1,000 or fewer |
Small | 800 | 50 | 2,000 or fewer |
Medium | 2,000 | 100 | 10,000 or fewer |
Large | 5,000 | 250 | 30,000 or fewer |
#Managed devices refers to devices that have an IP address and can therefore be remotely connected to over an Ethernet network.
Recommended hardware specifications*
Click here to download a VSDX file (Microsoft Visio 2013) that contains a copy of this diagram that you can customize to your planned environment.
*The diagram displays specifications for medium environment.
BMC has published guidelines for hardware sizing based on a series of enterprise-scale tests to demonstrate the scalability and performance of the following applications:
- BMC Remedy IT Service Management Suite (BMC Remedy ITSM Suite)
- BMC Service Request Management
- BMC Atrium Configuration Management Database (BMC Atrium CMDB)
- BMC Remedy Smart Reporting
- BMC Remedy with Smart IT (Smart IT) and BMC MyIT
Carefully review the following hardware requirements for sizing.
Note
The following size estimates must be used as a starting point. You should conduct benchmarks in your environment because sizing will vary depending on your workload mix, data volumes, and data composition.
| Component | POC | Small | Medium | Large |
|---|---|---|---|---|
BMC Remedy AR System Mid Tier servers | None: Services combined with AR System server | Two servers: | Two servers: | Five servers: |
BMC Remedy AR System Web Services | None: Services combined with AR System server | One server: | One server: | Two servers: |
| BMC Remedy Single Sign-on | None: Services combined with AR System server | One Server:
| Two Servers:
| Four Servers:
|
| BMC Remedy Smart Reporting | One server: 2 CPU core 12 GB RAM 60 GB disk space | One server: 4 CPU core 12 GB RAM 200 GB disk space | Two server: | Two servers: |
BMC Remedy AR System server (user-facing) User-loaded servers | One server: | Two servers: | Three servers: | Four servers: |
BMC Remedy AR System server (back end) Non-user-loaded servers for back-end BMC Remedy AR System processes, integrations, reconciliations, and notifications | One server: | Two servers: | Two servers: | Two servers: |
| Smart IT and BMC MyIT | None: Services combined with AR System server | One Server:
| Two Servers:
| Three Servers:
|
Other deployment sizing considerations
- VChat is deployed on the same Tomcat server on which BMC Remedy AR System Mid Tier is installed.
- BMC Remedy Single Sign-on can be deployed on the same Tomcat server on which BMC Remedy AR System Mid Tier is installed. Ensure that you have adequate resources on the system to support both the applications.
- A typical MongoDB server requires three node deployment, one primary and two secondary. Another option is to deploy Mongo DB using two servers, one primary and one secondary, with an arbiter on one of the Smart IT/MyIT servers.
- For Smart IT deployment, add CPU capacity to your AR System servers as Smart IT relies heavily on full-text search (FTS), a CPU intensive process. Refer to Smart IT/My IT benchmark reports for sizing guidelines at
Smart IT 1.3 performance
or
Smart IT 1.4 performance
.
Hardware considerations for data
The disk sizes in the following table indicate the disk space that is consumed by the data and indices. Always include additional space for additional data, OS, and other software installed. You can download a copy of the planning spreadsheet by clicking here.
Consider the following points:
- Atrium Web Registry database is not transactional in nature and hence much smaller in size. For all small, medium, and large deployments, this database can be installed on the same Microsoft SQL Server instance.
- The sizing in the preceding table is based on benchmark tests for specific use cases only.
- Transaction log sizing is mainly driven by the following factors, and BMC recommends sizing transaction log files based these factors:
- Database recovery model
- Database backup strategy and frequency
Database tier sizing requirements
Note:
The following size estimates must be used as a starting point. You should conduct benchmarks in your environment because sizing will vary depending on your workload mix, data volumes, and data composition.
Component | POC | Small | Medium | Large |
|---|---|---|---|---|
Master BMC Remedy AR System Database | 1 server: | One cluster: | One cluster: | One cluster: |
Replicated BMC Remedy AR System Database for Reporting | None: Services combined with AR System database | One server: | One server: | One server: |
| Mongo DB (social database for Smart IT and MyIT) | -- | Two Servers: 2 CPU core | Two Servers: 4 CPU core | Three Servers: 4 CPU core |
The BMC Performance Lab conducted a set of online and batch workloads to benchmark the performance and scalability of the BMC IT Service Management Suite and to characterize the system behavior under various workload conditions. The supporting environment and IT infrastructure used for these workloads were constructed to reflect the typical deployment architecture. For more information, see 2019-01-22_00-11-16_Benchmark summary .
Related topics
Software dependencies for BMC Remedy AR system
2019-01-22_00-13-54_Benchmarking results for BMC Remedy Single Sign-on
Comments
Can't access the Sizing and deployment link on the Related Topics. get the following message:
Page level restrictions have been applied to a parent of the current page. These restrictions limit access to certain user(s) or group(s) and apply to all pages underneath the parent.
Hello Diego,
We are looking into the issue and will get back to you soon.
Thanks,
Bhakti
Could you please update the hardware requirements to include Smart reporting feature? or where I can find the sizing with SmartReporting.
Thanks
Does BMC have any recommendation on CPU clock speed/generation? The installer says a minimum of 2.8 GHz CPU is required but I couldn't find any reference of such a requirement on the BMC doco. Can this be included on this page??
Hi Sandeep,
We don't have recommendations documented. For guidance on such information, please refer to the following section:
https://docs.bmc.com/docs/display/public/brid90/BMC+Remedy+ITSM+Suite+9.0.01+Solution+Performance+Benchmarks
Regards,
Hemant
Hi Hemant,
I do not have access to the link you shared. Remedy 9 benchmark pages have no information on CPU generation/type. Just clock speed is meaningless on its own. If there is no minimum CPU requirement, it should be explicitly stated. We do not want to build an environment and find out our CPUs did not meet vendor recommendation.
Hi Sandeep,
You should be able to see the topic now.
Regards,
Hemant
Good day all,
I'm trying to find the documentation stating the requirements for virtualized on-premise environments regarding the disk provisioning. i.e. Is thick provisioning required or is thin provisioning also supported in production implementations. According to CLM 4.5: "https://docs.bmc.com/docs/display/public/clm45/Manually+installing+BMC+Small+RDS":
"NFS supports thin-provisioning only on newer NAS devices and you should avoid this for this implementation."
And then "Deploying the images to the vCenter" step 6 states you should select thin provisioning
Thus I assume it is supported. Is there official documentation I can refer to regarding the provisioning for ARS (and/or ITSM with Smart IT)?
HI Wallace,
You might the information in the following section:
https://docs.bmc.com/docs/display/public/brid90/BMC+Remedy+ITSM+Suite+9.0.01+Solution+Performance+Benchmarks
Smart IT 1.2 performance
Thanks,
Hemant
under "Recommended production deployment of applications and hardware" there is a diagram in which there clearly 3 mid-tier servers and it even states '3 mid-tiers' but in none of POC, Small, Medium or Large environments state 3 mid-tiers are needed... this diagram should match up with one of the recommended environments or else it's confusing.
Under Data considerations you mention Atrium Webservices Registry. Afaik WS Registry 9 does not use any DB space. Smart Reporting does use its own DB space but is not mentioned.
Hello Joachim,
Thanks for writing to us.
In our POC, Smart Reporting points to the BMC Remedy AR System database and the sizing details have accordingly been mentioned in the Database tier table just underneath the bulleted list that mentions Atrium Web Registry.
Regards,
Amit
Hello Amit! Thanks for your reply. SmartReporting has its own database for configuration data (and cache?). Even if the db is small it should be mentioned.
Hello Jaochim,
Sorry for the delay in response. I am working with the concerned SMEs to get the details specific to Smart Reporting.
Regards,
Amit
Where are the details on Remedy SSO, i'm looking for Remedy SSO not Atrium SSO and i cannot find a simple satement on the hardware requirements for this. I want to be able to cost out a HA scenario as well as a PoC. I thought I'd seen this but i can't find it now. Thanks
Hello Stephen,
Sorry about this! We are in the process of updating this document. RSSO sizing considerations is on our list of components for which the information has to be included. I will notify you as soon as we have the information.
Regards,
Amit
Hello Stephen,
We have performance bench marking results conducted on a clustered environment for BMC Remedy Single Sign-on 9.0.01 available at https://docs.bmc.com/docs/display/public/brid90/BMC+Remedy+Single+Sign-on+9.0.01
Hope this helps.
Regards,
Amit
Hello Stephen,
We have updated RSSO sizing information.
Regards,
Amit
Hello,
I saw, in the first table (last column) a term that is confusing : Managed Devices.
Considering that we are not talking about monitoring can you please explain what this term mean?
I need this for an urgent RFP where the sizing is a very delicate subject..
Thank you
Rodian
Hello Rodian,
The number of managed devices refers to configuration items such as computer systems, printers, network devices in your environment.
"The term managed device has historically referred to devices that have an IP address and can therefore be remotely connected to over an Ethernet network"
Regards,
Amit