As we increase the block size and number of threads so does the performance up to a certain point. The hardware is capable of high performance without having to go and tweak a lot of things.
Technical information related to setting up FC-NVMe instead of FC (SCSI) seems to be non existing for the GEN3 and/or AIX at time of writing.
DRAID6 seems like a good alternative to the traditional RAID10 even for critical workloads, if you are concerned about disk failures then configure it for two rebuild areas which allows you to loose two disks.
If you are upgrading from a RAID10 spinning disk (15K) array to NVMe SSD array, strongly consider DRAID6 as an alternative.
It was not possible to assign a stand-by hot-spare in a DRAID6 configuration, you can still mark an SSD as a spare but the software will not automatically consume it if a disk fails.
No issues whatsoever failing one of the active/active storage nodes and monitoring the events inside AIX, everything worked as expected in a redundant path host and storage configuration.
Traditional Raid 10 Benchmarks (two mdisk devices, total of 16 drives + 1 spare)
I noticed that once you deploy headless windows servers (domain controllers as an example) you can manage everything remotely (mmc, event viewer, rsat, etc.) except Windows Firewall right out of the box.
To be able to manage the firewall remotely, you need to open additional ports on the headless instance using:
netsh advfirewall firewall set rule name="Windows Firewall Remote Management (RPC)" new enable=yes
netsh advfirewall firewall set rule name="Windows Firewall Remote Management (RPC-EPMAP)" new enable=yes
Most evaluation versions can be converted to full retail versions, but the method varies slightly depending on the edition. Before you attempt to convert the version, verify that your server is actually running an evaluation version.
For releases of Windows Server 2016 prior to 14393.0.161119-1705.RS1_REFRESH, you can only perform this conversion from evaluation to retail with Windows Server 2016 that has been installed by using the Desktop Experience option (not the Server Core option). Starting with version 14393.0.161119-1705.RS1_REFRESH and later releases, you can convert evaluation editions to retail regardless of the installation option used.
To confirm you are running evaluation version, use:
DISM /online /Get-CurrentEdition
Next we need to figure out what version we can convert into using:
If you need to convert to other editions, use the correct keys below.
Windows Server 2012 R2 Server Standard: D2N9P-3P6X9-2R39C-7RTCD-MDVJX
Windows Server 2012 R2 Datacenter: W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9
Windows Server 2016 Datacenter: CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Standard: WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2019 Datacenter: WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Standard: N69G4-B89J2-4G8F4-WWYCC-J464C
I have observed that it can take up to a few hours for this process to complete (TiWorker.exe taking up lots of CPU during this task) in Server 2016. It was observed that the process was much quicker in Server 2012 R2.
This guide will show you how to deploy two headless Windows Server 2016 domain controllers in a new environment. This guide (first of the series) assumes you are standing up a hybrid Microsoft environment within a VMware homelab.
First we need to get a few things out of the way:
2 Windows 2016 virtual machines with 2 vCPUs and 4-8GB RAM
Make sure you are using VMXNET3 network adapters
Install latest VMware Tools
Apply latest OS updates
Change the HOSTNAME of the VMs (XXX-DC01 and XXX-DC02)
Change the host to use static TCP/IP and DNS
If you are deploying domain controllers from a base Windows 2016 VM template, do not forget to generate a new SID using: C:\Windows\System32\Sysprep\sysprep.exe
We are going to deploy two domain controllers at a bare minimum, the domain name is going to be called corp.fixmytech.ca and our network will be 192.168.1.1/25.
The domain name you choose should be resolvable from the internet, so choose a domain that you have registered with a domain registrar and that of which you have full control of.
Some common candidates for xxx.fixmytech.ca are:
One common 3 letter server prefix used for the internal server names is the IATA 3-Letter Codes of the closest airport.
To do most of the basic first steps you can use sconfig (shell GUI) or issue the following: