Whatever decisions you make should compliment your larger protection strategies, as this is just one piece of the puzzle. But the tips I provide have stood up to the rigors of a production environment, and have actually worked in real recovery scenarios. The information provided may or may not align with best practices from Dell, or your own practices. Just as with any solution, there are a number of different ways to achieve the same result. Let me preface that these are just my suggestions off of personal use with all versions of the HIT over the past 3 years. Surprisingly, many of the same practices that have served me well with the older version adopt quite well to the new version. Because I had been lagging behind in updating vSphere, I was still using 2.x up until recently, and skipped right over 3.0 to 3.1. This reduced overhead, complexity, and removed some of the quirks with the older implementations. The others being HIT/ME and HIT/LE for Microsoft and Linux respectively.Įver since HIT/VE 3.0, Dell EqualLogic thankfully transitioned toward and appliance/plug-in model. HIT/VE is one of three Host Integration toolsets. This consists of the following EqualLogic Auto-Snapshot Manager, EqualLogic Datastore Manager, and the EqualLogic Virtual Desktop Deployment Utility. A lot has changed, as it is now part of a larger suite of VMware-centric tools from EqualLogic called the Host Integration Tools / VMware Edition or HIT/VE. The first generation of HIT/VE was really nothing more than a single tool referred to as “Auto-Snapshot Manager / VMware Edition” or ASM/VE. Well, it’s been a while since I’ve touched on any information about ASM/VE, and since I’ve updated my infrastructure to vSphere 5.0 and the HIT/VE 3.1, I thought I’d share a few pointers that have helped me work with this tool in my environment. This is one of the reasons why I’ve written so much about ASM/ME, ASM/LE, and SANHQ.
#Dell equallogic group manager series#
It appears that the storage array has not been configured.Ever since my series of posts on replication with a Dell EqualLogic SAN, I’ve had a lot of interest from other users wondering how I actually use the built-in tools provided by Dell EqualLogic to protect my environment. Netmgtd:1610994816.78:rcc_util.c:1032:AUDIT:25.7.0:CLI: Login to account grpadmin succeeded, using local authentication. Netmgtd:1610994816.78:rcc_util.c:1024:INFO:25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. Jan 18 13:33:26 init: kernel security level changed from 0 to 1
Plat_pfgxlp_wait_for_battery: Smart Battery Remaining Capacity = 506 mAh after 0-second delaySP:1.00:cache_:1058:INFO:28.2.39:Active control module cache set to write-back mode. Sp = 0xffffffff8f24dfe0, gp = 0xffffffff8f24c000 * 2x Type 15 Controllers – 2x 10GB SFP+ & 2x 10GB RJ-45 * 24x 2.5″ SAS (no hard drives OR caddies)