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 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)?
Security, privacy, and performance have always been a priority for many businesses even over the limitless scalability offered by the cloud. Join us for a new video, on how to transform two on-prem VMware vSphere hosts into a bulletproof high-availability (HA) cluster for improved cost-effectiveness, high VM performance and enhanced security, in 5 easy steps.
Want to optimize your storage infrastructure? Learn how StarWind Virtual SAN (VSAN) helps organizations achieve high availability and resilience.
Worried about keeping your business data safe from ransomware and other threats? Discover how StarWind Virtual SAN (VSAN) can fortify your backup strategy as a hardened repository for Veeam Backup & Replication (B&R).
Most admins know that VMware offers Free and Evaluation versions of their hypervisor. However, there are still some nuances that explain why people would actually buy ESXi.
V2V in Focus: What’s virtual-to-virtual migration all about? Learn what V2V is, why it matters, and how it works. Check out reasons for migration, hot vs. cold migration, and tools like StarWind V2V Converter.
VMware vSphere and Microsoft Hyper-V are among the most popular type 1 enterprise hypervisors. However, their VM formats are incompatible, and it is not uncommon for users to look for an easy way to migrate a virtual machine from one hypervisor to another.
In the previous article, we have covered the basics of Microsoft Windows Server Core installation. After configuring the operating system and specifying the networks and storage for the future configuration, there are few more things left.
When it comes to SQL Server database indexes there is a wide scale of variation in depth of knowledge on this important topic among IT professionals leveraging SQL Server power while not necessarily being specialist DBA. Let’s discuss SQL server indexes a bit here with non-SQL DBAs/non-DB developers audience in mind covering why and how sides of the subject.
Microsoft’s Hybrid Cloud appliance to run Azure in your datacenter has finally reached to General Availability (GA) and the Integration Systems (Dell EMC, HPE and Lenovo for this first iteration) are formally taking orders from customers, which will receive their Azure Stack solution in September. But, what exactly represents Azure Stack? Why is this important to organizations?
This series of articles will guide you through the basic deployment of Microsoft Windows Server 2016 Core version, covering all the steps from an initial installation to the deployment of Hyper-V role and Failover Cluster configuration. The first and the main thing you need to double-check before installing the Windows Server 2016 Core is whether your hardware meets the system requirements of WS 2016. This also is very important in the process of planning your environment, in order to be sure that you have enough amount of compute resources for running your production workload.
Orchestrator is a workflow management solution for the data center. Orchestrator lets you automate the creation, monitoring, and deployment of resources in your environment. Orchestrator is also known as “SCORCH” or “SCO”. Orchestrator uses a drag and drop graphical interface to allow admins to define runbooks. A runbook is a compilation of routine procedures and operations that Orchestrator will run depending on your scheduling. Finally, Orchestrator is capable of managing multiple operating systems. After reading this guide, you should have a basic understanding of how to upgrade/install Orchestrator.
I recently looking for Azure Automation, from top to bottom. It’s why, in the next 2 articles, we will see how to use this tool, from A to Z:
Start with the first article.
Very often, VMware vSphere administrators have to find the reasons of performance issues by analyzing the historical data of various metrics on the VMware vCenter Server. However, sometimes the default set of metrics is not enough if you view performance data for the previous night or the end of the past week – in this case, you need to change the level of collected metrics and, possibly, the frequency of their collection and retention. In the VMware vCenter Server settings, you can set the data collection levels, different collection intervals and the time period that the data will be stored on the Server. In addition, you can set an approximate size of the virtual infrastructure in the host servers and virtual machines, which will allow to roughly estimate the size of the vCenter database. Let’s take a closer look at these settings.
As we referenced several times, security is one of the main topics for cloud providers looking to guarantee privacy for their customers’ data and information. Microsoft just announced the public availability for Storage Service Encryption (SSE) for Azure Managed Disks, with no additional cost.
VMDK file to LUN storage architecture has been the most usable scenario for years until VMware released Virtual Volumes in vSphere 6.0. In the case of an array with block access, own VMware file system – VMFS – was used -, and NFS was used for file storage. The array capacity was divided into LUNs or NFS-shares and presented ESXi hosts in the datastore form. Frequently, datastore is a large capacity storage housing numerous VMs. In fact, allocating a separate datastore for each VM is quite inconvenient and time-consuming in terms of administration.
Many IT administrators or virtualization guys run their homelabs at home. It is a good way to learn new technologies, be able to break things in a lab to get stronger skills. It is sometimes a challenge, to squeeze as much RAM as possible from it. The main challenge is always a memory utilization. VMware VMs are getting memory hungry all the time and they are not “optimized” for Homelab use, but rather for production environments. Yes, it is the main purpose of those VMs after all.