WishMesh http://wishmesh.com Real men don't make backups Fri, 05 Jun 2015 13:03:45 +0000 en-US hourly 1 http://wordpress.org/?v=4.2.3 No more sense to keep all these MSDN disks http://wishmesh.com/2015/06/no-more-sense-to-keep-all-these-msdn-disks/ http://wishmesh.com/2015/06/no-more-sense-to-keep-all-these-msdn-disks/#comments Fri, 05 Jun 2015 13:03:45 +0000 http://wishmesh.com/?p=1384 Continue reading No more sense to keep all these MSDN disks ]]> I have several active Microsoft MSDN licenses / subscriptions, and the oldest one comes with the biggest MSDN disc collection (more than 1500 CDs and DVDs). The 2015 is the year when the Cloud has won. Disks are going to recycling plant, and I am left with a small virtual .iso collection, and big collection at the MSDN download site. Internet is so fast here in Latvia, that full DVD disk is downloaded faster, than I can make a cup of coffee.

R.I.P. my MSDN collection.

Too many MSDN disks with cases More than 1500 MSDN disks More than 1500 MSDN disks, zoom out Some random MSDN disks MSDN CD disk from October 2001 MSDN disk from June 2007 "Old style" MSDN disks MSDN disk case / binder ]]>
http://wishmesh.com/2015/06/no-more-sense-to-keep-all-these-msdn-disks/feed/ 0
Real men do not test backups, remember? http://wishmesh.com/2015/04/real-men-do-not-test-backups-remember/ http://wishmesh.com/2015/04/real-men-do-not-test-backups-remember/#comments Wed, 08 Apr 2015 14:03:25 +0000 http://wishmesh.com/?p=1377 Continue reading Real men do not test backups, remember? ]]> I always said, real men don’t make backups for their important data :)
I do not want to lose data. I am in IT industry for some time, and I know, that it is not “IF hard drive will fail”** … but “when will it fail”. Here is the story we all can learn from:

About 20 years ago, I worked for a company which I shall not name, which used CVS as its source repository. All of the developers’ home directories were NFS mounted from a central Network Appliance shared storage (Network Appliance was the manufacturer of the NAS device), so everyone worked in and built on that one central storage pool. The CVS repository also lived in that same pool. Surprisingly, this actually worked pretty well, performance-wise.

One of the big advantages touted for this approach was that it meant that there was a single storage system to back up. Backing up the NA device automatically got all of the devs’ machines and a bunch more. Cool… as long as it gets done.

One day, the NA disk crashed. I don’t know if it was a RAID or what, but whatever the case, it was gone. CVS repo gone. Every single one of 50+ developers’ home directories, including their current checkouts of the codebase, gone. Probably 500 person-years of work, gone.

Backups to the rescue! Oops. It turns out that the sysadmin had never tested the backups. His backup script hadn’t had permission to recurse into all of the developers’ home directories, or into the CVS repo, and had simply skipped everything it couldn’t read. 500 person-years of work, really gone.

Almost.

Luckily, we had a major client running an installation of our hardware and software that was an order of magnitude bigger and more complex than any other client. To support this big client, we constantly kept one or two developers on site at their facility on the other side of the country. So those developers could work and debug problems, they had one of our workstations on-site, and of course *that* workstation used local disk. The code on that machine was about a week old, and it was only the tip of the tree, since CVS doesn’t keep a local copy of the history, only a single checked-out working tree.

But although we lost the entire history, including all previous tagged releases (there were snapshots of the releases of course… but they were all on the NA box), at least we had an only slightly outdated version of the current source code. The code was imported into a new CVS repo, and we got back to work.

In case you’re wondering about the hapless sysadmin, no he wasn’t fired. That week. He was given a couple of weeks to get the system back up and running, with good backups. He was called on the carpet and swore on his mother’s grave to the CEO that the backups were working. The next day, my boss deleted a file from his home directory and then asked the sysadmin to recover it from backup. The sysadmin was escorted from the building two minutes after he reported that he was unable to recover the file.

from Slashdot by swillden.

** I am talking not only about HDD, but about media in general. And this also applies to humans, because we humans are making mistakes too, and we lose data every day.

]]>
http://wishmesh.com/2015/04/real-men-do-not-test-backups-remember/feed/ 0
Solution to “The term ‘-Version’ is not recognized as the name of a cmdlet…” http://wishmesh.com/2015/03/solution-to-the-term-version-is-not-recognized-as-the-name-of-a-cmdlet/ http://wishmesh.com/2015/03/solution-to-the-term-version-is-not-recognized-as-the-name-of-a-cmdlet/#comments Fri, 27 Mar 2015 17:39:26 +0000 http://wishmesh.com/?p=1374 Continue reading Solution to “The term ‘-Version’ is not recognized as the name of a cmdlet…” ]]> When trying to run PowerShell.exe with command line argument -Version, you may get the following error:
-Version : The term '-Version' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ -Version 2.0 -InputFormat none -File C:\SomeFolder\YoutScript.ps1
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (-Version:String) [], CommandNot
FoundException
+ FullyQualifiedErrorId : CommandNotFoundException

The command line used:
powershell.exe -ExecutionPolicy Bypass -Version 2.0 -InputFormat none -File C:\SomeFolder\YoutScript.ps1

You can resolve this error, by changing order of Version parameter:

powershell.exe -Version 2.0 -ExecutionPolicy Bypass -InputFormat none -File C:\SomeFolder\YoutScript.ps1

This seems like a bug, because official documentation for the PowerShell does not mention order of parameters. Even more, the use Execution Policy before Version. See the following PowerShell help article in MS site.

]]>
http://wishmesh.com/2015/03/solution-to-the-term-version-is-not-recognized-as-the-name-of-a-cmdlet/feed/ 0