IBM Storage Defender

IBM Storage Defender

Early threat detection and secure data recovery

 View Only
Expand all | Collapse all

Weekly Full Backup failing from command

Prem Singh

Prem SinghSun September 11, 2016 11:54 PM

Prem Singh

Prem SinghMon September 12, 2016 10:31 AM

Prem Singh

Prem SinghWed September 14, 2016 10:24 AM

Anthony Whitchurch

Anthony WhitchurchWed September 14, 2016 06:20 PM

  • 1.  Weekly Full Backup failing from command

    Posted Sat September 10, 2016 12:43 PM

    Hi,

    I am facing one issue i have setup a weekly schedule which is failing with error code 1 , not able to understand why it is happening i have 2 different company's setup one is on workgroup where the same script is working perfectly fine. another is on domain where my incremental backup is working fine but my weekly backup is failing with error code 1. I am attaching the snapshot for your reference for better understanding.

    Actlog-

    09/10/2016 16:25:25  ANR2017I Administrator PREM issued command: UPDATE
                          SCHEDULE gendom weekly_full_dsdmawprod1
                          objects=c:\DSDMAWPROD1.cmd starttime=now action=command
                          (SESSION: 31362)
    09/10/2016 16:25:25  ANR2502I Schedule WEEKLY_FULL_DSDMAWPROD1 updated in
                          policy domain GENDOM. (SESSION: 31362)
    09/10/2016 16:25:37  ANR0403I Session 31359 ended for node DSDMAWPROD1
                          (WinNT). (SESSION: 31359)
    more...   ( to continue, 'C' to cancel)

    09/10/2016 16:25:37  ANR0406I Session 31368 started for node DSDMAWPROD1
                          (WinNT) (Tcp/Ip 10.66.250.194(54971)). (SESSION: 31368)
    09/10/2016 16:25:37  ANR0403I Session 31368 ended for node DSDMAWPROD1
                          (WinNT). (SESSION: 31368)
    09/10/2016 16:25:44  ANR0480W Session 31363 for node DSDMAWPROD1 (WinNT)
                          terminated - connection with client severed. (SESSION:
                          31363)

     

    Regards

    Prem

     

     

     

     



  • 2.  RE: Weekly Full Backup failing from command

    Posted Sat September 10, 2016 01:13 PM

    Hi,

    Current new log.

    09/10/2016 12:06:50 Options:               
    09/10/2016 12:06:50 Server Window Start:   16:25:25 on 09/10/2016
    09/10/2016 12:06:50 ------------------------------------------------------------
    09/10/2016 12:06:50 Command will be executed in 1 minute.
    09/10/2016 12:07:50
    Executing scheduled command now.
    09/10/2016 12:07:52 Node Name: DSDMAWPROD1
    09/10/2016 12:07:52 Session established with server DSDBK01: Linux/x86_64
    09/10/2016 12:07:52   Server Version 7, Release 1, Level 1.0
    09/10/2016 12:07:52   Server date/time: 09/10/2016 17:07:52  Last access: 09/10/2016 17:06:50

    09/10/2016 12:07:52
    Executing Operating System command or script:
       c:\DSDMAWPROD1.cmd
    09/10/2016 12:07:52 Finished command.  Return code is: 1
    09/10/2016 12:07:52 ANS1909E The scheduled command failed.
    09/10/2016 12:07:52 ANS1512E Scheduled event 'WEEKLY_FULL_DSDMAWPROD1' failed.  Return code = 1.
    09/10/2016 12:07:52 Sending results for scheduled event 'WEEKLY_FULL_DSDMAWPROD1'.
    09/10/2016 12:07:52 Results sent to server for scheduled event 'WEEKLY_FULL_DSDMAWPROD1'.

    Regards

    Prem



  • 3.  RE: Weekly Full Backup failing from command

    Posted Sun September 11, 2016 11:54 PM

    Hi Guys,

    Any option you can suggest which i can check.

     

    Prem



  • 4.  RE: Weekly Full Backup failing from command

    Posted Mon September 12, 2016 10:31 AM

    Hi,

    I am waiting for your response on it.

     

    Regards

    Prem



  • 5.  RE: Weekly Full Backup failing from command

    Posted Tue September 13, 2016 04:26 AM

    You have to post the content of c:\DSDMAWPROD1.cmd. Return code 1 is because of a failing command in this batch file.



  • 6.  RE: Weekly Full Backup failing from command

    Posted Tue September 13, 2016 04:38 AM

    Espen,

    Thank you so much for the response, I have attached the script already in the first post itself attaching once again

    Regards

    Prem



  • 7.  RE: Weekly Full Backup failing from command

    Posted Wed September 14, 2016 10:24 AM

    Hi,

    waiting for the suggestion.

    Regards

    Prem



  • 8.  RE: Weekly Full Backup failing from command

    Posted Wed September 14, 2016 06:20 PM

    Is the weekly backup running at the same time as the nightly backup?



  • 9.  RE: Weekly Full Backup failing from command

    Posted Thu September 15, 2016 12:08 AM

    Espen,

    I have schedule 2 backup for this node one is incremental which is running in the morning at 7 AM daily and weekly backup run on saturday night 10 PM.

    pls let me know if any other details i need to share.

    Regards

    Prem



  • 10.  RE: Weekly Full Backup failing from command

    Posted Thu September 15, 2016 04:56 PM

    Has the incremental backup completed and stopped before the Weekly backup starts?



  • 11.  RE: Weekly Full Backup failing from command

    Posted Thu September 15, 2016 09:32 PM

    Hi Anthony,

    Thanks for the response, yes it is completed before that. i have no clue why batch file is not executing.

     

    Regards

    Prem



  • 12.  RE: Weekly Full Backup failing from command

    Posted Thu September 15, 2016 09:34 PM

    Do the commands from the batch file work if they are run from a command line on the backup client server?



  • 13.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 12:43 AM

    Hi,

    Pls find the output below which i am getting while executing the batch file from command prompt.

    Output-

    C:\>DSDMAWPROD1
    The process cannot access the file because it is being used by another process.
    The process cannot access the file because it is being used by another process.
    The process cannot access the file because it is being used by another process.
    The process cannot access the file because it is being used by another process.
    The process cannot access the file because it is being used by another process.
    The process cannot access the file because it is being used by another process.
    C:\Program Files\Tivoli\TSM\baclient>

    Although it's not true, becuase when i checked no process is running.

     

    Regards

    Prem



  • 14.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 03:24 AM

    backupfull.log is the problem. You have to delete or rename backupfull.log, and try the batch again.



  • 15.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 04:12 AM

    Espen,

    I have renamed the file backupfull.log under baclient folder. and reschedule the backup for today after 15 minutes lets see how it goes. if any other suggestion pls do let me know.

     

    Regards

    Prem



  • 16.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 04:50 AM

    Espen,

    This time command is executed after changing the log file name but still it's not completed cleanly it throwing error code 4. I am attaching the log also.

    9/16/2016 03:25:08
    Executing Operating System command or script:
       c:\DSDMAWPROD1.cmd
    09/16/2016 03:42:27 Finished command.  Return code is: 4
    09/16/2016 03:42:27 ANS1909E The scheduled command failed.
    09/16/2016 03:42:27 ANS1512E Scheduled event 'WEEKLY_FULL_DSDMAWPROD1' failed.  Return code = 4.
    09/16/2016 03:42:27 Sending results for scheduled event 'WEEKLY_FULL_DSDMAWPROD1'.
    09/16/2016 03:42:27 Results sent to server for scheduled event 'WEEKLY_FULL_DSDMAWPROD1'.

     

    Regards

    Prem



  • 17.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 06:15 AM

    Any errors in backupfull.log?



  • 18.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 06:53 AM

    I could not find any specific error but I am attaching the log file for your reference.

     

    Regards

    Prem



  • 19.  RE: Weekly Full Backup failing from command

    Posted Fri September 16, 2016 07:30 AM

    You get better control if you schedule backup with action=selective (instead of action=command in this case).

     

    Here is return codes from dsmc explained:

    http://www.ibm.com/support/knowledgecenter/SSTG2D_7.1.0/com.ibm.itsm.client.doc/c_sched_rtncode.html

     

    Return code 4 is usually "the object is in use by another process"



  • 20.  RE: Weekly Full Backup failing from command

    Posted Sat September 17, 2016 01:41 AM

    Espen,

    Thanks for the response, but if i will choose selective the problem is client don't know what he requires that's why i have choose whole c drive in selective case i have to give the exact path what i require moreover i won't be able to cover system state backup. which is my prime requirement. if any option is there to choose selective and i can cover server system state backup pls do let me know. I don't want to trigger/schedule the system state backup from server then take it.

     

    Regards

    Prem



  • 21.  RE: Weekly Full Backup failing from command

    Posted Sun September 18, 2016 05:46 PM

    Looking at the log you attavched it would appear that the backup is running. It is failing to backup up 72 objects which are in use by another process. These may be system files or Database files which are locked open by system level accounts. Since a lot of them are in the C$\Winodws\Temp.. folder I would speculate that they are temporary files created by an application which is running.As a suggestion, it may be worth checking with the application owner to see what these files are and whether they need to be backed up.



  • 22.  RE: Weekly Full Backup failing from command

    Posted Sun September 18, 2016 10:12 PM

    Hi Anthony,

    Thanks for the response, is there any option i can exclude specifically these files which is in use.I checked with the concerned person they do not require these files.

     

    Regards

    Prem



  • 23.  RE: Weekly Full Backup failing from command

    Posted Sun September 18, 2016 10:21 PM

    You could add an include/exclude list to the dsm,.opt file for that client.

    Have a look at this knowledge base article for the basics on creating a list.

     

    http://www.ibm.com/support/knowledgecenter/SSTG2D_7.1.0/com.ibm.itsm.client.doc/t_cfg_crtinclexcl.html

     



  • 24.  RE: Weekly Full Backup failing from command

    Posted Mon September 19, 2016 12:04 AM

    Hi Anthony,

    Thank you very much, will try this option and after post changes will share the result.

     

    Regards

    Prem



  • 25.  RE: Weekly Full Backup failing from command

    Posted Wed September 21, 2016 01:56 PM

    This is not the solution i'm replying to you.

    But a suggestion. TSM use progressive backup methodology. It is not needed to take weekly full or monthly full.

    This is needed only by other backup tools. TSM BA Version 6.3 onwards "SYSTEMSTATE BACKUP" is only incremental on daily basis.

    If you run "backup systemstate" it will take full backup of SystemState. Else, if you run "i" which takes incremental backup of SystemState and Drives available.

    Thanks,



  • 26.  RE: Weekly Full Backup failing from command

    Posted Wed September 21, 2016 11:40 PM

    Thank you Ravindra for the response, you mean to say if i run backup systemstate my purpose will solve. if i understand correctly that's what you are saying correct. if yes every time i have to run that command if yes then it is a big headche,  if you have schedule it can you please share a sample schedule which will help me to understand better. how it can be schedule.

     

    Regards

    Prem



  • 27.  RE: Weekly Full Backup failing from command

    Posted Tue November 01, 2016 08:38 AM

    Hello,

    Why are you using a command instead of selective action in TSM schedule? You have 2 commands in your script, if the first fail (systemstate) the error will not be reported to TSM (It is a problem). You also need deal with return code in the script.

    My suggestion to you is create a new job like example below and try again:

    TSM>define sched DOMAIN_NAME SCHEDULE_NAME action=selective objects='C:\*' options='-subdir=yes' startt=xxx day=xxx

    TSM>define assoc DOMAIN_NAME SCHEDULE_NAME NODE_NAME


    But if you really want to use your script the problem should be dsmc executable, probably because dsmc is not set in PATH variable. You have to add "backup_dir" variable (that you set in the beginning of the script) before as a path for dsmc.


    %backup_dir%\dsmc backup systemstate >> backupfull.log
    %backup_dir%\dsmc sel C:\* -su=yes >> backupfull.log


    Regards,



  • 28.  RE: Weekly Full Backup failing from command

    Posted Sat November 05, 2016 01:49 AM

    Hi Marcel,

    Appreciate your response, why I am using batch file the answer is i have to take whole c drive and system state backup every week. I don't know any other option other than that. if i use the option which you are suggesting then I won't be able to cover the system state backup on the same schedule, probaly i have to create  another schedule for that, I am not sure about it. additionally as you suggested to add the variable if you really want to run the executable, My answer is it is working and taking backup also of system state and c drive but not cleanly(means) it's throwing some error usually error code 4 and 8, which I am not able to calculate it why, in logs also nothing clear. waiting for your view on this.

     

    Regards

    Prem



  • 29.  RE: Weekly Full Backup failing from command

    Posted Sat November 05, 2016 10:02 AM

    Hello Prem,

    1: Yes, you need to create two schedules if you are running selective backup.

    I need analyse log files (the log you generate with >>), dsmerror and dsmsched logs.

    Just a little question, why do you need a selective backup of C drive weekly?



  • 30.  RE: Weekly Full Backup failing from command

    Posted Mon November 07, 2016 02:44 AM

    Hi Marcel,

    Thank you for the response I am attaching the log file as requested.

    1. how do i cover the system state backup if i will create a new schedule objects=? and action=? to create the system state backup.

    2. why i am taking selective then my answer is i don't know, but who has created this while implementing the schedule what they discuss with client and what they have suggested, don't know , although what i know is every time when ever backup trigeers from selective it takes all the objects every time. addidtioanlly we are taking one incremental for those obejcts already i don't know what is the use of it but client doesn't want any changes on this.

    dsmschedlog- it's not allowing me to upload due to size restriction of this site/forum.

     

    Regards

    Prem

     



  • 31.  RE: Weekly Full Backup failing from command

    Posted Mon November 07, 2016 07:48 AM

    Hi Prem, 

    To create a systemstate schedule you must use action=backup and subaction=systemstate (see help 3.15.29.1)

    '-ACTion--=--+-Incremental-------------------------------+-'

    +-Selective---------------------------------+
    +-Archive--+----------------------------+---+
    | | .-""-------. | |
    | '-SUBACTion--=--+----------+-' |
    | '-FASTBack-' |
    +-Backup--+-------------------------------+-+
    | | .-""----------. | |
    | '-SUBACTion--=--+-------------+-' |
    | +-FASTBack----+ |
    | +-SYSTEMSTate-+ |
    | +-VApp--------+ |
    | '-VM----------' |

     

     

    About the erros, I thin you may try options below:

    • Use VSS during windows backup operations (add option "snapshotproviderfs VSS" in your dsm.opt file):
    • Change you copygroup to use serialization SHRDYnamic
    • Exclude files that is not important to restore (like NTUSER.DAT)

     



  • 32.  RE: Weekly Full Backup failing from command

    Posted Mon November 07, 2016 10:43 PM

    Hi Marcel,

    Thanks for the response.  I highlighted my response on red.

    About the erros, I thin you may try options below:

    • Use VSS during windows backup operations (add option "snapshotproviderfs VSS" in your dsm.opt file): This is already added on the .opt file.
    • Change you copygroup to use serialization SHRDYnamic- Changed after your instruction.
    • Exclude files that is not important to restore (like NTUSER.DAT)- excluded

     Lets wait for the result will post the result soon.

     

    Regards

    Prem