1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

unable to backup new FS in schedule mode

Discussion in 'Backup / Archive Discussion' started by briner, Oct 3, 2012.

  1. briner

    briner New Member

    Joined:
    Mar 5, 2012
    Messages:
    9
    Likes Received:
    1
    Hello,

    We are not able to backup new FS when they get created!

    Let me show you the timeline:
    |
    |
    |-20:20 previous backup finished
    |
    |-20:21 few moment after the scheduler tell us that the next backup will happen
    | at 20:00 tomorrow
    |


    |-midnight


    |
    |-19:00 we destroy the FS which are mounted somewhere under /dolly/backup
    |-19:05 we create some new FS which are mounted somewhere under /dolly/backup
    |
    |-20:00 the scheduler starts and the FS newly mounted under
    | /dolly/backup are not backup at all. This is sad, because we are only
    | interested in this FS
    |
    |-20:05 the scheduler finished… and nothing get backup :(
    |
    |-20:06 few moment after the scheduler tell us that the next backup will happen
    | at 20:30 tomorrow
    |
    v

    What can be done. Is there a way to tell the scheduler to backup this file ?
     
  2.  
  3. smajl

    smajl Senior Member

    Joined:
    Dec 10, 2009
    Messages:
    134
    Likes Received:
    19
    Location:
    Brno
    You need to restart TSM scheduler in order to reflect new changes in mounted filesystems.
     
  4. briner

    briner New Member

    Joined:
    Mar 5, 2012
    Messages:
    9
    Likes Received:
    1
    Thaks for the working response. But could you tell me if there is a way to do it in a dsmc commamd such as:
    dsmc init ?
     
  5. domino

    domino Senior Member

    Joined:
    Nov 16, 2005
    Messages:
    716
    Likes Received:
    32
    Occupation:
    System Engineer
    Location:
    Germany
  6. smajl

    smajl Senior Member

    Joined:
    Dec 10, 2009
    Messages:
    134
    Likes Received:
    19
    Location:
    Brno
    you can simply "refresh" (only) scheduler using kill

    ps -ef|grep "dsmc sched"
    find the PID of process, ie 1234
    as root issue command:
    kill -HUP 1234

    But first make sure there is no scheduled action running.
     
  7. markus

    markus New Member

    Joined:
    Jun 24, 2004
    Messages:
    44
    Likes Received:
    0
    You can start your Scheduler via the TSM-Webclient. This will take care of FS-Changes automaticly.
     

Share This Page