Educational Episodes: Hyperconverged Infrastructure (HCI)

You may have heard that RAID is no longer applicable for enterprise storage: that it’s time had passed. RAID has dominated enterprise storage for decades and, while not a hot topic of conversation today, it remains a key strategic approach for businesses to consider. To some degree, it is true, RAID is no longer the singular answer to enterprise storage that it once was.  For decades it was unchallenged as a technology and as an approach, and so reigned alone – a foregone conclusion in a giant sea of storage.  Today, RAIN has joined the space and is a viable alternative to RAID in many scenarios.  But just because RAIN is newer and the darling of storage conversations does not mean that RAIN will simply displace RAID nor that RAID’s position of importance has been eliminated.  Not at all.

This blog is going to be all about the secure certificate side of things, by setting these headers you reduce the chances of certain types of probes and attacks from being successful. The server itself and whatever applications you are running on it still need to be upgraded and configured to reduce the chances of someone gaining unauthorised access to your systems.

Some admins prefer the Cluster updates to be done automatically. To do so, Microsoft designed a feature to facilitate patching of Windows Servers from 2012 to 2016 that are configured in a failover cluster. Cluster Aware Updating (CAU) does this automatically, thereby avoiding service disruption for clustered roles. In this article, we are going to take a look into how we can achieve this assuming that Cluster is built with hyperconverged scenario and VSAN from StarWind used as a shared storage. Before going in the steps to set the CAU, we will investigate this scenario.

The term User Interface (UI) is used for specifying how a user interacts with a specific device, or software. CLI and GUI are two different types of possible user interfaces. Let’s analyze those different approaches and the pro and cons of them, using the VMware vSphere environment as an example.

SMI-S or ‘Storage Management Initiative – Specification’ is a standard of a storage management (surprise!) which gives you a chance to administrate the storage layer using ‘Common Information Model’ and Web-Based Enterprise Management technologies and logic. The main point of SMI-S is to provide a single standard to manage various storage systems from different vendors pretty much in the same way. In this article (?) we will show you how to manage your storage using SCVMM 2016 (Server Center Virtual Machine Manager) through SMI-S, and how this whole thing works in general. We’ll use VSAN from StarWind as a reference distributed storage platform, but the primary scope of this document is to cover the subject in general, so any SMI-S compatible storage will work.

Many words were said about NFS (Network File System), but what exactly NFS can give us? In general, NFS used as the ISO library or just simple network file share with easy access from any Windows or Linux based machine. However, starts from NFS 3.0 protocol can give us the good performance and can be as the shared storage for ESXi or any Linux based Hypervisors. In this article, I will create the NFS share on the Windows Server 2016 and then mount NFS share on the ESXi 6.5 and will create the VM on it.

Before we dive into how to enable Active Directory Recycle Bin in Windows Server 2016, we will first explain what it is and when Microsoft introduced this feature. Active Directory Recycle Bin simply allows you to restore deleted objects from Active Directory. It can be a user account, computer account or a whole Organizational Unit (OU). Who did not accidentally delete an AD object in his career? Without this feature enabled, you had only a few choices. Either you could restore if you used a backup solution allowing you to restore individual AD objects (many virtualization backup vendors do that nowadays). Or you have had less chance and your AD server wasn’t configured to be backed up and you have to recreate the user and reinstall his profile on his computer.  

Companies often store critical client mailbox data on an Exchange server database. The Exchange database is a warehouse of critical mailbox information such as contacts, notes, calendar items and emails of thousands of users. One of the most serious issues companies can face is the corruption of the Microsoft Exchange 2013 database file leading to unavailability of important data for the client. The Microsoft Exchange 2013 database can become vulnerable to crashes due to unavoidable hardware issues, software malfunctions, system freezes, server or boot failures, accidental shutdowns or any unforeseen circumstances. Since the last thing a company wants is to endanger business goals such as data availability during disasters, the first step is to make efforts to recover the damaged file.

Before the time when SSDs took their irreplaceable place in the modern datacenter, there was a time of slow, unreliable, fragile, and vacuum filled spinning rust drives. A moment of change divided the community into two groups – the first with dreams of implementing SSDs in their environment, and the second, with SSDs already being part of their infrastructure. The idea of having your data stored on the associated tier has never been so intriguing. The possibility of granting your mission-critical VM the performance it deserves in the moment of need has never been more appropriate.