What computer configuration should be used for file 1C:Enterprise 8.3 and everyday tasks?

Question

Iron

It is necessary to assemble a computer for everyday tasks (working with documents and accounting programs) and file 1C: Enterprise 8.3, several databases and several users who work with them through a thick client. It is necessary to assemble a computer for these needs, which would be not only fast but also reliable.
I'm going to use the following configuration:
OS Microsoft Windows 10 Pro;
Processor INTEL Core i5-7500;
Motherboard GIGABYTE GA-B250M-DS3H (rev. 1.0);
RAM Kingston KVR24N17S8/4 (2 pcs.);
Hard drive Western Digital WD RE 500 GB WD5003ABYZ.
More specifically, on the questions:
1. Is this assembly redundant, if so, what should I change for?
2. Is it worth using an SSD (if so, how, install an OS on it, a 1C base, or all together just by dividing it)?
3. How to securely organize data storage?
I expected to use an SSD for the OS and the 1C base, periodically make a full copy of it (after a noticeable change in software versions and other things, but not often), and set up backups on the hard drive. Unfortunately, the budget is limited and the implementation of RAID 1 is possible only at the expense of the above assembly. Maybe someone else has experienced something similar and can share their personal experience.

Answer 1

Initially, you need to decide what configurations you will use on this machine and how users will connect to it? What is the volume of data and the number of analytics in accounting? Several users work each with their own base or at the same time with several?
If "standard" configurations like "Bukh", "UT", "ZuP", estimate 2GB per user, install an SSD and be sure (!) to let them in RDP mode. 1C in thick client mode loves to drive huge data through the network. And it will be easier to maintain when you need to install all sorts of Vip net csp for Reporting or EDI.
If "heavy" configurations, make sure you have enough file mode. In client-server mode emulation (with a file base) there is a limit of 3GB RAM. On the same ERP, there may simply not be enough memory to calculate the cost, if the database has a large amount of documents, the presence of a counter issue, etc. The mode of operation is also RDP only, the reasons are higher.
The latest configuration releases have built-in backup setup wizards, everything is simple to set up there. It is better to copy to a separate machine or connect a service from 1C - Cloud Archive (for Bukh 3.0 and UNF). Don't bother with Raid, especially to the detriment of this build!