I'd like to run containers on a Windows Server 2022. Unfortunatelly it says The container operating system does not match the host operating system.
My host ver is: 10.0.20348.261 (I haven't found any description of this on Google)
My dotnet image ver is: 10.0.20348.230 (which is probably the RTM)
Is it caused by installed latest updates? Is the best practice leaving the host unpatched?
I've followed the documentation, host can connect to remote log port using nc, but no logs are received. As a remote syslog I'm using Loki and Promtail which only supports RFC 5424.
Does ESXi ship this format? How the format can be changed?
I have 3 ESXi 6.5 hosts with the same network configuration: single Standard Switch with four networks with same naming on all hosts. This is what I see at ESXi web client.
Inside vCenter I see another four networks with different names (their names suggest that these names were used some time ago). Each of them is attached to a single VM and no host. Is it possible to delete them somehow? The reason why I am asking is that I tried to deploy vSphere Integrated Containers, but with no luck. The wizzard hangs on Network tab.
I have a service to check if a src.ods file was changed. When the system is rebooted, it keeps looping. When I update the file it starts to behave correctly (restarts only at file change). How to avoid the loop at system start before file change?
while inotifywait -q -m -e close_write /home/admin/data/src.ods; do
echo $(date -Iseconds) Restarting
done
I'm testing S2D now and I would like to calculate MTBF for the whole system. It seems very fragile to me:
Let's have 4 nodes (x) with 12 drives (y) in each. MTBF for one node is 1/12 of single drive value. For three-copy mirror we can tolerate 2 node failures (equals two failed disks in different nodes). That gives me 2/4 MTBF of single node value. In total it is 1/24 or 2/(x*y) MTBF in comparison to single drive.
This value is quite low and gets even lower for larger deployments. Is my calc correct? I know that Microsoft recommends to reserve capacity of 2 disks in the pool aka hot-spares, but is it sufficient for production use?
I'm testing S2D. I have created cluster from 2 VMs and call PowerShell
Enable-ClusterStorageSpacesDirect -SkipEligibilityChecks -Confirm -CacheState Disabled
List of storage
Type Node Size Used Percent
---- ---- ---- ---- -------
HDD 1 21GB 0 0%
HDD 1 129GB 0 0%
HDD 1 107GB 0 0%
HDD 1 140GB 0 0%
HDD 1 118GB 0 0%
HDD 1 11GB 0 0%
HDD 2 21GB 0 0%
HDD 2 129GB 0 0%
HDD 2 107GB 0 0%
HDD 2 118GB 0 0%
HDD 2 140GB 0 0%
HDD 2 11GB 0 0%
In Failover Manager I can see that S2D Clustered Windows Storage has 986 GB free space, but when I try to create new volume, the maximum available capacity is 51 GB. I would expect ~490 GB. Any clues why the maximum is such low? Which steps am I missing?
Update Adding extra 300 GB drive to each VM increased free space to 1.51 TB and maximum volume size to 63 GB. Still not satisfied with the result.
I've tiered storage 10GB SSD and 300GB HDD on Windows 2012 R2 guest at ESXi. I've extended the SSD disk as usual, but at Server manager -> Storage pools I still see the old size of SSD in Physical disk section. Can it be refreshed somehow or is it possible to add new SSD disk to existing storage pool?
I've found nice Technet blog which gives some advices when to use which replica init method, but without any technical detail. To make a good decision I would like to know how the replication using Use an existing virtual machine as the initial copy actually works. There is no requirement for snaphosts, not changed VHDs, just the virtual machine ID has to be the same. Does it read whole disks on both nodes, checks block hashes and sync blocks which differs?
I have a simple file share on Windows 2012 R2 server which I would like to be high available. I created failover cluster, but I'm not able to set up FileServer service as there is no shared storage. For my purposes buying high available shared storage is very expensive option.
The manual way would be to create secondary file share and use robocopy for syncing. In case of failover I would need to change network path to 2nd server.
Is there any fully-automated solution which is free or included in Windows licence?
I have several servers with local SATA/SAS RAID arrays. I would like to run there virtual machines with some level of automated failover - sync VM to secondary node in 1 minute interval and automated start when primary node died at least.
I've already created failover cluster with fileshare witness on another machine. In Failover Manager I'm not able to add any Disk, says "No suitable disk". I tried to add virtual iSCSI disk via MS iSCSI Target but it didn't appear either. Hyper-V Replica Broker can't be enabled without shared stored.
How to achieve failover with current hardware on Hyper-V? If not is there any other virtualization platform for my needs? Based on my search with VMWare I would need HA + vSAN which is quite expensive, Google's Ganeti doesn't work well with Windows guests.