Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Microsoft Windows deployment sizing


Note

For new 4.6 installations of Windows products, BMC requires:

  • Microsoft Windows Server 2012 R2 Standard Edition, Microsoft Windows Server 2012 Standard Edition 64-bit, or Microsoft Windows Server 2016 Standard Edition 64-bit as the operating system.
  • Microsoft SQL Server 2012 64-bit SP1 or SP2, Microsoft SQL Server 2014 Enterprise Edition 64-bit, or Microsoft SQL Server 2016 Enterprise Edition 64-bit as the database.

 You must consider several core technologies when sizing a BMC Cloud Lifecycle Management environment. Sizing of each product in the value path is based on the individual load the sample use case of each product. The following topics are covered in this section:

Sizing by deployment type

The following table explains the sizing requirements for each product in the solution.

Note

Some installations might have specific requirements and complexities that are not reflected here. You must account for these differences when designing a deployment. Compact Deployment is now only supported when upgrading to BMC Cloud Lifecycle Management 4.7.

Deployment type

Number of managed devices

Rate of Change (VM Create, Update, Retire)

Concurrent Cloud Admins

Concurrent Cloud End Users

Compact Deployment (if upgrading to 4.7, and using an external database)

5,000

50 per hour

5

25

Small

10,000

50 per hour

10

50

Medium

25,000

100 per hour

50

250

Application tier hardware sizing

Note

The following table does not include sizing for Compact Deployment (25 Peak Concurrent Users , 5000 VMs). You use a single VM for Compact Deployment to minimize hardware requirements. The minimum requirement for Compact Deployment is 12 VCPU 2+GHz x1, 32 GB RAM, 120 GB Disk.

The table below describes the number of nodes needed for each deployment size.

Product

Small 
50 Peak Concurrent Users 
10,000 VMs

Medium 
250 Peak Concurrent Users 
25,000 VMs

BMC AR System Server – Cloud Portal and Database (Primary)

Includes Cloud Portal AR Extensions and Cloud Database Extensions

8 CPUs 2+GHz x1  2+GHz x1 

16  GB RAM

120 HDD

10 GB Temp Space

4 VCPU 2+GHz x2 
16 GB RAM 
60 GB Disk

BMC Remedy AR System Mid Tier

4 CPUs 2+GHz x1 

8  GB RAM

120 HDD

10 GB Temp Space

4 CPUs 2+GHz x1 

8  GB RAM

120 HDD

10 GB Temp Space

BMC CMDB (formerly called Atrium Web Services)

4 CPUs 2+GHz x1

8 GB RAM

60 HDD

10 GB Temp Space

4 CPUs 2+GHz x1

8 GB RAM

60 HDD

10 GB Temp Space

Cloud Platform Manager 

8 CPUs 2+GHz x1

16  GB RAM

60 HDD

5 GB Temp Space

8 CPUs 2+GHz x1

16  GB RAM

60 HDD

5 GB Temp Space

TrueSight Server Automation Application Server and Console

8 CPUs 2+GHz x1

16  GB RAM

60 HDD

6 GB Temp Space

8 CPUs 2+GHz x1

16  GB RAM

60 HDD

6 GB Temp Space

TrueSight Server Automation File Server 

4 CPUs 2+GHz x1

8  GB RAM

200 HDD

6 GB Temp Space

4 CPUs 2+GHz x1

8  GB RAM

200 HDD

6 GB Temp Space

TrueSight Server Automation Multiple Application Server

8 CPUs 2+GHz x1

16  GB RAM

60 HDD

6 GB Temp Space

8 CPUs 2+GHz x1

16  GB RAM

60 HDD

6 GB Temp Space

TrueSight Network Automation 

4 CPUs 2+GHz x1

16  GB RAM

60 HDD

6 GB Temp Space

4 CPUs 2+GHz x1

16  GB RAM

60 HDD

6 GB Temp Space

BMC Cloud Portal Web Application (clmui)

4 CPUs 2+GHz x1

16  GB RAM

60 HDD

5 GB Temp Space

4 CPUs 2+GHz x1

16  GB RAM

60 HDD

5 GB Temp Space

BMC CLM Self-Check Monitor (optional)

2 CPUs 2+GHz x1

8  GB RAM

60 HDD

5 GB Temp Space

2 CPUs 2+GHz x1

8  GB RAM

60 HDD

5 GB Temp Space

TrueSight Orchestration (CDP) 

4 CPUs 2+GHz x1

12  GB RAM

60 HDD

10 GB Temp Space

4 CPUs 2+GHz x1

12  GB RAM

60 HDD

10 GB Temp Space

BMC AR System Server – Cloud Portal and Database – Secondary

Includes Cloud Portal AR Extensions - Secondary

8 CPUs 2+GHz x1

16  GB RAM

120 HDD

10 GB Temp Space

8 CPUs 2+GHz x1

16  GB RAM

120 HDD

10 GB Temp Space

PXE

2 CPUs 2+GHz x1

8 GB RAM

60 HDD

5 GB Temp Space

2 CPUs 2+GHz x1

8  GB RAM

60 HDD

5 GB Temp Space

TrueSight Server Automation Device Agent

2 CPUs 2+GHz x1

8  GB RAM

60 HDD

5 GB Temp Space

2 CPUs 2+GHz x1

8 GB RAM

60 HDD

5 GB Temp Space

Note

The sizing for BMC Server Automation is based on our test that does not include compliance or auditing. Compliance jobs are CPU-intensive. For the use cases that include compliance, use following table.

 

Product

Small 
50 Peak Concurrent Users 
10,000 VMs

Medium 
250 Peak Concurrent Users 
25,000 VMs

TrueSight Server Automation App Server 

8 VCPU 2+GHz  
x1  
20 GB RAM 
60 GB Disk

8 VCPU 2+GHz
x3  
20 GB RAM
60 GB Disk

Database tier hardware sizing

You might want to host product databases on single physical server or on separate servers. The decision is based on multiple factors, including, but not limited to hardware and licensing cost, performance, administration & maintenance efforts and security requirements.

This section discusses the sizing factors for hosting product databases on single versus separate servers.

Note

Physical servers are required for the database servers.  BMC recommends that you do not run databases on virtualized hardware. 

Sizing for separate database servers

Note

The following table does not include sizing for Compact. You use a single database server for Compact Deployment to minimize hardware requirements.

The following table provides the sizing guidelines for scenarios where you want to host product databases on separate servers.

Database Instance

Small

Medium

Cloud Portal and Database Server

8 CPU-Cores 2+GHz 
x1 
16 GB RAM 
Data File: 16 GB 
Log File: 3 GB

16 CPU-Cores 2+GHz 
x2 
16 GB RAM  Data File: 26 GB Log File: 3 GB

TrueSight Server Automation Database 

4 CPU-Cores 2+GHz 
x1 
8 GB RAM  
Data File: 15 GB Log File: 2 GB

8 CPU-Cores 2+GHz 
x2 
8 GB RAM  
Data File: 25 GB Log File: 2 GB

TrueSight Network Automation Database

2 CPU-Cores 2+GHz 
x1 
4 GB RAM   
Data File: 20 GB Log File: 2 GB

4 CPU-Cores 2+GHz 
x2 
8 GB RAM   
Data File: 30 GB Log File: 2 GB

Sizing for single database server

The following table provides the sizing guidelines for scenarios where you want to host product databases on single servers.

Database Instance

Compact

Small

Medium

Database Server 

Three separate database instances: 
Cloud Portal and Database Server + Atrium Web Registry 
TrueSight Server Automation Database
TrueSight Network Automation Database

8 VCPU 2+GHz x1 
16 GB RAM 
60 GB Disk

16 CPU-Cores 2+GHz x1  
32 GB RAM  
80 GB Disk

32 CPU-Cores 2+GHz x2
32 GB RAM  
120 GB Disk

Note

  • The disk size mentioned above indicates disk space consumed by the data and indexes. Include additional space for OS and other software installed.
  • Atrium Web Registry database is not very transactional in nature and hence much smaller in size.  For all Small and Medium deployments, you can install this database on the same SQL server instance.
  • The sizing above is based on benchmark tests for CLM specific use cases only
  • Transaction Log sizing is mainly driven by two factors. Customers should size transaction log files based on the following factors:
    • Database recovery model
    • DB backup strategy and frequency.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*