Windows 10: Different storage in windows server 2022 failover cluster

In windows failover cluster of four nodes is it possible that two nodes have different storage and the other two nodes have different storage?

:)

 

Failover Cluster Storage Replication

We have a Windows failover cluster containing a shared disk assigned to a Role and want to set up replication from it.

We tried removing the disk from the cluster to use DFS Replication, however we lose access to the network shares of the disk even once they are recreated with the same permissions and pathways. We regained access once we recreated the role with the shared disk.

Going off of that, we need to replicate within the cluster. When configuring storage replication, our second shared disk that is in available storage is ineligible due to the flag "Not in a different site."

I'm unable to find anything related to this error, and the Windows guides I have found all show Cluster to Cluster replication.

Could anyone explain this flag or does anyone know of the proper way to configure the cluster storage replication?

 

Failover Cluster

Dears

We upgraded our environment from Windows Server 2012 R2 into Windows 2019

Everything seems to work normally except for Windows Failover Cluster Service

The service is not able to run at all with the event id1090

We removed the failover cluster feature and re-add it again; however, the problem persists

Please advise

Thank you

 

Issues with report server setup during Install of MBAM using a SQL failover cluster

I'm trying to setup MBAM 2.5SP1 on Server 2016 using a SQL 2016 on a Failover Cluster (but not using AO).

The initial database configuration went smooth, but setting up the next step (Reports) is causing an issue because it cannot find the instance of the report server.

"Unable to find an instance of the Reporting Services.

That said, I realize that the report server is not supported with the failover cluster, but is there a way to point the Report feature to another SQL server or a server that has the reporting services (ie: one of the Failover cluster nodes) instead of auto-detecting
the SQL failover cluster name/IP?

I'm trying to avoid having a SQL server just for MBAM if I can avoid it (for cost and manageability reasons).