Hi,

I am surprise with error code 1 is coming while hitting q eve * * when i checked on log it says command failed to run, at the same time when i checked actlog it shows backup is completed. I am assuming not sure 100% on this it is due to hot fix issue i read somewhere in one article. pls find the details below give me few tip to overcome from this issue if any applicable.

Actlog details:-07/28/2016 19:22:23  ANR2507I Schedule DC_BKP for domain VM_DOM started at
                      07/28/2016 18:00:00 for node DC completed successfully at
                      07/28/2016 19:22:23. (SESSION: 3686)

q eve * * status:- 07/28/2016 18:00:00  07/28/2016 18:00:43  DC_BKP        DC            Failed  1

Dsmsched_dc:-

07/28/2016 18:00:46
Executing scheduled command now.
07/28/2016 18:00:48 Node Name: DC
07/28/2016 18:00:48 Session established with server ITSM01: Windows
07/28/2016 18:00:48   Server Version 5, Release 5, Level 6.100
07/28/2016 18:00:48   Server date/time: 07/28/2016 18:00:48  Last access: 07/28/2016 18:00:43

07/28/2016 18:00:48
Executing Operating System command or script:
   E:\VCB\Scripts\dc.cmd
07/28/2016 18:01:06 Finished command.  Return code is: 1
07/28/2016 18:01:06 ANS1909E The scheduled command failed.
07/28/2016 18:01:06 ANS1512E Scheduled event 'DC_BKP' failed.  Return code = 1.
07/28/2016 18:01:06 Sending results for scheduled event 'DC_BKP'.
07/28/2016 18:01:06 Results sent to server for scheduled event 'DC_BKP'.

07/28/2016 18:01:06 TSM Backup-Archive Client Version 6, Release 2, Level 2.2   
07/28/2016 18:01:06 Querying server for next scheduled event.
07/28/2016 18:01:06 Node Name: DC
07/28/2016 18:01:06 Session established with server ITSM01: Windows
07/28/2016 18:01:06   Server Version 5, Release 5, Level 6.100
07/28/2016 18:01:06   Server date/time: 07/28/2016 18:01:06  Last access: 07/28/2016 18:00:48

07/28/2016 18:01:06 --- SCHEDULEREC QUERY BEGIN
07/28/2016 18:01:06 --- SCHEDULEREC QUERY END
07/28/2016 18:01:06 Next operation scheduled:
07/28/2016 18:01:06 ------------------------------------------------------------
07/28/2016 18:01:06 Schedule Name:         DC_BKP
07/28/2016 18:01:06 Action:                Command
07/28/2016 18:01:06 Objects:               E:\VCB\Scripts\dc.cmd
07/28/2016 18:01:06 Options:               
07/28/2016 18:01:06 Server Window Start:   18:00:00 on 07/29/2016
07/28/2016 18:01:06 ------------------------------------------------------------
07/28/2016 18:01:06 Schedule will be refreshed in 6 hours.

Regards

Prem

 

 

 

Hi,

Anyone has any cl ue in log it shows it is sucessfully compelted but when i run q eve * * it shows failed 1 error code.07/29/2016 18:00:09
Executing Operating System command or script:
   E:\VCB\Scripts\dc.cmd
07/29/2016 19:18:40 Finished command.  Return code is: 0
07/29/2016 19:18:40 ANS1908I The scheduled command completed successfully.
07/29/2016 19:18:40 Scheduled event 'DC_BKP' completed successfully.

07/29/2016 18:00:00  07/29/2016 18:00:09  DC_BKP        DC            Failed  1

one additional update on this the log file is creating with a different schedule note which i created recently and till now no backup has been initiated for that schedule.

log file name-dsmsched_esso and the schedule is failing of dc.

pls advice everyday that message is coming now.

 

Regards

Prem

Experts,

Waiting for the response I am not able to figure out the solution.

Regards

Prem

Can you list content of the file dc.cmd? The problem is that this file exits with errorlevel 1 after running.

Hi Espen,

It is not a file level backup it's picking the full vm image backup for pemission prospective i checked everything seems to be fine. additionally backup is coming in my local drive. but status is not updating. one more thing today i executed one command details below.

upd sched vm_dom dc_bkp objects=E:\VCB\Scripts\dc.cmd after running this today all the previous backup event output in not showing . you can see here 6 PM schedule entry is missing of all previous backup which was failed or sucessful.

tsm: ITSM01>q eve * * begind=-5

Scheduled Start      Actual Start         Schedule Name Node Name     Status
-------------------- -------------------- ------------- ------------- ---------
07/27/2016 04:30:00  07/27/2016 04:30:07  SENDMAILCFG   SENDMAILCFG   Completed
07/27/2016 05:00:00  07/27/2016 05:11:07  TSM_E_MOVETO- VCMS-TSM      Completed
                                           _TAPE
07/27/2016 09:30:00  07/27/2016 09:31:31  TSM_VCB_F_DR- VCMS-TSM      Completed
                                           IVE_TOTAPE
07/27/2016 13:00:00  07/27/2016 13:06:10  TSM_VCB_G_DR- VCMS-TSM      Completed
                                           IVE
07/27/2016 16:00:00  07/27/2016 16:00:06  SQLDB         SQLDB         Completed
07/27/2016 16:00:00  07/27/2016 16:00:08  TSM_DEL_SCRI- VCMS-TSM      Failed  2
                                           PTS
07/27/2016 17:30:00  07/27/2016 17:31:51  TSM_DELSQL_S- VCMS-TSM      Completed
                                           CRIPTS
07/27/2016 19:30:00  07/27/2016 19:32:18  ADC_BKP_DLY   ADC           Completed
07/27/2016 22:00:00  07/27/2016 22:14:00  BIS_VM        BIS           Completed

 

 

Regards

Prem

07/28/2016 18:01:06 ------------------------------------------------------------
07/28/2016 18:01:06 Schedule Name:         DC_BKP
07/28/2016 18:01:06 Action:                Command
07/28/2016 18:01:06 Objects:               E:\VCB\Scripts\dc.cmd
07/28/2016 18:01:06 Options:               
07/28/2016 18:01:06 Server Window Start:   18:00:00 on 07/29/2016
07/28/2016 18:01:06 ------------------------------------------------------------

 

This is a command schedule (Action: Command). At the specified time (18:00) the node executes the script file dc.cmd. So to know what is done in the script file and why it fails, you have to go throug the content of dc.cmd.

 

Some times the problem is that TSM scheduler service is running in local system user context, and some permissions is missing. In that case, it will run successfully when you manually executes dc.com, but not when scheduled.

Look at your actlog and query for this schedule. Review what the error condition reports there, this is possibly an issue with the tcpserveraddress, tcpclientaddress or the client tcpport defined in your dsm.sys file.

From: Espen Wallin [mailto:storage-ti@lists.imwuc.org]
Sent: Monday, August 01, 2016 7:44 AM
To: storage-ti@lists.imwuc.org
Subject: [storage-ti] - RE: Error Code 1 while running schedule through command


07/28/2016 18:01:06 ------------------------------------------------------------
07/28/2016 18:01:06 Schedule Name: DC_BKP
07/28/2016 18:01:06 Action: Command
07/28/2016 18:01:06 Objects: E:\VCB\Scripts\dc.cmd
07/28/2016 18:01:06 Options:
07/28/2016 18:01:06 Server Window Start: 18:00:00 on 07/29/2016
07/28/2016 18:01:06 ------------------------------------------------------------



This is a command schedule (Action: Command). At the specified time (18:00) the node executes the script file dc.cmd. So to know what is done in the script file and why it fails, you have to go throug the content of dc.cmd.



Some times the problem is that TSM scheduler service is running in local system user context, and some permissions is missing. In that case, it will run successfully when you manually executes dc.com, but not when scheduled.

-----End Original Message-----
[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com

Brenda,

Appreciate your response I checked the actlog in actlog also it is showing completing sucessfully. I am attaching the reponse below for your reference.

Actlog-

08/01/2016 19:20:58  ANR2507I Schedule DC_BKP for domain VM_DOM started at
                      08/01/2016 18:00:00 for node DC completed successfully at
                      08/01/2016 19:20:58. (SESSION: 4192)
08/01/2016 19:20:58  ANR2576W An attempt was made to update an event record for
                      a scheduled operation which has already been executed for
                      node DC. (SESSION: 4192)
08/01/2016 19:20:58  ANR0403I Session 4192 ended for node DC (WinNT). (SESSION:
                      4192)
08/01/2016 19:20:58  ANR0406I Session 4199 started for node DC (WinNT) (Tcp/Ip
                      VCMS-TSM.viomnetworks.com(60022)). (SESSION: 4199)
08/01/2016 19:20:58  ANR0403I Session 4199 ended for node DC (WinNT). (SESSION:
                      4199)

dsmsched:-

08/01/2016 12:00:50 Schedule will be refreshed in 6 hours.
08/01/2016 18:00:50 TSM Backup-Archive Client Version 6, Release 2, Level 2.2   
08/01/2016 18:00:50 Querying server for next scheduled event.
08/01/2016 18:00:50 Node Name: DC
08/01/2016 18:00:50 Session established with server ITSM01: Windows
08/01/2016 18:00:50   Server Version 5, Release 5, Level 6.100
08/01/2016 18:00:50   Server date/time: 08/01/2016 18:00:50  Last access: 08/01/2016 13:19:12

08/01/2016 18:00:50 --- SCHEDULEREC QUERY BEGIN
08/01/2016 18:00:50 --- SCHEDULEREC QUERY END
08/01/2016 18:00:50 Next operation scheduled:
08/01/2016 18:00:50 ------------------------------------------------------------
08/01/2016 18:00:50 Schedule Name:         DC_BKP
08/01/2016 18:00:50 Action:                Command
08/01/2016 18:00:50 Objects:               E:\VCB\Scripts\dc.cmd
08/01/2016 18:00:50 Options:               
08/01/2016 18:00:50 Server Window Start:   18:00:00 on 08/01/2016
08/01/2016 18:00:50 ------------------------------------------------------------
08/01/2016 18:00:50
Executing scheduled command now.
08/01/2016 18:00:52
Executing Operating System command or script:
   E:\VCB\Scripts\dc.cmd
08/01/2016 19:20:58 Finished command.  Return code is: 0
08/01/2016 19:20:58 ANS1908I The scheduled command completed successfully.
08/01/2016 19:20:58 Scheduled event 'DC_BKP' completed successfully.
08/01/2016 19:20:58 Sending results for scheduled event 'DC_BKP'.
08/01/2016 19:20:58 Results sent to server for scheduled event 'DC_BKP'.

dc.opt file content:-

nodename dc
PASSWORDACCESS    GENERATE
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
EXCLUDE.BACKUP "*:\...\EA DATA. SF"
EXCLUDE.BACKUP "*:\IBMBIO.COM"
EXCLUDE.BACKUP "*:\IBMDOS.COM"
EXCLUDE.BACKUP "*:\IO.SYS"
EXCLUDE.BACKUP "*:\...\system32\config\...\*"
EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
EXCLUDE.ARCHIVE "*:\IO.SYS"
EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
EXCLUDE.DIR "*:\System Volume Information"
EXCLUDE.DIR "*:\...\Temporary Internet Files"
EXCLUDE.DIR "*:\Recycled"
EXCLUDE.DIR "*:\Recycler"
EXCLUDE.DIR "*:\$Recycle.Bin"
TCPSERVERADDRESS    10.50.59.73

 

additionally I have a doubt the file name which is creating dsmsched_esso under bacclient I am guessing that should not be the name of this file it should be dsmsched_dc recenty i have created one schedule that's name is ESSO I am guessing that could be the reason.

q sched f=d output

 Policy Domain Name: VM_DOM
              Schedule Name: DC_BKP
                Description: Daily Image Level backup for DC
                     Action: Command
                    Options:
                    Objects: E:\VCB\Scripts\dc.cmd
                   Priority: 5
            Start Date/Time: 01/11/2011 18:00:00
                   Duration: 10 Minute(s)
             Schedule Style: Classic
                     Period: 1 Day(s)
                Day of Week: Any
e...   (<ENTER> to continue, 'C' to cancel)

                      Month:
               Day of Month:
              Week of Month:
                 Expiration:
Last Update by (administrator): PREM
      Last Update Date/Time: 08/01/2016 10:38:51
           Managing profile:

 

Regards

Prem

 

 

Hi Espen/Brenda,

Thanks after detail research of log I am able to manage and kill the issue this is happening becuase of node password is not autheticating although this is a surprise mystery for me how node password is expired and changed. I am the one who is handling this anyways thank you both of you for all your effort and support.

08/03/2016 18:00:00  08/03/2016 18:04:33  DC_BKP        DC            Completed

 

Regards

Prem

Espen,

Thank you very much for your continuous response I am pasting the content just removing the admin password from the content.

Content of dc.cmd:-

c:
cd \
cd Program Files (x86)
cd VMware
cd VMware Consolidated Backup Framework

vcbMounter.exe -h 10.50.59.73 -u admin -p xyzabcd -a ipaddr:10.50.58.51 -t fullvm -r g:\VCB\dc -m san

additionally at the time of schedule on g drive as written above in script dc folder is creating and backup file is coming tha't why I am confused why it is showing this error.

Regards

Prem