Microsoft SQL Server is the backbone of many businesses, but when it comes to high availability, which path should you take: Always On Availability Groups (AG) or Failover Cluster Instances (FCI)?
Microsoft Azure offers its services on a pay-as-you-go basis. This means that your expenditure depends on the cloud resources used. You’ll want to keep them as close to an application’s needs as possible. Otherwise, you’ll either experience slowdown or unreasonable costs. Thankfully, you can alter your VM disk size and performance on the fly.
Virtualization machines (VMs) have various use cases, each defined by the IT resources at hand and respective end-goals. VMware vSphere and Horizon offer three types of cloning when it comes to VM interoperability: full, linked, and instant cloning. Each type has its benefits but also takes its own toll on the system.
Azure Migrate has recently seen an update to its features. It can now help you move your ASP.NET and Java applications to an Azure Kubernetes Service (AKS) container. Usually, such apps would be hosted on Tomcat/IIS. It would be quite a chore to move them to Kubernetes. However, said new capability makes the process much more streamlined.
More and more people turn to hyperconverged infrastructures each year because, well, they do have a lot to offer. Many people are starting with such well-known and admirable solutions as VMware vSAN, enabling you to replace physically shared storage. That is an excellent choice, but there are a few things you need to know before you start.
We readily discuss everything new coming out each month from Microsoft and Azure. Modern cloud and hyperconvergence services take up most of our discussions and wallets when it comes to virtualization. But there are a lot of people who still use Unix-based cloud services, and their monitoring and management tools can be quite different.
Azure Resource Mover is a feature that helps to move your Azure resources from one Azure region to another with ease. The feature also notifies you about relevant dependencies to help prepare your target and source region for proper functionality after moving. This removes the need to exercise the procedure using various windows and services. Everything is done in one place.
Everybody knows how tedious it may be working with self-signed SSL certificates. That’s why it’s easier to add the Microsoft Certificate server role to your Active Directory. However, manual certificate enrollment is not so handy when there are dozens of users within one IT infrastructure, and if that’s the case, it won’t hurt to learn how to cut a corner or two!
In the previous article, I have shared a working algorithm on replacing the ESXi SSL certificate with a self-signed one, but, as you know well, there’s always room for perfection. So, I have been practicing with a more universal scenario that could also work with a domain infrastructure and domain certificate services. That’s what I came up with.
Along with various recent updates, VMware released its new version of vSphere Replication 8.4. It’s a free perk that comes included with the vSphere package and has a limited potential to enable and operate VM replication to remote locations. Although it’s quite a basic feature, it can still provide valuable benefits for small deployments scenarios.
Operating VMs can be overwhelming when you’re overseeing an enterprise-class IT environment. Azure Automanage is a new feature that applies Azure best practices configurations to a VM based on its services. Once the VM is onboard, the feature applies the most appropriate configs to it, monitors it for drift, and auto-corrects it in case of deviation.