Filespace shows wrong "Last Backup Completion Date/Time"

blankgap

ADSM.ORG Member
Joined
Jun 5, 2018
Messages
64
Reaction score
2
Points
0
PREDATAR Control23

Hi folks,

on one of my TSM Backup-Servers, there is one certain filespace from another Backup-Server whos Backup Completion Date/Time is not beeing updated:

Backup-Server (lets call it SERVER1) runs TSM v 8.1.5., the Node (called SERVER2) runs TSM 7.1.9



Protect: SERVER1>q fi SERVER2 f=d

Node Name: SERVER2
Filespace Name: \\server2\c$
Hexadecimal Filespace Name: 5c5c75676c626b7030315c6324
FSID: 2
Collocation Group Name: ALL-WINDOWS
Platform: WinNT
Filespace Type: NTFS
Is Filespace Unicode?: Yes
Capacity: 136 GB
Pct Util: 91.7
Last Backup Start Date/Time: 12/20/2018 07:25:15
Days Since Last Backup Started: <1
Last Backup Completion Date/Time: 11/17/2018 04:03:44



Please notice the last Backup START Date is 12/20/2018 and the Backup Completion Date 11/17/2018 while the Backup completed successfully:

Protect: SERVER1>q ev * * node=SERVER2

Scheduled Start Actual Start Schedule Name Node Name Status
-------------------- ------------- ----------- ---------- --------
12/20/2018 02:00:00 12/20/2018 03:13:11 TSM_SERVER SERVER2 Completed




Does anyone have an explanation for this?

Thanks!


EDIT: Format of the eventlog query is bit missed up, but I think you'll get the point.
 
PREDATAR Control23

One possibility is that this filespace is not processed by that backup schedule.
Are there any objects specified on the schedule?
Does the domain statement in the option file include C: or all-local?
In the dsmsched.log, does it show that C: was backed up successfully?
 
PREDATAR Control23

Hi Marclant,

thank you for your quick reply.

There are no objects specified:
But I do have a PRESCHEDULECMD for malware scanning. But this has been running flawless for months on multiple servers.

Policy Domain Name: LAG
Schedule Name: TSM_SERVER
Description:
Action: Incremental
Subaction:
Options:
Objects:
Priority: 5
Start Date/Time: 04/13/2015 02:00:00
Duration: 1 Hour(s)
Maximum Run Time (Minutes): 0
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expiration:
Last Update by (administrator): SYSADLH
Last Update Date/Time: 03/09/2016 15:34:14

Managing profile:

Domain statement:
domain C: systemstate

Sched_log:
12/21/2018 04:12:27 ANS1802E Incremental backup of '\\server2\c$' finished with 1 failure(s)

The error in the TSM error_log:
12/21/2018 03:10:44 ANS1751E Error processing '\\server2\c$\$recycle.bin\s-1-5-21-886401270-2187314956-1048491642-3023\$r63putn': The file system can not be accessed.

So this error should not be the reason not to update the backup completion date, right?
 
PREDATAR Control23

What's the schedule completion code? If it's 12, then yes. I suspect it's 12 given that error.
 
PREDATAR Control23

Scheduler completed with RC 4 - The operation completed successfully, but some files were not processed.
 
Top