I'm on a mission to spec out new servers for a robotic warehouse system we're implementing at work, specifically the AutoStore system. The specs they've given seem a bit on the low side for smooth operation. Here are the details:
**AutoStore App Server Requirements:**
- 4 vCPU @ ~3.6 GHz
- 16 GB RAM
- ~100 GB disk
- 1 Gbps NIC
- Windows Server 2019/2022
**SQL Server Requirements:**
- 4 vCPU @ ≥3.0 GHz
- 32 GB RAM
- C: 100 GB, D: 200 GB
- SQL Server 2016+
The system will have continuous writes, and I'm aware that what we're currently running is a single Windows Server 2012 for SAP. I'm aiming to upgrade this, and I'm not sure how many servers will be needed. I plan to over-spec the hardware and was thinking about setting everything up on Proxmox VE with high availability and frequent local backups.
I'm looking for guidance on two main points:
1. How should I spec these servers?
2. What would be the best way to set everything up?
I'd like to avoid any major mistakes since this is pretty critical for us. I have the spec PDF, and I'm happy to share it to get some feedback!
5 Answers
Looks like you’re set on a good path. The vendor's specs aren't unusually low, and if you’re virtualizing, scaling up is easier later if you need more resources. Just keep an eye on SQL licensing, as it can add to your costs quickly!
You can always tweak the resources while monitoring usage—VMs give you that flexibility!
You definitely want to run these servers as VMs. Trust me, going with bare metal can lead to some serious headaches later on. VM management will save you a lot of hassle down the line!
You're right! I can already see how rolling back patches could be a nightmare without VMs!
Once you start rolling updates, you'll wish you had virtualization!
Make sure your backup strategy suits SQL. Don't just rely on third-party tools; set SQL to handle hourly backups of its databases. Also, consider how many VMs you’re running and provision enough resources for peak loads.
I appreciate the tips! I'm realizing there's a lot more to think about.
So many factors to cover; it's good you're being thorough. Keep asking questions!
Before anything, check the expected IOPs for the database. This will ensure that your storage can handle the load. Also, make sure that your backup solution is configured for databases so it quiesces them properly during backups. Otherwise, you could end up with a corrupted database if not all changes are saved correctly during that time.
Here's the PDF I got for reference if anyone wants to take a look: [PDF Link] (https://drive.google.com/file/d/17kOnC3CAKrQj7hJoo8SZl69j01K9maUI/view?usp=drivesdk)
Make sure to over-spec your hypervisor. While Proxmox is great, consider using Hyper-V instead, especially if you need support. Never underestimate the importance of having your database drives and backup system in order. You'll thank yourself later when you need to add more resources!
Proxmox does have paid support, but you're right that moving to Hyper-V could streamline things. Guess I'll need to learn that too!
If something goes wrong, you’re the one responsible for fixing it. Knowing Hyper-V could help mitigate that risk.
Ugh, more to read on licensing. Thanks for the heads-up!