Dell PowerEdge Server Refresh - Planning a Multi-Year Infrastructure Lifecycle

We just completed a server refresh at Julius Silvert - 8 new Dell PowerEdge R760 servers replacing aging R730s that were approaching 7 years old. Here's how we planned, procured, and executed the refresh while keeping operations running.

The Planning Phase

Server refreshes shouldn't be emergencies. We maintain a hardware lifecycle plan that projects replacements 3-5 years out. Every server has an expected replacement year based on warranty expiration, workload demands, and technology relevance.

For this refresh, planning started 18 months before procurement. We evaluated workload requirements, considered cloud alternatives for each function, and sized new hardware based on projected growth.

Key decisions:

• VMware remains our hypervisor (despite Broadcom concerns)
• vSAN for storage continues to make sense for our scale
• 4 hosts per site provides N+1 redundancy
• NVMe-based storage for all production workloads

Vendor Negotiation

Dell enterprise sales is relationship-driven. Tips that saved us money:

Quote at quarter-end. Sales reps have targets. A deal that closes in the last two weeks of a quarter gets better pricing than the same deal at quarter start.

Bundle everything. Servers plus support plus ProDeploy plus accessories. The more you combine, the more flexibility they have on pricing.

Get competing quotes. Even if you prefer Dell, quotes from HPE create negotiation leverage. Dell knows their competition.

Negotiate support terms. ProSupport Plus is expensive but worth it for production infrastructure. But the first quote is always high - there's margin to negotiate.

Migration Strategy

We migrated over three weekends, moving VMs from old to new hardware with minimal downtime. vMotion made most migrations seamless. The few servers requiring maintenance windows got scheduled for off-hours.

Old servers were repurposed for dev/test before eventual disposal. Never throw away hardware that can serve as a test bed for the next 2-3 years.

Lessons Learned

Start planning earlier than you think necessary. Lead times for enterprise hardware fluctuate wildly - we saw 12-week delivery times during supply chain constraints.

Document everything before migration. You'll need it when a VM doesn't behave the same on new hardware.

Test thoroughly before production cutover. What works in lab doesn't always work at scale.