SQL (DPM) Database Running Out of Space - Advice? RRS feed

  • Question

  • Hi all,

    We are running out of space and am wondering the best way to approach this - not sure a SHRINK would do, or what affect that would have.

    The DB size is -> Space available:

    The table which appears to be consuming the space is:

    Table Name # Records Reserved (KB) Data (KB) Indexes (KB) Unused (KB)
    dbo.tbl_ARM_DirAndFile 32,721,721 56,479,928 4,444,272 141,880 51,893,776

    Can someone please advise best method to shrink, free up space.

    Kind Regards - Travis

    Monday, April 16, 2018 12:49 PM

All replies

  • Hi, Tbl_ARM_DirAndFile and/or Tbl_ARM_Path The tape catalog pruning settings can cause these tables to be large. To reduce the size of these tables, modify the tape catalog retention values to reduce the amount of data we are storing in the DPMDB: The default is to allow it to remove the entries as the tapes expire. If tapes are kept for multiple years, this can lead to a large amount of data retained in the DB. Change the settings to “Prune catalog for tapes older than” and set it to a sensible value (e.g. one month). Updating this will not delete data on tape, but will mean that tapes older than this value will need to be re-cataloged in order to restore data from them. See this blog for more information: Kind regards, Leon

    Blog:  LinkedIn:   

    Wednesday, May 16, 2018 9:17 AM
  • Could try go through this mine was actually the TaskTrail table that was large.  
    Thursday, May 17, 2018 9:54 PM