TDP TSMPIPE error

2004-01-26 Thread Subbu, Mohan (OFT) 
Hi,

I have a problem with the TDP.

I can connect to the tsm server using the tdp gui and able to see the
storage groups.but if I start the backup by selecting the storage groups
I get an communication rejection error.

Following is the error in the TDPdsmerror.log

01/24/2004 03:52:32 sessOpen: Failure in communications open call. rc:
-190
01/24/2004 03:52:32 ANS1029E Communications have been dropped.
01/24/2004 04:12:32 NpOpen: Named pipe error connecting to server
INVALID HANDLE.
NpOpen: call failed with return code:2 pipe name \\.\PIPE\TSMPIPE
01/24/2004 04:12:32 sessOpen: Failure in communications open call. rc:
-190
01/24/2004 04:12:32 ANS1029E Communications have been dropped.

No changes were made to the dsm.opt file and they r configured correctly
Iam able to telnet to port 1500 of the tsm server.Also Iam able to do
the backup using the tsm backup archive client in the same box.But not
able to do backup with the tdp.

Thanks,

Mohan

Re: TSM Connectivity issue

2004-01-15 Thread Subbu, Mohan (OFT) 
Telnet did not give a connection to the server on 1500 port. this brings
to the source of the problem.
I have another client with the same issue.It is also in the same
network.


Thank you!

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
French, Michael
Sent: Thursday, January 15, 2004 3:55 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM Connectivity issue

Stupid question, but from the command line can you telnet to the
TSM server port?

Ex:
telnet 10.70.113.60 1500

If you get a black screen, you've got connectivity.  Otherwise,
something is block access at the network layer.

Michael French
Savvis Communications
IDS01 Santa Clara, CA
(408)450-7812 -- desk
(408)239-9913 -- mobile
 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Subbu, Mohan (OFT)
Sent: Thursday, January 15, 2004 12:49 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM Connectivity issue


Paul,

I have restarted the scheduler service and also tried to connect with
the GUI and command line..I get the follwing message

tsm> q session
Node Name: EXCNYSM0A1AB
ANS1017E Session rejected: TCP/IP connection failure


Also there is no entry for any error at the TSM server activity log
except for the last night missed backup

01/15/04 03:00:01 ANR2578W Schedule EXCHANGE_01AM in domain EXCHANGE
for
   node EXCNYSM0A1AB has missed its scheduled start
up  
   window.


So could there be any issue with the tcp ip port configuration?Also both
the TSM client and TSM server are in different network each. 

Thanks,

Mohan


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bergh, Paul
Sent: Thursday, January 15, 2004 2:17 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM Connectivity issue

Mohan,

since your lan is up, because of the ping, you don't have a lan
connection problem. This error can occur if the lan connection went down
OR if someone canceled a backup operation.

try stopping and restarting the scheduler on the client machine.

I assume the client is still register to tsm, and is associated with a
schedule.

Let me know what's up after you complete these actions.

Paul

"Subbu, Mohan (OFT)" wrote:

> One of my tsm client(10.66.81.67) is able to ping the tsm 
> server(10.70.113.60).But Iit is not able to connect with the TSM 
> server using the TSM BA GUI.Till yesterday it was working fine.
> My dsm.opt file is configured correctly and no configurations were 
> changed.
> I have the follwing errors in my tsm schedule log.
> What could be the problem?
>
> 01/15/2004 11:21:37 Querying server for next scheduled event. 
> 01/15/2004 11:21:37 Node Name: OWANYSM0A1AB 01/15/2004 11:22:19 
> ANS1017E Session rejected: TCP/IP connection failure
> 01/15/2004 11:22:19 Will attempt to get schedule from server again in 
> 10 minutes.
> 01/15/2004 11:32:19 Querying server for next scheduled event.
> 01/15/2004 11:32:19 Node Name: OWANYSM0A1AB
> 01/15/2004 11:33:01 ANS1017E Session rejected: TCP/IP connection 
> failure
> 01/15/2004 11:33:01 Will attempt to get schedule from server again in 
> 10 minutes.
>
> Thanks,
>
> Mohan

Re: TSM Connectivity issue

2004-01-15 Thread Subbu, Mohan (OFT) 
Paul,

I have restarted the scheduler service and also tried to connect with
the GUI and command line..I get the follwing message

tsm> q session
Node Name: EXCNYSM0A1AB
ANS1017E Session rejected: TCP/IP connection failure


Also there is no entry for any error at the TSM server activity log
except for the last night missed backup

01/15/04 03:00:01 ANR2578W Schedule EXCHANGE_01AM in domain EXCHANGE
for
   node EXCNYSM0A1AB has missed its scheduled start
up  
   window.


So could there be any issue with the tcp ip port configuration?Also both
the TSM client and TSM server are in different network each. 

Thanks,

Mohan


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bergh, Paul
Sent: Thursday, January 15, 2004 2:17 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM Connectivity issue

Mohan,

since your lan is up, because of the ping, you don't have a lan
connection problem.
This error can occur if the lan connection went down OR if someone
canceled a backup operation.

try stopping and restarting the scheduler on the client machine.

I assume the client is still register to tsm, and is associated with a
schedule.

Let me know what's up after you complete these actions.

Paul

"Subbu, Mohan (OFT)" wrote:

> One of my tsm client(10.66.81.67) is able to ping the tsm 
> server(10.70.113.60).But Iit is not able to connect with the TSM 
> server using the TSM BA GUI.Till yesterday it was working fine.
> My dsm.opt file is configured correctly and no configurations were 
> changed.
> I have the follwing errors in my tsm schedule log.
> What could be the problem?
>
> 01/15/2004 11:21:37 Querying server for next scheduled event.
> 01/15/2004 11:21:37 Node Name: OWANYSM0A1AB
> 01/15/2004 11:22:19 ANS1017E Session rejected: TCP/IP connection 
> failure
> 01/15/2004 11:22:19 Will attempt to get schedule from server again in 
> 10 minutes.
> 01/15/2004 11:32:19 Querying server for next scheduled event.
> 01/15/2004 11:32:19 Node Name: OWANYSM0A1AB
> 01/15/2004 11:33:01 ANS1017E Session rejected: TCP/IP connection 
> failure
> 01/15/2004 11:33:01 Will attempt to get schedule from server again in 
> 10 minutes.
>
> Thanks,
>
> Mohan

TSM Connectivity issue

2004-01-15 Thread Subbu, Mohan (OFT) 
One of my tsm client(10.66.81.67) is able to ping the tsm
server(10.70.113.60).But Iit is not able to connect with the TSM server
using the TSM BA GUI.Till yesterday it was working fine.
My dsm.opt file is configured correctly and no configurations were
changed.
I have the follwing errors in my tsm schedule log.
What could be the problem?


01/15/2004 11:21:37 Querying server for next scheduled event.
01/15/2004 11:21:37 Node Name: OWANYSM0A1AB
01/15/2004 11:22:19 ANS1017E Session rejected: TCP/IP connection failure
01/15/2004 11:22:19 Will attempt to get schedule from server again in 10
minutes.
01/15/2004 11:32:19 Querying server for next scheduled event.
01/15/2004 11:32:19 Node Name: OWANYSM0A1AB
01/15/2004 11:33:01 ANS1017E Session rejected: TCP/IP connection failure
01/15/2004 11:33:01 Will attempt to get schedule from server again in 10
minutes.

Thanks,

Mohan

Re: TDP for exchange error rc=610

2004-01-06 Thread Subbu, Mohan (OFT) 
Uninstalling and installing both Backup Archive client and TDP solved
the problem.

Thanks Del! 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Tuesday, January 06, 2004 5:09 PM
To: [EMAIL PROTECTED]
Subject: Re: TDP for exchange error rc=610

Mohan,

Try reinstalling the TSM API Runtime feature from the Version 5.1.5 (or
later) TSM Backup Archive client package. If it still fails,
uninstall... then reinstall the TSM Backup Archive client and the Data
Protection for Exchange client.

Thanks,

Del



> Following is the TDP Schedule log file.
> We are taking a full backup of the exchange database using TDP.
> You can see that the TDP full backup was successful yesterday.But 
> today it got failed.There was no change done to the configuration.It 
> is a daily scheduled job which failed today with the error mentioned 
> at the end of the log.
>
> I get an API intialisation error when I try to bring the TDP for 
> exchange GUI to do manual backup, after the schedule backup failed 
> with error.
> I then did a uninstallation and then again a fresh installation of TDP

> for Exchange.Then I tried to bring up the TDP for exchange GUI.b..but 
> I failed.

TDP for exchange error rc=610

2004-01-06 Thread Subbu, Mohan (OFT) 
Following is the TDP Schedule log file.
We are taking a full backup of the exchange database using TDP.
You can see that the TDP full backup was successful yesterday.But today
it got failed.There was no change done to the configuration.It is a
daily scheduled job which failed today with the error mentioned at the
end of the log.

I get an API intialisation error when I try to bring the TDP for
exchange GUI to do manual backup, after the schedule backup failed with
error.
I then did a uninstallation and then again a fresh installation of TDP
for Exchange.Then I tried to bring up the TDP for exchange GUI.b..but I
failed.

Help me make this node backup again.

Thanks,
Mohan

Copy and paste of the TDP for exchange log file:

Current date is: 
Mon 01/05/2004 
Current time is: 
01:47 AM

IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 5, Release 2, Level 1.0
(C) Copyright IBM Corporation 1998, 2003. All rights reserved.

ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\exchsch.log log
file has been pruned successfully.

Starting storage group backup...

Beginning full backup of SG1, 1 of 3.
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec 
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec 
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec 
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec 
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec 
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec 
Full: 3   Read: 3145728  Written: 0  Rate: 0.00 Kb/Sec  Waiting for
TSM
server..
..
Full: 3   Read: 4194304  Written: 1048576  Rate: 8.09 Kb/Sec 
Full: 3   Read: 13631488  Written: 10485760  Rate: 80.24 Kb/Sec 
Full: 3   Read: 23068672  Written: 19922944  Rate: 151.27 Kb/Sec 
Full: 3   Read: 32505856  Written: 29360128  Rate: 221.21 Kb/Sec 
Full: 3   Read: 41943040  Written: 38797312  Rate: 290.08 Kb/Sec 
Full: 3   Read: 48234496  Written: 45088768  Rate: 334.55 Kb/Sec 
Full: 3   Read: 49283072  Written: 46137344  Rate: 339.75 Kb/Sec 
Full: 3   Read: 58720256  Written: 55574528  Rate: 406.18 Kb/Sec 
Full: 3   Read: 68157440  Written: 65011712  Rate: 471.63 Kb/Sec 
Full: 3   Read: 78643200  Written: 75497472  Rate: 543.66 Kb/Sec 
Full: 3   Read: 85983232  Written: 82837504  Rate: 592.15 Kb/Sec 
Full: 3   Read: 91226112  Written: 88080384  Rate: 625.05 Kb/Sec 
Full: 3   Read: 101711872  Written: 98566144  Rate: 694.42 Kb/Sec 
Full: 3   Read: 109051904  Written: 105906176  Rate: 740.79 Kb/Sec 
Full: 3   Read: 118489088  Written: 115343360  Rate: 801.06 Kb/Sec 
Full: 3   Read: 128974848  Written: 125829120  Rate: 867.71 Kb/Sec 
Full: 3   Read: 139460608  Written: 136314880  Rate: 933.43 Kb/Sec 
Full: 3   Read: 148897792  Written: 145752064  Rate: 991.10 Kb/Sec 
Full: 3   Read: 159383552  Written: 156237824  Rate: 1,055.06 Kb/Sec

Full: 3   Read: 169869312  Written: 166723584  Rate: 1,118.13 Kb/Sec

Full: 3   Read: 180355072  Written: 177209344  Rate: 1,180.35 Kb/Sec

Full: 3   Read: 190840832  Written: 187695104  Rate: 1,241.73 Kb/Sec

Full: 3   Read: 201326592  Written: 198180864  Rate: 1,302.27 Kb/Sec

Full: 3   Read: 211812352  Written: 20824  Rate: 1,362.01 Kb/Sec

Full: 3   Read: 98112  Written: 219152384  Rate: 1,420.96 Kb/Sec

Full: 3   Read: 232783872  Written: 229638144  Rate: 1,479.12 Kb/Sec

Full: 3   Read: 242221056  Written: 239075328  Rate: 1,529.82 Kb/Sec

Full: 3   Read: 252706816  Written: 249561088  Rate: 1,586.52 Kb/Sec

Full: 3   Read: 263192576  Written: 260046848  Rate: 1,642.49 Kb/Sec

Full: 3   Read: 273678336  Written: 270532608  Rate: 1,697.74 Kb/Sec

Full: 3   Read: 282066944  Written: 278921216  Rate: 1,739.21 Kb/Sec

Full: 3   Read: 292552704  Written: 289406976  Rate: 1,793.14 Kb/Sec

Full: 3   Read: 300941312  Written: 297795584  Rate: 1,833.48 Kb/Sec

Full: 3   Read: 311427072  Written: 308281344  Rate: 1,886.15 Kb/Sec

Full: 3   Read: 320864256  Written: 317718528  Rate: 1,931.79 Kb/Sec

Full: 3   Read: 331350016  Written: 328204288  Rate: 1,983.19 Kb/Sec

Full: 3   Read: 341835776  Written: 338690048  Rate: 2,033.97 Kb/Sec

Full: 3   Read: 352321536  Written: 349175808  Rate: 2,084.12 Kb/Sec

Full: 3   Read: 362807296  Written: 359661568  Rate: 2,133.67 Kb/Sec

Full: 3   Read: 373293056  Written: 370147328  Rate: 2,182.62 Kb/Sec

Full: 3   Read: 382730240  Written: 379584512  Rate: 2,224.83 Kb/Sec

Full: 3   Read: 393216000  Written: 390070272  Rate: 2,272.65 Kb/Sec

Full: 3   Read: 403701760  Written: 400556032  Rate: 2,319.90 Kb/Sec

Full: 3   Read: 414187520  Written: 411041792  Rate: 2,366.60 Kb/Sec

Full: 3   Read: 424673280  Written: 421527552  Rate: 2,412.74 Kb/Sec

Full: 3   Read: 435159040  Written: 432013312  Rate: 2,458.35 Kb/Sec

Full: 3   Read: 444596224  Written: 441450496  Rate: 2,497.50 Kb