BUG REPORT: Backup jobs are hanging on Windows 2003 clients when the Volume Shadow Copy Service (VSS) is disabled in Windows. VSP is still enabled for the client's backups, though vsp.sys is not installed or running.

Which points to possible 'issues' with VSS

Or the following:
BUG REPORT: VSS Writers is providing a "/" to NetBackup causing bpbkar to provide an "Application Pop Up Error"
which again indicates VSS issues.

Maybe give you something to investigate further.

I'll try..

thanks Andy

I have read some files that the C++ must be installed and the shadow copy service should be manual  none of these solved.

wierd

I have updated Windows (the server that do not want to be saved hehe)
I have updated the netbackup environmet,
6.5.4  master (solaris 10)
6.5.4 client (windows 2003 server as a WTS thinclient server)

The instalation was made w/ an ISO from ms official site.

VERY wierd

Hi,

 While reviewing the bpbkar logs i found following error; this error shows that bpbkar process is terminated due to some TCP failure. If i am not wrong u was trying to backup system state / Os. 

02:55:16.585 PM: [4852.6036] <16> dtcp_write: TCP - failure: send socket (1856) (TCP 10053: Software caused connection abort)

this error shows that bpbkar process is terminated due to some TCP failure. 

What Microsoft say about it:

This error message can occur under any of the following circumstances:

• The external Internet Protocol (IP) address is resolved by internal clients. This can occur if Windows Internet Naming Service (WINS) name resolution is used and the external network adapter has registered itself instead of the internal network adapter.
• The client's IP address is not contained within the Local Address Table (LAT).
• The Internet publishing server (destination server) is on a Microsoft Proxy server as well as the client that is trying to reach this server. This can occur if the Proxy server containing the publishing server does not have the Publishing option enabled. This option is disabled by default.

Note that "10053" is a generic WinSock error code that may be displayed for other reasons than those listed in this article.

To resolve the issue, use the appropriate method:

• Delete the IP address entry that corresponds to the the Proxy server's external adapter, disable WINS support on the external adapter, and then reboot the server. To unbind the WINS client (TCP/IP) interface:
  1. In Control Panel, double-click Network.
  2. Click the Bindings tab.
  3. In the Show Bindings For box, click All Adapters.
  4. Expand all of the adapters.
  5. Click WINS Client (TCP/IP), and then click Disable.

  For additional information, please refer to the WINS documentation. 
   

• Add the IP address of the client receiving the error message to the LAT table on the Proxy server:
  1. Start the Internet Service Manager tool.
  2. Right-click Web Proxy, and then click Properties.
  3. Click Local Address Table.
  4. Add the appropriate range that contains the IP address of the client.
  5. Click OK.
  6. Click OK.
• Test from the Proxy server itself or another from another client that is not behind a Proxy server to determine whether it is able to connect. If not, contact the administrator of the Publishing server and ask to have the Publishing option enabled on the Proxy server, which will allow incoming requests on port 80.

Here is Microsoft reference for this http://support.microsoft.com/kb/204594, I hope this will lead toward resolution.

Regards,

Taqauds. 

Thanks Taqadus, I'll try these. WINS..

-----------------------------
Andy, I'll reinstal the server w/ the same media in another server to see if the problem is the ISO that I downloaded from MS.

By the way, the restore gone fine - the HCART one that U helped me.. thanks again Andy.

nothing works

I really don't understand..

wierd

any other Idea?

our environmet is

Master/media     SUN v490                      solaris 10                            nb 6.5.4 
client                            HP                   windows 2003 server        nb 6.5.4 client

I have updated everything.

So  it happens everyday

Now We R having these problem in both TS servers.

I have installed another server, w/ the same Midia, everything is the same (this two servers were used to Load balance so hardware is almost equal)

the network is OK,

there is some issues about an N LITE  ISO instalation, and aboute vss.sys I have made every single test that is here (this topic)

Any other Idea?