B
B
Borzov Ivan2019-09-17 07:23:48
RAID
Borzov Ivan, 2019-09-17 07:23:48

How to distribute the load on the server disks?

We have:
1. Server HPE Proliant DL 380 Gen 10 Server
Configuration Processors: Two Xeon Silver 4110 2.1 Ghz processors, Cores 8, Threads-16, L3-11 Mb cache,
RAM: DDR4-2400 32GB,
Disks: 2 HPE disks 2Tb SAS, 2 HPE 480 Gb SSD
2. OS: Windows Server Standard 2019
3. Synology RS 818 storage, 4 x 4TB drives, SATA 3.0, 5400 rpm, 64 MB buffer
4. Veeam Backup & Replication Instances - Standard -1 Year Subscription Upfront Billing & Production (24/7).
6 DB 1s will be installed (2 Accounting, 2 ZUP, 2 1s Self-written) In total, terminal users 1s-16.
It is supposed to be installed in the future. 107 users
Planned:
on the server RAID 1 on 2 SSDs, RAID 1 on 2 SAS
on storage RAID 10 on 4 SATA disks
OS, 1s application server, Terminal Server, SQL, Lotus Server on SSD
temp, logs, database indexes on SAS
System backup via Veeam Backup to storage.
File storage on storage

Answer the question

In order to leave comments, you need to log in

1 answer(s)
R
RStarun, 2019-09-23
@RStarun

The main thing is not specified - the amount of data. Well, the raid controller.
Maybe the OS and database will fit on the SSD, then the question is closed.
But most likely you will only have enough SSD for the database
. The type of 1s used is also not indicated. If this is an enterprise 1c server, then it uses a SQL / Postgre database and it will most likely need more RAM for normal operation.
You really have very few options.
I would do this:
1. OS on SAS RAID 1. Enable the controller cache if there is a battery.
2. We put all applications that are not a database (1s itself, Lotus itself) on a disk with an OS.
3. All databases and files requiring quick access - on SSD RAID 1. Turn off caching.
4. If you need more space or want to take out some data to offload existing disks, then we connect the space we need from the storage system via iSCSI. For example, you can use such a capacity to run the "file history" functionality, the built-in Windows backup, just for folding copies of something made by hand.
5. If a file storage facility on the NAS needs to restrict access using a domain, then I would just hook it up via iscsi to the server and distribute it from it. The load on the server is usually negligible.
6. Be sure to consider how to protect backups on the NAS. I don’t know how in this case, but the general principle is this - there should be no access to data from the server. These may be snapshots, tape emulation, access to a disk with backups from a third-party account, etc.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question