Educational Episodes: Hyperconverged Infrastructure (HCI)

The fast-paced world of system administration is growing on a large scale and picking up steam all the time. The migration of business to the cloud we can see these days is a good example of the above said. Thus, the continuous pursuit of a tool that would simplify the life of a system administrator constantly stays on the agenda of the IT world. The main goal behind the development of the Storage Management Initiative (SMI) is eliminating the long journey of finding the right solution. To simplify the life of system administrators to an even greater extent, the StarWind team has decided to additionally complete the feature set by developing the StarWind Swordfish Provider.

We all already know the two biggest Public Cloud providers are Amazon Web Services (AWS) and Microsoft Azure and, unless a catastrophic event occurs, these two will be leading the market in the next couple of years. A recent study between 550 companies showed some interesting results: AWS is the most preferred vendor in SMBs; Microsoft the “most known” in enterprises; AWS has been reviewed the most between all companies but Azure is the most used.

As written in the previous post, for ROBO scenario the most interesting HCI (Hyper-Converged Infrastructure) configuration is a two nodes configuration, considering that two nodes could be enough to run dozen VMs (or also more). For this reason, not all hyperconverged solutions could be suitable for this case (for example Nutanix or Simplivity need at least 3 nodes). And is not simple scale down an enterprise solution to a small size, due to the architecture constraints.

Anyone who has configured and used SMB Direct with RoCE RDMA Mellanox cards appreciates the excellent diagnostic counters Mellanox provides for use with Windows Performance Monitor. They are instrumental when it comes to finding issues and verifying everything is working correctly.

NIC teaming is not something we got with Windows Server 2016, but I just find it interesting to review this functionality as we have it in the current iteration of Windows Server, as usual, touching a bit on the basics and history of this feature.

One of the things I come across time and again is a lack of monitoring in what are supposed to be corporate environments. I am honestly surprised at how little monitoring is carried out on infrastructure. These days, it is quite possible to carry out some very in-depth monitoring by using a freely available software on Linux and Windows. In this article, I’m going to go through the various monitoring tools that I use to monitor both production and my lab environment.

In this first blog post, I’ll walk you through to migrate Active Directory objects (users, groups, and workstations or member servers) between two domains in the same forest (Intraforest) using Active Directory Migration Tool (ADMT) 3.2. ADMT allows you to migrate objects (including users, groups, computers, profiles, service and managed service accounts) with the help of ADMT console, command line, and VBScript. However, in this post, I’ll focus only on ADMT console and command line.

Tapes have been on the “backup market” for a long time and still are considered as a good option to store and secure a high amount of backup data. However, the continuous increase of backup size becomes a bottleneck in terms of fitting backup windows and reduces a simplicity and redundancy of backup solutions. Today more and more companies consider backing up their production data to more reasonable storage solutions, like Clouds. Here comes in hand the technology that emulates physical tapes on top of inexpensive, fast, and high-capacity spindle drives.

In previous installments of this blog, we have deconstructed the idea of cognitive data management (CDM) to identify its “moving parts” and to define what each part contributes to a holistic process for managing files and more structured content. First and foremost, CDM requires a Policy Management Framework that identifies classes of data and specifies their hosting, protection, preservation and privacy requirements of each data class over its useful life.  This component reflects the nature of data, whose access requirements and protection priorities tend to change over time.