none
Cluster Node with Physical iSCSI port: ID 52 Details: The semaphore timeout period has expired (0x80070079) RRS feed

  • Question

  • I have a 2 node File server cluster. Both are Hyper-Vs but they have physial iSCSI connections to the "SAN"

    I'm running DPM 2010

    When trying to complete my initial recovery point of 2TB (direct to tape for now) I get the following error:

    Type:	Tape backup 
    Status:	Failed
    Description:	The DPM service was unable to communicate with the protection agent on Clust-01.Domain.com. (ID 52 Details: The semaphore timeout period has expired (0x80070079))
    	More information
    End time:	08/07/2011 11:39:23 AM
    Start time:	08/07/2011 8:35:26 AM
    Time elapsed:	03:03:57
    Data transferred:	468,350.56 MB
    Cluster node	Clust-01.Domain.com
    Source details:	E:\
    Protection group members:	39
    	Details
    Protection group:	Default Group: File and Print
    Library:	IBM TotalStorage 3576 Modular Tape Library
    Tape Label (Barcode):	Default Group: File and Print-00000013 (BDN097)
    Default Group: File and Print-00000012 (BDN042)
    
    

    Friday, July 8, 2011 5:34 PM

All replies

  • Hi,

    Try this workaround, increase the TcpMaxDataRetransmissions to 10 or more.

    How to modify the TCP/IP maximum retransmission timeout
    http://support.microsoft.com/kb/170359

     


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, July 8, 2011 5:53 PM
    Moderator
  • When DPM does a full backup to tape will it use its local copy of the data, if it has it on disk? Could my issue simply be a interoperability issue with my Library? If I do a full backup of my original server to tape then free up the disk and give it to my new fileserver do you think that will make a diference?

     

    I back up a lot of data and this is the only server that fails. The only difference is its pushing its short term backup to tape...thoughts?


    Monday, July 11, 2011 7:16 PM
  • So I freed up my disk and I'm now trying to copy to the SAN. Same issue though.
    Wednesday, July 13, 2011 11:07 PM
  • Try to update network card drivers.
    Thursday, August 30, 2012 12:03 PM