10 things to remember when upgrading the server

Network Administration - You can avoid some problems and get the most out of it by following some advice when upgrading servers.

10 things to remember when upgrading the server Picture 1 At first, servers were mostly deployed with some purpose in your mind. However, whether deployed in a small business or a large enterprise, server roles will change over time. Due to development, reduced budget, accompanying limitations and other factors, servers deployed for one purpose often have to meet additional services and responsiveness.

That is why it is so important to evaluate the system periodically. Considering and evaluating server resources can help you ensure optimal performance for your organization and avoid unnecessary downtime. However, system administrators cannot open the case and steal more RAM there or simply upgrade the hard drive here. Server upgrades always need a specific plan. Here are 10 things to remember when upgrading the server to ensure the system performs at its highest capacity.

1. Always start with an authenticated backup of data

Never make any changes to a server, even minor updates, before confirming a secure data backup. Whenever making changes to the server, there is no guarantee that the server will return to work immediately. There may be a rare case, but it has happened, when a simple task is to install security patches and performance of Windows, but the server has failed afterwards.

2. Consider creating an image backup

Some manufacturers provide professional cloning disk techniques to simply recover servers when an error occurs. Some of them include Acronis Inc. and StorageCraft Technology Corp, which provides a fairly common recovery option, this option allows you to restore a failed server to a completely new computer without installing any operating system. The time to stop working of machinery also decreased markedly. When updates are problematic, disk images can help you quickly recover not only data but also complex server configurations.

3. Do not create multiple changes at the same time

Most IT professionals understand the importance of minimizing the number of server restarts, so newcomers are also tempted to want to complete upgrades simultaneously via a machine shutdown. However, adding hard drives, replacing memory, reinstalling some additional cards and other tasks should all be done separately? Why? When a problem occurs a day or two later, the process of finding which component is causing the problem is very difficult. Therefore, to avoid these unnecessary difficulties, you should not create multiple changes at once for your server.

4. Check the record thoroughly after making changes

When upgrading the server, never acknowledge that everything works fine just because the server is working again and not showing errors. Check meticulous log files, error reports, backup operations and other important events like never before. Use Windows internal performance reports or third-party testing utilities, such as GFI Software's HoundDog and PacketTrap utilities, to make sure all goes well intended whenever the change or upgrade is completed.

5. Confirm the operating system

It's easy to forget the operating system of a server running. This is especially true for an entire room that has multiple servers but does not use the same type of operating system and instead is a mixture of different operating system versions. A veteran administrator may also make a mistake such as installing an additional 8GB of RAM for a 32-bit version of Windows Server 2003 server. Just by performing a quick audit (including 32-bit and 64-bit checks) for the system to be upgraded, you will confirm which operating system is compatible and possibly use more RAM (or other resources).

6. Confirm upgrade support

The more well-known server hardware is inconsistent. Manufacturers often have changes in model numbers and product configurations. So whenever you install additional components like disk controller, hard disk or memory, . you need to review the manufacturer's technical details online before proceeding. Only by opening the case, can you ensure that 100 servers deployed in your organization can allow those upgrades.

7. Do not acknowledge 'plug-and-play'

Whenever installing a new hardware, do not acknowledge that the device you install will be "plug-and-play" well with the server's operating system (even if the manufacturer declares that component. is compatible). Before performing the upgrade, search on Google to learn more about the necessary experience from other technology experts as they have encountered during the deployment process. The upgrade will be done on the server, so confirm the upgrade component listed in the operating system's hardware compatibility list. In addition, you also need to visit the server manufacturer's forums and learn more technical issues that are easy to encounter when installing similar devices on similar operating systems.

8. Optimized performance

The requirements for related software adjustments need to be followed for any upgrade. For example, just adding RAM to a Windows server will not automatically optimize Windows performance. Administrators must upgrade the server's virtual memory settings to optimize Windows operation according to new memory. In addition, when adding new hard drives, old files also need to be transferred to the new hard drive to get performance advantages.

9. Prioritize expensive things

Obviously, drives, RAM, power supplies and less expensive components are always available. However, when it comes to servers, abandon these savings concepts. Prioritize high quality components and high availability capabilities used in servers. These expensive things can make your total cost higher but its performance advantages and uptime will be totally worth what you spend.

10. Update documents

Log files should be maintained for each server. Inside the document for the newly upgraded server, you need to update in that document the notes about the newly upgraded component, manufacturer, manufacturer, even the order number and serial number if possible. In addition, there is also information about warranty and other support. The more information you have in your hand, the easier it will be for you to quarantine and fix problems later.