none
Storage Replication Not working

    Question

  • Hi,

    I have strange issue and I hope that someone can help me. I am configuring Storage Replication and replication is failing on Physical sector size.

    Server 1 Physical sector size is 512

    Server 2 Physical sector size is 4096

    I understand that all disks needs to have same size, same sector etc. but that what I don't understand is if I take one drive from server 2 and import it in server 1 physical sector size changes from 4096 to 512 and I am not able to change it back. 

    Can someone explain what is going on, please?

    Monday, February 6, 2017 12:23 PM

Answers

  • Storage replication is a general purpose, not an application specific, replication technology.  In fact, here is a direct quote from Ned Pyle, the PM for Storage Replication.

    Storage Replica is not Hyper-V Replica or Microsoft SQL AlwaysOn Availability Groups. Storage Replica is a general purpose, storage-agnostic engine. By definition, it cannot tailor its behavior as ideally as application-level replication. This may lead to specific feature gaps that encourage you to deploy or remain on specific application replication technologies.

    Here is the article from which that quote was taken - https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-replica/storage-replica-overview  Maybe Ned's description will help you understand why it is better to use a specifically designed tool like Hyper-V Replica for VM replication instead of a general purpose tool like storage replication.


    . : | : . : | : . tim

    • Marked as answer by Vendetta5 Tuesday, March 7, 2017 1:17 PM
    Wednesday, February 22, 2017 2:47 PM
  • Hi,

    Can you please tell us what are you trying to accomplish? Why do you want to use storage replica? Storage Replica is new Windows Server feature that provides volume-bases replication for high availability. If you have Hyper-V host or hosts and you would like to secure your VMs so if something happens that you can recover them than Storage replica is not the option for you. Hyper-V Replication would be best in that case or Hyper-V cluster (if you want to secure your self in case of host failure)

    ------------------------------------------------------------------------------------------------------------
    If you found this post helpful, please give it a "Helpful" vote. 
    Please remember to mark the replies as answers if they help

    • Marked as answer by Vendetta5 Tuesday, March 7, 2017 1:17 PM
    Tuesday, March 7, 2017 9:49 AM
  • Hi Tim,

    Sorry for the late reply. I tried to find article which explains when we can use Storage replica and no one could answer when. I do not see any scenario where this should work when we have Hyper-V replica for DR scenario



    Hi,

    you can for example use storage replica for:

    1) Stretch cluster scenario, where you have one cluster on multiple sites. You can set automated failover over stretch cluster and it will protect you againts clustered share volume (CSV) failures. In default configuration if one site is not responding for 20 seconds (20 heartbeats per 1 second) the site is considered as down and cluster is going to run in your second location and replicated clustered share volume

    2) Cluster to cluster with manual failover

    3) server to server with manual failover.

    Please note that Storage replica is available only on Datacenter edition of Windows server 2016

    Additionally I think that it depends on the created RAID array if your disk Physicall sector on server would be 4096 or 512. So all disk in RAID array on Server1 will allways be 512 and on Server2 will allways be 4096. Or are those disk just JBOD?

    Radek

    • Marked as answer by Vendetta5 Tuesday, March 7, 2017 1:17 PM
    Tuesday, March 7, 2017 1:08 PM

All replies

  • Hello.

    Couldn't understand what you mean with "if I take one drive from server 2 and import it in server 1 physical sector size changes from 4096 to 512 and I am not able to change it back. "

    But, disk block sizes are set when you first format then so there's no change back unless you delete the volume and recreate.

    So you really need to make sure all block sizes are equal.

    Monday, February 6, 2017 1:24 PM
  • Hi Diego,

    What I mean by that is that on server 1 physical sector size is 512 and on server 2 4096. They have to be the same to be able to use storage replication. If I take out hard drive from server 1 (I have 10 drives) which has physical sector size 512 and if I install it in server 2 that physical sector size will change to 4096. It will not remain 512. When I format disk I have no option to change or to setup that.

    Monday, February 6, 2017 2:29 PM
  • Hi Vendetta5,

    As far as I know, the physical sector size is determined by the manufacturer, and could not be changed on OS level.

    >>if I install it in server 2 that physical sector size will change to 4096. It will not remain 512.

    If you run Test-SRTopology , what result did you get?

    Best Regards,

    Leo


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 7, 2017 5:47 AM
    Moderator
  • Hi Leo,

    Thank you for your answer.

    I am not able to configure replication becuase of this. I found many articles about this and people said that this can't be changed but can someone explain this to me

    In server 1 that drive has 512 physical sector and when I unmount it from server 1 (same drive) and mount it on server 2 that physical sector change to 4096. 


    Tuesday, February 7, 2017 7:00 AM
  • Have you talked with your drive vendor to get their input on their product?

    . : | : . : | : . tim

    Tuesday, February 7, 2017 12:56 PM
  • Thank you Tim. I will contact them and ask. Can you please tell me if it is best practice or if we can use Storage replication to replicate VM storage or what is best practice to use this feature? 
    Tuesday, February 7, 2017 3:21 PM
  • If you are talking about VM storage, it seems more appropriate to use Hyper-V Replica to replicated everything associated with the VM instead of just the storage.

    . : | : . : | : . tim

    Tuesday, February 7, 2017 5:31 PM
  • Hi Tim,

    Can you please tell me why should we use storage replica if it is not good option for VMs? What are good scenarios for this feature?

    Wednesday, February 22, 2017 1:11 PM
  • Storage replication is a general purpose, not an application specific, replication technology.  In fact, here is a direct quote from Ned Pyle, the PM for Storage Replication.

    Storage Replica is not Hyper-V Replica or Microsoft SQL AlwaysOn Availability Groups. Storage Replica is a general purpose, storage-agnostic engine. By definition, it cannot tailor its behavior as ideally as application-level replication. This may lead to specific feature gaps that encourage you to deploy or remain on specific application replication technologies.

    Here is the article from which that quote was taken - https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-replica/storage-replica-overview  Maybe Ned's description will help you understand why it is better to use a specifically designed tool like Hyper-V Replica for VM replication instead of a general purpose tool like storage replication.


    . : | : . : | : . tim

    • Marked as answer by Vendetta5 Tuesday, March 7, 2017 1:17 PM
    Wednesday, February 22, 2017 2:47 PM
  • Hi Tim,

    Sorry for the late reply. I tried to find article which explains when we can use Storage replica and no one could answer when. I do not see any scenario where this should work when we have Hyper-V replica for DR scenario



    • Edited by Vendetta5 Tuesday, March 7, 2017 9:35 AM
    Tuesday, March 7, 2017 9:35 AM
  • I tried to find article which explains when we can use Storage replica and no one could answer when. I do not see any scenario where this should work when we have Hyper-V replica for DR scenario

    Hi,

    you could use Storage Replica for synchronous purposes, if your SMB Network is fast enough (think about the Acknowlegde). Hyper-V Replica transfers the data only asynchronous.

    bye,
    Marcel


    https://www.windowspro.de/marcel-kueppers

    I write here only in private interest

    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.


    Tuesday, March 7, 2017 9:44 AM
  • Hi Tim,

    Sorry for the late reply. I tried to find article which explains when we can use Storage replica and no one could answer when. I do not see any scenario where this should work when we have Hyper-V replica for DR scenario



    Hi,

    you can for example use storage replica for:

    1) Stretch cluster scenario, where you have one cluster on multiple sites. You can set automated failover over stretch cluster and it will protect you againts clustered share volume (CSV) failures. In default configuration if one site is not responding for 20 seconds (20 heartbeats per 1 second) the site is considered as down and cluster is going to run in your second location and replicated clustered share volume

    2) Cluster to cluster with manual failover

    3) server to server with manual failover.

    Please note that Storage replica is available only on Datacenter edition of Windows server 2016

    Additionally I think that it depends on the created RAID array if your disk Physicall sector on server would be 4096 or 512. So all disk in RAID array on Server1 will allways be 512 and on Server2 will allways be 4096. Or are those disk just JBOD?

    Radek

    • Marked as answer by Vendetta5 Tuesday, March 7, 2017 1:17 PM
    Tuesday, March 7, 2017 1:08 PM
  • Thank you everyone for your help.
    Tuesday, March 7, 2017 1:17 PM