Results 1 to 3 of 3

Thread: The specified network name is no longer available.

  1. #1

    Default The specified network name is no longer available.

    Pretty consistently within 1-3 gigs of a 140 gig backup the ZWC throws this error in the log and stops responding to the server. The server waits for 1 hour (dtimeout) before it gives up on the ZWC. Has anyone seen this and have any ideas how to fix this?

    Log snippet:

    224:2448:1/3/2011:14:50:614::ZWCBackup: Elapsed Time: 00:04:36 : Files Backed up: 608 : Backup Size: 1372 MB
    224:2448:1/3/2011:14:50:614::FS: NTFS: ReadStreams: Reading header of file \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy24\A pps\Development\VirtualBox-3.0.4-50677-OSX.dmg
    224:2448:1/3/2011:14:50:614::FS:NTFS:Read Streams:Opening file for reading \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy24\A pps\Development\VirtualBox-3.0.4-50677-OSX.dmg
    224:2448:1/3/2011:14:50:614::FS: NTFS: ReadStreams: Done reading metadata stream 3
    224:2448:1/3/2011:14:50:614::FS: NTFS: ReadStreams: Opening file \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy24\A pps\Development\VirtualBox-3.0.4-50677-OSX.dmg
    224:2068:1/3/2011:14:50:614::FS: NTFS: FindNextFile: Entering FindNext
    224:2068:1/3/2011:14:50:614::FS: NTFS: FindNextFile: Leaving FindNext
    224:2072:1/3/2011:14:51:99::Got error while reading from socket
    224:2072:1/3/2011:14:51:99::ZWC Failure error code: 64
    224:2072:1/3/2011:14:51:99::RemoveStaleClient : Last error code is 64
    224:2072:1/3/2011:14:51:99::The specified network name is no longer available.

    224:2072:1/3/2011:14:51:99::Communication Layer : Connection closed by server.
    224:2072:1/3/2011:14:51:99::CServiceSessionMgr : Cancelling the command
    224:2072:1/3/2011:14:51:99::CServiceSessionMgr : Cancelling the command
    224:2072:1/3/2011:14:51:99::CServiceSessionMgr : Cancelling the command
    224:1816:1/3/2011:14:51:99:224:3036:1/3/2011:14:51:99::Error in sending the data
    224:1816::1/3/2011:14:51:99::CZWCJobHandler : WriteFile failed while writing data to the pipe
    224:3036Error in sending the data
    :1/3/2011:14:51:99::CZWCJobHandler:: GetLastError = 232
    224:3036:1/3/2011:14:51:99::CZWCJobHandler : WriteFile failed while writing data info to the pipe
    224:3036:1/3/2011:14:51:99::CZWCJobHandler:: GetLastError = 232
    224:3036:1/3/2011:14:51:99::CZWCJobHandler : WriteFile failed while writing data to the pipe
    224:3036:1/3/2011:14:51:99::CZWCJobHandler:: GetLastError = 232
    224:3036:1/3/2011:14:51:99::CZWCJobHandler : WriteFile failed while writing data info to the pipe
    224:3036:1/3/2011:14:51:99::CZWCJobHandler:: GetLastError = 232
    224:3036:1/3/2011:14:51:99::CZWCJobHandler : WriteFile failed while writing data to the pipe
    224:3036:1/3/2011:14:51:99::224:2072:CZWCJobHandler:: GetLastError = 232
    1/3/2011:14:51:99::224CServiceSessionMgr : Invalid session in response
    :3036:1/3/2011:14:51:99::CZWCJobHandler : Failed writing data to the pipe after 3 retries

  2. #2
    Join Date
    Jul 2011
    Posts
    6

    Default

    Hi,

    I'm also having a similar problem. I use Amanda on 2 sites. I have a backup server at each site running Ubuntu 11.04 and Amanda 3.3, and back up Windows Server 2003 machines using the windows client.

    I regularly get the following errors at both sites which result in a failed backup:-

    8036:336:4/12/2011:01:25:137::Got error while reading from socket
    8036:336:4/12/2011:01:25:137::ZWC Failure error code: 64
    8036:336:4/12/2011:01:25:137::RemoveStaleClient : Last error code is 64
    8036:336:4/12/2011:01:25:137::The specified network name is no longer available.

    I'd really like to get to the bottom of these - Is it worth considering an alternative to the Windows client eg Samba? I can't see that this is a network issue as it's occurring on 2 different sites, so I'm guessing it's a bug in the client?

    I've invested a fair amount of time understanding Amanda, so don't want to move to something more reliable unless I absolutely have to - Would be great to hear from others with a similar issue.

    Rob

  3. #3
    Join Date
    Jul 2011
    Posts
    6

    Default

    Quote Originally Posted by robrauy View Post
    Hi,

    I'm also having a similar problem. I use Amanda on 2 sites. I have a backup server at each site running Ubuntu 11.04 and Amanda 3.3, and back up Windows Server 2003 machines using the windows client.

    I regularly get the following errors at both sites which result in a failed backup:-

    8036:336:4/12/2011:01:25:137::Got error while reading from socket
    8036:336:4/12/2011:01:25:137::ZWC Failure error code: 64
    8036:336:4/12/2011:01:25:137::RemoveStaleClient : Last error code is 64
    8036:336:4/12/2011:01:25:137::The specified network name is no longer available.

    I'd really like to get to the bottom of these - Is it worth considering an alternative to the Windows client eg Samba? I can't see that this is a network issue as it's occurring on 2 different sites, so I'm guessing it's a bug in the client?

    I've invested a fair amount of time understanding Amanda, so don't want to move to something more reliable unless I absolutely have to - Would be great to hear from others with a similar issue.

    Rob
    Just in case anyone else is having this problem, this fixed it for me..

    [url]http://wiki.zmanda.com/index.php/Mesg_read:_Connection_reset_by_peer[/url]

    Rob

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •