1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above 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 notice will disappear after you have made at least 3 posts.

ExpireDBBackupDays vs Del Volhist

Discussion in 'Disaster Recovery Module' started by ILCattivo, Jan 6, 2017.

  1. ILCattivo

    ILCattivo ADSM.ORG Member

    Joined:
    Jul 9, 2013
    Messages:
    48
    Likes Received:
    0
    Location:
    Oxford, United Kingdom
    I am fairly new to the realms of DRM and have previously used the del volhist type=dbs cmd to remove older TSM db backups.

    Now I have inherited a few TSM Servers running DRM (7.1.5) and have found both the ExpireDBbackupdays setting and del volhist type=db? applied. IBM do not recommend both to be used at the same time and I have seen this first hand recently when Tape volumes disappear off the radar. So, I wanted to gauge how best to configure a TSM server where the following DB backups are taking place under a DRM environment.

    backup db type=dbs devcl=<FileClass>

    backup db type=FULL devcl=<LTOClass>

    q drmstat...

    DB backup Series Expiration days: 3

    Now, I understand that DRM should take care of those db backups sent to a Tape file Class. (no probs there) So how does one manage the dbs ones sent to tape without using the 'del volhist type=dbs' cmd, which if set incorrectly can remove volume history from the DB?

    Thanks
     
  2.  
  3. inthesun

    inthesun ADSM.ORG Member

    Joined:
    Oct 15, 2014
    Messages:
    12
    Likes Received:
    1
    Location:
    Tucson
    Hi,

    The DRMDBBACKUPEXPIREDAYS option allows expiration to remove the volumes for you.

    The value set by this command applies to both a snapshot and a full plus incremental database backup series. Any type of database backup series is eligible for expiration if all of the following are true:
    • The age of the last volume of the series exceeds the expiration value set with the SET DRMDBBACKUPEXPIREDAYS command and the value that is specified for the DELgraceperiod parameter in the DEFINE SERVER command. The DELgraceperiod parameter applies only to remote database backups. The default value for the DELgraceperiod parameter is 5 days. For example, if you set the value for the SET DRMDBBACKUPEXPIREDAYS command to 7 days and set the value for the DELgraceperiod parameter to 6 days, the remote database backup series does not expire until 13 days elapse.
    • For volumes that are not virtual volumes, all volumes in the series are in the VAULT state.
    • The volume is not part of the most recent database backup series.
    Remember: The most recent backup series of either type is not deleted.

    Key is that this option is just for DRM volumes that have been moved from Mountable to DRM state of VAULT.

    So, for none DRM DB backups, you would still need to do the Delete Volhistory command.
    www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.7/srv.reference/r_cmd_volhistory_delete.html
     
  4. ILCattivo

    ILCattivo ADSM.ORG Member

    Joined:
    Jul 9, 2013
    Messages:
    48
    Likes Received:
    0
    Location:
    Oxford, United Kingdom
    Hi inthesun,

    Many thanks for this very useful information.

    So just to clarify, the DRMBACKUPEXPIREDAYS setting applies to both 'dbb' & 'dbs' backups regardless of whether they reside on FILE, DISK or LTO dev classes?

    For example...
    If DRMBACKUPEXPIREDAYS = 2 days, should I expect to see no more than the most recent 2 x dbs backup files located on my db backup file dev class location on any one day?

    Thanks
     

Share This Page