10 errors that are easy to make when consolidating a server need to be cautious

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

Because organizations want to improve the IT infrastructure to save costs, CIOs and data center managers have shifted to the process of consolidating servers to achieve cost savings. In fact, it is not easy to do so. Because organizations want to improve their IT infrastructure to save costs, CIOs and data

Heart managers are turning to the method of merging servers to achieve cost savings. In fact, it is not easy to do so.

From a financial standpoint, while server consolidation is valuable, it does not mean that the project is easy to implement. Some misconceptions make it difficult to achieve cost control and build efficient data centers.

Consolidation is buying new hardware

Consolidation does not mean buying expensive new hardware and merging with your existing products can save you money, which in many cases is the first thing you should consider. If you have made the best use of existing products, you may consider buying new products.

Consider only general workload patterns

Although the workload is an important factor in considering consolidation. However, it only means keeping things running smoothly and what should be compatible, not reflecting server compatibility, and what should be virtualized. In addition, workload analysis is often simplistic. The analysis should take into account how the server is operating most of the time, including what time of day the server's workload is the greatest. The server workload pattern usually shows the peak hours of the run, and if you can find that the server is running at peak times at different times of the day, even though the average workload may imply that the workload cannot be merged, the potential analysis shows that the workload can be merged.

Non-technical limitations are not considered

Rapid server consolidation or virtualization conversion without taking into account the non technical factors can also cause problems. While it's tempting to move many applications to the same entity server, if you do this, you're putting all applications under the same hardware. If these applications have different service level requirements or update Windows, then the problem comes.

Implement planning in accordance with outdated information

Server consolidation analysis may be a few months of work. In some cases, you need to ask a professional service company to guide the analytical work, which is usually the result of a report. Using this type of investigation as a guideline for project implementation is risky, and you have to consider the update speed of your service provider, and it is critical that you take the latest information to guide your actions.

Clarify intent before collecting data

IT staff may feel that consolidation is not a good idea, and some employees will feel that it will lead to a decline in their importance and influence because they manage less content and even feel that the implementation of the integration project will cause them to lose their jobs. There has been such a thing: Some companies in the engineering analysis phase let employees find their way out, to ensure the efficient operation of the future server. The best way to do this is to gather some relevant information from around you, and then talk to your staff about your intentions.

Virtualization as the only way to integrate

The idea that many CIOs view virtualization as the only way to do server consolidation is too limited. Virtualization is powerful and flexible, but some of the consolidation approaches like application software and operating system (storage) stacks are also attractive because they do not increase administrative costs for the enterprise, nor do they require complex virtualization processes. In addition, some servers cause the server to be virtualized to shrink because their application software is not suitable for virtualization.

Exclude the database server from the merge scope

I/O restrictions mean that the database server is not suitable for virtualization, database server expansion is a major problem for many enterprises, through the correct integration analysis and implementation, many methods can significantly reduce the number of database servers.

Exclude application Server from merge scope

Many integration plans do not consider application software servers, which is wrong. The integration of application software servers (Java EE environment and Web servers) will also bring additional benefits to the enterprise.

Exclude the detection/development environment from the merge scope

Developing and testing an environment is often the culprit for hardware and software unplanned scaling problems. Because they are not user-oriented, they are also least sensitive to workload issues. In many cases, a specific number of database servers can be merged without impacting utilization or productivity.

Failed to take into account the impact of financial profits and changes on ROI

There are many factors that can affect the financial effect of a merger. For example, the cost savings are obvious because the merged database server is easy to operate. And because time and manpower are too expensive, the consolidation of complex applications that require specific testing can lead to zero return on investment. So make sure you choose the right target. (Zebian Admin01)