@hobbit666 said in HA With switches:
Another things that got me confused. SPF+ modules.
I can see Ubiquiti SPF+ 10G MultiMode modules are £40 odd for a 2 pack.But a Fibre module for Netgear are £200+ each
Aruba £600 odd
SFP can be for copper or fibre. It can be active and passive with active pushing the signal further. Those are the differences between the modules IIRC.
@nadnerB said in Random Thread - Anything Goes:
Going to order the movie. Saw a clip of it go by in one of my feeds and it looked really good.
Mel Gibson.
@wrx7m said in PowerShell - Create New AD User Using Prompts and Variables:
If I get rid of the attempt to combine the 2 existing variables into a 3rd, I get this error.
New-ADUser : A positional parameter cannot be found that accepts argument '+'. At \\FP02\it\Scripts\AD\AD-InitialUserCreationVariables.ps1:5 char:1 + New-ADUser -Name "$GivenName $Surname" ` + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [New-ADUser], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.ActiveDirectory.Management.Commands.NewADUser
Like this I think:
New-ADUser -Name "$($GivenName) $($Surname)"`
From: https://blogs.technet.microsoft.com/stefan_stranger/2013/09/25/powershell-sub-expressions/
@dafyre said in Random Thread - Anything Goes:
@PhlipElder said in Random Thread - Anything Goes:
@nadnerB said in Random Thread - Anything Goes:
Going to order the movie. Saw a clip of it go by in one of my feeds and it looked really good.
Mel Gibson.
I'll take mine in Stetson please.
If you have the original 2019 .ISO file already then slipstream the latest Servicing Stack Update and Cumulative Update into the Install.WIM and recreate the .ISO file. The method we use is here.
Inception in the theatre. Twice.
Saw TENET on Thursday. Theatre's sound was hooped so missed most of the dialogue and came away with a migraine because of the over driven bass. Still got the gist of it, but need to see it in a better theatre.
Tonight, family friends coming over to watch The Dark Knight Rises. We've watched the previous two already (we get together once every two weeks). Previous to that was the Lord of the Rings Extended Editions. It's becoming a bit of a tradition here. 
@black3dynamite said in HyperV Server - Raid Best Practices:
Wouldn't it best to use the SSD for things like caching, page file?
Neither the host nor the guests should be paging. If they are, then there is a problem with the way things are set up host wise or in-guest resources wise.
Until the companies making vaccines have their indemnity removed there ain't no way we'll be anywhere near one of them.
Don't believe everything you read as far as "experts" go either.
"Cases" "Spiking" have nothing to do with virus movement through a population as is being inferred. That's a lie. It just means more testing with test results being positive.
@scottalanmiller said in HyperV Server - Raid Best Practices:
@PhlipElder said in HyperV Server - Raid Best Practices:
@black3dynamite said in HyperV Server - Raid Best Practices:
Wouldn't it best to use the SSD for things like caching, page file?
Neither the host nor the guests should be paging. If they are, then there is a problem with the way things are set up host wise or in-guest resources wise.
But there should be a file for emergencies.
Run on the host/node in elevated CMD:
wmic.exe computersystem where name="SERVERNAME" set AutomaticManagedPagefile=False
wmic.exe pagefileset where name="c:\\pagefile.sys" set InitialSize=4199,MaximumSize=4199
shutdown -r -t 0
The double slash is required.
For standalone hosts we set 8192 instead of 4199.
Either MiniDump or Active Crash Dump is set. That's about all the page file would be used for is helping to produce those dump file AFAIK. A full dump would require a full page file equal to installed RAM. That's nuts when we're deploying hosts/nodes with 512GB to 3TB of available RAM on one node.
@popester said in Covid: Antibodies 'fall rapidly after infection':
@JaredBusch said in Covid: Antibodies 'fall rapidly after infection':
@PhlipElder said in Covid: Antibodies 'fall rapidly after infection':
extremely costly and a lot less efficient than the US one.
HAHAHAHAHAHAHAHAHAHAHAHAHAHA
US says, hold my beer.
Being conditioned by the current messaging is one thing, knowing by experience is another.
Suffice it to say, despite the issues with the US medical system, it is nowhere near as bad as ours.
A simple solution to the US issue is to put the "price" of services in the consumer's hands. Publish the number insurance pays. Folks will start shopping around for a better price forcing competition. Those multi-million dollar admins hospitals need to run will be greatly reduced.
Up here, we have no choice. Public Unions and workers scream and Gov throws more money on it. Per capita here in Alberta we spend $10B more than any other province in the country.
Our system is so bloated and broken that it can take a year or more to get basic surgery services. People are dying up here man.
The grass is always greener.
The default algorithm in Server 2019 is Hyper-V Port for LBFO Teams. There's no reason to tweak anything beyond the "Share with host OS" setting. Choose the ports to be included in the team, bind a virtual switch to the team, and flip the VMs over to the newly created vSwitch.
Takes about 10 seconds to do the above in PowerShell. The link is to a guide for setting up a standalone host using PowerShell.
@popester said in Covid: Antibodies 'fall rapidly after infection':
@PhlipElder said in Covid: Antibodies 'fall rapidly after infection':
@popester said in Covid: Antibodies 'fall rapidly after infection':
@JaredBusch said in Covid: Antibodies 'fall rapidly after infection':
@PhlipElder said in Covid: Antibodies 'fall rapidly after infection':
extremely costly and a lot less efficient than the US one.
HAHAHAHAHAHAHAHAHAHAHAHAHAHA
US says, hold my beer.
Being conditioned by the current messaging is one thing, knowing by experience is another.
Suffice it to say, despite the issues with the US medical system, it is nowhere near as bad as ours.
A simple solution to the US issue is to put the "price" of services in the consumer's hands. Publish the number insurance pays. Folks will start shopping around for a better price forcing competition. Those multi-million dollar admins hospitals need to run will be greatly reduced.
Up here, we have no choice. Public Unions and workers scream and Gov throws more money on it. Per capita here in Alberta we spend $10B more than any other province in the country.
Our system is so bloated and broken that it can take a year or more to get basic surgery services. People are dying up here man.
The grass is always greener.
Understood, it just seems that we are trying really REALLY hard to ruin it. I personally liked my plan, I wanted to keep my plan. Didn't seem to work out that way. Don't know enough to argue it either way, just know that somebody is making bank on my premiums that have gone through the roof.
"I'm from the government and I'm here to help"
Always, always, always beware The Man.
As soon as Gov gets involved, things get EFFED up. Period.
The corruption up here is insane as it is down there. There's absolutely no will in Gov to deal with it. No cohones to put Public Unions in their place when "bargaining".
Unions portray Gov as evil but it's really "We the People" that end up paying for their largesse.
Dismissal Ladder. Know what that is? I didn't. No accountability. Folks in Health Services can practically kill someone up here and NOT BE DISMISSED!
Work Rules: Know that they are? They are a way to force an employer to create more positions. Why? Because unions don't get more dues on better wages they get more dues with more positions. The Work Rules Bible is key to the bloat in public services.
We're being r*ped up here. It's horrible. No accountability at all.
@jim9500 said in Safe to have a 48TB Windows volume?:
It seems like I remember Scott Miller talking about combining enterprise hardware + SAS/SATA Controller + Linux for storage requirements vs proprietary hardware raid controller.
@Donahue - Yes. I have a similar setup offsite backup several miles away for disaster recovery / hardware failure etc. I know raid != backups.
What's the air-gap to protect against an encryption event if any?
@PhlipElder Y'all see the "Great Reset" push that's coming down the pipe?
Do all y'all understand, and I mean understand, what it is implying and what it means for the regular Joes & Janes of this world?!?
My family has been through two Red Revolutions and one near miss with the Armenian Genocide. The whole thing is just too coincidental.
Sorry, not buying it. I'm not buying the virus push at all anymore.
I'm firmly in the Better Dead Than Red camp here.
@scottalanmiller said in Safe to have a 48TB Windows volume?:
@DustinB3403 said in Safe to have a 48TB Windows volume?:
Doesn't ntfs have a limit of 16TB per volume?
NTFS volume limit is 256TB in older systems.
NTFS has an 8PB volume limit in modern ones.
The one caveat to NTFS Volumes as far as size goes is the 64TB limit for Volume Shadow Copy snapshots. A lot of products use VSS for their purposes.
@nadnerb said in Random Thread - Anything Goes:
Reminds me of the times where a system drive would crash, we'd get the call, I'd show up, and low and behold a rare earth magnet was holding their entire kitten p*rn collection to the side of the PC right near the drive's location.
Heh ... those were the days.
@scottalanmiller said in Safe to have a 48TB Windows volume?:
@PhlipElder said in Safe to have a 48TB Windows volume?:
@scottalanmiller said in Safe to have a 48TB Windows volume?:
@Obsolesce said in Safe to have a 48TB Windows volume?:
@scottalanmiller said in Safe to have a 48TB Windows volume?:
@Obsolesce said in Safe to have a 48TB Windows volume?:
@jim9500 said in Safe to have a 48TB Windows volume?:
Have any of you used 48TB Windows volumes? Any resources on risk analysis vs ZFS?
I have two that are close to 60 TB. But they are REFS and hold a lot of large virtual disks.
REFS on 2019 is what I would wait for, for bare file storage.
Are you on 2019 now or looking to move off of a Windows file server?
ReFS has a bad track record. It's got a future, but has been pretty lacking and presents a bit of risk. Microsoft has had a disastrous track record with storage recently, even if ReFS is supposed to get brought to production levels with 2019, 2019 is questionably production ready. Remember... data loss is why it was pulled out of production in the first place.
It's been great in my experience. Though, I am using it in such a way the risk is worth the benefits... replication and backup repositories. It's been 100% solid. And like I said, it's all huge files stored on it, and probably not the use case that you seen results in data loss. I haven't seen that anywhere, so only taking your word for it unless you have links for me to do some reading. Not dumb stuff from Tom's or whatever, reputable scenarios in correct use cases.
The problem with storage is that we expect durability of something like seven nines as a "minimum" for being production ready. That means no matter how many people having "good experiences" with it, that tells us nothing. It's the people having issues with it that matter. And ReFS lacks the stability, safety, and recoverability necessary for it to be considered production ready to normal people as a baseline.
But even systems that lose data 90% of the time, work perfectly for 10% of people.
The problem I have with this perspective is that some of us have more direct contacts with folks that have had their SAN storage blow up on them but nothing gets seen in the public. One that does come to mind is the Australian Government's very public SAN blow-out a few years ago.
There is no solution out there that's perfect. None. Nadda. Zippo. Zilch.
All solutions blow up, have failures, lose data, and outright stop working.
Thus, in my mind citing up-time, reliability, or any other such statistic is a moot point. It's essentially useless.
Not at all. Reliability stats are SUPER important. There's ton of value. When we are dealing with systems expecting durability like this, those stats tell us a wealth of information. You can't dismiss the only data we have on reliability. It's far from useless.
BackBlaze is probably the only vendor I can think of that has told the drive vendors to take a flying leap and published what I consider to be real reliability statistics.
There are vendors, VMware for vSAN and Nutanix come to mind, that have specific NDAs in place that block any mention of their product's reliability and performance.
Drive vendors also have a similar clause but note BackBlaze.
Other than BackBlaze, the reliability statistics that I can find reliable are the ones that we have based on all of the solution sets we've built and deployed or worked with over the years. Those numbers tell a pretty good story. But, so too do the statistics that come about as result of the aforementioned panicked phone call.
Anything else in the public sphere has about the same weight as CRN, PCMag, ConsumerReports, or any other marketing fluff type.
@stuartjordan We have an aggregator that puts it together for us:
We are net importing energy because it costs more in CO2 taxes to run our coal plants.
EDIT: Forgot the link: https://twitter.com/ReliableAB/status/1393228855733805056
As a rule, the primary slot in each channel should be populated. So, 4 sticks per CPU.
Make sure Memory RAS settings are default and not stripe or mirror. That may be part of the problem.
Make sure the sticks are in the primary slot for each channel which is usually a different colour than the secondary and furthest from the CPU.
@nadnerb said in Random Thread - Anything Goes:
Ouch ... that brought back a painful memory.
ATI Rage Fury MAXX
(Image Credit: Internet)
We had a client with a fair number of very proficient Photoshop drivers. They needed way more GPU than the then current "best" could give them.
So, we built a bleeding edge system with this card.
Everything seemed to pan out but then the drivers came back and bit us in the arse.
Ultimately, a very expensive failed experiment.
