Technical Sales Specialist – Data Center
What should organizations considering new servers keep in mind to get what they need, instead of just paying for the latest and greatest?
You should start by asking, “What do we need to satisfy our actual workload requirements?” That in mind, it’s important to look for a solid platform with technology that isn’t going EoL within a year, management capabilities in line with your needs and comfort level, and robust and ongoing support.
How far ahead are most of your customers planning when considering new servers? How far ahead should they (or can they) be planning?
This runs the gamut, but there are some trends. For instance, companies with about 1,000 employees and a robust data center often engage in roadmapping conversations on an ongoing basis and plan for specific refreshes about 6 months ahead. Companies with over 100 employees and a well-planned data center may begin planning for significant server refreshes about 3-5 months ahead of time. And small environments with only a couple servers may allow their systems to age until there is a break/fix issue, or support costs more than new equipment.
Of course the more planning the better. If you are going to spend more than $50K on servers, you should have a couple roadmapping sessions with your preferred vendors each year and allow at least 30 days to fine tune your builds.
Which workloads have you tested AMD-based HP ProLiant servers against? Which workloads are these servers best suited to?
The AMD-based ProLiant servers are a good fit for physical environments, such as domain controllers, file servers, Active Directory and DNS servers. Also, organizations refreshing from Windows Server 2003 without much virtualization are strong candidates.
For organizations already using Intel-based servers, in which scenarios can they also adopt AMD-based servers to achieve their objectives?
Organizations currently using Intel servers might also consider adopting AMD servers for multiple scenarios, such as dedicated vCenter/System Center servers; refreshing older, underutilized Intel models with current-gen AMD servers; testing and development to ensure programs are solid under a variety of circumstances; and failover or high availability strategies.
Links to third party sites are provided for convenience and unless explicitly stated, AMD is not responsible for the contents of such linked sites and no endorsement is implied.
AMD is not responsible for third party content and does not necessarily endorse the comments made herein.
©Advanced Micro Devices, Inc. All rights reserved. AMD, the AMD Arrow logo, and combinations thereof are trademarks of Advanced Micro Devices, Inc. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
ARM and TrustZone are registered trademarks of ARM Limited in the UK and other countries. Windows is a registered trademark of Microsoft Corporation in the US and other jurisdictions.