Vault 2021 System Requirements

[Aline Braunbeck]

currentlythe job processor is running on a workstation of an engineer. This should change in the future. The job processor will be installed on a dedicated machine with his own license. This machine will be a virtual machine.

Keep in mind the kinds of tasks you will be asking your JP machine to perform, and look into the system requirements for those. Example: If the JP will need to open files from Inventor to perform some task, the system req's should reflect not only those for Vault, but also Inventor.

I'm looking to build my first NAS and have been researching OMV and FreeNas. I see that the forum posts on FreeNas recommend server grade hardware which can drive the cost of a rig higher than I was expecting. How come it appears that the specs for a machine to run OMV are not as high?

Can someone help with the minimum requirements and help explain the pros/cons and tradeoffs of using what is recommended for minimum specs for FreeNas versus lower spec'd components of a workstation or Consumer PC? I'm going with OMV, but want to know why such a disparity in spec levels.

Is quite simple. Server grade components are meant to be far more reliable for 24x7 service than regular consumer components. Is actually up to you what you want to spend on components but remember that you get what you pay for. OMV requirements are no greater than what Debian minimum hardware requirements are without a desktop environment:

Nowdays, a good Atom based system works absolutely fantastic if all you do is file serve and use download managers such as Transmission. Adding at least 4GB of RAM is very inexpensive as well, so there's no excuse to install any less than that. For the operating system, is preferred to use a solid state drive and I've seen 16GB and 32GB selling for fair prices. The storage drives are entirely up to you when it comes to size and how many you need.

Pros of using server grade hardware will always be stability, durability, compatibility and ease of remote management. Cons of course would be the price and at times, proprietary interfaces or chassis that can make future repairs or upgrades difficult and/or expensive.

There is some consumer hardware which at times surpass some of the enterprise counterparts. MSI is known for being over the top with some of their gaming boards, others such as Intel have always maintained great quality all across.

Ok, thanks a lot for the clarification and advice. Quick question on software RAID versus hw RAID. I've read consistently that HW RAID is more reliable and better than SW RAID. That said, any concerns I need to take into account before just using SW RAID in OMV? I would prefer to avoid having to purchase a separate RAID controller. The main purpose for the NAS is to host our family photos and videos and to be able to access/stream to multiple locations. I want to have redundancy and I'm looking for a separate backup solution.

As far as reliability goes, I've never had an issue with MDADM (Debian's soft RAID solution), but it can only be as reliable as the OS itself. The advantage is that is portable, so if your OS or system fails, you can simply move the whole array to another Debian hosted machine and recover your data.

A RAID controller doesn't have to rely on software, but in the event of hardware failure, it can be difficult to match the controller and recover the data. The latter doesn't seem to be an issue any longer with Intel's RST since it can be found in many boards and seems to be cross-compatible even with older generations of the chipset.

The only real issue with hardware RAID is that by nature, you have a layer that obscures direct access to the hard drives. Meaning that you will not be able to monitor things like SMART, or drive temperatures. For most people though, this is not an issue.

Software RAID it is. Do you have a recommendation for regular backups? I thought of a cloud backup service, but I think I can get buy with cycling through a couple of external Harddrives...rotate then put one in a fireproof safe.

If you're just serving photos and videos on your home network then you don't really need a full RAID setup. RAID has to spin up all of your disks on every access which is a waste of energy. And you can't access the data, in case of emergency, on a single disk outside the array. I'd use a JBOD setup with Snapraid for paraty. That has the advantage of being able to use different size disks.

Motherboard - I'm looking at Asus Mobos and was targeting their boards with business chipsets (Q87, B85) versus the consumer boards. Any considerations between the two categories - business/consumer? I am also targeting an Intel onboard NIC versus Realtek. Any recommendations on that as well?

Some people have problems with Realtek out of the 2k Series, but not all. 8k Series works fine. Intel works fine all the way. I have better transfer rates with a realtek chipset then people with intel chipsets.

Thanks. I see that for the WD and Seagate NAS drives, they say 1-5 bay NAS systems. Am I really limited to using 5 in an array for their entry level NAS drives? If so, why? is this HW or SW related? thanks.

It doesn't actually matter for the OS. The choice for SSD is quite simple: no moving parts, and for some, less noise. In contrast to the actual array, which you can put to sleep after inactivity, you won't be able to do that with the system drive since it is always writing logs. In theory, not having mechanical components can increase the reliability of the system.

On the other hand, I've seen hard drives lasting well over 10, even 15 years. As an example, I bought some WD Raptors 74 back in 2004, three of them to be exact, and they worked flawlessly on a RAID 0 array without a single failure in these 10 years, even after so many upgrades that I've done over the years. Just recently I retired them and replaced them with a single SSD, but they are still good.

HDD

1. Likely to have a longer lifespan

2. 2.5in sata drives are pretty quiet and have similar power consumption to an SSD.

3. Probably cheaper per mb, if money is an issue. New or refurbished laptop drives are easy to find in the 80-160gig range.. which is plenty.

both only slightly. Had an SSD as well as HDDs built in. Just a matter of a few seconds for booting and almost no time while using the webif. However. I have two 265 GB SSDs laying around here. Maybe Ill do a clean install when I have some spare time.

Hello,

I plan to install a Vaultwarden instance to host family passwords. I am unable to find any requirements about hardware specification to help me choose an appropriate VPS. So is there any minimal and recommended system specification:

Take into account in your considerations about the size of the system diskthat various plugins such as openmediavault-podman or openmediavault-k8sstore their data (e.g. container images) on the system disk.

If you use a Flash Drive, select one with static wear leveling [6], withoutthis the drive will have a very short lifetime. It is also recommended toinstall and activate the Flash Memory plugin. Theentire disk is used as system disk and can not be used to store user data.

While the following recommendations are intended as a general overview for most SOLIDWORKS PDM Professional vaults, determining proper server and client hardware is one of the first steps that Javelin will provide during a SOLIDWORKS PDM Implementation service.

We strongly recommend that you contact our specialists if you are considering the purchase of any hardware or software for PDM. The optimal hardware and configuration for your vault may vary depending on many aspects, including the number of users, number of files in the vault and other factors.

For medium and large PDM Vaults, It is recommended that a separate, dedicated server be used for the PDM Database Server. For performance reasons no other databases should be hosted on the same server that is hosting the PDM database. It is recommended that the SOLIDWORKS PDM Database Server Service (also called the Database Helper service) be installed on the same system that is hosting the SQL Server software.

NOTE: It is strongly recommended that the Microsoft SQL Server software not be installed on a system that acts as an Active Directory Domain Controller, this can lead to several known issues, including security risks.

For the Database Server, Microsoft SQL can take advantage of multi core processing. For optimal performance of PDM functions, it is recommended that the average CPU utilization be kept below 50%. If average utilization is above 50%, then more cores may be needed. Please note, If using Microsoft SQL Server Standard Core Licensing, adding additional cores may require also purchasing additional core licenses. This can be discussed with your Microsoft retailer.

As of the Service Pack 0 release, SOLIDWORKS PDM 2022 can only be installed on Windows 10, compatibility with Windows 11 may be announced with future service packs. SOLIDWORKS PDM 2020 SP5 was the last release compatible with Windows 7. SOLIDWORKS PDM 2022 will not install on Windows 7.

Although SOLIDWORKS does not test PDM in any cloud provider (please see the note regarding non-supported environments bellow), cloud based servers running Windows Server Operating Systems, such as AWS EC2 or Microsoft Azure, can be used for SOLIDWORKS PDM servers.

The database can be hosted on SQL Server Standard or SQL Server Enterprise, however due to performance limitations SQL Express should not be used to host a SOLIDWORKS PDM Professional vault database in a production environment.

NOTE: Ensure that you have the proper licensing for the version of SQL that you use for PDM Professional (your Microsoft Software Provider can help you determine if you have all the licenses needed for SQL).

3a8082e126