2015/04/14 § Leave a comment
It’s motorcycle season up here in Western New York, the season of paradise finally having returned to us: six months of weather-driven ecstasy that would make a poppy field jealous. Men and women (mostly men) who are rediscovering freedom mount up on hogs to ride away from fetters upon the low rumble of open internal combustion. Commemorating the rising spring sun of motorbiking, women set out the yellow “Look” signs in their front yards, weeping and ululating as women of yore did when the warriors set off in the spring, looking for war.
I think they should take them down. You cannot serve two masters: you must either love danger and hate safety or hate danger. To lay a wreath of guilt upon ordinary automobile motorists is unconscionable.
- Motorcyclists are, by nature, risk-takers. They would not be riding motorcycles otherwise. Actuarial tables do not lie.
- A motorcycle is much smaller…
View original post 845 more words
2013/07/11 § 1 Comment
I’m learning PowerShell. I’ve been told I needed to learn PowerShell or learn how to ask if the customer “wanted fries with that …” Or something.
Never mind the exaggeration, it’s a good idea to learn PowerShell if you’ve either been sentenced to or willingly (crazy bastard!) manage a Microsoft installation.
Magnus Andersson who looks more like a potentially marauding Viking than a mild mannered systems geek has written a good post on scheduling a PowerCLI (vSphere’s PoSh module) script in Windows task scheduler. Check it out, it’s rather useful.
2013/03/26 § Leave a comment
I’m tired of virtualization. Literally. As in saying and typing virtualization. I am a big, big fan of the technology, mind. I’m just tired of that word.
In the coming months, I will be working on virtualizing (ugh) our Exchange server installation and there’s a need to find out how to “size” (ugh) the virtual infrastructure for smooth 2010 or 2013 operations.
David Davis (echo, echo) has good recommendations that I will be using to help me decide what goes into the VM/ESX host combination, a sample of which follows:
- When allocating processors, only assign multiple virtual CPUs (vCPUs) if you can determine that your Exchange virtual machines (VMs) can really take advantage of the additional processors; otherwise, you’re wasting resources.Start with the smallest number of vCPUs and work your way up as more processors are needed.
- Ensure that the total number of vCPUs assigned to all Exchange 2010 VMs is equal to (or less than) the total number of cores on the ESX host machine. If you assign more vCPUs to mission-critical VMs than the physical host has available, you are overcommitting CPUs, and taking a chance that your Exchange VMs won’t have CPU cycles when they’re needed. Instead of a 1:1 mapping of cores to vCPUs, use CPU reservations to protect those CPU resources for Exchange VMs.
- Overcommitting memory with VMware vSphere is common — and even recommended — but don’t overcommit memory when virtualizing Exchange 2010. If you do, you’ll have to deal with memory ballooning, compression and paging — all of which will diminish performance.
- Use storage multi-pathing to ensure storage area network (SAN) availability.VMware recommends providing a minimum of four paths from a VMware ESX host to a storage array, which means the host requires at least two host bus adapter (HBA) ports, two Fibre Channel ports and two SAN ports.
- Allocate separate network adapters and networks for VMotion, VMware fault tolerant (FT) logging traffic and ESX console access management. Use at least two network adapters for Exchange production traffic to leverageVMware network interface card (NIC) teaming capabilities. Generally, at least four network adapters are recommended per ESX host.
- Use the VMXNET3 virtual network adapter driver instead of the default E1000. In mission-critical VMs like Exchange 2010, the para-virtualized VMXNET3 will result in better performance. Also, ensure that VMware Toolsis installed on each VM as the VMXNET3 virtual NIC driver.
- Don’t skimp on host server hardware. No amount of virtualization features can fix old or slow hardware.
- When virtualizing Exchange 2010, make sure you’re up-to-date with the latest service pack.
- Use vSphere High Availability (HA) to automatically restart your Exchange VMs in the event of a host failure.
Hold your nose, close your eyes and jump in for the rest.
2012/11/05 § Leave a comment
The truth leaves the mouth warm and enters the ear cold.
2012/09/13 § Leave a comment
I’m beginning to love slide rules of every sort. Such ingenuity!
2012/05/19 § Leave a comment
Arrived back in town after attending the SANS Security West in San Diego for six days.
Watch for a full review in the coming days.