Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015

NEXGEN N5 AND VORMETRIC DATA

SECURITY

Solution Validation

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 1

Overview

NexGen has validated the functionality of NexGen N5 hybrid flash arrays as a back-end storage solution within an infrastructure that utilizes Vormetric Data Security delivering data at rest encryption. The objective was to demonstrate and document the compatibility of NexGen hybrid flash storage in this environment.

Test Components

The solution components included in the base architecture: Cisco:

Cisco infrastructure consists of a pair of Cisco UCS 6248 Fabric Interconnects. The Fabric

Interconnects will be connected to 2 upstream Cisco Nexus 5548 switches and to a UCS 5108 chassis. The

solution components included in the base architecture include:

o UCS Blade Chassis model: 5108

2x Fabric Extender IO Module (FEX): 2208XP

o 2x Nexus Switches model: 5548UP

o 2x Fabric Interconnect model: 6248UP

o Blade Server model: B200-M3

Blade VIC: 1240 LOM

Blade Mezzanine Card: Empty

Blade Memory: 256GB

Blade Processor: quantity 2 of Xeon E5-2650 (2GHz, 16 cores total)

NexGen: o NexGen N5 Hybrid Flash Array

Virtualization Platform: o VMware vSphere 5.1 with ESXi 5.1 (1065491)

o vCenter 5.1 management platform

Vormetric: o Vormetric Data Security v5.1.3.1074

Vormetric Data Security Manager

Vormetric Transparent Encryption Agents

Microsoft: o Windows Server 2012 R2

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 2

o SQL Server 2012 Enterprise Edition x64 with SP1

Architecture

Figure 1: Solution Components

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 3

VM and Storage Configuration

Figure 2: Detailed VM and storage configuration

Details

Three virtual servers were created as per this document and testing consisted of NexGen N5 snapshots, cloning and replication of Vormetric protected volumes. Unlike prior Fusion ioMemory testing which utilized PCIe ioMemory configured as local storage and focused on File & SQL performance workloads1, this test utilized traditional ISCSI SAN connectivity and focused strictly on compatibility.

TEST CONFIGURATIONS

Three virtual servers were created as per this document and validation testing was be performed as follows.

SQL Testing: VM Parameters:

o Each SQL VM was built utilizing a unique VMDK file for each volume

o Each SQL VM was configured as per best practices: C:\binaries, E:\SQL Database, L:\SQL Logs

o Vormetric data encryption was configured for E:\ and L:\

SQL Database Parameters: o Database size: 25GB

o Number of databases: 1 per VM

1 http://www.fusionio.com/white-papers/vormetric-encryption-at-rest

VM name Qty. OS Role vCPUs Mem

(GB)

vDisk

(GB)

SQL1 1 Windows Server 2012 R2 SQL 2012 Server 2 4 3 x 50

SQL2 1 Windows Server 2012 R2 SQL 2012 Server 2 2 3 x 50

File 1 Windows Server 2012 R2 Generic Server 2 4 2 x 100

Vormetric 1 Data Security Manager 2 2 100

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 4

Test Runs:

o Test #1 entailed a full SQL install and custom database creation on server SQL1 and subsequent snapshot of E:\ and L:\ in a pristine state. Database volumes were then quiesced and a NexGen N5 snapshot was taken. After creation of a new populated table within the custom database, the volumes were then reverted to the snapshot previously taken.

o Test #2 entailed a full SQL install on servers SQL1 and SQL2 with unique populated databases on each server. A flat-file SQL backup was made of a SQL1 database via SQL Server backup utility. The SQL1 backup file was placed on an encrypted volume, a NexGen N5 snapshot was taken and the snapshot was cloned to a new volume. The new volume was mounted on SQL2 and a database restore was performed via SQL Server backup utility using the flat-file backup on the cloned volume

o Test #3 entailed a full SQL install on server SQL1 with a unique populated database on SQL1. Database volumes were then quiesced and replication was setup to a second NexGen N5 hybrid flash array. The SQL1 volumes were unmounted from SQL1 and the replicated volumes on the second NexGen N5 were then mounted to SQL1. SQL was then brought back online on SQL1.

Output: Pass/Fail

File Server Testing: VM Parameters:

o VM was built utilizing a unique VMDK file for each volume

o VM was configured as per best practices: C:\binaries, E:\File

o Vormetric data encryption was configured for E:\

Test Runs: o Test #1 entailed creation of standard word, Excel & PDF files on E:\ drive. The drive was then

quiesced and unmounted, a NexGen N5 snapshot was taken and the snapshot was cloned to a new volume. The new volume was mounted to the File Server and integrity of documents was validated

Output: Pass/Fail

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 5

Validation and Test Results

SQL TEST #1: PASSED

Figure 3: Vormetric GUI – protected volumes

Figure 4: SQL DB after reverting to snapshot

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 6

SQL TEST #2: PASSED

Figure 5: SQL DB flat file restore

Figure 6: SQL DB successful restore

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 7

SQL Test #3: Passed

Figure 7: NexGen N5 replication of DB volumes

Figure 8: NexGen N5 replicated snapshot of DB volume

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 8

Figure 9: NexGen N5l replicated snapshot of Log volume

Figure 10: Windows Server manager showing mounted replicated volumes

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 9

Figure 11: SQL DB back online with replicated volumes

File Test #1: Passed

Figure 12: File Server documents on cloned volume

Solution Validation: NexGen N5 and Vormetric Data Security | January 7, 2015 | 10

Summary

All test scenarios passed, confirming that Vormetric Data Security is fully compatible with NexGen N5 hybrid flash storage. The testing focused on a subset of typical applications and validated application data integrity when utilizing NexGen N5 array features such as snapshots, cloning and intra-array replication.