Epicor for Manufacturing

Kinetic Hardware
Sizing Guide
Epicor for Manufacturing

Contents
Hardware Sizing for up to 15-User Load......................................................................4
Application Usage Load Expectation for up to 15-User Load......................................5
Hardware Sizing for up to 50-User Load......................................................................6
Application Usage Load Expectation for up to 50-User Load......................................7
Hardware Sizing for up to 200-User Load....................................................................8
Application Usage Load Expectation for up to 200-User Load....................................9
APP01–Application Server/Virtual Host/Reporting Server.......................................10
SQL Server (SQL01).....................................................................................................11
Hardware Sizing for 1,000–4,000 Users......................................................................12
Scale-Out Configurations...........................................................................................13
Virtualizing Kinetic......................................................................................................14
Kinetic—Virtual Appserver on VMware® ....................................................................14
Kinetic—Virtual Appserver on Hyper-V .....................................................................15
Kinetic—Virtual SQL Server on VMware ....................................................................16
Kinetic—Virtual SQL Server on Hyper-V ...................................................................17
Kinetic Appserver .......................................................................................................18
Kinetic SQL Server ......................................................................................................18
Footnotes for Tables 14 and 15 ..................................................................................18
Hardware Requirements for Other Epicor Systems ..................................................19
Other Epicor Systems .................................................................................................20
Epicor Virtual Agent (EVA) ..........................................................................................22
Network.......................................................................................................................23
Hardware recommendations ....................................................................................23
Network bandwidth ...................................................................................................23
Network latency .........................................................................................................23
Remote client bandwidth ..........................................................................................23
Backup and Fault Tolerance UPS ..............................................................................24
Appendix.....................................................................................................................25

2 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Introduction
Welcome to the Kinetic Hardware Sizing Guide. The goal of this guide is to provide a
practical approach to sizing your Kinetic application and database server to obtain
the best performance possible from your Epicor software. It will also help you plan
for the future growth of your system.

The key to success in getting your hardware sized correctly is to define your
application load correctly and then to match it with the appropriate hardware
resources. Choosing a hardware architecture that can grow as your business and/or
application load grows is also important.

It is very difficult to accurately present a hardware recommendation that matches

your unique application usage. Many of our customers find this guide very useful
and accurate after they have followed all the steps described here. There are cases
where the provided recommendations may fall short of a company’s needs, so
please note these are general guidelines that should be tailored to your specific
business requirements. To improve the odds of success, we highly recommend that
you work with the Epicor technical solutions group and implement their hardware
sizing recommendations.

This guide is meant for customers buying new hardware and software, so we
recommend choosing the latest software versions supported by Kinetic. If you
want to determine if other versions of software are supported, contact Epicor
technical support.

Please note that you should consult Epicor technical services for high-availability
and business-continuity customer requirements as this sizing guide does not
cover these topics.

Kinetic Hardware Sizing Guide | 3

Epicor for Manufacturing

Hardware Sizing for up to 15-User Load

Table 1

Kinetic physical server. This configuration can support standard load of 15 Office + data
Small ERP
collection users. See table 2 for the definition of standard load.

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
OS Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

SQL Server® 2022 - Kinetic 2023.1 and above | (11.2.300 and above)
SQL SQL Server 2019 - (10.2.600 and above)
SQL Server 2017 - (10.2.200 and above)

Applications Kinetic, Epicor Web Access (EWA), Enterprise Search (ES)

1 x CPU Socket recommendations (or newer version of similar specifications)

• Latest available Intel Xeon or AMD processors with 16 Cores or more.

Processors
We recommend leaving Hyper-Threading enabled (check BIOS settings).
Disable Power Saving options and C-States in BIOS.
Enable Turbo Boost.

Memory (RAM) 32 GB ECC

2 x 300GB 15K RPM HDDs [or SSDs] in RAID 1, 12 Gbps

4 x 400GB SSDs in RAID 1 or 10, 6 Gbps Operating system and page file on HDD SQL Database and
Storage Option #1—HDD reports on SSDs.
and SSD (Recommended)
Note: MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting better by the day, if
you maintain a warranty coverage on Enterprise MLC SSDs then you can purchase MLCs.

To find out if your SAN delivers sufficient performance for SQL database, see the “Testing the
performance of an existing SAN” section in the Appendix for details on how to run a storage
benchmarking tool (Diskspd).
Storage Option #2 Required Diskspd results at all times including during peak load from other application
(you can use this option if your usage on the SAN:
SAN passes the Diskspd® test)
Database drive letter (location of SQL .mdf file): Must be able to deliver at least 100MB/sec at a
Existing Storage latency of less than 5ms.
Area Network (SAN)
Transaction log drive letter (location of SQL log file): Must be able to deliver at least 30MB/sec at a
latency of less than 5ms.
Tempdb drive letter (location of SQL temp db file):

4 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Application Usage Load Expectation for up to 15-User Load

Table 2

Load Expectation for up to 15-user-load (Small ERP)

Application Usage Load Description

Typical application usage by end-users using Kinetic via Smart Client and/or browser and/or
Interactive Application Load
mobile devices.

Automation and
Heavy Processing
If you are processing more than 25,000 transactions (insert, update, or delete) in any one-hour
1. Epicor Service Connect (ESC) period of the working day, then schedule this activity to a less busy time of the day. 25,000
2. Imports (e.g. PO, Sales Order, transactions is the sum total of all sources of automatic processing.
AR Invoice, and Shipping) If this activity cannot be scheduled to a less busy time of the day, please discuss the server sizing
3. Automatic updating of data with Epicor technical services.
not covered by ESC Heavy and concurrent reporting should be scheduled to a less busy time of the day or on a
4. Heavy Reporting separate reporting appserver.

5. DMT imports

Custom Code
In-house custom application
running on Kinetic machine No (If yes then discuss the increase in usage with Epicor technical services)
and/or using Kinetic
database and/or Kinetic
appserver directly

MRP regeneration will be scheduled during less busy times. For daily MRP runs, use
MRP
MRP net change.
(Manufacturing customers)
If your business requires you to run more than 2 processes and 2 schedulers for MRP run, discuss
the increased usage with Epicor technical services.

Growth and
Acquisition of New Users No

Seasonal Peaks No

Kinetic Hardware Sizing Guide | 5

Epicor for Manufacturing

Hardware Sizing for up to 50-User Load

Table 3

Kinetic Physical Server. This configuration can support standard load of 50 Office + Data
Medium ERP
collection users. See table 4 for the definition of standard load.

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
OS Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and abo

SQL Server® 2022 - Kinetic 2023.1 and above | (11.2.300 and above)
SQL SQL Server 2019 - (10.2.600 and above)
SQL Server 2017 - (10.2.200 and above)

Applications Kinetic, Epicor Web Access (EWA), Enterprise Search (ES)

1 x CPU socket recommendations:

• Latest available Intel Xeon or AMD processors with 16 Cores or more.

Processors
We recommend to leave Hyper-Threading enabled (check BIOS settings).
Disable Power Saving options and C-States in BIOS.
Enable Turbo Boost.

Memory (RAM) 64 GB ECC

2 x 300GB 15K RPM HDDs [or SSDs] in RAID 1, 12 Gbps

4 x 400GB SSDs in RAID 1 or 10, 6 Gbps Operating system and page file on HDD SQL Database and
Storage Option #1—HDD reports on SSDs.
and SSD (Recommended)
Note: MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting better by the day, if
you maintain a warranty coverage on Enterprise MLC SSDs then you can purchase MLCs.

To find out if your SAN delivers sufficient performance for SQL database, see the “Testing the
performance of an existing SAN” section in the Appendix for details on how to run a storage
benchmarking tool (Diskspd).

Storage Option #2 Required Diskspd results at all times including during peak load from other application
(you can use this option if your usage on the SAN:
SAN passes the Diskspd® test) Database drive letter (location of SQL .mdf file): Must be able to deliver at least 100MB/sec at a
Existing Storage latency of less than 5ms.
Area Network (SAN) Transaction log drive letter (location of SQL log file): Must be able to deliver at least 30MB/sec at a
latency of less than 5ms.
Tempdb drive letter (location of SQL temp db file): Must be able to deliver at least 50MB/sec at a
latency of less than 5ms.

6 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Application Usage Load Expectation for up to 50-User Load

Table 4

Load Expectation for up to 50-user-load (Medium ERP)

Application Usage Load Description

Typical application usage by end-users using Kinetic via Smart Client and/or browser and/or
Interactive Application Load
mobile devices.

Automation and
Heavy Processing
If you are processing more than 50,000 transactions (insert, update, or delete) in any one-hour
1. Epicor Service Connect (ESC) period of the working day, then schedule this activity to a less busy time of the day. 50,000
2. Imports (e.g. PO, Sales Order, transactions is the sum total of all sources of automatic processing.
AR Invoice, and Shipping) If this activity cannot be scheduled to a less busy time of the day, please discuss the server sizing
3. Automatic updating of data with Epicor technical services.
not covered by ESC Heavy and concurrent reporting should be scheduled to a less busy time of the day or on a
4. Heavy Reporting separate reporting appserver.

5. DMT imports

Custom Code
In-house custom application
running on Kinetic machine No (If yes then discuss the increase in usage with Epicor technical services)
and/or using Kinetic
database and/or Kinetic
appserver directly

MRP regeneration will be scheduled during less busy times. For daily MRP runs, use
MRP
MRP net change.
(Manufacturing customers)
If your business requires you to run more than 3 processes and 3 schedulers for MRP run, discuss
the increased usage with Epicor technical services.

Growth and
Acquisition of New Users No

Seasonal Peaks No

Kinetic Hardware Sizing Guide | 7

Epicor for Manufacturing

Hardware Sizing for up to 200-User Load

Table 5

Kinetic Physical Server Machine. This configuration can support standard load of 200 Office +
ERP Server
Data collection users. See table 6 for the definition of standard load.

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
OS Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

SQL Server® 2022 - Kinetic 2023.1 and above | (11.2.300 and above)
SQL SQL Server 2019 - (10.2.600 and above)
SQL Server 2017 - (10.2.200 and above)

Applications Kinetic, Epicor Web Access (EWA), Enterprise Search (ES)

2 x CPU socket recommendations:

• Latest available Intel Xeon or AMD processors with 16 Cores or more.
Processors
It is recommended to leave Hyper-Threading enabled (check BIOS settings). Disable Power
Saving options and C-States in BIOS. Enable Turbo Boost.

Memory (RAM) 96 GB ECC

Operating system and page file: 2 x 15K HDDs [or SSDs] in RAID 1. SQL database (MDF file): 4 x
Solid State Drive in RAID 10 PCIe SSD should hold SQL database (MDF file), SQL transaction log
(LDF file), and SQL tempdb files. Epicor Reports—2 x 15K HDDs [or SSDs] in RAID 1
Storage Option #1—HDD
Total:
and SSD (Recommended)
• 4 x 15K RPM HDDs [or SSDs] (3 Gbps SATA or SAS)
• Quantity 1, at least 785 GB, PCIe SSD card

Operating system and page file: 2 x 400 Solid State Drive in RAID 1. SQL transaction log (LDF file):
2 x 400 Solid State in RAID 1.(Only Epicor SQL Log file on this drive) SQL database (MDF file), SQL
Storage Option #2—
tempdb and Reports: 4 x 400 Solid State Drive in RAID 1. (This will house at least 8 tempdb files)
SSD (Recommended)
Solid State Drive (SAS/ Total Drives—8 Solid State Drives
SATA based) storage Note: MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting better by the day, if
you maintain a warranty coverage on Enterprise MLC SSDs then you can purchase MLCs.

To find out if your SAN delivers sufficient performance for SQL database, see the “Testing the
performance of an existing SAN” section in the Appendix for details on how to run a storage
benchmarking tool (Diskspd).
Storage Option #2— Required Diskspd results at all times including during peak load from other application usage on
SSD (Recommended) the SAN: Database drive letter (location of SQL .mdf file): Must be able to deliver at least 100MB/
Solid State Drive (SAS/ sec. at a latency of less than 5ms.
SATA based) storage Transaction log drive letter (location of SQL log file): Must be able to deliver at least 30MB/sec. at
a latency of less than 5ms.
Tempdb drive letter (location of SQL temp db file): Must be able to deliver at least 50MB/sec. at a
latency of less than 5ms.

8 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Application Usage Load Expectation for up to 200-User Load

Table 6

Load Expectation for up to 200-user-load (ERP Server)

Application Usage Load Description

Typical application usage by end-users using Kinetic via Smart Client and/or browser and/or
Interactive Application Load
mobile devices.

Automation and
Heavy Processing
If you are processing more than 100,000 transactions (insert, update, or delete) in any one-hour
1. Epicor Service Connect (ESC) period of the working day, then schedule this activity to a less busy time of the day. 100,000
2. Imports (e.g. PO, Sales Order, transactions is the sum total of all sources of automatic processing.
AR Invoice, and Shipping) If this activity cannot be scheduled to a less busy time of the day, please discuss the server sizing
3. Automatic updating of data with Epicor technical services.
not covered by ESC Heavy and concurrent reporting should be scheduled to a less busy time of the day or on a
4. Heavy Reporting separate reporting appserver.

5. DMT imports

Custom Code
In-house custom application
running on Kinetic machine No (If yes then discuss the increase in usage with Epicor technical services)
and/or using Kinetic
database and/or Kinetic
appserver directly

MRP regeneration will be scheduled during less busy times. For daily MRP runs, use
MRP
MRP net change.
(Manufacturing customers)
If your business requires you to run more than 6 processes and 6 schedulers for MRP run, discuss
the increased usage with Epicor technical services.

Growth and
Acquisition of New Users No

Seasonal Peaks No

Kinetic Hardware Sizing Guide | 9

Epicor for Manufacturing

APP01–Application Server/Virtual Host/Reporting Server

Table 7

Application Server APP01

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
Operating System Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

Applications Kinetic, Epicor Web Access (EWA), Enterprise Search (ES)

2 x CPU socket recommendations:

• Latest available Intel Xeon or AMD processors with 16 Cores or more.

Processors
It is recommended to leave Hyper-Threading enabled (check BIOS settings).
Disable Power Saving options and C-States in BIOS.
Enable Turbo Boost.

Memory (RAM) 64 GB ECC

Operating system: 2 x 15K RPM HDDs [or SSDs] in RAID 1.

The following files are stored in 2 x SSDs in RAID 1:

• Kinetic files
Solid State Drive • Reports and temporary data (EpicorData)
(SAS/ SATA based) • Two SSDs are required.
storage (recommended)
• Two SCSI/SAS HDDs are required.

When using this configuration as virtual host, buy enough disk space for all VMs that will be
running on this host.

For good network performance, use 1-Gigabit (or faster) network cards.
To ensure that network latency is as low as possible between the Epicor application server and
the SQL database server, add at least two network cards:

Network • One dedicated network card that is directly connected to the SQL database (Cable from
network card to network card).
• One dedicated network card that is connected to the LAN (and is processing all network traffic
except SQL database traffic).

10 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

SQL Server (SQL01)

Table 8

SQL Server—SQL01

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
OS Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

SQL Server® 2022 - Kinetic 2023.1 and above | (11.2.300 and above)
SQL SQL Server 2019 - (10.2.600 and above)
SQL Server 2017 - (10.2.200 and above)

Applications Kinetic, Epicor Web Access (EWA), Enterprise Search (ES)

2 x CPU socket recommendations:

• Latest available Intel Xeon or AMD processors with 16 Cores or more.

Processors
Disable Power Saving options and C-States in BIOS.
Enable Turbo Boost.

Memory (RAM) 128 GB ECC

Operating system: 2 x 15K RPM HDDs [or SSDs] in RAID 1

PCIe SSD should hold SQL database (MDF file), SQL transaction log (LDF file) and
Storage Option #1—PCIe SQL tempdb files.
SSD (Recommended)
Epicor Reports—2 x 15K HDDs [or SSDs] in RAID 1 Total
PCIe based card e.g. Fusion-IO
• 4 x 15K RPM HDDs [or SSDs] (12 Gbps SATA or SAS)
• 1 PCIe SSD card

Operating system and page file: 2 x 400 Solid State Drive in RAID 1
SQL transaction log (LDF file): 2 x 400 Solid State in RAID 1.(Only Epicor SQL Log file on this drive)
Storage Option #2—SSD
Solid State Drive (SAS/ SQL database (MDF file), SQL tempdb and Reports: 4 x 400 Solid State Drive in RAID 1. (This will
SATA based) storage house at least 8 tempdb files) Epicor Total drives—8 Solid State Drives (3 Gbps SATA or SAS)
Note: MLCs are cheaper than SLCs. SLCs are more reliable. MLCs are getting better by the day, if
you maintain a warranty coverage on Enterprise MLC SSDs then you can purchase MLCs.

To find out if your SAN delivers sufficient performance for SQL database, see the “Testing the
performance of an existing SAN” section in the Appendix for details on how to run a storage
benchmarking tool (Diskspd).
Storage Option #3 (you can use Required Diskspd results at all times including during peak load from other application
this option if your SAN passes usage on the SAN:
the Diskspd test) Database drive letter (location of SQL .mdf file): Must be able to deliver at least 100MB/sec. at a
Existing Storage latency of less than 5ms at all times.
Area Network (SAN) Transaction log drive letter (location of SQL log file): Must be able to deliver at least 30MB/sec. at
a latency of less than 5ms at all times.
Tempdb drive letter (location of SQL temp db file): Must be able to deliver at least 50MB/sec. at a
latency of less than 5ms at all times.

Kinetic Hardware Sizing Guide | 11

Epicor for Manufacturing

Table 8 (Cont)

For good network performance, use 1-Gigabit (10G card for a user load of 500 user or
higher) network cards.
To ensure that network latency is as low as possible between the Epicor application server and
the SQL database server, add at least two network cards:
Network (between SQL Server
and appserver(s))
• One dedicated network card that is directly connected to the SQL database (cable from
network card to network card).
• One dedicated network card that is connected to the LAN (and is processing all network traffic
except SQL database traffic).

Hardware Sizing for 1,000–4,000 Users

Table 9

Physical Servers Up to 2,000 Users Up to 4,000 Users

Interactive Appserver 1 x APP01 2 x APP01

SQL Server 1 x SQL01 1 x SQL01

Appserver for Reporting and

1 X APP01 1 X APP01
Integration Services

Load Balancer N/A F5 switch or KEMP LoadMaster

12 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Scale-Out Configurations

Load Balancer 4,000 Concurrent Users

Interactive Application
Servers (Qty: 2x APP01)

Reporting and
Integration Application
Servers (Qty: 1x APP01)

SQL Database Server

(Qty: 1x SQL01)

Kinetic Hardware Sizing Guide | 13

Epicor for Manufacturing

Virtualizing Kinetic
Kinetic—Virtual Appserver on VMware®
Table 10

VMWAREAPP01

Host Software VMwarevSphere or Hyper V

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
Guest OS Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

4 virtual CPUs

Virtual CPU Count Create a full CPU reservation to ensure that the virtual machine has dedicated access to
physical CPU cores.
It is not recommended to overcommit CPU resources.

20 GB (reserved RAM)
It is not recommended to overcommit memory resources. If needed, disable Memory
Memory (RAM)
Ballooning so that the virtual application server has a dedicated amount of RAM.
Ensure that the RAM on the host supports ECC.

Physical CPU Requirements

See APP01
(host requirements)

Use Thick Provisioning and ensure that Eager Zeroing is in use.

Virtual Hard Disk
(Optional) Enable Storage I/O Control (SIOC) and set the threshold to 25ms.

Virtual Hard Disk Controller Use the Paravirtual SCSI adapter.

Guest OS
Install and use the latest VMware Tools.
Virtualization Software

Ensure that the physical host has multiple physical network cards which are all utilized by the
hosted virtual machines.
Network
Use the VMXNET3 virtual network card

Load Balancing Physical load balancing appliance recommended like F5 switch or Kemp LoadMaster.

VM Backup Software VM level snapshot backup works for Kinetic.

File-level backups are supported.

14 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Kinetic—Virtual Appserver on Hyper-V

Table 11

VMWAREAPP01

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
Host Software Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

SQL Server® 2022 - Kinetic 2023.1 and above | (11.2.300 and above)
Guest OS SQL Server 2019 - (10.2.600 and above)
SQL Server 2017 - (10.2.200 and above)

4 virtual CPUs
Create a full CPU reservation to ensure that the virtual machine has dedicated access to
Virtual CPU Count
physical CPU cores.
It is not recommended to overcommit CPU resources.

20 GB (reserved RAM)
Select Static memory when you allocate memory to the virtual machine. It is not
Memory (RAM)
recommended to overcommit memory resources.
Ensure that the RAM on the host supports ECC.

Physical CPU Requirements

See APP01
(host requirements)

Virtual Hard Disk Use fixed-size virtual hard disks

Virtual Hard Disk Controller • Use the IDE Controller option for the virtual hard disk that contains the OS.
• Use the SCSI Controller option for all other virtual hard disks.

Guest OS
Install and use the latest Integration Services.
Virtualization Software

Network Use the Network Adapter virtual network card (and not the Legacy Network Adapter).

Physical load balancing appliance recommended, though software-based works,

Load Balancing too. Use Multicast Mode if you are using Microsoft® Network Load Balancing (NLB).
This is recommended for stability reasons.

VM level snapshot backup works for Kinetic.

VM Backup Software
File-level backups are supported.

Kinetic Hardware Sizing Guide | 15

Epicor for Manufacturing

Kinetic—Virtual SQL Server on VMware

Virtualization of SQL Server takes careful planning and appropriate resources to optimize performance.
You should work with the Epicor Technical Services Group or Hardware Sales Team to develop and approve a SQL
virtualization plan.

Table 12

VMWARESQL01

Host Software VMwarevSphere or Hyper V

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
Guest OS Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above)

Minimum 4 virtual CPUs, increase vCPU count as dictated by the load

Create a full CPU reservation to ensure that the virtual machine has dedicated access to
Virtual CPU Count
physical CPU cores.
It is not recommended to overcommit CPU resources.

24 GB (reserved RAM)
It is not recommended to overcommit memory resources.
Memory (RAM)
If needed, disable Memory Ballooning so that the virtual application server has a
dedicated amount of RAM.
Ensure that the RAM on the host supports ECC.

Physical CPU Requirements

See SQL01
(host requirements)

Use Thick Provisioning and ensure that Eager Zeroing is in use.

Virtual Hard Disk
(Optional) Enable Storage I/O Control (SIOC) and set the threshold to 25ms.

Virtual Hard Disk Controller Use the Paravirtual SCSI adapter.

Guest OS
Install and use the latest VMware Tools.
Virtualization Software

Ensure that the physical host has multiple physical network cards which are all utilized by the
Network
hosted virtual machines.
Use the VMXNET3 virtual network card.

VM level snapshot backup works for Kinetic. When you virtualize SQL Server be sure
VM Backup Software to test and make sure differential backup works correctly in your case.
File-level backups are supported.

16 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Kinetic—Virtual SQL Server on Hyper-V

Virtualization of SQL Server takes careful planning and appropriate resources to optimize performance.
You should work with the Epicor Technical Services Group or Hardware Sales Team to develop and approve a SQL
virtualization plan.

Table 13

HYPERVSQL01

Windows® Server 2022 - Kinetic 2022.1 and above | (11.2.100 and above)
Host Software Windows Server 2019 - (10.2.400 and above)
Windows Server 2016 - (10.1.500.9 and above

SQL Server® 2022 - Kinetic 2023.1 and above | (11.2.300 and above)
Guest OS (Recommended) SQL Server 2019 - (10.2.600 and above)
SQL Server 2017 - (10.2.200 and above)

Minimum 4 virtual CPUs, increase vCPU count as dictated by the load

Create a full (100%) virtual machine reserve to ensure that the virtual machine has dedicated
Virtual CPU Count
access to physical CPU cores.
It is not recommended to overcommit CPU resources.

24 GB (reserved RAM)
Memory (RAM) Select Static memory when you allocate memory to the virtual machine. It is not
recommended to overcommit memory resources.
Ensure that the RAM on the host supports ECC.

Physical CPU Requirements

See SQL01
(host requirements)

Virtual Hard Disk Use fixed-size virtual hard disks

Virtual Hard Disk Controller • Use the IDE Controller option for the virtual hard disk that contains the OS.
• Use the SCSI Controller option for all other virtual hard disks.

Guest OS
Install and use the latest Integration Services.
Virtualization Software

Network Use the Network Adapter virtual network card (and not the Legacy Network Adapter).

VM-level snapshot backup works for Kinetic. When you virtualize SQL Server be sure
VM Backup Software to test and make sure differential backup works correctly in your case.
File-level backups are supported.

Kinetic Hardware Sizing Guide | 17

Epicor for Manufacturing

Kinetic Appserver
1 application pool per VM, 1 Epicor ERP 10 appserver per application pool.

Table 14
Epicor ERP
Integration #vCPU Total RAM (GB) Disk OS 10 App Data
#Users Interactive Reporting EDI/Imports Total VM per VM vCPU per VM (GB) per VM Disk(GB)
per VM

15 1 0 0 1 4 4 20 60 40
50 1 1 0 2 4 8 20 60 40
100 1 1 1 2 8 16 20 60 40
200 2 1 1 4 8 32 20 60 40
400 3 2 1 6 8 48 20 60 40
500 4 2 2 8 8 64 20 60 40

Kinetic SQL Server

Table 15

#vCPU Disk OS SQL Database Size (GB) (You will need 40% for data,
#Users # of VM RAM (GB) Total VM
per VM (GB) 20% for log file, and 40% for temp db)

15 1 4 24 1 60 150
50 1 4 48 2 60 175
100 1 8 64 2 60 200
200 1 12 80 4 60 300
400 1 16 100 6 60 400
500 1 16 128 8 60 600

Footnotes for Tables 14 and 15

1. 200+ users—Add a second SQL server for SSRS®.Sizing of the SSRS SQL Server will be similar to the E10.Consult with Epicor technical
services if a separate SSRS Server is a right choice for your business.
2. 100+ users installation, highly recommended that you involve Epicor technical services.It is recommended that Epicor technical services
perform an infrastructure analysis.
3. Integrations—If you process a lot of EDI transactions and/or do heavy imports and/or do lots of automations into Kinetic, add an integration
appserver even if the Table 14 says zero.
4. SQL Database Disk Size—If you already have an SQL database and know the size and/or know the size and growth factors then use estimates
based on your experience.Discuss the actual disk size with Epicor technical services in case you need further help.
5. Above 500 users use table 14 and 15 and extrapolate the sizing.It is also recommended that you work with Epicor technical services on the
deployment architecture.
6. All SQL Server database drives should pass the Diskspd test described in the appendix.

18 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Hardware Requirements for Other Epicor Systems

Epicor client machine/Epicor workstation
For desktop/network clients, keep in mind that other installed applications, specifically Microsoft products, have
requirements of their own over and above the requirements for Epicor ERP 10. The Epicor client will perform better
on workstations that have sufficient memory and processor power to run all your applications.

Table 16

Recommended Configuration

Operating System Windows 10, 11

2.8 GHz or higher. Recommended 32-bit or 64-bit processor and SATA hard drives. SSD is
Processor
especially beneficial if the workstation runs multiple applications at the same time.

RAM 4 GB (add more RAM if the workstation is shared by multiple applications)

Disk Space for Epicor

2 GB
Smart Client Software

Monitor SVGA or higher adapter Color SVGA monitor with 1024 x 768 resolution

DVD-R DVD-R drive (if not on server)

Other Internet connection recommended for online support and downloading latest updates

Kinetic Hardware Sizing Guide | 19

Epicor for Manufacturing

Other Epicor Systems

Table 17

System Type Hardware Description

Remote Desktop Services For every 100 users, use server configuration

Epicor Service Connect 1 x VMWAREAPP01 OR 1 x HYPERVAPP01

Depending on load either use

EPM
1 x SQL01 or 1 x Medium ERP configuration

AFR 1 x VMWAREAPP01 OR 1 x HYPERVAPP01

Device Requirements

• Screen size minimum of 240 x 320

Handheld Equipment • Device must support MS Terminal Services client
• IEEE 802.11 Radio Frequency standards support Access Points IEEE 802.11 Radio Frequency
standards support
• Software: Requires Windows 2012 RDS CALs license
• Handheld MES no longer supported

Barcode Equipment Support for Bar 39 Barcode

Pioneer® POS StealthTouch M5

MES Workstation
Same configuration as Epicor workstation (Table 11)

At least one laser printer required for standard reports and forms
Printer
Must have current Windows driver

If you have purchased any other software license from Epicor, please work with the Epicor
Hardware for any other system? technical solutions or Epicor hardware sales group to see if you need extra servers to run them.
Some applications can be installed on one shared server.

An Internet connection is required to access the Epicor Online Support Center for interim and
Communications
commercial releases and remote support. DSL or higher-quality connection recommended.

20 | Kinetic Hardware Sizing Guide

Epicor for Manufacturing

Table 18

Mobile Compatibility Configuration

• Kinetic 2021.2 and up | (11.1.200 and up)

• Mobile:
Time and Expense • Android 8+
• iOS 11+

• Kinetic 2021.2 and up | (11.1.200 and up)

• Mobile:
CRM • Android 8+
• iOS 11+

Any device that meets the system specs detailed above is optimum for using our apps.
Some specific recommendations are included below.

• Recommended Android Devices:

• Samsung Galaxy 21+ and their variants
• Samsung Galaxy Tab S8+
Device Recommendations • Pixel 6+ and their variants
• Recommended IOS Devices:
• iPhone12+ & their variants
• iPad 10.2+
• iPad Air
• Brands Not Recommended
• Huawei

21 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Epicor Virtual Agent (EVA)

Mobile device compatibility configurations.

Table 19

EVA for Android Configuration

Google Store Link https://play.google.com/store/apps/details?id=com.epicor.eva&hl=es_SV

Android Support all “active” (maintained) versions of Android

Available Size 15 mb

RAM 1 GB

EVA for iOS Configuration

Google Store Link https://apps.apple.com/us/app/epicor-virtual-agent-eva/id1453584162

iPhone iOS 11 or later

iPad iOS 11 or later

Available Size 15 mb

RAM 1 GB

Kinetic Hardware Sizing Guide | 22

 Epicor for Manufacturing

Network
Hardware recommendations Network latency
For the connectivity between the Kinetic application Network bandwidth is not the only factor that
server and the SQL Server a 1-Gbit (or faster) network determines the “speed” of a network as perceived by the
is recommended. In some cases a 10-Gbit network end user. The other key element of network performance
connection will provide additional benefit. Fiber is latency. While it would often appear that data is
optic cable recommended in environment with transmitted instantly between one point and another
electrical noise. (that is, with no delay at all), this is typically not the case.
Network latency may be caused by:
When designing the network, try to minimize the latency
(one way to measure latency is ping time) between • The time it takes for a packet to travel from
the Kinetic Smart Client workstations and Kinetic EWA point to point
Server and the Kinetic application server box. For • The transmission medium (optical fiber, wireless, etc.)
example, users having a 125ms ping time will see slower may introduce some delay because larger packets
response than the users having a ping time of 25ms typically take longer to move from place to place
between the workstation and the application server box. • Routers and other processing points each take time to
There should be almost no latency between SQL Server examine and possibly make changes to packet header
and the appserver(s). • Intermediate devices such as switches and bridges
may cause delays
WAN accelerator—Consider implementing WAN
accelerators on both sides of a WAN if you get It is often difficult to diagnose a network bandwidth
environments with high latency and/or low bandwidth. or latency issue, and this is best left to professional
network analysts.
If using Kinetic from a wireless network, make sure
that your hardware switch or router provides good Remote client bandwidth
performance and has error correction/prevention As a general rule, the Kinetic Smart Client and Kinetic
measures built in—a 800.11ac or better hardware EWA Client has a bandwidth requirement of 10 Kbps
is recommended. (Kilobits per second) to 500Kbps. For a typical use
that does not require large dataset (above 100 rows
Network bandwidth or a five-page report), the Kinetic Smart Client uses
The bandwidth of a network defines the amount of 12 Kbps bandwidth. This will vary depending on the
data that can be transferred across the network at volume of data transferred between the client and the
once. If the bandwidth of the network is insufficient for server. Additionally, file attachments require increased
the amount of information being transmitted (usually bandwidth as well as the report output format chosen.
because too many users are on a single network
segment), performance drops noticeably. In these A simplified rule of thumb for the number of clients to
cases, the network will need re-configuring to lower connect per network segment is to determine the worst-
the amount of traffic or increase the bandwidth of case acceptable throughput for each network client,
the network. Traditional hubs are being replaced by then divide that amount into the selected network
high-speed data switches, which further help alleviate throughput. For example, if each client should have
network bottlenecks. Multiple server network cards and no less than 1.5 Mbps of available bandwidth, and the
automated load balancing may be considered, too. network supports 100 Mbps, the segment could possibly
support 66 clients.

Kinetic Hardware Sizing Guide | 23

Epicor for Manufacturing

Unfortunately, this simple calculation does not take hard drives, and power supplies. You should also
into account the network latency, network media consider network hub/switch redundancy.
characteristics, or network traffic in addition to Epicor,
but it does provide a good starting point for the Such components contribute to a “highly available”
maximum amount of clients per network segment. solution that is tolerant of most hardware failures
and allows for service to be postponed to off-hours.
If you have users in remote sites, consider placing a Businesses requiring continuous availability (24x7) may
Remote Desktop Services (RDS) server on the same also want to consider hot plug support for controllers,
location (same LAN) as the Kinetic server. Instead of online spare hard drives, redundant processor power
running the Kinetic client locally and connecting to the modules, and redundant hot-swappable fans to
Kinetic server over a WAN, users can access the client on provide the highest-availability solution that can be
a Remote Desktop session. This improves performance serviced during business hours without an interruption
as the Kinetic server and Kinetic client are both in productivity. Network hubs, routers, and server
on the same LAN. monitors should also be considered when assessing
UPS requirements.
If you are using Kinetic client over the internet
we recommend that you host the Kinetic Test the validity of backup files, systems, and processes
using HTTP bindings.
It is important that you put processes in place to
Backup and Fault Tolerance UPS check the backup and restore files. Do mock runs
Hardware and restore backup files to validate that the backup is
• Tape backup devices meeting your needs.
• Uninterruptible power supply and
redundant components

Tape backup devices

It is extremely important that your business information
is backed up on a regular basis. The frequency
and type of backup should be discussed with your
implementation team, but one or more tape drives on
the server can ensure a timely backup is made. It is also
possible to backup to the local disk, and then copy the
file elsewhere for storage.

Uninterruptible power supply (UPS) and

redundant components
The production server is the key to the business and
should be protected. Power outages can damage the
server hardware and can occasionally corrupt the
software; therefore, the server should be protected
with a UPS, specifically one with server software that
is capable of initiating a clean shut-down of the server.
Recovery from a power outage is usually not a problem,
but it’s better to avoid the risk.

The mission-critical nature of an ERP system

necessitates consideration of redundant processors,
network controllers, storage controllers, hot-swappable

24 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

Kinetic
Hardware
Sizing Guide
Appendix

Kinetic Hardware Sizing Guide | 25

Epicor for Manufacturing

Diskspd utility is downloaded as a zipped file and can be

Testing performance of an existing extracted to your local drive as C:\Diskspd-v2.0.15\
SAN
If you have an existing SAN and want to ensure that Diskspd doesn’t require installation—Diskspd.exe can be
it can deliver good performance, then you can run a run via command prompt (with elevated permissions).
Microsoft storage benchmark utility named Diskspd.
Based on the version of SQL Server installed, choose the
The following tests are designed to test various aspects correct path:
of an I/O disk subsystem i.e., bandwidth (Megabytes/ ..\Diskspd-v2.0.15\x86fre (For 32Bit)
second i.e.MB/ dec.), Latency ..\ Diskspd-v2.0.15\amd64fre (For 64Bit)

(milliseconds), performance of your I/O system with To run each test:

desired block size (64KB), and file size and type of 1. Open up a Windows Command Prompt on the server
I/O—read or write and sequential v/s random writes. where you have downloaded and unzipped the
The parameters described in previous statement have Diskspd utility.For example START—RUN—CMD, this
a great impact on IOPS and hence they are specified opens up the command window.
exactly as needed here for testing using Diskspd. On 2. Change the directory to the location where Diskspd
the same machine you will get a different IOPS number utility is extracted.For example C:\Diskspd-v2.0.15\
if you change any one parameter. Testing with Epicor- 3. Run the three tests below using specified parameters
recommended parameters is highly recommended.

DOWNLOAD DISKSPD UTILITY

1. Database (.mdf) drive letter test

This test will test 64k random writes.
diskspd -w100 -t8 -o8 -d900 -r -b64k -h -L -c80G c:\iotest.dat > c:\mdfiotestresult.txt

[Note: All the parameters supplied are case sensitive]

Parameter Recommended Configuration

-w100 100% Writes, No Read

-t8 8 Worker threads used against test file
-o8 8 outstanding IO requests
-d900 The test will last for 900 seconds
-r Random write test
-b64k 64kb block size per IO
-h Disabling software caching, only hardware caching
-L Capture Latency Information
-c80G Creates a workload file of 80GB
This is the workload file of 80GB that will be created, the drive should be same as the one which
C:\iotest.dat
has .mdf filewhich has .mdf file
C:\mdfiotestresult.txt The results of Diskspd would be printed on C:\mdfiotestresult.txt

26 | Kinetic Hardware Sizing Guide

 Epicor for Manufacturing

2. Transaction log (.ldf) drive letter test

This will test 64k sequential writes.
diskspd -w100 –t2 -o8 -d900 -b64k -h -L -c80G c:\iotest.dat > c:\ldfiotestresult.txt

[Note: All the parameters supplied are case sensitive]

Parameter Recommended Configuration

-w100 100% Writes, No Read

-t8 2 Worker threads used against test file
-o8 8 outstanding IO requests
-d900 The test will last for 900 seconds
-r Sequential write test
-b64k 64kb block size per IO
-h Disabling software caching, only hardware caching
-L Capture Latency Information
-c80G Creates a workload file of 80GB
This is the workload file of 80GB that will be created, the drive should be same as the one
C:\iotest.dat
which has .mdf file
C:\mdfiotestresult.txt The results of Diskspd would be printed on C:\mdfiotestresult.txt

3. Tempdb drive letter test

This will test 64k sequential writes.
diskspd -w100 -t8 -o8 -d900 -r -b64k -h -L -c80G c:\iotest.dat > c:\tempdbiotestresult.txt

[Note: All the parameters supplied are case sensitive]

Parameter Recommended Configuration

-w100 100% Writes, No Read

-t8 8 Worker threads used against test file
-o8 8 outstanding IO requests
-d900 The test will last for 900 seconds
-r Sequential write test
-b64k 64kb block size per IO
-h Disabling software caching, only hardware caching
-L Capture Latency Information
-c80G Creates a workload file of 80GB
This is the workload file of 80GB that will be created, the drive should be same as the one
C:\iotest.dat
which has .mdf file
C:\mdfiotestresult.txt The results of Diskspd would be printed on C:\tempdbiotestresult.txt

Kinetic Hardware Sizing Guide | 27

Epicor for Manufacturing

We’re here for the hard-working businesses that keep the world turning. You’re the companies that make, move, and sell the
things we all need. Trust Epicor to help you do business better. Your industry is our industry, and we understand you better than
anyone. By working hand-in-hand, we get to know your business almost as well as you do. Our innovative industry solution sets
are carefully built to fit your needs and respond flexibly to your fast-changing reality. We accelerate ambitions, whether you want
to grow and transform, or simply become more productive and effective. That’s what makes us the essential partner to the world’s
most essential businesses.

Contact Us Today: [email protected] | www.epicor.com

This document is informational only. Epicor Software Corporation makes no guarantees, representations, or warranties to the information and disclaims, any implied warranties, such as fitness
for a particular purpose, merchantability, satisfactory quality, or reasonable skill and care. Testimonials are unique to the particular user and may vary. Epicor and the Epicor logo are trademarks
of Epicor Software Corporation. Other trademarks are the property of their respective owners. Copyright © 2023 Epicor Software Corporation. All rights reserved. Rev. Date August 21, 2023.