backup of cluster blocked

[pferreir]

Hi,
I'm trying to backup a cluster under TSM Client (5.3.4.0). when I start an INCR backup, the backup is blocked after 5, 10 or more minutes.

I do not have any messages in TSM Server (5.4.3.0) or in TSM Client and the session is still in TSM.

some one has an idea ?

 

[nezih]

what q sess says?
if there is no messages on server or client how can you know it's blocked?

 

[pferreir]

Hi,

Q Sess is in "Wait Status" and nothing more happens. To test backups I send them by command line and and nothing is moving more when the backup is blocked.

 

[nezih]

send us Q SESS F=D

 

[pferreir]

here is :

Sess Number: 2,386,027
Comm. Method: Tcp/Ip
Sess State: RecvW
Wait Time: 4.5 M
Bytes Sent: 273.4 M
Bytes Recvd: 113.5 M
Sess Type: Node
Platform: WinNT
Client Name: GRC-FS.SPI.SER.COM
Media Access Status:
User Name:
Date/Time First Data Sent: 11/22/07 11:55:25
Proxy By Storage Agent:


Sess Number: 2,386,030
Comm. Method: Tcp/Ip
Sess State: IdleW
Wait Time: 44.6 M
Bytes Sent: 340
Bytes Recvd: 289
Sess Type: Node
Platform: WinNT
Client Name: GRC-FS.SPI.SER.COM
Media Access Status:
User Name:
Date/Time First Data Sent:
Proxy By Storage Agent:

 

[nezih]

session state is receive wait which means tsm server waiting for client sends the data, if this is the first backup of node, tsm client sends the directory tree to the tsm database and after that starts the send files to the target storage pool, I recommend wait for a while...

 

[JohanW]

It may take hours.

I have one server where I set up journaling, because just the directory tree going from the server to the client was more than a GB, and the backup wouldn't start for something like 6 hours. This went on day after day, not just the initial incremental.

 

[pferreir]

Hello,
thanks for this, what I do not understand is :

The backup starts and it stops in randoom, sometimes after 1GB backuped, sometimes after 2Gb.

When your backup is in wait status, did it backup something ?
Regards,
Paulo

 

[nezih]

if session in idlew state it means client opens a session and do nothing. check the tsm server documentation for session states and meanings.

 

[pferreir]

the backup is running since yerterday afternoon, it started backuping. after 9 Gb of backup TSM is waitting for TSM client ... here are some print screens .

on TSM server when it was running normally :
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name
Number Method State Time Sent Recvd Type
------- ------ ------ ------ ------- ------- ----- -------- -------------------
2,692,624 Tcp/Ip RecvW 0 S 273.5 M 3.7 G Node WinNT GRC-FS.SPRI.SERONO.COM

on TSM client :
Normal File--> 1,075,533 \\grc-fs\f$\users\cemaux\perso\raq....
Normal File--> 1,086,803 \\grc-fs\f$\users\cemaux\perso\raq....
Normal File--> 1,032,595 \\grc-fs\f$\users\cemaux\perso\raq....
Normal File--> 1,083,977 \\grc-fs\f$\users\cemaux\perso\raq....
Normal File--> 982,360 \\grc-fs\f$\users\cemaux\perso\raq....
Normal File--> 807,273 \\grc-fs\f$\users\cemaux\perso\raq....
Normal File--> 877,890 \\grc-fs\f$\users\cemaux\perso\raq....
< 9.19 GB> [ -]


Now the back is not any more in TSM ... that's normal after so much hours of inactivity ....

some ideas ????