Export (0) Print
Expand All
Expand Minimize
0 out of 1 rated this helpful - Rate this topic

New-StoragePool

Windows Server 2012 R2 and Windows 8.1

Updated: April 10, 2014

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

New-StoragePool

Creates a new storage pool using a group of physical disks, and a specific storage subsystem exposed by a storage provider.

Syntax

Parameter Set: ByFriendlyName
New-StoragePool [-StorageSubSystemFriendlyName] <String[]> -FriendlyName <String> -PhysicalDisks <CimInstance[]> [-AsJob] [-AutoWriteCacheSize <Boolean> ] [-CimSession <CimSession[]> ] [-EnclosureAwareDefault <Boolean> ] [-LogicalSectorSizeDefault <UInt64> ] [-OtherUsageDescription <String> ] [-ProvisioningTypeDefault <ProvisioningType> ] [-ResiliencySettingNameDefault <String> ] [-ThrottleLimit <Int32> ] [-Usage <Usage> ] [-WriteCacheSizeDefault <UInt64> ] [ <CommonParameters>]

Parameter Set: ByName
New-StoragePool -FriendlyName <String> -PhysicalDisks <CimInstance[]> -StorageSubSystemName <String[]> [-AsJob] [-AutoWriteCacheSize <Boolean> ] [-CimSession <CimSession[]> ] [-EnclosureAwareDefault <Boolean> ] [-LogicalSectorSizeDefault <UInt64> ] [-OtherUsageDescription <String> ] [-ProvisioningTypeDefault <ProvisioningType> ] [-ResiliencySettingNameDefault <String> ] [-ThrottleLimit <Int32> ] [-Usage <Usage> ] [-WriteCacheSizeDefault <UInt64> ] [ <CommonParameters>]

Parameter Set: ByUniqueId
New-StoragePool -FriendlyName <String> -PhysicalDisks <CimInstance[]> -StorageSubSystemUniqueId <String[]> [-AsJob] [-AutoWriteCacheSize <Boolean> ] [-CimSession <CimSession[]> ] [-EnclosureAwareDefault <Boolean> ] [-LogicalSectorSizeDefault <UInt64> ] [-OtherUsageDescription <String> ] [-ProvisioningTypeDefault <ProvisioningType> ] [-ResiliencySettingNameDefault <String> ] [-ThrottleLimit <Int32> ] [-Usage <Usage> ] [-WriteCacheSizeDefault <UInt64> ] [ <CommonParameters>]

Parameter Set: InputObject (cdxml)
New-StoragePool -FriendlyName <String> -InputObject <CimInstance[]> -PhysicalDisks <CimInstance[]> [-AsJob] [-AutoWriteCacheSize <Boolean> ] [-CimSession <CimSession[]> ] [-EnclosureAwareDefault <Boolean> ] [-LogicalSectorSizeDefault <UInt64> ] [-OtherUsageDescription <String> ] [-ProvisioningTypeDefault <ProvisioningType> ] [-ResiliencySettingNameDefault <String> ] [-ThrottleLimit <Int32> ] [-Usage <Usage> ] [-WriteCacheSizeDefault <UInt64> ] [ <CommonParameters>]




Detailed Description

The New-StoragePool cmdlet creates a new storage pool using a group of physical disks, and a specific storage subsystem exposed by a storage provider.

Parameters

-AsJob

Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell® background jobs, see about_Jobs.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-AutoWriteCacheSize<Boolean>

Indicates whether to set the size of the write-back cache to 1 GB for all types of storage spaces, which include simple, mirror, and parity, to create from the pool. If the number or size of the solid-state drives (SSDs) or journal disks in the storage pool is not sufficient and you specify a value of $True for this parameter, the cmdlet sets the write-back cache size to 0 for simple and mirror spaces, and to 32 MB for parity spaces.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-CimSession<CimSession[]>

Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.


Aliases

Session

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-EnclosureAwareDefault<Boolean>

Specifies the default allocation policy for virtual disks created in an enclosure-aware storage pool. For example, an enclosure-aware subsystem could balance each data copy of the virtual disk across multiple physical enclosures such that each enclosure contains a full data copy of the virtual disk.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-FriendlyName<String>

Specifies a friendly name for the storage pool to be created. The friendly name may be defined by a user and is not guaranteed to be unique.


Aliases

StoragePoolFriendlyName

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-InputObject<CimInstance[]>

Accepts an object from the pipeline as input.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByValue)

Accept Wildcard Characters?

false

-LogicalSectorSizeDefault<UInt64>

Specifies the default logical sector size to use for virtual disks created in this pool. Valid logical sector size values (in bytes) for virtual disks created by using the Storage Spaces subsystem are 512 and 4096.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-OtherUsageDescription<String>

Specifies the usage description for the storage pool.


Aliases

StoragePoolOtherUsageDescription

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-PhysicalDisks<CimInstance[]>

Accepts one or more PhysicalDisk objects as input. The Physical Disk CIM objects represent the physical disks to be added to the storage pool.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ProvisioningTypeDefault<ProvisioningType>

Specifies the default type of provisioning for virtual disks created in this pool. The acceptable values for this parameter are: Unknown, Fixed or Thin.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ResiliencySettingNameDefault<String>

Specifies the default resiliency setting name for virtual disks created in this pool.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-StorageSubSystemFriendlyName<String[]>

Specifies the friendly name of the storage subsystem on which you want to create the storage pool.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-StorageSubSystemName<String[]>

Specifies the name of the storage subsystem (provided by the Storage Management) on which you want to create the storage pool.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-StorageSubSystemUniqueId<String[]>

Specifies the ID of the storage subsystem on which you want to create the storage pool


Aliases

StorageSubsystemId

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-ThrottleLimit<Int32>

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Usage<Usage>

Specifies the usage setting for the storage pool. The acceptable values for this parameter are: Other, ReservedAsDeltaReplicaContainer, ReservedForComputerSystem, ReservedForLocalReplicationServices, ReservedForMigrationServices, ReservedForRemoteReplicationServices, ReservedForSparing, and Unrestricted.


Aliases

StoragePoolUsage

Required?

false

Position?

named

Default Value

Other

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WriteCacheSizeDefault<UInt64>

Specifies the default write-back cache size for virtual disks in the storage pool.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Notes

  • The Microsoft.Management.Infrastructure.CimInstance object is a wrapper class that displays Windows Management Instrumentation (WMI) objects. The path after the pound sign (#) provides the namespace and class name for the underlying WMI object.

Examples

Example 1: Create a new storage pool using Storage Spaces

This example creates a new storage pool named CompanyData using the Storage Spaces subsytem, using the minimum parameters, and assuming that there are no other storage subsystems attached to the computer that have available disks.


 

This line uses the Get-PhysicalDisk cmdlet to get all PhysicalDisk objects than are not yet in a (concrete) storage pool, and assigns the array of objects to the $PhysicalDisks variable.


PS C:\> $PhysicalDisks = (Get-PhysicalDisk -CanPool $True)

 

This line creates a new storage pool using the $PhysicalDisks variable to specify the disks to include from the Storage Spaces subsystem (specified with a wildcard * to remove the need to modify the friendly name for different computers).


PS C:\> New-StoragePool -FriendlyName CompanyData -StorageSubsystemFriendlyName "Storage Spaces*" -PhysicalDisks $PhysicalDisks

Example 2: Create a new pool and set defaults for virtual disks

This example creates a new storage pool named CompanyData using the Storage Spaces subsystem and sets default values for virtual disk creation.


 

PS C:\> $PhysicalDisks = (Get-PhysicalDisk -CanPool $True)
PS C:\> New-StoragePool -FriendlyName CompanyData -StorageSubsystemFriendlyName "Storage Spaces*" -PhysicalDisks $PhysicalDisks -ResiliencySettingNameDefault Mirror -ProvisioningTypeDefault Thin –Verbose

Example 3: Create a new storage pool, virtual disk, partition, and volume

This example creates a new storage pool, and then makes use of the pipeline to create a new virtual disk in the pool, initialize the disk, create a new partition on the disk, and then format the new partition (volume). Alternatively you can use the New-Volume cmdlet to achieve a similar result in a single command.


 

The first line ($PhysicalDisks =…) gets the storage subsystem object for the Storage Spaces subsystem, passes it to the Get-PhysicalDisk cmdlet, which then gets the physical disks in the specified subsystem that are available to add to a storage pool, and assigns these disks to the $PhysicalDisks variable.

The second line of the command has five parts, connected by the pipeline (|). The first part (New-StoragePool…) creates a new storage pool using the physical disks in the $PhysicalDisks variable, and then passes the new storage pool down the pipeline. All of the following commands are logically part of one command and should be entered as such.

The second part (New-VirtualDisk…) creates a new virtual disk on the passed in storage pool and then passes the new virtual disk down the pipeline.

The third part (Initialize-Disk…) initializes the disk that was passed in, and then passes the disk down the pipeline.

The fourth part (New-Partition…) creates a new partition on the disk that was passed in, assigns it the next available drive letter, and then passes the partition down the pipeline.

The final part of the command (Format-Volume) formats the partition that was passed in.


PS C:\> $PhysicalDisks = Get-StorageSubSystem -FriendlyName "Storage Spaces*" | Get-PhysicalDisk -CanPool $True 
PS C:\> New-StoragePool -FriendlyName "CompanyData" -StorageSubsystemFriendlyName "Storage Spaces*" -PhysicalDisks $PhysicalDisks |New-VirtualDisk -FriendlyName "UserData" -Size 100GB -ProvisioningType Thin |Initialize-Disk -PassThru |New-Partition -AssignDriveLetter -UseMaximumSize |Format-Volume

Related topics

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.