{"id":9634,"date":"2017-11-09T08:28:19","date_gmt":"2017-11-08T21:28:19","guid":{"rendered":"https:\/\/www.backupassist.com\/blog\/?p=9634"},"modified":"2025-06-12T05:02:45","modified_gmt":"2025-06-12T05:02:45","slug":"when-should-i-replace-my-server","status":"publish","type":"post","link":"https:\/\/www.sandbox.backupassist.com\/blog\/when-should-i-replace-my-server","title":{"rendered":"When Should You Replace Your Server?"},"content":{"rendered":"

Deciding when to replace your server is a real balancing act<\/strong>. If you replace it too soon, you\u2019ll be tossing out a perfectly good (and very expensive) piece of hardware.<\/p>\n

Leave it too long? The server crashes and you lose more in downtime and lost productivity than a brand new server would have cost \u2013 AND you\u2019ve got to buy a new server anyway!<\/p>\n

Well, wonder no more. Here\u2019s exactly how you should decide if you should replace your server completely, or keep it for just a bit longer.<\/p>\n

1. More than 3+ Years Old<\/strong><\/h3>\n

If your server is three years old (or more), you should seriously consider replacing it.<\/p>\n

\u201cBut I just bought it\u201d, I can hear you saying. And you may be tempted to eke out a bit more life out of it. And you definitely could do that – perhaps you already have!<\/p>\n

But the reason you want to ditch a server after three years out isn\u2019t just to avoid a potential server outage.<\/p>\n

According to IDC, the moment your server hits its fourth birthday, support costs raise by approximately 40%. In its fifth year, this raises to 200%. And if for some reason you get to seven years without replacing, you\u2019re looking at a 400% increase in costs.<\/p>\n

And your users often won\u2019t report the troubles they\u2019re having with your slow server \u2013 employees are notorious for working around these issues. If a process takes ten minutes like booting something up or running reports, they may make a coffee or chat with other employees.<\/p>\n

But that lost time adds up. Several minutes for a process for one employee, spread across a whole department, adds up to a lot of lost time and money. A slow server can lead to you getting nickel-and-dimed to death.<\/p>\n

2. The Warranty<\/strong><\/h3>\n

If you get one takeaway from this article, it would be this: your server should never outlast the warranty it came with.<\/p>\n

Unsurprisingly, this warranty will be approximately three years, though some will go up to five years. The reason you will want to replace your server after the warranty runs out is very simple \u2013 this is the period that if it crashes, someone will bail you out.<\/p>\n

At the point in which the manufacturer is not going to do this, you should take this as a sign that your server has reached its use-by date.<\/p>\n

It\u2019s worth noting that just because you\u2019re within a warranty period, it doesn\u2019t mean your server won\u2019t wear out! There are other factors that can bring about its end of life a lot sooner, such as a high workload.<\/p>\n

Choosing Your Warranty:<\/strong> When you\u2019re choosing your new server warranty, it can cost you a lot of money, and they often come in different levels to fit your needs. Typically, it covers replacement parts and an onsite tech to replace those parts.<\/p>\n

3. Hardware Support<\/strong><\/h3>\n

When you\u2019re considering replacing your server, you should check to see if it is still being built.<\/p>\n

If your server is still in production, that\u2019s great! If something goes wrong, it won\u2019t be that hard to find replacement parts.<\/p>\n

However, if it\u2019s not, that means you\u2019re not going to be able to fix it quickly if there\u2019s a hardware issue. The parts you are going to get \u2013 if you\u2019re lucky enough to get them \u2013 are going to be more expensive, second-hand, and take a while to get to you.<\/p>\n

That\u2019s why if your server is out of production, it\u2019s good to make sure you shelve it as well. That way you won\u2019t be hit as hard by hardware failure.<\/p>\n

Much like with a warranty, if your manufacturer has decided to shelve the server, it\u2019s likely you should too.<\/p>\n

4. Your Server is Acting Up<\/strong><\/h3>\n

Sounds obvious, but a lot of people try ignoring a temperamental server instead of just replacing it. And the longer you leave it, the worse the symptoms get \u2013 as well as the effort to replace it.<\/p>\n

There are some things that can’t be fixed no matter how many parts you replace. While switching out a bad stick of ram or a new drive might fix some issues, if this strategy isn’t working, then you may need a whole new server.<\/p>\n

As mentioned earlier, your server may be acting up right now and your users may not be reporting it \u2013 they\u2019ll often just work around issues and grumble to themselves. If you’re seeing persistent issues on top of that, then a replacement is likely on the cards.<\/p>\n

5. You Need More from Your Server<\/strong><\/h3>\n

Organizations grow. And when they grow, the demand on your server increases. When use of your server reaches 70% of maximum, or drive space is running low, you\u2019re going to see a drop in server performance.<\/p>\n

This is where virtualization can come in handy. If you\u2019ve got two or more servers \u2013 or you suddenly have the need for them \u2013 you can purchase one really good server and run virtual machines off it. (See our \u2018Going Virtual\u2019 article series)<\/p>\n

Since you can scale VMs to your needs, this means you can change your infrastructure to fit your growing business needs.<\/p>\n

If your organization is opening new sites, this is also a big flag to consider upgrading your server.<\/p>\n

6. Significant Advancements Have Been Made<\/strong><\/h3>\n

Advancements in server technology are being made all the time, aided by Moore\u2019s law. Engineers are constantly working to shrink the transistors and other internal components that make up the underlying microprocessors.<\/p>\n

These kind of advancements lead to faster and more powerful processing, often with less energy being used. So why not take advantage of this to speed up your business?<\/p>\n

A common fallacy people make is waiting for a new model that is two to three times faster than the model you have. While advancements are great, this sort of boost is unlikely. But as stated earlier, even a 10 minute boost is a big business saver \u2013 and a return on investment.<\/p>\n

It\u2019s worth reiterating that since your server is constantly in a state of decline, the speed your server is now is likely not what it was when you first bought it. That means the upgrade after a while leads to a significant boost, even if you exclude new advancements.<\/p>\n

7. OS \/ App Support<\/strong><\/h3>\n

In the end, server hardware is just there to support the OS and applications that you\u2019re running off it. And if it\u2019s not doing that well, it\u2019s time to upgrade.<\/p>\n

If your rig is barely running Windows Server 2008 properly, then how is it going to handle it when you move up to 2012 or 2016? The short answer: it\u2019s not.<\/p>\n

When you\u2019re upgrading your OS, it can be the perfect time to upgrade your server as well. Yes, it does mean a lot more work, and you\u2019re probably going to want to do it as a staged process. But in many ways, it\u2019s best to tackle two birds with one stone.<\/p>\n

You may also find that new operating systems and software packages you are running have minimum hardware requirements. While you shouldn\u2019t use minimum requirements as a baseline – you\u2019re setting the bar really low for productivity \u2013 it\u2019s still something to look into.<\/p>\n

8. Industry Regulations<\/strong><\/h3>\n

When laying out the timeline to replace your server, another consideration is industry regulatory requirements that may put added constraints on your server lifespan. Continue to check on industry standard requirements and follow those guidelines in conjunction with your manufacturer\u2019s warranty.<\/p>\n

You may find if you are storing people\u2019s information, you need to have a certain level of hardware stability to meet your GDPR obligations. You can read our articles on it here and here.<\/p>\n

9. You Don\u2019t Have a Server<\/strong><\/h3>\n

It\u2019s alluring to completely discard in-house infrastructure these days, when cloud computing is coming to the fore. After all, why manage your own infrastructure when you can make it someone else’s problem?<\/p>\n

There are definite pros and cons to having cloud servers over in house servers \u2013 and the answer to which one is best depends on your business model.<\/p>\n

If these things are of concern to you – and you don\u2019t have an in-house server already – then you may want to get one:<\/p>\n