Windows Tivoli backups failing

T

tsmhelum

Active Newcomer
Joined
Aug 24, 2006
Messages
450
Reaction score
0
Points
0
Hi all,

For the past couple of day's an abnormal number of Windows Clients have been failing with the following error. I have noticed there all windows 2003 clients with TSM client 5.5. Also, this error seemed to start to occur around the time we recently upgraded TSM Server to 5.5.2.

Has anyone experienced this type of error? I was thinking VSS but I don't know why out of nowhere this would occur on a bunch of clients a once.

Can anyone think of what might be the cause?

01/12/2009 00:11:13 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/13/2009 00:10:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896708239
01/13/2009 00:13:48 ANS1327W The snapshot operation for 'SNJCUS\SystemState\NULL\System State\SystemState' failed with error code: 51.
01/13/2009 00:13:48 ANS1228E Sending of object 'SNJCUS\SystemState\NULL\System State\SystemState' failed
01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use

01/13/2009 00:13:48 ANS1375E The snapshot operation failed.

01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use

01/13/2009 00:13:48 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.

09/2009 07:58:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/09/2009 07:58:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/12/2009 00:18:08 ANS1327W The snapshot operation for 'ADABAS1\SystemState\NULL\System State\SystemState' failed with error code: 51.
01/12/2009 00:18:08 ANS1228E Sending of object 'ADABAS1\SystemState\NULL\System State\SystemState' failed
01/12/2009 00:18:08 ANS1351E Session rejected: All server sessions are currently in use

01/12/2009 00:18:08 ANS1375E The snapshot operation failed.



01/11/2009 00:47:20 ANS1327W The snapshot operation for 'SIFT22\SystemState\NULL\System State\SystemState' failed with error code: 51.
01/11/2009 00:47:20 ANS1228E Sending of object 'SIFT22\SystemState\NULL\System State\SystemState' failed
01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use

01/11/2009 00:47:20 ANS1375E The snapshot operation failed.

01/11/2009 00:47:20 ANS1351E Session rejected: All server sessions are currently in use

01/11/2009 00:47:20 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.



01/12/2009 00:23:03 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/13/2009 00:19:07 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-896738674
01/13/2009 00:20:27 ANS1327W The snapshot operation for 'SNC700\SystemState\NULL\System State\SystemState' failed with error code: 51.
01/13/2009 00:20:27 ANS1228E Sending of object 'SNC700\SystemState\NULL\System State\SystemState' failed
01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use

01/13/2009 00:20:27 ANS1375E The snapshot operation failed.

01/13/2009 00:20:27 ANS1351E Session rejected: All server sessions are currently in use

01/13/2009 00:20:27 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/14/2009 00:20:45 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-897022474
 
Increase max sessions on TSM server. Also look to as what might have changed if was working with current number of sessions before.


01/13/2009 00:13:48 ANS1351E Session rejected: All server sessions are currently in use
 
Thanks DJ,

I think it does have to do with what changed because these failures just started out of the blue. The only thing that has changed is the upgrade to TSM 5.5.2 but the errors are not occuring on all clients. I am going to have to look further
 
Thats because some clients are able to actually establish sessions. Are some nodes getting errors every single time and others none at all?
 
Thanks DJ,

Yes, some nodes are getting errors every single time and others not at all and some get them one every other day or every two days. We are still getting errors We have just upgraded some of our clients to 5.1.10 (the latest client I believe)

ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/21/2009 00:32:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.


01/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/22/2009 00:32:33 ANS1351E Session rejected: All server sessions are currently in use
01/22/2009 00:52:35 ANS1351E Session rejected: All server sessions are currently in use

01/21/2009 01:32:49 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/21/2009 01:32:49 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/22/2009 01:52:59 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/22/2009 01:52:59 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.

DisableScheds No
MaxSessions 75
Maximum Sessions 75 Maximum Scheduled Sessions 75


We have the set maximum schedule sessions allowed = 100

Again this is happening on mostly Windows 2003 clients SP2 and sometimes SP1
 
this error:

Removing previous incomplete group '\System State\0\SystemState

is, afaik a vss/windows error - you should use google ;-) this problem is a tsm 5.5.xx problem
 
Toxy13 thanks,

I only updated the Set maximum schedule sessions allowed Maximum percent 100.
Also, I ran 4 manual Incremental Backups this morning and all were successful except 1

Which received the following error

1/23/2009 09:16:05 ANS2054E Operating system error 13: ????????d.
01/23/2009 09:16:05 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Unable to lock local repository
TSM return code : 101
TSM file : vssback.cpp (6353)
01/23/2009 09:16:05 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Verifying Local Backups Failed!
TSM return code : 101
TSM file : vssback.cpp (5725)
01/23/2009 09:16:13 ANS2054E Operating system error 13: ????????d.
01/23/2009 09:16:13 ANS5250E An unexpected error was encountered.
TSM function name : vssCreateDCInLocalAndTsm
TSM function : Failed to lock LSM repository.
TSM return code : 101
TSM file : vssback.cpp (4742)
01/23/2009 09:16:13 ANS5250E An unexpected error was encountered.
TSM function name : baProcessRequest
TSM function : VSS create DCs failed
TSM return code : 101
TSM file : incrdrv.cpp (8190)
01/23/2009 09:16:15 ANS1074W The operation was stopped by the user.

01/23/2009 09:19:25 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-901607868
01/23/2009 09:19:25 ANS2054E Operating system error 13: ????????d.
01/23/2009 09:19:25 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Unable to lock local repository
TSM return code : 101
TSM file : vssback.cpp (6353)
01/23/2009 09:19:25 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Verifying Local Backups Failed!
TSM return code : 101
TSM file : vssback.cpp (5725)
01/23/2009 09:19:30 ANS2054E Operating system error 13: ????????d.
01/23/2009 09:19:30 ANS5250E An unexpected error was encountered.
TSM function name : vssCreateDCInLocalAndTsm
TSM function : Failed to lock LSM repository.
TSM return code : 101
TSM file : vssback.cpp (4742)
01/23/2009 09:19:30 ANS5250E An unexpected error was encountered.
TSM function name : baProcessRequest

Yes, Toxy I have googled this problem but found no clear cut solution, However I will try again. When you say it is a TSM 5.5.xx problem you do mean the client version correct? Or the Server Version? I know we didn’t have this VSS/Windows issue with 5.3 clients as far as I can remember. Is there a way to turn off this VSS for temporary and get a good backup? I think IBM should should just put a fix in for a client that would take care of this issue once and for all.

Right now the main issue is the below error.

01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.

01/23/2009 02:12:47 ANS1351E Session rejected: All server sessions are currently in use
01/23/2009 02:32:47 ANS1351E Session rejected: All server sessions are currently in use
01/23/2009 02:52:53 ANS1351E Session rejected: All server sessions are currently in use



01/22/2009 00:52:36 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/22/2009 00:52:36 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/23/2009 00:12:33 ANS1351E Session rejected: All server sessions are currently in use

Or

01/23/2009 02:52:55 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/23/2009 02:52:55 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.
01/23/2009 07:36:58 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-900146022

01/18/2009 01:16:19 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
01/18/2009 01:16:19 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12.

Thanks again!
 
Hello,

I don't believe I mentioned this


TSM SERVER LOG which is showing the following during midnight backups doesn't cause our Novell/Linux/AIX/solaris clients to fail only WINDOWS clients

XXXX (WinNT) refused -maximum server sessions (75) exceeded.
XXX-XXXXX (WinNT) refused - maximum server sessions (75) exceeded.

(LinuxPPC) refused - maximum server sessions (75) exceeded.
XXXXX (LinuxPPC) refused - maximum server sessions (75) exceeded.

XXXXX (WinNT) refused - maximum server sessions (75) exceeded.
XXXXXX (WinNT) refused - maximum server sessions (75) exceeded.
 
hi tsmhelum,

you're right thats only windows errors :-(
yeah, the "systemstate" error only occurs on 5.5. client version

I think should use the 2 Microsoft Patches (vssrollup package & com+ package) are they installed?
 
The "Removing previous incomplete group '\System State\0\SystemState'" entry you are seeing is not a true "Error", it is rather a statement of fact. When a Windows backup fails, that is using VSS, the next backup attempts to "clean up" the previous failed backup, by removing the "incomplete group".

Not everything reported in TSM is an error.

dennis_in_texas
 
I've exactly the same problems with 'some' windows 2003 (sp1 / sp2) clients where the backups is failing everytime via scheduled jobs. when I run the backup manually it's working without errors.

first I thought also about this systemstate and vss backup errors to disable the systemstate backup for testing porpuses but I still receive the same erros.

dsmerror.log:
Code: 
01/27/2009 00:21:08 ANS1228E Sending of object '\\cceufrts005\c$' failed
01/27/2009 00:21:08 ANS1063E The specified path is not a valid file system or logical volume name.
01/27/2009 00:21:08 ANS1512E Scheduled event 'W2KNIGHTLY' failed. Return code = 12.

dsmsched.log:
Code: 
01/27/2009 00:21:07 --- SCHEDULEREC QUERY BEGIN
01/27/2009 00:21:07 --- SCHEDULEREC QUERY END
01/27/2009 00:21:07 Next operation scheduled:
01/27/2009 00:21:07 ------------------------------------------------------------
01/27/2009 00:21:07 Schedule Name: W2KNIGHTLY
01/27/2009 00:21:07 Action: Incremental
01/27/2009 00:21:07 Objects: 
01/27/2009 00:21:07 Options: 
01/27/2009 00:21:07 Server Window Start: 21:00:00 on 01/26/2009
01/27/2009 00:21:07 ------------------------------------------------------------
01/27/2009 00:21:07 
Executing scheduled command now.
01/27/2009 00:21:07 --- SCHEDULEREC OBJECT BEGIN W2KNIGHTLY 01/26/2009 21:00:00
01/27/2009 00:21:07 Incremental backup of volume '\\cceufrts005\c$'
01/27/2009 00:21:08 ANS1228E Sending of object '\\cceufrts005\c$' failed
01/27/2009 00:21:08 ANS1063E The specified path is not a valid file system or logical volume name.
01/27/2009 00:21:08 --- SCHEDULEREC STATUS BEGIN
01/27/2009 00:21:08 --- SCHEDULEREC OBJECT END W2KNIGHTLY 01/26/2009 21:00:00
01/27/2009 00:21:08 ANS1512E Scheduled event 'W2KNIGHTLY' failed. Return code = 12.
01/27/2009 00:21:08 Sending results for scheduled event 'W2KNIGHTLY'.
01/27/2009 00:21:08 Results sent to server for scheduled event 'W2KNIGHTLY'.

settings on the tsm server:
Maximum Sessions: 100
Maximum Scheduled Sessions: 80

what I find really confusing is that 'ANS1228E' doesn't make sense in my eyes because this are my settings in the dsm.opt:

Code: 
TCPSERVERADDRESS myserver
PASSWORDACCESS GENERATE
 
TCPBUFFSIZE 31
TCPWINDOWSIZE 63
TXNBYTELimit 2097152
TCPNodelay yes
 
DOMAIN C: -SYSTEMSTATE
 
INCLUDE * WINDOWS
DIRMC WINDOWS
 
EXCLUDE.DIR "C:\Windows\Installer"
EXCLUDE.DIR "C:\Windows\$hf*"
EXCLUDE.DIR "C:\Source"
EXCLUDE.DIR "C:\DRV"
EXCLUDE.DIR "C:\ibmtools"
EXCLUDE.DIR "C:\drivers"
EXCLUDE.DIR "C:\Source"

baclient level is 5.5.1.10
tsm server 5.4.3.2
 
You must log in or register to reply here.

Data Privacy Impact Assessment

Compliance Assurance in Every Byte: Discover the Impact of Our DPIA Services.

Sponsor ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

Navigation Menu

Forums
   IBM TSM
   EMC Backup and Recovery
   Symantec NetBackup  
   SAN  
   NAS
   Platforms / OS
Mailing List Archives
   ADSM-L
User Groups

NordVPN 3 Months FREE

Help Support ADSM.ORG and Get NordVPN with 64% Off and 3 Months FREE.

NordVPN with 64% off + 3 months FREE

Forum statistics

Threads
31,982
Messages
135,471
Members
21,953
Latest member
smeegama
Back
Top