IT tutorials
 
Technology
 

Windows Server 2012 : Highly available, easy-to-manage multi-server platform - Cost efficiency - Storage Spaces

11/2/2013 8:55:23 PM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

Keeping costs in line is an important consideration for many organizations, and Windows Server 2012 includes new features and enhancements that can help relieve the pressure faced by IT budgets. Features like Hyper-V virtualization, already enable businesses to reduce costs by creating private clouds and by virtualizing workloads, applications, and services.

The following sections highlight other features of the new platform that can help your organization. For example, Storage Spaces lets you store application data on inexpensive file servers with similar performance to what you’ve come to expect from expensive SAN solutions. Thin provisioning and trim allow just-in-time allocations of storage and let you reclaim storage when it is no longer needed, which enables organizations to use storage infrastructures in a more cost-efficient fashion. And the enhanced Network File System (NFS) functionality included in Windows Server 2012 lets you save money by running VMware ESX on VMs that are using Server for NFS as a data store instead of more expensive SAN technologies.

1. Storage Spaces

SANs are a traditional “heavy iron” technology often used for storing large amounts of data, but they tend to be very expensive to acquire and fairly complex to manage. A new feature of Windows Server 2012 called Storage Spaces is designed to change the storage task for enterprises by providing an in-box storage virtualization that can use low-cost commodity storage devices.

Storage Spaces is designed to address a simple question: How can you pool together commodity storage devices so you can provision storage as you need it? The result is Storage Spaces, and by combining this feature with the new scale-out file server and other capabilities of Windows Server 2012, the result is a highly available storage solution that has all the power and flexibility of a SAN but is considerably cheaper and also easier to manage.

Storage Spaces terminology

Storage Spaces can virtualize storage to create what are called storage pools. A storage pool is an aggregation of unallocated space on physical disks installed in or connected to servers. Storage pools are flexible and elastic, allowing you to add or remove disks from the pool as your demand for storage grows or shrinks.

Once you’ve created a storage pool using Storage Spaces, you can provision storage from the pool by creating virtual disks. A virtual disk behaves exactly like a physical disk except that it can span multiple physical disks within the storage pool. Virtual disks can host simple volumes or volumes with resiliency (mirroring or parity) to increase the reliability or performance of the disk. A virtual disk is sometimes called a LUN.

Configuring a storage pool

Configuring a storage pool using Storage Spaces requires that you have at least one unallocated physical disk available (a disk with no volumes on it). If you want to create a mirrored volume, you’ll need at least two physical disks; a parity volume requires at least three physical disks. Pools can consist of a mixture of disks of different types and sizes. Table 1 shows the different types of disks supported by Storage Spaces. These disks could be installed inside servers on your network or within just-a-bunch-of-disks (JBOD) enclosures.

Table 1. Types of Disks Supported by Storage Spaces

Type of drive

Stand-alone file servers

Clustered file servers

SATA

Supported

 

SCSI

Supported

 

iSCSI

Supported

Supported

SAS

Supported

Supported

USB

Supported

 

You can use Server Manager or PowerShell to configure your storage pools, virtual disks, and volumes. To create a new storage pool using Server Manager, select Storage Pools under File And Storage Services. The primordial pool contains unallocated physical disks on the servers you are managing.

To create a new storage pool, click Tasks in the Storage Pools tile and select New Storage Pool:

image with no caption

The New Storage Pool Wizard is started, and after specifying a name for your new pool, you can select which physical disks you want to include in your pool. We’ll select all three available Serial Attached SCSI (SAS) disks for our pool, with the first two disks used for storage and the third designated as a “hot spare” disk that Storage Spaces can bring online automatically if it needs to, such as if one of the other two disks fails:

image with no caption

On completing the wizard, you have the option of creating a new virtual disk when the wizard closes:

image with no caption

The New Virtual Disk Wizard lets you provision storage from your new pool to create virtual disks that span one or more physical disks within your pool:

image with no caption

After you have selected a pool and specified a name for your new virtual disk, you can choose whether to create a simple virtual disk or one with resiliency:

image with no caption

Next, you will select either fixed or thin as the provisioning type :

image with no caption

You’ll also need to specify the size of your new virtual disk. Once you’ve finished provisioning your new virtual disk, you can create volumes on it using the New Volume Wizard by selecting a server and virtual disk and specifying size, drive letter, and file system settings for the volume.

Once you’ve finished creating your storage pools, virtual disks, and volumes, you can manage them using the Storage Pool page of Server Manager:

image with no caption

Provisioning and managing storage using PowerShell

Although the new Server Manager user interface in Windows Server 2012 provides a very convenient and intuitive workflow to provision and manage storage, interaction with PowerShell is required to access many of the advanced features afforded by the new Storage Management application programming interface (API). For example, you can easily create a virtual disk in the user interface; however, the wizard only allows setting the following parameters:

  • Underlying storage pool name

  • Virtual disk name

  • Resiliency setting (Simple, Mirror, or Parity)

  • Provisioning type (Thin or Fixed)

  • Virtual disk size

In contrast, when creating a virtual disk via PowerShell, you can specify additional parameters to tune both resiliency and performance:

  • Number of columns: The number of columns the virtual disk contains

  • Number of data copies: Number of complete copies of data that can be maintained

  • Disk interleave: Number of bytes forming a stripe

  • Physical disks to use: Specific disks to use in the virtual disk

For example, assume that I have an existing pool with the following attributes:

  • Friendly Name: Pool01

  • Disks: nine 450-GB disks (each allocated as Data Store)

  • Pool Capacity: 3.68 TB

If I then create a simple 200-GB virtual disk via the user interface named VDiskSimpleUI, the resulting virtual disk uses eight columns and maintains one copy of the data. But when creating the virtual disk via PowerShell, I can force the stripping across all nine of the disks and optimize performance as follows:

     New-VirtualDisk -StoragePoolFriendlyName Pool01 -ResiliencySettingName Simple -Size 200GB
-FriendlyName VDiskSimplePS -ProvisioningType Fixed -NumberOfDataCopies 1 -NumberOfColumns 9

And creating a mirrored 200-GB virtual disk via the user interface named VDiskMirrorUI produces a virtual disk with four columns and two data copies. But with PowerShell, I can create a slightly different configuration, increasing the data protection (and also the disk footprint):

     New-VirtualDisk -StoragePoolFriendlyName Pool01 -ResiliencySettingName Mirror -Size 200GB
-FriendlyName VDiskMirrorPS -ProvisioningType Fixed -NumberOfDataCopies 3 -NumberOfColumns 3

The results and differences of these various permutations can be easily displayed via PowerShell:

   Get-VirtualDisk | ft FriendlyName, ResiliencySettingName, NumberOfColumns,
NumberOfDataCopies, @{Expression={$_.Size / 1GB}; Label="Size(GB)"}, @{Expression={$_.
FootprintOnPool / 1GB}; Label="PoolFootprint(GB)"} -AutoSize

Here is some output from running this command:

   FriendlyName   ResiliencySettingName NumberOfColumns
NumberOfDataCopies Size(GB) PoolFootprint(GB)

------------ --------------------- --------------- ------------------
-- ------ -----------------

VDiskSimpleUI Simple 8 1
200 200

VDiskMirrorUI Mirror 4 2
200 400

VDiskSimplePS Simple 9 1
200.25 200.25

VDiskMirrorPS Mirror 3 3
200.25 600.75

Some additional tips:

  • The number of columns multiplied by the number of data copies cannot exceed the number of disks in the underlying pool.

  • 256 MB of each physical disk is consumed when adding to a pool.

  • Default resiliency settings:

    • Simple: Striping with no redundancy using a default stripe size of 64 K

    • Mirror: Two-way mirroring with a 64-K default stripe size

    • Parity: Striping with parity using a default column width of 3 (i.e., three disks per row with two containing data and the other containing parity) and a default stripe size of 64 K

  • Although not enforced, it is recommended that pools with more than 24 disks use Manual allocation (as opposed to the auto allocation default of Data Store)

  • Clustering tips:

    • Clustering virtual disks requires the underlying hardware to support persistent reservations.

    • Clustered Storage Spaces require fixed provisioning.

    • Removing a clustered Storage Pool from Failover Clustering will cause the underlying pool to be marked Read Only.


2. Thin Provisioning and Trim

Thin provisioning is a new capability in Windows Server 2012 that integrates with supported storage technologies, including the built-in Storage Spaces feature to allow just-in-time allocation of storage. Trim capability complements thin provisioning by enabling the reclaiming of provisioned storage that is no longer needed.

Thin provisioning is designed to address several issues with traditional models for provisioning storage used by enterprises:

  • The challenges associated with forecasting your organization’s future storage needs makes it hard to pre-allocate storage capacity to meet changing demand for storage.

  • Pre-allocated storage is often underused, which leads to inefficiencies and unnecessary expenditures.

  • Managing an enterprise storage system can often add considerable overhead to the overall cost of managing your IT infrastructure.

The goals of thin provisioning technologies are to address these different needs and deliver the following business benefits:

  • Maximizing how the organization’s storage assets are used

  • Optimizing capital and operational expenditures for managing storage assets

  • Provisioning storage with high availability, scalability, performance, and resilience


3. Server for NFS data store

Server for NFS has been enhanced in Windows Server 2012 to support continuous availability. This makes possible new scenarios, such as running VMware ESX VMs from file-based storage over the NFS protocol instead of using more expensive SAN storage. This improvement enables Windows Server 2012 to provide continuous availability for VMware VMs, making it easier for organizations to integrate their VMware infrastructure with the Windows platform.

Using Server for NFS as a data store for VMware VMs requires using VMware ESX 4.1. You also need a management server with VMware vSphere Client version 4.1 installed. You can use PowerShell to provision and configure shared files on your Server for NFS data store.

 
Others
 
- System Center Configuration Manager 2007 : Client Management - Client Discovery (part 2) - Network Discovery
- System Center Configuration Manager 2007 : Client Management - Client Discovery (part 1) - Active Directory User Discovery
- Windows Vista : Providing User Data Protection (part 3) - Putting data protection in place - Enabling roaming profiles, Enabling folder redirection
- Windows Vista : Providing User Data Protection (part 2) - Putting data protection in place - Enabling the Distributed File System
- Windows Vista : Providing User Data Protection (part 1) - Completing a data protection strategy
- Windows Vista : Protecting User Data - Protecting User Profiles
- SharePoint 2013 : Associate a Workflow with a List or Library
- SharePoint 2013 : Track the Progress of a Workflow
- SharePoint 2013 : Start a Workflow
- What's New in Microsoft Lync Server 2013 : Voice Enhancements - Inter-Trunk Routing
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us