Posts made by R3dPand4

@networknerd Oh no problem! I don't want a load of people to be inconvenienced for my sake. I'm looking forward to attending one when the schedule lines up. Thursday would probably be ideal for me if I had to pick a weekday.

Late to the party....but just my two cents...haven't found a situation in which I'd want to join my hosts to a domain. The only consideration I could see here is if you're configuring failover clustering, but I'm fairly certain that applies to pre-2016. Generally when we're talking about Hyper-V Hosts and management pc's I have a dedicated workstation/laptop that's off domain and then create a mirrored Administrator account on the Hyper-V Hosts that's also off domain.

I'm hoping I'll be catching the next one in the area that's not on a Tuesday.

+100 for Ubiquiti, also take a look at Mikrotik

@scottalanmiller Exactly, just above InfoPath on the priorities list.

@olivier So essentially just deduplication?

@olivier Thank you for clarifying, I'm assuming this would apply principally at least the same to a 2 node cluster? One goes down, writes are briefly suspended, writes resume on the Active node, failed node is replaced, then rebuild/healing process continues on the New node. How long are you expecting for rebuilds? I'm sure that's a loaded question because it's data dependent.....

@olivier We're talking about node failure where you're replacing hardware correct?
"On a 2 node setup, there is an arbiter VM that acts like the witness. If you lose the host with the 2x VMs (one arbiter and one "normal"), you'll go in read only."
So are Writes suspended until the 2nd node is brought back online and introduced to the XOSAN? Obviously that's going to be a lot longer than a few seconds even if you're talking about scaling outside of a 2 node cluster. Do you mean that Writes are suspended or cached in the event of a failure while Host is shutting down and then Writes resume as normal on the Active node? If this is the case when the new Host is introduced to the cluster the replication resumes, correct?

@dashrender The same thing as if you lost a mirrored pair with RAID1 or 10.

@olivier So you only gain in capacity scaling in 2's? Again as I mentioned earlier I'm curious how the Write suspension functions during failure....

@olivier So you just can't make any writes during this period of node failure/recovery? Are the writes cached? If so how much can be cached and for how long?

@dustinb3403 Or at least in my opinion a lack of interest and or resources. If we think about it from a business perspective, are they going to sell more Datacenter Licenses just because they have a viable SDS bundled with it? I'm not sure, but I'd guess probably not enough for them to dedicate what would likely be needed to get them there.

@scottalanmiller And we're still no closer to having a production ready MS SDS product....

@olivier Have you tested how it behaves if you shut down both hosts and then fire them back up? Do you have either of them weighted or master/slave? Suppose you have to replace an entire node, do you just mount the XOSAN and it begins replicating? Sorry if I'm jumping way ahead, but this is very interesting.

Relatively tidier by the second as I get ready for a long weekend, while I faceroll on my KB Paradise V80 w/Matias QC experimenting in the lab with a CentOS 7/KVM & Ceph deployment.

@fateknollogee I mean that's depending on your deployment, it's included with 2016 Datacenter....

Neither, but some areas of note just from looking at that site briefly:

"To begin with you need atleast three servers, but the more the better.
To be able to use as much raw disk as possible it's better to build many nodes rather then less nodes with lot's of storage disk in them."

"All data is stored in multiple copies and possibly geographically separated locations within the cluster."

"Start as small as four nodes"

There are some strangely semi-conflicting statements within the site itself, and seeing the word "possibly" when describing where your data stripes are distributed within the cluster doesn't really fill me with too much confidence. You could always try it in the lab, but I haven't seen or heard of anyone using it in production at this moment in time. Also I'm not sure what your node count is looking like but if you're in the 2-4 range I'd recommend just sticking with what's industry proven.

Hey everyone,

I just wanted to get a discussion going regarding one thing that's always puzzled me about Windows Server Administration, and that's Kerberos mismatches breaking Secure Channels between DC's. I understand in theory why this happens, when it definitely will happen, but I've also seen seemingly random occurrences of this.
I'm currently working on a POSH script to proactively check the Secure Channel status and Replication health between all DCs to minimize the client side impact these breaks can cause. At the moment I'm just needing a reliable way to break the secure channel between DCs in the lab for further testing of the script.
Our group is not an MSP officially yet so when I'm called it's time to clean up the aftermath, sadly at this moment I'm not day to day monitoring these clients, if I was obviously this would be more straight forward. That being said I'm still looking to improve the end user experience where possible.
What's your preferred method in dealing with these issues?

Thanks @scottalanmiller , @QuixoticJeremy , and @dafyre ! Happy to be here! I work for a group who's slowly but surely moving into the official MSP space as an Enterprise Support Tech. I'm looking to move into the Engineering space in the near future as I'm currently working towards my MCSE. Looking forward to speaking with and hopefully meeting some of you soon!