Clustered Storage Spaces - 3 disk minimum for 2-way mirror?

Why will a 2 disk, 1 column, 2-way mirrored space work fine outside of a cluster? Yet, when I want to use clustered storage spaces I need a minimum of 3 physical disks for a 2-way mirrored space? Killing me...
I mean if I add 2 additional disks and do a 4 disk, 2 column, 2-way mirrored space it's ok. What would be the purpose of using 3 disks as a minimum?
Thanks,
Scott

Hi,
Could you please give us more detailed explanation to help us understand your question?
“Cluster storage space” did you mean “Cluster Share Volume” for Hyper-V Cluster?
What did you mean “mirrored space”, did you mean software mirrored volume? For a cluster, we recommend you use a shared storage and configure disk fault tolerance with hardware RAID.
Give us more information of your questions for further troubleshooting.
For more information please refer to following MS articles:
Mirrored Volumes
http://technet.microsoft.com/en-us/library/cc938487.aspx
How to Configure a Clustered Storage Space in Windows Server 2012
http://blogs.msdn.com/b/clustering/archive/2012/06/02/10314262.aspx
Understanding Requirements for Failover Clusters
http://technet.microsoft.com/en-us/library/cc771404.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

Similar Messages

  • Clustered Storage Spaces Management

    What is the best way to manage 2 node windows clustered storage spaces. I have two storage Pool and have General Purpose(NFS), ISCSI target Server(ISCSI) and Scale out file server (SMB) roles installed in MS cluster.  Storage will be provisioned to
    many servers for internal customers as NFS, SMB and ISCSI
    1- What is the best to manage virtual disk, volume ? What I create one virtual disk and and one volume for each server ? or create two virtual disk from each storage pool one for mirror and one for parity and expand as needed ?
    2- Why I assign drive letter to volume i create. Is there better way to manage this ?
    Any best practice document or  KB or help will be really appreciated
    Thank you,
    Adnan
    ad

    What is the best way to manage 2 node windows clustered storage spaces. I have two storage Pool and have General Purpose(NFS), ISCSI target Server(ISCSI) and Scale out file server (SMB) roles installed in MS cluster.  Storage will be provisioned to
    many servers for internal customers as NFS, SMB and ISCSI
    1- What is the best to manage virtual disk, volume ? What I create one virtual disk and and one volume for each server ? or create two virtual disk from each storage pool one for mirror and one for parity and expand as needed ?
    2- Why I assign drive letter to volume i create. Is there better way to manage this ?
    Any best practice document or  KB or help will be really appreciated
    Thank you,
    Adnan
    That's a bad idea to mix Scale-Out File Server role with anything else... Make your SoFS nodes feed shared storage to Hyper-V layer and spawn all other services (failover iSCSI, clustered SMB3 and NFSv4) as a set of a separate VMs.
    Hyper-V Shared Nothing Cluster. Only two Hyper-V hosts needed.

  • Allocation of space for 3-Way Mirror

    A picture paints a thousand words, so I painted. Far easier than tying myself up in knots of words.
    Many thanks.

    Hi,
    A1: 450GB is correct.
    A2: The 2 disks requirement is not static. See the explanation in following article, that why it needs 5 disks for a 3-way mirror:
    http://blogs.technet.com/b/tip_of_the_day/archive/2013/08/29/tip-of-the-day-3-way-mirrors.aspx
    The reason is that a 3-way mirror uses a quorum.  In order to keep running, the mirror space must keep over 50% of the disks functioning.  So a 3-way mirror must have at least 5 physical disks to be able to survive the loss of up to 2 physical
    disks.
    Below is my personal view: With 9 disks act as 3-way mirror, we could lost 6 disks in maximum. As it must keep over 50% of disks in running, we need more than 4.5 disks which is 5, so we need 2 more disks.
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Thanks for this, Shaon Shan.
    When it comes to a 3-way mirror, is a better way of calculating the total amount of enclosure storage for the desired amount of usable storage, to multiply your desired usable storage by a factor of 5? 
    So, if using 500GB drives, to have 1TB of usable storage from a 3-way mirrored virtual disk, I would need to have 5TB of total storage, so a complete total of 10 drives?

  • Storage Spaces: Virtual Disk taken offline during file copy, marked as "This disk is offline because it is out of capacity", but plenty of free space

    Server 2012 RC. I'm using Storage Spaces, with two virtual disks across 23 underlying physical disks.
    * First virtual disk is fixed provisioning, parity across 23 physical disks: 10,024GB capacity
    * Second virtual disk is fixed provisioning, parity across the remaining space on 6 of the same physical disks: 652GB capacity
    These have been configured as dynamic disks, with an NTFS volume spanned across the two (larger virtual disk first). Total volume size 10,676GB. For more details of the hardware, and why the configuration is like this, see: http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/c35ff156-01a8-456a-9190-04c7bcfc048e
    I'm copying several TB from a network share to this volume. It is very slow at ~12MB/sec, but works. However, three times so far, several hours in to the file copy and with plenty of free space remaining, the 10,024GB virtual disk is suddenly taken offline.
    This obviously then fails the spanned volume and stops the file copy.
    The second time, I took screenshots, below. The disk (Disk27) is marked offline due to "This disk is offline because it is out of capacity". And the disk in the spanned volume is marked as missing (which is what you would expect when one of its member disks
    is offline).
    I can then mark the disk (Disk27) back online again, and this restores the spanned volume. I can then re-start the file copy from where it failed. There doesn't appear to be any data loss, but it does cause an outage that requires manual attention. As you
    can see, there is plenty of space left on the spanned volume.
    Each time this has happened, there are a few event 150 errors in the System event log: "Disk 27 has reached a logical block provisioning permanent resource exhaustion condition.". Source: Disk.
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="disk" /> 
      <EventID Qualifiers="49156">150</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2012-06-07T11:24:53.572101500Z" /> 
      <EventRecordID>14476</EventRecordID> 
      <Channel>System</Channel> 
      <Computer>Trounce-Server2.trounce.corp</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>\Device\Harddisk27\DR27</Data> 
      <Data>27</Data> 
      <Binary>000000000200300000000000960004C0000000000000000000000000000000000000000000000000</Binary> 
      </EventData>
      </Event>
    This error seems to be related to thin provisioning of disks. I found this:
    http://msdn.microsoft.com/en-us/library/windows/desktop/hh848068(v=vs.85).aspx. But both these Virtual Disks are configured as Fixed, not Thin provisioning, so it shouldn't apply.
    My thoughts: the virtual disk should not spuriously go offline during a file copy, even if it was out of space. And in any case, there is plenty of free space remaining. Also, I don't understand the reason for why it is marked as offline ("This disk is offline
    because it is out of capacity"). Why would a disk go offline because it was out of thin capacity, rather than just returning an "out of disk space" error while keeping it online.

    Interesting Thread, I've been having the same issue. I had a failed hardware RAID that was impossible to recover in place, so after being forced to do a 1:1 backup, I find myself with 5 2TB hard drives to play with. Storage Spaces seemed like an interesting
    way to go until I started facing the issues we share.
    So my configuration is A VM Running Windows Server 2012 RC with 5 Virtualized Physical drives using a SCSI interface, 2TB in size that make up my storage pool. A Single Thinly provisioned Disk of 18 TB (using 1 disk for parity)
    Interestly enough, write speed has not been an issue on this machine (30~70MB/s, up from 256k on the beta) 
    Of note to me is this error in my event log 13 minutes before the drive disappeared:
    "The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time.Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."Source: volsnap, Event ID: 25, Level: Error
    followed by:
    "The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume17.(The physical resources of  this disk have been exhausted.)"Source: Ntfs (Microsoft-Windows-Ntfs), Event ID: 140, Level: Warning
    I figure the amount of space available to me before I start encountering physical limits is in the vicinity of about 7TB. It dropped out for the second time at 184 GB.
    FYI, the number of columns created for me is 5
    Regards,
    Steven Blom

  • Not enough temporary storage space on disk

    I'm new to Access.  I've imported some tables from a co-worker, who cannot help troubleshoot this issue.
    When I run a query, I get the error "Query cannot be completed.  Either the size of the query result is larger than the maximum size of the database or there is not enough temporary storage space on the disk to store the completed result."
    I've compacted the database.
    I've searched online about how to increase the storage space on the disk.
    Unsure what to do next

    Hi,
    Which Access version do you use? The issue might be related to some reasons.
    1. Access database has its max size (2GB). While running a query it often needs temporary storage. It means that the normal size plus the temp size hits the 2GB file size limit of Access.
    2. Caused by the query, any non-trivial query or operation can use a larger amount of temporary space.
    3. Caused by the database, the column name in database is not the same of the output in the transformation.
    Thus, we may try:
     1. Using SQL Server 2008 Express as back-end database
     2. Splitting your database into front-end and back-end - due to the size eventually multiple back-end files- and using linked tables.
    http://office.microsoft.com/en-us/access-help/split-an-access-database-HA010342026.aspx
    Regards,
    George Zhao
    TechNet Community Support

  • Repair Degraded Storage Spaces Virtual Disk - All physical disks show healthy

    I've seen this mentioned a few times but no definitive answers. I have a Storage Pool with 8 physical disks. Each physical disk shows as healthy and auto select. I have thick provisioned Virtual Disk created on this Storage Pool in a parity configuration.
    This virtual disk is configured for the maximum amount on the storage pool. 50% of the space is available on the volume of the virtual disk...I click repair it does nothing.
    Tested yanking a physical disk. Virtual disk becomes unavailable. No redundancy currently. How the heck do I fix this???

    Hi,
    First please try to run a repair again with Powershell cmdlet:
    Repair-VirtualDisk
    If issue still exists please try optimize to see if it will help:
    Optimize-Volume
    If you have any feedback on our support, please send to [email protected].
    Repair-VirtualDisk:
    Runs shows a progress bar for a very short period of time. Goes back to prompt. No messages or errors. Running Get-Virtual disk still shows the VD as degraded.
    Optimize-Volume:
    PS C:\Users\Administrator> Optimize-Volume -driveletter D -analyze -defrag -verbose
    VERBOSE: Invoking defragmentation on DATA (D:)...
    Optimize-Volume : A general error occurred that is not covered by a more specific error code.
    At line:1 char:1
    + Optimize-Volume -driveletter D -analyze -defrag -verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
    imize-Volume], CimException
    + FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
    PS C:\Users\Administrator> Optimize-Volume -driveletter D -analyze -defrag -verbose
    VERBOSE: Invoking defragmentation on DATA (D:)...
    Optimize-Volume : A general error occurred that is not covered by a more specific error code.
    At line:1 char:1
    + Optimize-Volume -driveletter D -analyze -defrag -verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
    imize-Volume], CimException
    + FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
    PS C:\Users\Administrator> Optimize-Volume D -analyze -verbose
    VERBOSE: Invoking analysis on DATA (D:)...
    Optimize-Volume : A general error occurred that is not covered by a more specific error code.
    At line:1 char:1
    + Optimize-Volume D -analyze -verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
    imize-Volume], CimException
    + FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
    PS C:\Users\Administrator> Optimize-Volume D -Verbose
    VERBOSE: Invoking defragmentation on DATA (D:)...
    Optimize-Volume : A general error occurred that is not covered by a more specific error code.
    At line:1 char:1
    + Optimize-Volume D -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (MSFT_Volume (Ob...8-8907-3485...):ROOT/Microsoft/...age/MSFT_Volume) [Opt
    imize-Volume], CimException
    + FullyQualifiedErrorId : HRESULT 0x89000000,Optimize-Volume
    Both error out...

  • Being disabled you offer a lot. Do you offer more storage space in the cloud for disabled people?

    I haven't used or have a lot of things on my old IPhone and IPad. My phone though is full and I can hardly use it. I don't have any idea how much storage I have on my phone so I am wondering since Apple is helping through the Accessibility program do you offer more space in the Cloud?

    I have a Ipad, Iphone and a PC with a lot of memory. What my problem is I am not under memory problem it is I have duplicates of to many problems using and running Adobe product. Nothing installs like it should so I keep trying and now I don't know what is what. I need help from Adobe but I cann't seem to get any. I have done so much to just download files and nothing downloads like it should.
    I tried to download through creative cloudCS6 and I get CC files. Why did I get CC files when I wanted CS6 files. Am I suposed to upgrade the CC files to CS?

  • Columns in a 2way Mirror Storage Space

    Hi
    I have a similar question like J_Rod: http://social.technet.microsoft.com/Forums/en-US/7a37e6ed-7e22-485c-a5d1-6460b2c4d63b/mimicing-raid-10-resiliency-with-storage-spaces?forum=windowsserverpreview
    Why should I consider using more than 2 Columns in a 2 way mirror Storage Space? For me it makes little difference between a Storage Space with a 2 Column 2 Way Mirroring and a 6 Column 2 Way Mirroring on a 12 Disk Storage Pool (like in the Picture).
    Apart from:
    big write/reads  which are processed by 6 disk in the 6 column configuration instead of 2 in the 2 column configuration
    Filling of the disk is not synchron over all disk with the 2 column configuration
    therefor i get exactly what I expect of the Storage Space when I use the 2 column configuration and try to achieve the same Result as a classic RAID10 (RAID 0 over X RAID1)

    So when I create a 2 Column Mirror Storage Space can I be certain sure that I will have a disk configuration like:
    Disk1 -- Disk2 -- Disk3 -- Disk4 -- Disk5 -- Disk6
    Data1 -- Data1 - Data2 -- Data2 - Data3 -- Data3
    So I could loose disk 1,3 and 5?
    Or is there some other Magic in Storage Spaces?

  • Using Clustered Storage on DFS - SQL Server reports insufficient space

    We have a Clustered Storage Space setup within our DFS at \\ournamespace\shares\sofs. This server has 9TB of space, but the namespace root has only 100GB. When trying to migrate/restore databases larger than 100GB, SQL server complains about the storage
    availability at the \\ournamespace\shares. Is there any way to tell SQL server that the complete path should be evaluated instead?
    Our solution to this is to create a new namespace that is hosted by our CSV.

    This is my restore command and the resulting error message:
    Note here, I'm specifying the full path for the restore location, yet SQL server seems to complain about the "shares" namespace.
    RESTORE
    DATABASE [TEST_DEV]
    FROM
    DISK =
    N'\\ournamespace\shares\Backups\Databases\TEST-DB-Dev\TEST_dev\Week_Of_20140928\TEST_DEV_20141001_110200_CO.bak'
    WITH
    FILE = 1,
    MOVE N'TEST_PROD'
    TO N'\\ournamespace\Shares\SOFS\DB\Gaine-DB14-Dev\TEST_DEV.mdf',
    MOVE N'TEST_PROD_LOG'
    TO N'\\ournamespace\Shares\SOFS\DB\Gaine-DB14-Dev\TEST_DEV_log.ldf',
    NOUNLOAD,
    REPLACE,
    STATS = 5
    GO
    Msg 3257, Level 16, State 1, Line 1
    There is insufficient free space on disk volume '\\local\Shares\' to create the database. The database requires 121447448576 additional free bytes,
    while only 97941053440 bytes are available.
    Msg 3119, Level 16, State 4, Line 1
    Problems were identified while planning for the RESTORE statement. Previous messages provide details.
    Msg 3013, Level 16, State 1, Line 1
    RESTORE DATABASE is terminating abnormally.

  • Replacing a failed disk in storage space ! unable to remove a retired disk

    Hi Folks 
    Not really asking for much !! we are using windows 2012 R2 storage space ; one disk failed 
    and marked as retired. 
    today we received replacement disk ; added that to storage pool - fine. 
    then I repaired all Virtual Disk - process was very quick and went to 100% like a flash. 
    then I tried to remove faulty disk by using following commands :
    $DeadDisk=Get-PhysicalDisk -FriendlyName PhysicalDisk-1 
    FriendlyName        CanPool             OperationalStatus   HealthStatus        Usage                            
     Size
    PhysicalDisk-1      False               Lost Communication  Warning             Retired                        185.5
    GB
    Remove-PhysicalDisk -PhysicalDisks $deaddisk -StoragePoolFriendlyName storagePool
    this errored out ; basically saying that the above disk is still in-use ! 
    Any suggestions ? does repair job take some time ? it looked very fast ; when I did get-storagejob ; it showed 100 percent completed . 

    Hi,
    Please reboot the server then set the failed disk to "Retired" and remove the retired physical disk.
    You could refer to the thread below to troubleshoot the issue:
    Degraded Storage Spaces Storage Pool after single HDD failure
    http://social.technet.microsoft.com/Forums/en-US/3a7e2a7d-4ad7-48cc-8165-0d6673e37436/degraded-storage-spaces-storage-pool-after-single-hdd-failure
    Regards,
    Mandy
    If you have any feedback on our support, please click
    here .
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • First cluster - Server 2012 r2 - storage spaces issues

    Hi Everyone
       We just purchased two new servers (Lenovo RD640's) and an external SAS JBOD enclosure (the Lenovo SA120), and we would like to set up a 2012 r2 failover cluster with clustered storage spaces as the shared storage.  Currently they are
    on their own domain with the virtual active directory server residing locally on one of the servers.
       Preface: I've created and destroyed the cluster and storage spaces multiple times trying to solve this issue, so I don't know if I may have "leftovers" from those attempts now causing issues for me.
      I can create the cluster, and it passes validation, and can create a clustered storage pool, but every time I try to create a virtual disk (either through the Failover cluster manager, the server manager, or powershell), it won't attach.  If
    I try to manually attach it I get the message: "Error attaching or detaching virtual disk: Failed to attach virtual disk to <node name>. Access denied"
    Finally (and I don't know if this is related or not), when in storage spaces on the server manager, there is a gold banner at the top that says "Incomplete communication with cluster <cluster name>. The following cluster nodes or clustered roles
    might be offline or have connectivity issues: <cluster name>"
     I'm logged in with full domain administrator credentials, and have been running my head against this wall for a few days now.  Any help would be appreciated!

    Thanks for your responses. Here is what I have to report:
    When I destroy the cluster, and create the storage spaces on just one of the two servers (with the other server powered down), I'm able to create the storage pool - using all the HDDs and SSDs - and virtual disks (both tiered and non-tiered) without issue. 
    As soon as I create the cluster again, the virtual disks become "detached", and I'm back to the situation described initially.
    @Apamnapat, here's the output of the powershell commandlets you suggested:
    PS C:\Windows\system32> get-storagepool | fl *
    Usage                             : Other
    OperationalStatus                 : OK
    HealthStatus                      : Healthy
    ProvisioningTypeDefault           : Fixed
    SupportedProvisioningTypes        : {Thin, Fixed}
    ReadOnlyReason                    : None
    RepairPolicy                      : Parallel
    RetireMissingPhysicalDisks        : Auto
    WriteCacheSizeDefault             : Auto
    FileSystem                        : Unknown
    Version                           : Windows Server 2012 R2
    ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                        ="{1cca13ee-d45c-11e3-80b5-806e6f6e6963}:SP:{1cca13ef-d45c-11e3-80b5-806e6f6e6963}"
    PassThroughClass                  :
    PassThroughIds                    :
    PassThroughNamespace              :
    PassThroughServer                 :
    UniqueId                          : {1cca13ef-d45c-11e3-80b5-806e6f6e6963}
    AllocatedSize                     : 24962849046528
    ClearOnDeallocate                 : False
    EnclosureAwareDefault             : False
    FriendlyName                      : Primordial
    IsClustered                       : False
    IsPowerProtected                  : False
    IsPrimordial                      : True
    IsReadOnly                        : False
    LogicalSectorSize                 :
    Name                              :
    OtherOperationalStatusDescription :
    OtherUsageDescription             :
    PhysicalSectorSize                :
    ResiliencySettingNameDefault      : Mirror
    Size                              : 25264456597504
    SupportsDeduplication             : False
    ThinProvisioningAlertThresholds   : {70}
    WriteCacheSizeMax                 : 107374182400
    WriteCacheSizeMin                 : 0
    PSComputerName                    :
    CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
    CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
    CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
    Usage                             : Other
    OperationalStatus                 : OK
    HealthStatus                      : Healthy
    ProvisioningTypeDefault           : Fixed
    SupportedProvisioningTypes        : Fixed
    ReadOnlyReason                    : None
    RepairPolicy                      : Parallel
    RetireMissingPhysicalDisks        : Auto
    WriteCacheSizeDefault             : Auto
    FileSystem                        : Unknown
    Version                           : Windows Server 2012 R2
    ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                        ="{3407c278-597d-4d38-b877-b2eff1e8a936}:SP:{05303524-5f93-4829-b84a-44955d1eb28e}"
    PassThroughClass                  :
    PassThroughIds                    :
    PassThroughNamespace              :
    PassThroughServer                 :
    UniqueId                          : {05303524-5f93-4829-b84a-44955d1eb28e}
    AllocatedSize                     : 24962849046528
    ClearOnDeallocate                 : False
    EnclosureAwareDefault             : False
    FriendlyName                      : Primordial
    IsClustered                       : True
    IsPowerProtected                  : False
    IsPrimordial                      : True
    IsReadOnly                        : False
    LogicalSectorSize                 :
    Name                              :
    OtherOperationalStatusDescription :
    OtherUsageDescription             :
    PhysicalSectorSize                :
    ResiliencySettingNameDefault      : Mirror
    Size                              : 25264456597504
    SupportsDeduplication             : False
    ThinProvisioningAlertThresholds   : {70}
    WriteCacheSizeMax                 : 107374182400
    WriteCacheSizeMin                 : 0
    PSComputerName                    :
    CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
    CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
    CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
    Usage                             : Other
    OperationalStatus                 : OK
    HealthStatus                      : Healthy
    ProvisioningTypeDefault           : Fixed
    SupportedProvisioningTypes        : Fixed
    ReadOnlyReason                    : None
    RepairPolicy                      : Parallel
    RetireMissingPhysicalDisks        : Auto
    WriteCacheSizeDefault             : Auto
    FileSystem                        : Unknown
    Version                           : Windows Server 2012 R2
    ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.ObjectId
                                        ="{3407c278-597d-4d38-b877-b2eff1e8a936}:SP:{48e0189b-db8c-11e3-80d3-f80f41fcd134}"
    PassThroughClass                  :
    PassThroughIds                    :
    PassThroughNamespace              :
    PassThroughServer                 :
    UniqueId                          : {48e0189b-db8c-11e3-80d3-f80f41fcd134}
    AllocatedSize                     : 17179869184
    ClearOnDeallocate                 : False
    EnclosureAwareDefault             : False
    FriendlyName                      : Storage Pool
    IsClustered                       : True
    IsPowerProtected                  : False
    IsPrimordial                      : False
    IsReadOnly                        : False
    LogicalSectorSize                 : 512
    Name                              :
    OtherOperationalStatusDescription :
    OtherUsageDescription             :
    PhysicalSectorSize                : 4096
    ResiliencySettingNameDefault      : Mirror
    Size                              : 24951612506112
    SupportsDeduplication             : False
    ThinProvisioningAlertThresholds   : {70}
    WriteCacheSizeMax                 : 107374182400
    WriteCacheSizeMin                 : 0
    PSComputerName                    :
    CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_StoragePool
    CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
    CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties
    PS C:\Windows\system32> get-virtualdisk | fl *
    Usage                             : Other
    NameFormat                        :
    OperationalStatus                 : Detached
    HealthStatus                      : Unknown
    ProvisioningType                  : Fixed
    ParityLayout                      : Rotated Parity
    Access                            : Read/Write
    UniqueIdFormat                    : Vendor Specific
    DetachedReason                    : By Policy
    WriteCacheSize                    : 1073741824
    ObjectId                          : {1}\\CBC116\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.ObjectId
                                        ="{3407c278-597d-4d38-b877-b2eff1e8a936}:VD:{48e0189b-db8c-11e3-80d3-f80f41fcd134}{
                                        c1894936-db95-11e3-80d5-f80f41fcd134}"
    PassThroughClass                  :
    PassThroughIds                    :
    PassThroughNamespace              :
    PassThroughServer                 :
    UniqueId                          : 364989C195DBE31180D5F80F41FCD134
    AllocatedSize                     : 7516192768
    FootprintOnPool                   : 8589934592
    FriendlyName                      : Disk Witness
    Interleave                        : 262144
    IsDeduplicationEnabled            : False
    IsEnclosureAware                  : False
    IsManualAttach                    : True
    IsSnapshot                        : False
    LogicalSectorSize                 : 512
    Name                              :
    NumberOfAvailableCopies           :
    NumberOfColumns                   : 8
    NumberOfDataCopies                : 1
    OtherOperationalStatusDescription :
    OtherUsageDescription             :
    PhysicalDiskRedundancy            : 1
    PhysicalSectorSize                : 4096
    RequestNoSinglePointOfFailure     : False
    ResiliencySettingName             : Parity
    Size                              : 7516192768
    UniqueIdFormatDescription         :
    PSComputerName                    :
    CimClass                          : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDisk
    CimInstanceProperties             : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}
    CimSystemProperties               : Microsoft.Management.Infrastructure.CimSystemProperties

  • How to calculate the disk failure level for a 3-way mirror pool?

    On another post in this forum, the following information regarding a 3-way mirroring storage pool is given:
    Pool requires a quorum of 50% plus drives to be present to survive.
    with 3 way mirror - we have a guarantee of surviving 2 disk failure.
    Maintaining the above requirements and providing the guarantee -
    mandates us to have minimum 5 disks in pool. As if we loose 2, we still
    have 3 in the pool (>50%) for pool to maintain it's quorum.
    Just to be sure, I would like Microsoft to confirm that the following calculation applies to any number of disks in a 3-way mirroring pool.
    If the number of disks in a 3-way mirroring pool is n, INT(n/2) disks can fail without data loss.
    Examples:
    With 5 disks, INT(5/2)=INT(2.5)=2 disks can fail.
    With 6 disks, INT(6/2)=INT(3)=3 disks can fail.
    With 9 disks, INT(9/2)=INT(4.5)=4 disks can fail.
    Am I right in this assumption?
    Thanks for your answer.

    Hi,
    >>Am I right in this assumption?
    Based on my understanding, it’s not this case.
    Mirror spaces are designed for increased performance and protect your files from drive failure by keeping more than one copy. Two-way mirror spaces make two copies of your
    files and can tolerate one drive failure, while three-way mirror spaces can tolerate two drive failures.
    Regarding this point, the following thread can be referred to for better understanding.
    Storage Spaces - Disk resiliency
    http://social.technet.microsoft.com/Forums/en-US/8f13ecf3-61c8-4505-90da-e8a01023c62d/storage-spaces-disk-resiliency?forum=winserverfiles
    In addition, regarding storage spaces, the following article can be referred to for more information.
    Storage Spaces Overview
    http://social.technet.microsoft.com/wiki/contents/articles/15198.storage-spaces-overview.aspx
    Best regards,
    Frank Shen

  • How to create a local, non-clustered storage pool

    Hello,
    I have setup a two-node Failover Cluster, with a shared SAS DAS. So far so good.
    One of the nodes also has internal disks that I wish to use for system backups.
    This storage pool should not be clustered, as the disks cannot be seen from the other node. The trouble is that as soon as I create the pool it gets added to the cluster (in failed state).
    In fact, the "Storage Pools" window in the server manager will only show me the "clustered storage spaces", with my internal disks in the Primordial pool.
    Get-StorageSubSystem will show me both subsystems (Clustered Storage Space on ... + Storage Spaces on node-1) but fails to create a storage pool on the "local" subsystem.
    How can I create a local, non clustered storage pool on internal disks ?
    Cheers
    alex

    Hi,
    SpackTime_ is right, the DA storage usually for the localdata backup, but if you want to use for remote computer backup, you can share a floder then you can storage your backup, but also that backup won't work the shared computer crash.
    The simlar thread:
    Schedule Backup to Remote Shared Folder
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/726d3765-5f82-4590-b970-d45e17412281/schedule-backup-to-remote-shared-folder?forum=winserverfiles
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • How can I configure ReFS to NOT fail read operations when a checksum error is detected (on non-Storage-Spaces volumes where data integrity streams are enabled)?

    According to William Stanek, in his Windows Server 2012 R2 Inside Out: Configuration, Storage & Essentials book, this is apparently possible: (pg. 615 - here it is on Google Books: https://books.google.ca/books?id=0IyfBAAAQBAJ&pg=PT819&lpg=PT819&dq=read+operation )
        Integrity can be enabled when the system is not running on Storage Spaces. When
        integrity is enabled and ReFS detects a checksum mismatch, ReFS logs an event and
        fails the read operation by default. If you don’t want the read operation to fail, you
        can configure ReFS to continue with the read operation. A related event will be logged
        regardless.
    So then how do I configure it to do that???
    (And just to make it super-clear, I'm NOT using Storage Spaces, so there is no redundancy via mirroring/parity, and I'm not expecting any file repair - just detection of corruption. It's just a basic volume formatted with ReFS and
    with integrity streams enabled, via format E: /fs:ReFS /i:enabled
    For those who want more details, here's the situation: 
    I try to perform a read operation on a file with corrupted data (purposely done for testing using a low-level disk editor), I get a the following error message:
    And an event ID 133 from ReFSv1 gets logged in the System log:
    Clicking "Try Again" just brings up the same message, and clicking "Skip" skips the operation entirely.
    This is indeed the correct default behaviour.
    What I want instead is for the read operation to be allowed to complete, with corrupt data and all, and ONLY for the event to be logged. And according to William Stanek, this is supposed to be configurable somewhere - and after hours of searching, I haven't
    been able to find anything.

    Hi Tommy,
    >>How can I configure ReFS to NOT fail read operations when a checksum error is detected
    We can use PowerShell command Set-FileIntegrity to configure this. The specific parameter for controlling this behavior is
    -Enforce <Boolean>which indicates whether to enable blocking access to a file if integrity streams do not match the data.  
    Regarding this point, the following article can be referred to as reference.
    Set-FileIntegrity
    https://technet.microsoft.com/en-us/library/jj218351.aspx
    Best regards,
    Frank Shen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Storage Spaces: SSD tier size incorrect when using EnclosureAware option in a pool

    Hi folks,
    We're about to deploy Storage Spaces in our test environment, but we encountered an issue while configuring Enclosure Awareness on Storage Pools.
    When we create a Storage Pool (over 3 JBOD's) and set the option EnclosureAwarenessDefault to $True, the SSD tier size automatically decreases / shrinks to 12GB (sometimes 18GB sometimes 0GB).
    Without EnclosureAwarenessDefault, we get 1110 GB of SSD size available.
    The same behavior is seen when enabling -EnclosureAwareness on Storage Space (virtual disk) level.
    A summary of our configuration:
    3 SOFS connected twice to each JBOD (LSI 9207-8e - SES 3 ) = HCL certified
    3 JBOD arrays (Quanta M4600H) (Firmware Management SCSI Enclosure Service (SES-2) = HCL certified
    Each JBOD array has 16 HDD and 4 SSD.
    SOFS are fully patched, including KB 2913766
    Below 2 screenshots:
    EnclosureAwareDefault = $True
    https://onedrive.live.com/redir?resid=BB5A32452CA3BD6C%21436
    EnclosureAwareDefault = $False
    https://onedrive.live.com/redir?resid=BB5A32452CA3BD6C%21437

    Hi Partner,
    Thank you for your detailed information and sorry for the delayed response.
    After consulting with some senior engineers, please check the following:
    Server manager does not let you set the column count of the space, which means that it is automatically selecting 6 as the column count, as there are 12 SSDs.  Unfortunately, the column count must be less than the number of disks of each type in each
    enclosure (limited by 4 SSDs), otherwise space creation will fail, and estimation will produce a small, somewhat random number.  If you create a space through powershell and specify –NumberOfColumns 4 then it should work.
    Hopefully it helps.
    Feel free to let me know if you have any question. Thank your for your time.
    Best Regards,
    Sophia Sun
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Maybe you are looking for