Jump to content

thubbardphysactg.com

Members
  • Content count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thubbardphysactg.com

  • Rank
    Newbie
  1. thubbardphysactg.com

    Exchange Full Backup Errors

    First, download from Microsoft Exchange Best Practices Analyzer for the exchange version you have. This will help confirm your exchange install doesn't have any major problems. I am thinking along the lines of your AD domain Microsoft exchange Security Groups or services/Microsoft Exchange/CN=domain.biz may be missing something. If the analyzer finds nothing, I have other ideas.
  2. thubbardphysactg.com

    Windows 2008 Server x64

    We have had daily -519, -530 and -541 problems all resulting on no backups. We were using a server with 4 nics, each with it's own ip address on a single subnet. The following appears to have resolved most if not all of this running EMC Retrospect on a Windows 2008 server. If your server has more than 1 nic per sub-net, try the following on the server. Network settings, Internet Protocol Version 4(TCP/IPv4, advanced tab, on interface 1 usually where the default gateway is set, uncheck automatic metric and set it to 10. Set the metric on interface 2 to 20, metric to 30 on interface 3, metric to 40 on interface 4 etc. This will cause windows to route any traffic not bound to a specific interface to the interface with the lowest metric. When multiple network interfaces operate on the same sub-net using the default metric of 10, windows can route upd or tcp traffic onto any of the 4 interfaces. This I believe is how clients hear the server communicating on more than 1 interface which leads the client to spawn a second listener thread. Once that has happened, -519, -530 and -541 errors until the client is restarted. No guarantee on this but I would be interested on feedback on this issue. It has been a major problem here. This appears to have helped in resolving client connection link lost, disconnection, client not found, etc. issues. I'm not absolutely convinced this is the FIX, but try it and let me know. I haven't seen a -519, -530, -541 error in over 10 days since I implemented this on our server. If it helps everyone, then I will believe it is fixed. Feedback welcome.
  3. thubbardphysactg.com

    Retrospect client consuming all available memory?

    The server is Windows 2008, Retrospect server version is 7.6.2.101. The client is all our Linux Red Hat servers. Linux 2.6.18 Kernel for Red Hat 4 and 5, both 32 and 64 bit Dell 1950 and 2950 servers. Esx VMWare 3.5 and and Overland Storage snap server all exhibit this behavior. The events for the retrospect client are logged at the rate of up 10 12 per minute 24/7 when backups are running or when backups are idle. The client version is 7.6.107. This event generates a tremendous volume of entries in the log of all these clients. We are having to do scheduled restarts of these clients to prevent the server memory from being exhausted.
  4. I have observed retroclient having an issue with memory consumption until all available memory is used resulting in a file server hanging requiring a hard reset. Is this a known issue with a resolution? ATTENTION:File service was denied for a connection request from MEMORY subsystem because your system is running at capacity. Please disconnect redundant connections. Please also contact tech support to learn how to upgrade your system smbd 10/16 7:51:30 AM I ATTENTION:File service was denied for a connection request from SWAP subsystem because your system is running at capacity. Please disconnect redundant connections. Please also contact tech support to learn how to upgrade your system smbd 10/16 7:51:30 AM W last message repeated 12 times 10/16 7:51:23 AM W last message repeated 14 times 10/16 7:50:28 AM W last message repeated 12 times 10/16 7:49:23 AM W last message repeated 14 times 10/16 7:46:24 AM W last message repeated 13 times 10/16 7:45:20 AM W last message repeated 14 times 10/16 7:42:17 AM W last message repeated 13 times 10/16 7:41:12 AM W last message repeated 14 times 10/16 7:38:09 AM W last message repeated 13 times 10/16 7:37:05 AM W last message repeated 14 times 10/16 7:34:01 AM W last message repeated 13 times 10/16 7:32:57 AM W last message repeated 14 times 10/16 6:49:22 AM W last message repeated 12 times 10/16 6:48:17 AM W last message repeated 13 times 10/16 6:45:18 AM W last message repeated 12 times 10/16 6:44:17 AM W last message repeated 14 times 10/16 6:41:14 AM W last message repeated 12 times 10/16 6:40:09 AM W last message repeated 14 times 10/16 6:37:09 AM W last message repeated 13 times 10/16 6:36:05 AM W last message repeated 13 times 10/16 6:33:02 AM W ServicePurge: service not found Retrospect[3307] 10/16 6:32:01 AM W ServicePurge: service not found Retrospect[3307] 10/16 5:49:16 AM W connTcpConnection: invalid code found: 145 Retrospect[3307] 10/16 5:49:16 AM W ServicePurge: service not found Retrospect[3307] 10/16 5:49:12 AM W connTcpConnection: invalid code found: 145 Retrospect[3307] 10/16 5:49:12 AM
  5. thubbardphysactg.com

    Lets talk modern hardware performance

    We are trying to run retrospect. We also run BackupExec. Typically Retrospect backup throughput is 1/3 of BackupExec running on similarly configured hardware. I all due respect though, I have never tried to dial in retrospect. I use default settings for windows and linux systems for both backup products.
  6. thubbardphysactg.com

    error -530

    We have had daily -519, -530 and -541 problems all resulting on no backups. We were using a server with 4 nics, each with it's own ip address on a single subnet. The following appears to have resolved most if not all of this running EMC Retrospect on a Windows 2008 server. If your server has more than 1 nic per sub-net, try the following on the server. Network settings, Internet Protocol Version 4(TCP/IPv4, advanced tab, on interface 1 usually where the default gateway is set, uncheck automatic metric and set it to 10. Set the metric on interface 2 to 20, metric to 30 on interface 3, metric to 40 on interface 4 etc. This will cause windows to route any traffic not bound to a specific interface to the interface with the lowest metric. When multiple network interfaces operate on the same sub-net using the default metric of 10, windows can route upd or tcp traffic onto any of the 4 interfaces. This I believe is how clients hear the server communicating on more than 1 interface which leads the client to spawn a second listener thread. Once that has happened, -519, -530 and -541 errors until the client is restarted. No guarantee on this but I would be interested on feedback on this issue. It has been a major problem here. This appears to have helped in resolving client connection link lost, disconnection, client not found, etc. issues. I'm not absolutely convinced this is the FIX, but try it and let me know. I haven't seen a -519, -530, -541 error in over 10 days since I implemented this on our server. If it helps everyone, then I will believe it is fixed. Feedback welcome.
  7. We have had daily -519, -530 and -541 problems all resulting on no backups. We were using a server with 4 nics, each with it's own ip address on a single subnet. The following appears to have resolved most if not all of this running EMC Retrospect on a Windows 2008 server. If your server has more than 1 nic per sub-net, try the following on the server. Network settings, Internet Protocol Version 4(TCP/IPv4, advanced tab, on interface 1 usually where the default gateway is set, uncheck automatic metric and set it to 10. Set the metric on interface 2 to 20, metric to 30 on interface 3, metric to 40 on interface 4 etc. This will cause windows to route any traffic not bound to a specific interface to the interface with the lowest metric. When multiple network interfaces operate on the same sub-net using the default metric of 10, windows can route upd or tcp traffic onto any of the 4 interfaces. This I believe is how clients hear the server communicating on more than 1 interface which leads the client to spawn a second listener thread. Once that has happened, -519, -530 and -541 errors until the client is restarted. No guarantee on this but I would be interested on feedback on this issue. It has been a major problem here. This appears to have helped in resolving client connection link lost, disconnection, client not found, etc. issues. I'm not absolutely convinced this is the FIX, but try it and let me know. I haven't seen a -519, -530, -541 error in over 10 days since I implemented this on our server. If it helps everyone, then I will believe it is fixed. Feedback welcome.
  8. thubbardphysactg.com

    Listening but not working

    We have had daily -519, -530 and -541 problems all resulting on no backups. We were using a server with 4 nics, each with it's own ip address on a single subnet. The following appears to have resolved most if not all of this running EMC Retrospect on a Windows 2008 server. If your server has more than 1 nic per sub-net, try the following on the server. Network settings, Internet Protocol Version 4(TCP/IPv4, advanced tab, on interface 1 usually where the default gateway is set, uncheck automatic metric and set it to 10. Set the metric on interface 2 to 20, metric to 30 on interface 3, metric to 40 on interface 4 etc. This will cause windows to route any traffic not bound to a specific interface to the interface with the lowest metric. When multiple network interfaces operate on the same sub-net using the default metric of 10, windows can route upd or tcp traffic onto any of the 4 interfaces. This I believe is how clients hear the server communicating on more than 1 interface which leads the client to spawn a second listener thread. Once that has happened, -519, -530 and -541 errors until the client is restarted. No guarantee on this but I would be interested on feedback on this issue. It has been a major problem here. This appears to have helped in resolving client connection link lost, disconnection, client not found, etc. issues. I'm not absolutely convinced this is the FIX, but try it and let me know. I haven't seen a -519, -530, -541 error in over 10 days since I implemented this on our server. If it helps everyone, then I will believe it is fixed. Feedback welcome.
  9. thubbardphysactg.com

    Exchange Mailbox Backup - Fail.

    I have exchange 2007 backing up datastores and mailboxes. If you can provide me some more detail I will try to point you to the resources I used. The exchange tools have to be installed on the retrospect server. I disabled ipv6on the exchange server. This may not have been necessary. There are permissions applied through the exchange management shell that apply to the service account used to connect to exchange. Get through all this and it should work.
×