Lifespan Assumptions: Converged Architecture and Long-Term Workloads

Lifespan Assumptions: Converged Architecture and Long-Term Workloads

The change in assumptions about server lifespan means changing assumptions about why and when server hardware needs to be retired.

When many IT professionals first got into server administration, Moore’s Law meant that servers hosting critical workloads had a very limited effective lifespan. Newer processors outpaced those being used for specific server workloads within months. And it was only a matter of years before a formerly cutting-edge server was relegated to a less-processor-intensive role--such as a file server or, in smaller environments, a domain controller.

Times sure have changed: A decade or so ago, IT departments deployed a server for three to five years; today, most organizations assume that a newly purchased server will be able to effectively host its designated workload for up to 10 years. Indeed, unless an organization is buying bargain-basement components, a server deployed today should still be chugging along in 2025.

This change in assumptions about server lifespan means changing assumptions about why and when server hardware needs to be retired. These days, it’s less likely that a server will need to be replaced because its constituent hardware is underpowered for the workload it handles. Instead, a server is likely to be replaced because some of its constituent hardware has failed and replacement parts are difficult, if not impossible, to locate.

A big advantage of converged architecture is that it is modular. This means it’s easy to expand as workload requirements increase, but it also means that it’s simpler to replace components should they begin to fail at some point in their operational lifespan. While converged architecture vendors do their utmost to ensure that the constituent components of their systems are of high quality and reliable, even the highest-quality parts can suffer failures and need to be replaced.

Organizations need to think longer-term when developing their hardware strategies—and when developing plans to source parts for that hardware throughout its lifespan.

What benefits are you seeing—or do you hope to see--from converged infrastructure? Please let us know in the comments section below.

Underwritten by HPE

Part of HPE’s Power of One strategy, HPE Converged Architecture 700 delivers infrastructure as one integrated stack. HPE Converged Architecture 700 delivers proven, repeatable building blocks of infrastructure maintained by one management platform (HPE OneView), built and delivered exclusively by qualified HPE Channel Partners. This methodology saves considerable time and resources, compared to the do-it-yourself (DIY) approach.

Based on a complete HPE stack consisting of HPE BladeSystem with Intel® Xeon® E5 v3-based HPE ProLiant BL460c Gen9 blades, HPE 3PAR StoreServ all-flash storage, HPE Networking, and HPE OneView infrastructure management software, the HPE Converged Architecture 700 can be easily modified to fit within your existing IT environment.

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish