Previous session running for more than 5 days

[tmlsuresh]

Hi All,

I have a TDP backup running for more than 5 days.

I have cancelled the session, immediately a new session starts running.
If i can cancel the new session , but still a new session starting.

When checking the activity log i could see the files are backed up to server all the time 24X7 for five days.

Can anyone help me in resolving the issue.

 

[GregE]

What TDP is this? MS SQL, Oracle, Domino?
Is the backup scheduled from the TSM server scheduler? or a non-TSM scheduler?

 

[tmlsuresh]

Hi GregE,

Its Domino, It is scheduled from TSM server scheduler.

 

[tariq.kaifi]

Show us the schedule status then.

 

[tmlsuresh]

Hi Tariq,

Here is the input for your reference,

tsm: ADSM>q schedule * usubnsh01_tdp_* f=d
Policy Domain Name: NT_BACKUP
Schedule Name: USUBNSH01_TDP_DAILYBACKUP
Description: Backup of Notes Server H01
Action: Command
Options:
Objects: c:\domarc.cmd
Priority: 5
Start Date/Time: 10/05/02 20:30:00
Duration: 1 Hour(s)
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Last Update by (administrator): DEM2084
Last Update Date/Time: 10/21/02 10:56:42
Managing profile:

tsm: ADSM>



tsm: ADSM>q fi usubnsh01_tdp f=d
Node Name: USUBNSH01_TDP
Filespace Name: USUBNSH01.DOMDBS
Hexadecimal Filespace Name:
FSID: 1
Platform: WinNT
Filespace Type: APIominoData
Is Filespace Unicode?: No
Capacity (MB): 0.0
Pct Util: 0.0
Last Backup Start Date/Time: 09/09/11 20:35:14
Days Since Last Backup Started: 20
Last Backup Completion Date/Time: 09/09/11 07:19:57
Days Since Last Backup Completed: 20
Last Full NAS Image Backup Completion Date/Time:
Days Since Last Full NAS Image Backup Completed:




tsm: ADSM>q session
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name
Number Method State Time Sent Recvd Type
------- ------ ------ ------ ------- ------- ----- -------- -------------------
506,832 Tcp/Ip Run 0 S 76.2 M 141 Admin AIX RLP5365
611,068 Tcp/Ip Run 0 S 11.7 K 7.1 G Node TDP Dom- USUBNSH01_TDP
ino
683,985 Tcp/Ip RecvW 1 S 3.9 K 2.7 G Node TDP Dom- USUBNSH01_TDP
ino




tsm: ADSM>q session 611068 f=d
Sess Number: 611,068
Comm. Method: Tcp/Ip
Sess State: Run
Wait Time: 0 S
Bytes Sent: 11.7 K
Bytes Recvd: 7.1 G
Sess Type: Node
Platform: TDP Domino
Client Name: USUBNSH01_TDP
Media Access Status:
User Name:
Date/Time First Data Sent: 09/16/11 15:55:01
Proxy By Storage Agent:

tsm: ADSM>q session 683985 f=d
Sess Number: 683,985
Comm. Method: Tcp/Ip
Sess State: RecvW
Wait Time: 1 S
Bytes Sent: 3.9 K
Bytes Recvd: 2.7 G
Sess Type: Node
Platform: TDP Domino
Client Name: USUBNSH01_TDP
Media Access Status:
User Name:
Date/Time First Data Sent: 09/29/11 08:15:02
Proxy By Storage Agent:

tsm: ADSM>



tsm: ADSM>q node usubnsh01_tdp f=d
Node Name: USUBNSH01_TDP
Platform: WinNT
Client OS Level: 4.00
Client Version: Version 5, release 1, level 7.0
Policy Domain Name: NT_BACKUP
Last Access Date/Time: 09/29/11 20:31:08
Days Since Last Access: <1
Password Set Date/Time: 08/12/11 20:30:59
Days Since Password Set: 48
Invalid Sign-on Count: 0
Locked?: No
Contact: Don Mosher or Bill Kmak,computer.operations@if-
f.com,Ops,3
Compression: Client
Archive Delete Allowed?: Yes
Backup Delete Allowed?: No
Registration Date/Time: 09/24/02 14:31:14
Registering Administrator: DEM2084
Last Communication Method Used: Tcp/Ip
Bytes Received Last Session: 9,132.62 M
Bytes Sent Last Session: 15,229
Duration of Last Session: 194,686.23
more... (<ENTER> to continue, 'C' to cancel)
Pct. Idle Wait Last Session: 0.01
Pct. Comm. Wait Last Session: 99.80
Pct. Media Wait Last Session: 0.00
Optionset:
URL: http://client.host.name:1581
Node Type: Client
Password Expiration Period:
Keep Mount Point?: No
Maximum Mount Points Allowed: 0
Auto Filespace Rename : No
Validate Protocol: No
TCP/IP Name: USUBNSH01
TCP/IP Address: 10.11.93.80
Globally Unique ID:
Transaction Group Max: 0
Data Write Path: ANY
Data Read Path: ANY
Session Initiation: ClientOrServer
High-level Address:
Low-level Address:
Collocation Group Name:
Proxynode Target:
Proxynode Agent:
more... (<ENTER> to continue, 'C' to cancel)
Node Groups:
Email Address:

 

[tariq.kaifi]

Session number 611068 has started on 16-Sep and still running!! Network issue? Data transfer speed?

Run one backup in foreground from the TDP and see how it goes.

How many session it opens up when backup starts? When you say cancel the session, you cancelling only one session or more?

Just also paste the output of below (if you are keeping the events history for 10 days) :

"query event NT_BACKUP USUBNSH01_TDP_DAILYBACKUP begind=-10 endd=-0 node=USUBNSH01_TDP"

I see your platform is "WinNT" in your node's definition, it should have been TDP I believe. Did you run normal dsmc using that opt file for some reason before posting?

 

[tmlsuresh]

Hi Tariq,

I have started a new backup session in foreground using the command "domdsmc incremental * /subdir=yes /adsmoptfile=dsm.opt /logfile=domasch.log>>domarc1.log"

The bcakup session is running for nore than 5 hours, i will let you know the result.

There is only one session started, when i started the backup.

Here is the output of the command you requested

tsm: ADSM>q event * usubnsh01_tdp_dailybackup begindate=-10 enddate=today node=u
subnsh01_tdp

Scheduled Start Actual Start Schedule Name Node Name Status
-------------------- -------------------- ------------- ------------- ---------
09/20/11 20:30:00 09/20/11 20:32:05 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/21/11 20:30:00 09/21/11 20:32:05 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/22/11 20:30:00 09/22/11 20:38:05 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/23/11 20:30:00 09/23/11 20:37:07 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/24/11 20:30:00 09/24/11 20:41:07 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/25/11 20:30:00 09/25/11 20:30:07 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/26/11 20:30:00 09/26/11 20:31:07 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
more... (<ENTER> to continue, 'C' to cancel)

UP
09/27/11 20:30:00 09/27/11 20:30:07 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/28/11 20:30:00 09/28/11 20:36:08 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/29/11 20:30:00 09/29/11 20:31:08 USUBNSH01_TD- USUBNSH01_TDP Failed 1
P_DAILYBACK-
UP
09/30/11 20:30:00 USUBNSH01_TD- USUBNSH01_TDP Future
P_DAILYBACK-
UP

tsm: ADSM>

I am not clear about you requirement in the last question " Did you normal dsm using that opt file for some reason before postin?"

What option file you are mentioning here " TSM Opt file or TDp opt file"?

And do you want me run TSM Backup incr using the TDP option file ?

Awaiting response.

 

[tariq.kaifi]

How much the data its backing up since its running for 5 hours? What is the data transfer speed are you getting?

I meant TSM opt file only because I noticed platform as WinNT in your node definition. It should be TDP Domino if you connect to this node using TDP. Maybe it’s due to scheduler service. That’s ok. Just verify you have correct TDP opt file pointing to it.

And no, it’s not required to run TSM incremental backup using TDP option file.

Do you see anything in TSM server actlog when backup fails with RC=1?

Did it ever run fine? If yes, since when it started failing? Any recent changes you aware of?

I am not much familiar with TDP domino, but still would like to see the cmd file - c:\domarc.cmd.

Also, show us the entries in TDP log files. By the way, why two files - "/logfile=domasch.log>>domarc1.log"? One should be fine.

I know too many questions, but all requires answer to help you if we can.

 

[tmlsuresh]

It backed up 5 GB data for the whole day and it is still running

No I don’t have any entry for the the RC=1

I have joined to this environment recently not aware of any changes, I need to check with my onsite counter-part.


When I cancel all the active session, it starts the two sessions immediately.

The Schedmode option is set as polling .

 

[tariq.kaifi]

Could you post the content of below files?

TDP opt file
c:\domarc.cmd
domasch.log
domarc1.log

5 GB in a day! Looks quite slow. How is the throughput of other nodes in the same network?