EMC Announcement

vSphere 6 Data Protection: Part 2 – Deploy virtual EMC Data Domain

Posted on

In the second part of the VMWare vSphere 6 Data Protection series we will deploy the EMC virtual Data Domain.

Post series:

Part 1 – Deploy VDP

Part 2 – Deploy virtual EMC Data Domain

Part 3 – Integrate VDP with EMC Data Domain

Introduction: What is EMC Data Domain?

The EMC Data Domain is a PBBA, a purpose-built backup appliance. It has one primary task and that is to serve as backup appliance and deliver benefits in your backup environment as a backup to disk target. So what are the main benefits?

  • Inline Deduplication: In a backup environment you backup the same data on a regular basis. With inline deduplication you save a lot of space on your appliance and even better: The more you backup the more you will save and will have a higher retention of your data.
  • DD Boost: Even better inline deduplication is when the application/backup software is talking to the data domain which segments are unique and only transfer the unique parts over the network. As such you are saving a lot of bandwidth and you can always perform a full backup but only the changes will be transmitted over the network. Also a lot of applications (Oracle RMAN, MS SQL, etc.) and 3rd party backup applications (Symantec, VEEAM) are supporting the DD Boost protocol.
  • Efficient replication: You can replicate your backups to a second location with a second data domain. Backup 2 disk and replicate it offsite … get rid of tapes and tape handling.
  • And when we are talking about tape handling – do you check your tapes on a regular basis? Data Domain checks it filesystem on a regular schedule and has a lot of mechanism to ensure your backuped data is valid at any time and can be restored.
  • Easy integration in existing environments: The Data Domain can be used as a CIFS/NFS target and can be used with almost every software. If it supports DD Boost it´s getting even better.
Data Domain with and w/o DD Boost
Data Domain with and w/o DD Boost


  • Deploy the OVA template of the EMC virtual Data Domain
  • Add an additional (third) disk to the deployed appliance for the backup data. The first two disks are system only and should not be touched or modified.
  • Restart the appliance


Connect via Remote Console to the data domain appliance

  • Login via default credentials
  • Start the configuration wizard
    • define FQDN
    • define ip settings
    • save settings

Connect to the Data Domain CLI via ssh

  • Add license
  • Add the third disk to the system with the following commands:
    • disk show hardware
    • storage add dev3
    • filesys create
    • filesys enable

EMC Virtual Data Domain


Connect to Data Domain via Web Interface: http://<IP/FQDN>

Data Domain Web Interface
Data Domain Web Interface
  • Set NTP time settings
Data Domain Time Settings
Data Domain Time Settings
  • DD Boost
    • Enable DD Boost
    • Create a user for DD Boost
    • User must have admin rights (needed when you add the data domain to VMWare VDP)
Data Domain DD Boost Settings
Data Domain DD Boost Settings
  • Create SNMP Community

The EMC Virtual Data Domain is up and running and in the next part we will integrate it to the VDP appliance. Link to the next part.

Edit 28.05.2015: The virtual Data Domain was announced during this years EMC World and is not yet available / GA.

EMC Data Domain

vSphere 6 Data Protection: Part 1 – Deploy VDP

Posted on

With vSphere 6 Data Protection all features from the previous vSphere 5.x vDPA were moved to the standard VDP without any additional costs.

Post series:

Part 1 – Deploy VDP

Part 2 – Deploy virtual EMC Data Domain

Part 3 – Integrate VDP with EMC Data Domain

What’s more in the Advanced version and now with vSphere 6 available for everyone:

  • Application-level replication
  • Ability to expand current datastore
  • Backup to a Data Domain
  • Granular level restore of Microsoft Servers
  • Automatic backup verification
  • Application consistent backup support – guest-level backups and restores of Microsoft SQL Servers, Exchange Servers, and Share Point Servers, providing for application consistent backups of these servers.
  • 8TB of deduplicated data for storage of backups (per appliance)
  • Up to 400 VMs per VDP Advanced appliance


  • No surprise, the VDP Appliance comes in the form of an OVA template. As such the first step is to deploy this template.
  • There is a bug right now that you can´t access the config portal via Chrome & Firefox. There is already a VMWare KB and a hotfix. But I´ve also experienced the bug with Internet Explorer and I had to install this hotfix.
    • Login local (via Remote Console) to the VDP
    • Enable root access: vi /etc/ssh/sshd_config and uncomment the line “PermitRootLogin”
    • Copy the hotfix to the appliance (e.g. with WinSCP)
    • Follow the instructions given from the VMWare KB
  • Open https://<ip/fqdn>:8543/vdp-configure/
  • Login with default credentials: root / changeme
  • Follow the wizard to do the basic appliance configuration
  • Reboot the appliance
  • In vCenter you should see a configuration task which is finalizing the setup2015-05-17 13_53_23-vSphere Web Client
  • After the succesful configuration task there should be a VDP menu item in the vSphere Web Client2015-05-02 13_39_51-vSphere Web Client


The basic configuration settings were already set during the intial setup. But I want to show you the two configuration pages.

  • via VDP Web Interface: For the basic settings of the appliance. We will get back to it when we add the data domain.

2015-05-02 14_06_01-https___192.168.2.213_8543_vdp-configure_ - Internet Explorer

  • via vSphere Web Client: For all Backup&Restore related tasks

2015-05-02 14_11_06-vSphere Web Client

The next step will be the deployment of the EMC virtual Data Domain … Link to Part 2


Homelab update to vSphere 6.0

Posted on

Unfortunately my homelab got a little bit dusty in the last few months due to a lot of work and my recent move to Munich. But with the “new” release of vSphere 6 there was the perfect opportunity to get the homelab shiny again 😉 But first of all I had to tidy up my workroom and find a nice spot for my NUCs.

Homelab (2 x Intel NUC, pfSense Firewall)
Homelab (2 x Intel NUC, pfSense Firewall)

ESXi 6.0 installation:

The vSphere ESXi 6.0 installation worked as usual. Just like with vSphere 5.5 you had to inject the network driver to work with Intel NUCs – but no problems at this point. You can lookup the exact procedure in one of my former posts: Click me

2015-05-01 14_24_17-ESXInstall - VMware Workstation
The ESXi setup procedure didn´t change a lot compared to vSphere 5.5

vCenter Server Appliance (VCSA) 6.0 installation:

With vSphere 6.0 a lot has changed with the vCenter architecture itself or let´s say got reorganized. With vSphere 5.x we were talking about vCenter Server, Inventory service and SSO. With vSphere 6.x we are talking about two “new” components:

  • Platform Services Controller (SSO, Licensing, Lookup service, Directory service, certificate authority)
  • vCenter Services (vCenter Server, Web Client, Inventory Service, Auto Deploy, Dump Collector, Syslog Collector)

You can look up the details on this VMWare blog post:


Also the VCSA got a new deployment method – you don´t have to import a OVF/OVA anymore.

1. Install the Client Integration Plugin located within the ISO file

2015-05-01 17_44_43-vcsa


2. Open the vcsa-setup.html with a browser


2015-05-01 17_42_38-BD-ROM-Laufwerk (Z_) VMware VCSA

3. Click Install or Upgrade and follow the Step-by-Step wizard

2015-05-01 17_45_25-vCenter Server Appliance 6.0

4. Here you go, up and running in a matter of minutes.



2015-05-01 19_29_19-vSphere Web Client


Some homelab tweaks:

1. Activate Transparent Page Sharing (TPS)

2015-05-02 09_32_37-VMware KB_ Additional Transparent Page Sharing management capabilities and new d

With the latest patches in vSphere 5.x and per default with vSphere 6.x there is no inter-vm TPS anymore, but only intra-vm TPS. This change was made due to some security concerns when memory pages are shared between virtual machines. There is the possibility to control which groups of virtual machines can share pages with the salt value. The salt value for the sharing group has to be the same on a per-vm setting.

In a homelab environment I don´t have any security concerns (more likely “I need more RAM!!! concerns”) and I will reactivate the classic TPS mechanism. Just set Mem.ShareForceSalting to 0 in the advanced ESXi settings.


2. Enforce small pages

2015-05-01 19_33_52-vSphere Web Client

A similiar discussion (already with vSphere 5.x) is with small pages vs large pages. You have to choose between more performance (large pages) and transparent page sharing (small pages). Also the VMKernel and memory mgmt will break up the large pages to small pages when the host is under memory pressure, I choose to enforce small pages from the beginning.


3. Ignore Network Redundancy Warnings

2015-05-02 09_26_39-vSphere Web ClientIgnore Network Redundancy Warnings:

A small tweak regarding the fact I have only one network adapter for all traffic. As such I have no redundancy at all in my homelab (shame on me! 😉 ) but I don´t want to see the annoying warning everytime.

  • HA Advanced Setting
  • Add “das.ignoreRedundantNetWarning” with value “true”
  • “Reconfigure for HA” on each host



First impression of vSphere 6.0:

  • I really like how they pushed the VCSA in a lot of points to compete with the “normal” one
  • The vSphere web client is way more reactive and I start getting along with it
  • The first-time setup procedure with VCSA worked like a charm

I´m looking forward to explore some new features like:

  • Repository
  • Certificate management
  • The (now) free version of VMWare Data Protection Advanced (VDPA, EMC Avamar) in combination with my EMC Data Domain

pfSense 2.2 Update – finally 802.11n wifi

Posted on

A while ago I was writing about my new pfSense firewall appliance (look here). One remaining problem was pfSense 2.1 (based on FreeBSD 8.x) was not able to operate 802.11n wifi and there was the statement the support for 802.11n will come with pfSense 2.2 (based on FreeBSD 10.x).

After some very busy first quarter in this year I´ve finally managed to upgrade my appliance to pfSense 2.2 – and I can confirm it is working with my setup. A few screens:

2015-04-09 18_27_13-fw.metzelcorp.local - Status_ Dashboard
pfSense Status Dashboard


WIFI adapter settings
WIFI adapter settings


2015-04-09 19_30_11-fw.metzelcorp.local - Status_ Wireless
Wireless Clients – connected with higher data rates after the update to pfSense 2.2 and switching to 802.11gn mode.

I have read that mixed mode (n+g) costs some performance regarding link speed, but I have to use it to connect my older devices like my tablet and I have to say that the data rate right now is enough for my purposes.

You can find the new images here: https://www.pfsense.org/download/


EMC Recoverpoint

Recoverpoint for Virtual Machines Part – What is it?

Posted on


Recoverpoint for Virtual Machines will soon be available – but what is it doing?

  • Protects at virtual machine level
  • local or remote replication (sync/async)
  • 100% software solution, no hardware appliance necessary
  • VMWare vCenter integrated – all administrative tasks can be done from the VMWare admin
  • Support for SAN/vSAN/NAS/DAS
  • Recover to any point in time

For those knowing EMC RecoverPoint – imagine the features of RecoverPoint as software-only solution and on a per-vm basis.

For those not knowing EMC RecoverPoint – a small picture which shows how RecoverPoint delivers Continuous Data Protection

Continuous data protection
Continuous data protection

And where does the magic happen? How does this work?

  • Deployment of the recoverpoint appliances & installation of RecoverPoint IO splitters to the ESXi hosts via VIB File (next part of this series)
  • The VMWare admin can protect a virtual machine via the WebClient through a wizard driven workflow
  • When an IO is issued to a virtual machine the ESXi host splits the IO with the installed RecoverPoint splitter. The original IO is directed to the storage system and the duplicated IO is redirected to the RecoverPoint appliances
  • Those appliances take care of replicating each IO to a Journal volume and finally to the Replica of the virtual machine disk (depending on the way [sync/async and local/remote] you are protecting your virtual machine the exact way is differing)

2014-11-21 19_41_01-Recoverpoint_VM.pptx - PowerPoint


Demonstration video from my coworker Itzik Reich

EMC product page


Also read the post from Chad Sakac



Stay tuned, in the next post I will install RecoverPoint for virtual machines to my homelab.


Build your own firewall appliance with ALIX / APU & pfSense

Posted on

What did I say to a friend of mine a few weeks ago after his modem was broken: “Oh my modem is working without any concerns for years now …”

Well another 2-3 weeks later … guess what … yep my modem was also broken … karma? Long story short I was forced to get a new modem. When I was installing the new modem I was thinking about my network equipment right now and was considering to update it at another point. Behind my modem I had a pfsense firewall appliance on a ALIX2C3 board running and I was thinking about upgrading this box aswell. Therefore I was doing some research if there were any new releases of the ALIX boards … and yep there was the brand-new APU boards released.

Equipment at the moment: ALIX2C3 & pfSense

Though I have been very happy with my ALIX pfSense firewall as it was running for ages, but it had its limitations by now. (well at this point karma would have also stroke it down by lightning or by whatever anyways …)

  • wrong casing (the fitting casing was not available at that point)
  • no wi-fi because of the wrong casing (no holes for the antennas)
  • only 100 Mbit LAN interfaces (not bad for internet connection but between the local interfaces)
  • not enough CPU & RAM for additional workloads like VPN etc.
  • only 512 MB CF Card

New Equipment:

Overview over all components
Overview over all components


  • APU1C4 board (1 Ghz Dual Core, 4 GB DDR3 RAM, 2x mini-PCIe, 3 x Gb LAN) & heat spreader
  • APU 1C4 casing
  • mini-PCIe wi-fi Adapter Compex WLE200NX a/b/g/n
  • 2x TP-Link TL-ANT2408CL (2,4 GHz, 8 dBi)
  • 2x UFL/IPX to RP SMA pigtail (~15cm length)

Assembling all parts wasn´t that hard but you should not forget to install the heat spreader. It´s new to the PCEngines boards that they require such a thing, but without it the board won´t live that long. Here you can find a tutorial from the manufacturer how to install it: http://www.pcengines.ch/apucool.htm

All parts assembled
All parts assembled

Time to boot the appliance the first time and connect via serial connection at 115200 baud. At this time we will enter the bios and adjust the boot order to boot from usb1+2 followed by the mSATA drive. We need to boot from usb to install pfSense to the mSATA SSD and afterwards we will boot directly from the SSD drive. The installation steps are explained in the following passage.

ALIX APU boot order
APU boot order

First we have to download the right installer ISO for pfSense: https://www.pfsense.org/download/mirror.php?section=downloads

We have an AMD64 architecture and want to install it from usb stick. Therefore we have to choose the following settings on the download page.

pfSense download
pfSense download

In order to write the downloaded image to the usb stick I was using this nifty tool called “Win32 Disk Imager”. You can find it for download here: http://www.askvg.com/win32-disk-imager-write-any-bootable-image-to-usb-drive-in-windows/

After we have written the image to the usb stick boot the appliance from the usb stick and connect again via serial connection but this time with a baud rate of 9600 (ALIX / APU bios & bootup is 115200 but pfsense 9600!). You can change the baud rate of pfSense to match the ALIX / APU board later in the settings if you want to. On the pfSense setup screen choose the third option named “Boot pfsense using USB Device” – otherwise we would boot pfsense “live” from the usb stick. But in this case we want to install it to the SSD.

pfSense installer
pfSense installer

I´ve installed pfSense to the SDD drive and let the installer create his recommended disk layout and partition sizes. After the straight forward installation process pull the usb stick and reboot the appliance. We will now enter the basic configuration mode on the console where we have to map the initial interfaces to its function like WLAN and LAN. We can later configure interfaces for the wi-fi and for the optional interface(s) within the web interface.

interface assignment
interface assignment

After we have configured an ip address to the LAN interface we can log in to the web interface and complete the setup wizard, which is asking for settings like name, dns servers, ntp etc. One funky new feature I´ve noticed after the final reboot is the internal pc speaker jingle sound when the pfSense bootup is completed … I was remembering long gone pc speaker games.

One still existing problem is that you can´t operate your wi-fi with 802.11 n, because of some limits within FreeBSD 8 on which pfSense 2.1 is running on. But with the new 2.2 release (not yet globally available) it will be based on FreeBSD 9 and there will be no problems with the support of 802.11n anymore.

pfSense web interface
pfSense web interface

pfSense is up and running! And if you ask why pfSense?

Well as you know I have my homelab running and like to play around with tech stuff and therefore I need a feature rich and mighty firewall appliance. Furthermore I really use some features for my daily work and now with the new board I can try out some new add ons which you can install via packages to pfSense (e.g. IDS/IPS like snort and squid as a proxy). And of course it´s a really good & secure firewall appliance I really learned to appreciate over the years. pfSense is still completely free to use but they are offering commercial support services and there are also enough shops delivering prebuilt pfSense appliances nowadays.

My top 5 things I love about pfSense:

  • OpenVPN server
  • Certification management
  • You can set very detailed options for everything (drawback is of course it gets complex at some points)
  • Modular package system to install additional community driven or 3rd party software
  • So many features …

Update 1: 18.09.2014 13:25

John just posted a comment on this post regarding some people having boot problems with pfSense and running into an error stating “ROOT MOUNT ERROR”. I did not experience this error with any of my pfSense installations over the last years but I wanted to share  a possible solution (also provided by John, thanks a lot!) to this problem for the case you are encountering such problems.

At the prompt (OK), for an SD card, type:

set kern.cam.boot_delay=10000

or for an mSATA drive, type:

set hw.ata.atapi_dma=”1″
set hw.ata.ata_dma=”1″
set hw.ata.wc=”1″

then type


After you have successfully booted the system you would have to edit the configuration file of the boot loader via the shell (/boot/loader.conf.local) to make those options persistent.

Update 2: 09.04.2015

The mentioned 802.11n wifi incompabilities are finally history with the new pfsense 2.2 release. Link



Useful wordpress plugins

Posted on

A small and quick overview of the useful wordpress plugins I´m using right now.


Broken Link Checker – Link

Checks your blog for broken links and missing images and notifies you on the dashboard if any are found.

Easy Columns – Link

Easy Columns provides the shortcodes to create a grid system or magazine style columns for laying out your pages just the way you need them.

Gist GitHub Shortcode – Link

Adds Github Gists in your posts via shortcode.

Google Analytics for WordPress – Link

This plugin makes it simple to add Google Analytics to your WordPress blog, adding lots of features, eg. custom variables and automatic clickout and download tracking.

NextGEN Gallery – Link

The most popular gallery plugin for WordPress and one of the most popular plugins of all time with over 9 million downloads.

Redirection – Link

Manage all your 301 redirects and monitor 404 errors.

Shortcodes Ultimate – Link

Supercharge your WordPress theme with mega pack of shortcodes.

Simple Share Buttons Adder – Link

A simple plugin that enables you to add share buttons to all of your posts and/or pages.

Simple Social Icons – Link

A simple, CSS and icon font driven social icons widget.

SyntaxHighlighter Evolved – Link

Easily post syntax-highlighted code to your site without having to modify the code at all.

TinyMCE Spellcheck – Link

Adds a contextual spell, style, and grammar checker to WordPress.

WordPress SEO – Link

The first true all-in-one SEO solution for WordPress, including on-page content analysis, XML sitemaps and much more.


Building my new homelab Part 2 – vSphere basic environment

Posted on

It is time to replace and rebuild my homelab and I will document these steps in different chapters. In part 2 I will talk about the vSphere basic environment installation.

Part 1 – Hardware

Part 2 – vSphere basic environment


Creation of custom ESXi image:

In order to get ESXi installed on the Intel NUC you have to create a customized image, because the necessary device driver for the Intel NUC network adapter (82579LM Gigabit Ethernet Controller) is not part of the ESXi base image. In order to create this image I was using the tool ESXi customizer from Andreas Peetz (www.v-front.de) in the past. The tool would still do the job (and would do it good!) but I wanted to try a new and more “onboard” way to customize the image with PowerCLI.

What parts do you need?


PowerCLI customization part:

[ps] # Add ESXi Offline Bundle
Add-EsxSoftwareDepot .\update-from-esxi5.5-5.5_update01.zip

# View ESXi Image Profiles and check software packages

# Add Network Driver and check available software packages again
Add-EsxSoftwareDepot .\net-e1001e-1.0.0-offline_bundle_by_chilly.zip

# Create new ESX Image and integrate software
Get-EsxImageProfile | select name
New-EsxImageProfile -CloneProfile "ESXi-5.5.0-20140302001-standard" -Name "ESXi-5.5.0-20140302001-standard-IntelNUC" -AcceptanceLevel "CommunitySupported" -vendor "GetVirtual"

# Integrate the network driver in the cloned ESXi Image Profile
Add-EsxSoftwarePackage -ImageProfile "ESXi-5.5.0-20140302001-standard-IntelNUC" -SoftwarePackage "net-e1001e"

# Export to ISO
Export-EsxImageProfile -ExportToIso -ImageProfile "ESXi-5.5.0-20140302001-standard-IntelNUC" -FilePath .\ESXi-5.5.0-20140302001-custom.iso

VMware vSphere PowerCLI 5.5 Release 2_2014-05-24_19-19-41
ESXi basic image software packages without e1001
VMware vSphere PowerCLI 5.5 Release 2_2014-05-24_19-23-56
Added e1001 to the available software packages

Installation of ESXi on the Intel NUC via VMWare Workstation:

I could now burn the image and use a USB CDROM drive to install the image to the usb stick on the Intel NUC, but I prefer a more efficient way to do the installation. I´ve created an empty virtual machine on my desktop PC with VMWare Workstation (standard vm, no disk, 2x vCPU, 4 GB RAM) and mounted the custom iso image and passed-through the usb stick.

Can´t import the usb stick because it says it is in use? Remove the drive letter, safely remove it and plug it into an usb2 port instead of usb3
Generate a new mac address when you install another ESXi with the same “ESXi helper” virtual machine to avoid some duplicate mac address in your network
ESXInstall - VMware Workstation_2014-05-24_20-07-36
ESXi installation on USB stick via VMWare Workstation


Perform a standard ESXi installation and basic network configuration … I will only summarize these steps.

But there was one strange error I was getting when booting up one of the NUC boxes with ESXi stating “multiboot could not setup the video subsystem”. I´ve found a few suggestions on the net to solve this problem, but none of them fixed it anyways. The resulting problem of this error was that I couldn´t access the DCUI to make the basic configuration settings. Finally I made a work around with booting the stick in my VMWare Workstation virtual machine, made the necessary configuration settings and booted the NUC with the “pre-configured” USB stick. You can boot from a USB stick in VMWare Workstation (I´m still using version 9) with Plop Boot Manager.


ESXInstall - VMware Workstation_2014-05-31_11-49-21
PLOP Boot Manager

Basic ESXi config

  • network configuration
  • enable ssh
  • configure iSCSI connectivity
  • configure scratch location

Deploy W2k8 + Active Directory

  • deploy Windows Server 2008 R2
  • install AD Domain Services & DNS (Domain: get-virtual.local)
Active Directory


Deploy vSphere vCenter Appliance

  • reduce memory to 4 GB (enough reduction without editing configuration files for memory settings, VMWare KB)
  • basic network configuration
  • add AD identity source

There was an error after adding the AD identity source stating “Client is not authenticated to VMware Inventory Service”. This VMWare KB resolved the issue.

vSphere Web Client_2014-05-31_11-33-09
Basic vSphere homelab environment deployed


Voilà, basic homelab is up and running.




Building my new homelab Part 1 – Hardware

Posted on

It is time to replace and rebuild my homelab and I will document these steps in different chapters. In part 1 I will talk about the hardware I will use for my homelab.

Part 1 – Hardware

Part 2 – vSphere basic environment


Existing homelab components:

  • HP NL54L Microserver (G7)
  • HP ML 110 G6
  • Custom desktop PC
  • Synology DS 209+II

Assessment of existing homelab:

  • Loud (the desktop PC is louder than the HP servers …)
  • High power consumption
  • unbalanced & incompatible cluster
Existing Homelab


Future homelab components:

  • 2 x Intel® NUC-Kit DC53427HYE with 16 GB of RAM each
  • HP NL54L Microserver (G7) … will be reused as backup server
  • Synology DS 209+II … but there are plans to replace it with a newer and bigger box (upcoming chapter of this homelab series)

Here you can find some additional information about Intel NUCs. With the new 4th generation you have additional support for a 2.5″ drive with the existing mSATA SSD. I was also thinking about taking three of these and create a VSAN/ScaleIO cluster but finally discarded it due to the costs of the additional third box and the drives.


Shopping list:

Summing up to about 470 € per box and I´m going to build a 2-node cluster. In my point of view that is a fair price when you look at the specs such a small box delivers (16 GB RAM!) and has the following advantages.

Assessment of future homelab:

  • Low power consumption
  • More RAM (2x 16 GB)
  • Less space consumption
  • No noise


Future homelab components


Hardware installation:

Well it couldn´t be any easier … open the NUC and install the RAM kit … plug it in and turn it on. That´s it!

Well one thing to mention would be that the Intel NUC has only HDMI ports and no VGA/DVI resulting in diverting my television from it´s intended use. But hey … when do you get the opportunity to watch an ESXi server booting up on your large TV screen.

ESXi booting up on television


In the upcoming chapter I will install the basic vSphere environment (ESXi, Active Directory, vCenter Server Appliance, …).


EMC Announcement

VNXe 3200 announced and shown at EMC World 2014

Posted on

Finally EMC announced the new VNXe 3200 last week and the box was demonstrated at EMC World 2014 this week.

I just want to summarize the main features for you:

  • Storage processor specs: 2U, 8 Sandybridge cores, 48GB of system memory,  8 10GbE ports, up to 4 8Gbps FC ports
  • The well-known and awesome FAST technology from the VNX series (FAST VP + FAST Cache) are available in the VNXe 3200!!!
  • No longer iSCSI only – now it´s FC, iSCSI, FCoE, NAS protocols …
  • Starts at under $12K … so awesome technology in a small box for a small price!

VNX vs VNXe architecture:


As you can clearly see the “unified control path” from its predecessor is continued in the VNXe3200.


Read the announcement from EMC:


Here you can find the VNXe simulator to get a look & feel for the VNXe 3200:


Read the full virtual geek article regarding VNXe 3200 and read about project liberty (!!!):