Connection to DS-System drops

[Samuel]

We've setup a new 2008 Server for data vaulting and set up DS-User on the system. When we run a "Repair DS-Client Database" activity it fails. It looses it's connection with DS-System. We have attempted it many times, but it's always the same. It only goes for about 2 1/2 minutes and in the even log it says "Software caused connection to abort".

Has anyone had similar trouble or trouble staying connected to the DS-System?

[jay]

Samuel

May have seen that one in the past... Have a few ideas of things I would try but a few questions first.

1.When you kick off the “repair” do you see a entry in the ds-operator? Curious if it ever establishes a connection.
2. I am assuming you reset the hardware and "registered" the ds-client with the ds-system and ran the repair in in a short window? I believe within 10 minutes of a hardware reset.
3. Does the ds-client service stay up after it aborts?
4. Is the ds-client the same version of the ds-client as the ds-client db that you are trying to repair?
5. Are you using the same database for the ds-client?

[Samuel]

Thanks for your reply. I unregistered and re-registered the DS Client and reset hardware. I can see it come up in DS Operator. After I did the re-register and launched another DB Repair it went for over 10 minutes this time before it dropped. I was running SysInternals Process Monitor at the time, and those monitor logs reveal nothing but successful operations. DS Client stays up after the abort. We are repairing the database because this is a new computer we sent to the client site, and we're setting it up remotely to continue where the old server left off.

We have virtually never seen this issue. What we're thinking at this point is that it is a network problem and not an Asigra oriented problem. I will post a resolution if that is the case.

[jay]

Samuel

If it is the network a internal test of restoring the DB should help prove against that. I am curious to see if that is the issue. Any type of antivirus software/windows firewall etc... on the new server that could interfear with the transmission? Also you may want to check the ds-system logs to verify the daily/weekly admins for this account had been successful. If there were errors I am sure it could throw some unusual errors when trying to repair.

Did the original machine have a older version of SQL perhaps?

Curious to see the the end solution... Best of luck with it.

-Jay

[Samuel]

We're not out of the woods yet. My department manager is working with our Network Operations team, and they're telling us that can't trace the problem to the network. Our team however is not ruling it out. It's not just the one client location where there are problems. There are four locations, all in the same region. This is why we are pointing to the network. But passing the buck can lead to embarrassment when it turns out to be your problem after-all...

The main problem client is where we are trying to repair the database on a new Windows 2008 Server (the others are normal backup scenarios). We are trying to determine if there are some security features of 2008 that could be causing the problem. If you get the properties dialog for DS-User, there is a "Run as Administrator" checkbox. We had high hopes as we checked that box and tried the repair again. But, no luck. It failed again.

When we go into the logs the most info we get is the message "Software closed the connection." This is very ambiguous and we are dying to get some detail on that, but there is none. What software? DS-User? Windows 2008? A firewall? This is my next line of investigation.

I'm not familiar with 2008 Server yet. I'll look through other posts here, but if anybody knows about 2008 Server security interactions with Asigra, that may be very helpful.

Samuel

[Samuel]

We think we have resolution from the Network Operations team after all. It was a third party we work with. Apparently a switch on their side was "port flapping". Things are supposed to be cleared up over the weekend as they reset the device.