Skip to main content

ESXi storage migration

Figured I'd post something useful about this experience.

Really, it's all about planning. Not just having a plan, or even having a plan that covers the basics, but having a plan that allows for practical things, like time off, shipping errors, configuration oversights, and just plain bad luck.

We've had all of the above and then some on this latest project. No matter how hard we tried to make our deadlines, we either forgot a key point (ESXi doesn't do storage migration on its own), or were given misinformation or not enough information (ET RS-16 IP-4 doesn't handle jumbo frames including/past 8000), or just plain bad luck abounded (the crux of the project lay across a perfect storm of not one but three long weekends (Christmas, Boxing day, New Years) compounded by different locations having different ideas about which days to take off.

I've spent my New Years Eve (well, 95% of it) on one task: Migrate the storage of all the VMs on our NY site's ESXi box from local to an iSCSI server we just shipped down and arrived in the nick of time. Simple enough, but man we messed up on some basics.

Now granted, we're a bit overworked lately, but dood, we both were in agreement that I just had to storage migrate from one datastore to the other. Simple! Except ESXi cannot do storage migration, as that is a VCenter function (could be ESX as well). So I tried FastSCP. Nothing fast about it, and it also destroys any thin-provisioned disks. Big bada boom.

The fix? Well, we have a great candidate for a VCenter host - that physical server hosting the iSCSI targets! Except it doesn't have the VIM ISO. FTP that over, 1.2 hours. Install Daemon tools, reboot. Try adding host to VCenter after install, fails. ESXi needs patching. Patch, it reboots. Added host. Works! Started moving over storage, working like a charm. So we're okay at this point...

The last piece that's weighing on my mind is that one disk has failed in the iSCSI array (an MD1000). Local people can't pick one up, so I have to get one when I arrive in NY on Sunday, Lord willing.

Ok time to go enjoy the last bits of New Years and go to bed.

Last thought of the evening: Backlit keyboards should be mandatory. Thank you Apple for forcing Dell on the bandwagon.

Edit: The VPN died shortly after posting this, around 1am. Had to give up after spending 2 hours messing about trying to get back in. D was able to get in via logmein and reboot the VPN server, but it's still acting up. I managed to get back in via VPN this morning and set up logmein straightaway.

Comments

  1. I've begun a migration from Pure XenServer to ESXi for our server environment and we may have a little extra scratch to buy utilities/tools. Are there any ESXi/vSphere specific things that you would rather not live without? I know Veeam is pretty sick for backup.

    ReplyDelete
  2. Veeam for backup is essential if backups are a business requirement. We're currently also using 'vCOPS' but I'm not convinced it's helpful in a small org. Really, the big thing about a VMware environment is that it can basically run itself, so if you have a bigger install stuff you'd want to look at is automation tooling. If you can't automate it, you don't want it.

    Another thought is 'what's the business case I'm trying to solve?' A lot of problems are solved via public cloud stuff these days. And 'how can we measure change?' is a big question to ask.

    ReplyDelete

Post a Comment

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…