This eBook explains how to identify problems with vSphere and how to solve them. Before we begin, we need to start off with an introduction to a few things that will make life easier. We’ll start with a troubleshooting methodology and how to gather logs. After that, we’ll break this eBook into the following sections: Installation, Virtual Machines, Networking, Storage, vCenter/ESXi and Clustering.
ESXi and vSphere problems arise from many different places, but they generally fall into one of these categories: Hardware issues, Resource contention, Network attacks, Software bugs, and Configuration problems.
A typical troubleshooting process contains several tasks: 1. Define the problem and gather information. 2. Identify what is causing the problem. 3. Fix the problem, implement a fix.
One of the first things you should try to do when experiencing a problem with a host, is try to reproduce the issue. If you can find a way to reproduce it, you have a great way to validate that the issue is resolved when you do fix it. It can be helpful as well to take a benchmark of your systems before they are implemented into a production environment. If you know HOW they should be running, it’s easier to pinpoint a problem.
You should decide if it’s best to work from a “Top Down” or “Bottom Up” approach to determine the root cause. Guest OS Level issues typically cause a large amount of problems. Let’s face it, some of the applications we use are not perfect. They get the job done but they utilize a lot of memory doing it.
In terms of virtual machine level issues, is it possible that you could have a limit or share value that’s misconfigured? At the ESXi Host Level, you could need additional resources. It’s hard to believe sometimes, but you might need another host to help with load!
Once you have identified the root cause, you should assess the impact of the problem on your day to day operations. When and what type of fix should you implement? A short-term one or a long-term solution? Assess the impact of your solution on daily operations. Short-term solution: Implement a quick workaround. Long-term solution: Reconfiguration of a virtual machine or host.
Now that the basics have been covered, download the eBook to discover how to put this theory into practice!
If you’re here to gather some of the best practices surrounding vSphere, you’ve come to the right place! Mastering vSphere: Best Practices, Optimizing Configurations & More, the free eBook authored by me, Ryan Birk, is the product of many years working with vSphere as well as teaching others in a professional capacity. In my extensive career as a VMware consultant and teacher (I’m a VMware Certified Instructor) I have worked with people of all competence levels and been asked hundreds - if not thousands - of questions on vSphere. I was approached to write this eBook to put that experience to use to help people currently working with vSphere step up their game and reach that next level. As such, this eBook assumes readers already have a basic understanding of vSphere and will cover the best practices for four key aspects of any vSphere environment.
The best practices covered here will focus largely on management and configuration solutions so should remain relevant for quite some time. However, with that said, things are constantly changing in IT, so I would always recommend obtaining the most up-to-date information from VMware KBs and official documentation especially regarding specific versions of tools and software updates. This eBook is divided into several sections, and although I would advise reading the whole eBook as most elements relate to others, you might want to just focus on a certain area you’re having trouble with. If so, jump to the section you want read about.
Before we begin, I want to note that in a VMware environment, it’s always best to try to keep things simple. Far too often I have seen environments be thrown off the tracks by trying to do too much at once. I try to live by the mentality of “keeping your environment boring” – in other words, keeping your host configurations the same, storage configurations the same and network configurations the same. I don’t mean duplicate IP addresses, but the hosts need identical port groups, access to the same storage networks, etc. Consistency is the name of the game and is key to solving unexpected problems down the line. Furthermore, it enables smooth scalability - when you move from a single host configuration to a cluster configuration, having the same configurations will make live migrations and high availability far easier to configure without having to significantly re-work the entire infrastructure. Now the scene has been set, let’s get started!
Each version of Windows and Windows Server showcases new technologies. The advent of PowerShell marked a substantial step forward in managing those features. However, the built-in graphical Windows management tools have largely stagnated - the same basic Microsoft Management Console (MMC) interfaces had remained since Windows Server 2000. Microsoft tried out multiple overhauls over the years to the built-in Server Manager console but gained little traction. Until Windows Admin Center.
WHAT IS WINDOWS ADMIN CENTER?Windows Admin Center (WAC) represents a modern turn in Windows and Windows Server system management. From its home page, you establish a list of the networked Windows and Windows Server computers to manage. From there, you can connect to an individual system to control components such as hardware drivers. You can also use it to manage Windows roles, such as Hyper-V.
On the front-end, Windows Admin Center is presented through a sleek HTML 5 web interface. On the back-end, it leverages PowerShell extensively to control the systems within your network. The entire package runs on a single system, so you don’t need a complicated infrastructure to support it. In fact, you can run it locally on your Windows 10 workstation if you want. If you require more resiliency, you can run Windows Admin Center as a role on a Microsoft Failover Cluster.
WHY WOULD I USE WINDOWS ADMIN CENTER?In the modern era of Windows management, we have shifted to a greater reliance on industrial-strength tools like PowerShell and Desired State Configuration. However, we still have servers that require individualized attention and infrequently utilized resources. WAC gives you a one-stop hub for dropping in on any system at any time and work with almost any of its facets.
ABOUT THIS EBOOKThis eBook has been written by Microsoft Cloud & Datacenter Management MVP Eric Siron. Eric has worked in IT since 1998, designing, deploying, and maintaining server, desktop, network, and storage systems. He has provided all levels of support for businesses ranging from single-user through enterprises with thousands of seats. He has achieved numerous Microsoft certifications and was a Microsoft Certified Trainer for four years. Eric is also a seasoned technology blogger and has amassed a significant following through his top-class work on the Altaro Hyper-V Dojo.
With a software-based approach, IT organizations see a better return on their storage investment. DataCore’s software-defined storage provides improved resource utilization, seamless integration of new technologies, and reduced administrative time - all resulting in lower CAPEX and OPEX, yielding a superior TCO.
A survey of 363 DataCore customers found that over half of them (55%) achieved positive ROI within the first year of deployment, and 21% were able to reach positive ROI in less than 6 months.
Download this white paper to learn how software-defined storage can help reduce data center infrastructure costs, including guidelines to help you structure your TCO analysis comparison.
The emphasis on fast flash technology concentrates much attention on hot, frequently accessed data. However, budget pressures preclude consuming such premium-priced capacity when the access frequency diminishes. Yet many organizations do just that, unable to migrate effectively to lower cost secondary storage on a regular basis.In this white paper, explore:
• How the relative proportion of hot, warm, and cooler data changes over time• New machine learning (ML) techniques that sense the cooling temperature of data throughout its half-life• The role of artificial intelligence (AI) in migrating data to the most cost-effective tier.
Scripting and PowerCLI are words that most people working with VMware products know pretty well and have used once or twice. Everyone knows that scripting and automation are great assests to have in your toolbox. The problem usually is that getting into scripting appears daunting to many people who feel like the learning curve is just too steep, and they usually don't know where to start. The good thing is you don't need to learn everything straight away to start working with PowerShell and PowerCLI. Once you have the basics down and have your curiosity tickled, you’ll learn what you need as you go, a lot faster than you thought you would!
ABOUT POWERCLI
Let's get to know PowerCLI a little better before we start getting our hands dirty in the command prompt. If you are reading this you probably already know what PowerCLI is about or have a vague idea of it, but it’s fine you don’t. After a while working with it, it becomes second nature, and you won't be able to imagine life without it anymore! Thanks to VMware's drive to push automation, the product's integration with all of their components has significantly improved over the years, and it has now become a critical part of their ecosystem.
WHAT IS PowerCLI?
Contrary to what many believe, PowerCLI is not in fact a stand-alone software but rather a command-line and scripting tool built on Windows PowerShell for managing and automating vSphere environments. It used to be distributed as an executable file to install on a workstation. Previously, an icon was generated that would essentially launch PowerShell and load the PowerCLI snap-ins in the session. This behavior changed back in version 6.5.1 when the executable file was removed and replaced by a suite of PowerShell modules to install from within the prompt itself. This new deployment method is preferred because these modules are now part of Microsoft’s Official PowerShell Gallery. 7 These modules provide the means to interact with the components of a VMware environment and offer more than 600 cmdlets! The below command returns a full list of VMware-Associated Cmdlets!
With digital transformation a constantly evolving reality for the modern organization, businesses are called upon to manage complex workloads across multiple public and private clouds—in addition to their on-premises systems. The upside of the hybrid cloud strategy is that businesses can benefit from both lowered costs and dramatically increased agility and flexibility. The problem, however, is maintaining a secure environment through challenges like data security, regulatory compliance, external threats to the service provider, rogue IT usage and issues related to lack of visibility into the provider’s infrastructure.
Find out how to optimize your hybrid cloud workload through system hardening, incident detection, active defense and mitigation, quarantining and more. Plus, learn how to ensure protection and performance in your environment through an ideal hybrid cloud workload protection solution that:
• Provides the necessary level of protection for different workloads• Delivers an essential set of technologies• Is structured as a comprehensive, multi-layered solution• Avoids performance degradation for services or users• Supports compliance by satisfying a range of regulation requirements• Enforces consistent security policies through all parts of hybrid infrastructure• Enables ongoing audit by integrating state of security reports• Takes account of continuous infrastructure changes
Welcome to this free eBook on Office 365 and Microsoft 365 brought to you by Altaro Software. We’re going to show you how to get the most out of these powerful cloud packages and improve your business. This book follows an informal reference format providing an overview of the most powerful applications of each platform’s feature set in addition to links directing to supporting information and further reading if you want to dig further into a specific topic. The intended audience for this book is administrators and IT staff who are either preparing to migrate to Office/Microsoft 365 or who have already migrated and who need to get the lay of the land. If you’re a developer looking to create applications and services on top of the Microsoft 365 platform, this book is not for you. If you’re a business decision-maker, rather than a technical implementer, this book will give you a good introduction to what you can expect when your organization has been migrated to the cloud and ways you can adopt various services in Microsoft 365 to improve the efficiency of your business.
THE BASICS
We’ll cover the differences (and why one might be more appropriate for you than the other) in more detail later but to start off let’s just clarify what each software package encompasses in a nutshell. Office 365 (from now on referred to as O365) 7 is an email collaboration and a host of other services provided as a Software as a Service (SaaS) whereas Microsoft 365 (M365) is Office 365 plus Azure Active Directory Premium, Intune – cloud-based management of devices and security and Windows 10 Enterprise. Both are per user-based subscription services that require no (or very little) infrastructure deployments on-premises.
The primary goal of a multi-cloud data management strategy is to supply data, either via copying or moving data to the various multi-cloud use cases. A key enabler of this movement is the data management software applications. In theory, data protection applications can perform both of the copy and move functions. A key consideration is how the multi-cloud data management experience is unified. In most cases, data protection applications ignore the user experience of each cloud and use their proprietary interface as the unifying entity, which increases complexity.
There are a variety of reasons organizations may want to leverage multiple clouds. The first use case is to use public cloud storage as a backup mirror to an on-premises data protection process. Using public cloud storage as a backup mirror enables the organization to automatically off-site data. It also sets up many of the more advanced use cases.
Another use case is using the cloud for disaster recovery.
Another use case is “Lift and Shift,” which means the organization wants to run the application in the cloud natively. Initial steps in the “lift and shift” use case are similar to Dev/Test, but now the workload is storing unique data in the cloud.
Multi-cloud is a reality now for most organizations and managing the movement of data between these clouds is critical.
There are a number of limitations today keeping organizations from not only lifting and shifting from one cloud to another but also migrating across clouds. Organizations need the flexibility to leverage multiple clouds and move applications and workloads around freely, whether for data reuse or for disaster recovery. This is where the HYCU Protégé platform comes in. HYCU Protégé is positioned as a complete multi-cloud data protection and disaster recovery-as-a-service solution. It includes a number of capabilities that make it relevant and notable compared with other approaches in the market: