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)?
This day has come – vSphere 6.5 has been just announced. As many of you I have been waiting for the presentation of new vSphere during VMworld event in the USA, but I guess VMware preferred to use vSphere 6.5 as a treat for those who were in doubt whether to attend VMworld Europe or not after all VMworld US were made available online to everyone; or perhaps VMware hasn’t decided what features should be included into the GA release. In this post, I will try to cover all new features of vSphere 6.5 and VSAN 6.5, but if I missed something feel free to let me know by leaving a comment. To be honest, there is so much to talk about and some of the new features require separate posts to be explained properly. Therefore, please don’t expect detailed review of the every single feature.. This is more ‘What’s new in vSphere 6.5 and VSAN 6.5’ overview, but in the future posts I will be talking about some of the most interesting improvements and enhancements in detail.
Security is a critical requirement of any organization’s system. With the release of Windows Server 2016, Microsoft puts a lot of efforts around security and added a lot of new features. One hot feature that will add a lot of benefits to any small, medium and enterprise business environments is Shielded Virtual Machines and Key Storage Drive (KSD). Be sure that’s going to help you to increase the security whether you are a service provider or enterprise customer.
What works for 100 users very often doesn’t work for 10,000, and vice versa. Few vendors worry about making software created for the enterprise meet the needs of the SMB. Those who try to fit both worlds, rarely succeed. Specifically, let us look at Active Directory (AD) replication times. By default, AD is scheduled to do inter-site replication every 180 minutes (three hours), which makes sense if the AD is huge, and one or more of the sites is on the other end of connectivity from the past. This value can be changed from the default to occur as frequently as once every 15 minutes, representing a somewhat conservative minimum replication interval.
With the release of Windows Server 2016, there’s a lot of new features that have been added to increase availability and security. One hot feature that will add a lot of benefits for small, medium and enterprise business environments is Storage Replica (SR). Be sure that’s going to help you in your Disaster Recovery Plan and protect your data against catastrophic losses.
Microsoft has released the final version of Windows Server 2016. I thought that it might be a good idea to create a USB stick that can be used as a source to install the Windows Server 2016 OS to other servers/workstations.
There are many free tools that can be used to do the job, but sometimes you just don’t have that option or simply you do not want to use any free tools for this job. It is not so difficult to create a bootable USB, and this post will teach you how to do that in 6 easy steps.
Interestingly, in the enterprise data center trade shows I have attended recently, the focus was on systemic risk and systemic performance rather than on discrete products or technologies; exactly the opposite of what I’ve read about hypervisor and cloud shows, where the focus has been on faster processors, faster storage (NVMe, 3D NAND) and faster networks (100 GbE). This may be a reflection of the two communities of practitioners that exist in contemporary IT: the AppDev folks and the Ops folks.
vRops 6.3 has been announced. I have already upgraded a test environment of mine and a few production environment and are talking to customers who what’s to upgrade ASAP. There are different great features that make an upgrade worthwhile.
Before I jump in and show case all the cool improvements and added features. A word of caution BEFORE upgrading make sure all endpoint operations agents have been upgraded. vRops 6.3 is not backward compatible with 6.x agents.
The placement of the virtual machines in a Hyper-V cluster is an important step to ensure performance and high availability. To make a highly available application, usually, a cluster is deployed spread across two or more virtual machines. In case of a Hyper-V node is crashing, the application must keep working.
But the VM placement concerns also its storage and its network. Let’s think about a storage solution where you have several LUNs (or Storage Spaces) according to a service level. Maybe you have an LUN with HDD in RAID 6 and another in RAID 1 with SSD. You don’t want that the VM which requires intensive IO was placed on HDD LUN.
Samsung announced its 960 PRO and 960 Evo, the next generation M.2 PCIe SSDs. Like the 950 Pro, the 960 Pro and 960 Evo are PCIe 3.0 x4 drives using the latest NVMe protocol for data transfer. The 960 Pro offers a peak read speed of 3.5GB/s and a peak write speed of 2.1GB/s, while the Evo offers 3.2GB/s and 1.9GB/s respectively. The 950 topped out at a mere 2.5GB/s and 1.5GB/s.
The 960 Pro and the 960 Evo are planned for release in October. The Pro starts at $329 for 512GB of storage, rising up to a cool $1,299 for a 2TB version. The Evo price goes from $129 for a 250GB version to $479 for a 1TB version.
In Windows Sever 2016 Microsoft improved Hyper-V backup to address many of the concerns mentioned in our previous Hyper-V backup challenges Windows Server 2016 needs to address: