Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
2008R2 DFS will not replicate via USB3 Interface

Unanswered 2008R2 DFS will not replicate via USB3 Interface

  • Wednesday, May 23, 2012 8:32 PM
     
     
    Sign In to Vote
    0

    Issue:
    Replication for Data Collection does not work when targeting an External Hard Drive Enclosure via USB3 Interface.

    Update - 05/28/2012:
    Removable Media Bit appears to be the issue, see below.

    If anyone knows how to tell Windows the drive is MediaType = "Fixed hard disk media" vs. MediaType = "External hard disk media", I’d greatly appreciate it.

    Overview:
    I can create a New Replication Group / Replication Group for Data Collection with zero issues as long as the target(s) are internal drives, internal arrays, or external drives / arrays / enclosures attached via eSATA or Multilane.  If I try and create a Replication Group with a target attached via a USB interface, replication fails.

    I was able to successfully create a Replication Group on an external enclosure & drives using an eSATA connection and then attempted to create the exact same configuration using the exact same hardware, only changing the cable/connection to USB3, same server, enclosure, and drives, and it fails.

    Setup:
    2 Windows 2008R2 SP1 Domain Members

    Installed Roles:
    Distributed File System
    DFS Namespaces (zero Namespaces configured - Data Collection only)
    DFS Replication

    *** Update - 05/28/2012 ***

    It appears to be the Removable Media Bit causing all the trouble.  Look at the following eSATA vs. USB3 comparison.  Keep in mind this is the exact same server, drive, and enclosure, only the cable changed.

    eSATA
    Caption : WDC WD10 01FALS-00J7B1
    Description : Disk drive DeviceID : \\.\PHYSICALDRIVE5
    InterfaceType : IDE
    MediaType : Fixed hard disk media
    Model : WDC WD10 01FALS-00J7B1
    Name : \\.\PHYSICALDRIVE5
    Path : \\(Server Name Edited)\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE5"

    USB3
    Caption       : WDC WD10 01FALS-00J7B1 USB Device
    Description   : Disk drive
    DeviceID      : \\.\PHYSICALDRIVE5
    InterfaceType : USB
    MediaType     : External hard disk media
    Model         : WDC WD10 01FALS-00J7B1 USB Device
    Name          : \\.\PHYSICALDRIVE5
    Path          : \\(Server Name Edited)\root\cimv2:Win32_DiskDrive.DeviceID=\\\\.\\PHYSICALDRIVE5

    Error Details:
    20120523 15:07:17.635  664 DOWN  4186 [ERROR] DownstreamTransport::EstablishSession Failed on connId:{28C6E444-3D4E-4149-A819-94A8205B6BF0} csId:{05A08C97-411B-4DD9-B4E5-FB4596D85B7D} rgName:OneLastTime Error:
    + [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 664 C A failure was reported by the remote partner]
    + [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 664 C The content set was not found]
    20120523 15:07:17.635  664 INCO  7487 InConnection::RestartSession Retrying establish contentset session. connId:{28C6E444-3D4E-4149-A819-94A8205B6BF0} csId:{05A08C97-411B-4DD9-B4E5-FB4596D85B7D} csName:DFS
    20120523 15:07:17.635  664 INCO  1042 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
    + [Error:9027(0x2343) InConnection::EstablishSession inconnection.cpp:6172 664 C A failure was reported by the remote partner]
    + [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4200 664 C A failure was reported by the remote partner]
    + [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 664 C A failure was reported by the remote partner]
    + [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 664 C The content set was not found]

    Conclusion???:
    DFS will not replicate to a USB attached drive/enclosure/array.  It’s a shame to have to use the 3Gb eSATA interface just because DFS will not target the 5Gb USB3 interface.

    Any thoughts or suggestions would be greatly appreciated.






    • Edited by Clint-5150 Monday, May 28, 2012 5:50 PM
    •  
     

All Replies

  • Thursday, May 24, 2012 1:37 PM
     
     
    Sign In to Vote
    0
    It is probably not supported, since the IOPS from a USB connected disk will be very less. There will be performance issues when multiple users will access the data simultaneously

    Thanks and Regards, Mukesh. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • Thursday, May 24, 2012 2:18 PM
     
     
    Sign In to Vote
    0

    Mukesh,

    First, thanx for the reply!  Second, I should have made it clear, no users are connecting to any of the replicated data, there are zero Namespaces configured, this is being used for data collection only.

    Also, you get greater IOPs with USB3 (5Gb) than you do with SATA II (3Gb).  The server we have does not have an eSATA III (6Gb) port, only eSATA II.

    More importantly, the error is "The content set was not found", which to me makes no sense.  All the same equipment, same configuration, just a different cable is all it takes to make DFS stop working.
     
    And yes, we’ve tried different cables.Thanx again for the reply!

    Cheers,
    Clint



    • Edited by Clint-5150 Thursday, May 24, 2012 2:20 PM
    •