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.

How to delete filespaces with retention protected data?

Discussion in 'Backup / Archive Discussion' started by smith_ja, Mar 20, 2017.

  1. smith_ja

    smith_ja ADSM.ORG Member

    Joined:
    Apr 28, 2005
    Messages:
    53
    Likes Received:
    0
    I had a client node named TNS8DB. This node was remove 6 months ago. The node had some archived files that are archived for 365 days. I am trying to delete the filespaces for TNS8DB and I get this error "ANR0125W DELETE FILESPACE /u01 (fsId=1) for node TNS8DB contains retention protected data and cannot be deleted." We no longer need the archived files. It there any way to remove the retention protection from this data so that it can be deleted?

    Thanks,
    Judy
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,424
    Likes Received:
    343
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    No.

    You could use the "decommission node" command, it will delete the filespace and the node as soon as all the data has expired.
     
  4. smith_ja

    smith_ja ADSM.ORG Member

    Joined:
    Apr 28, 2005
    Messages:
    53
    Likes Received:
    0
    Thanks for the reply. I don't want to wait another 6 months to a year for the data to expire. I need the storage space these old archive items are using. Is there a way to get the data to expire, now?
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,424
    Likes Received:
    343
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
  6. smith_ja

    smith_ja ADSM.ORG Member

    Joined:
    Apr 28, 2005
    Messages:
    53
    Likes Received:
    0
    Yes. I get all that, but what if you change you mind on how long you want to keep that archived data? I work for a community college and the users changed their minds about how long they wanted to keep archives when they realized how expensive the storage tapes are. Sometimes it takes a little while for non technical people to realize that it is not magic and there is a cost to consider.
     
  7. smith_ja

    smith_ja ADSM.ORG Member

    Joined:
    Apr 28, 2005
    Messages:
    53
    Likes Received:
    0
  8. LED888

    LED888 ADSM.ORG Moderator

    Joined:
    Oct 15, 2002
    Messages:
    804
    Likes Received:
    62
    With the "archive data retention protection" enable, there are no changing. It is like pouring concrete.
    One may say that you can destroy and re-pour the concrete.
    To disable the "archive data retention protection" , uninstall the TSM Server, reinstall the TSM Server, make sure that the
    "archive data retention protection" is not enable and then reinstall the database.
    The only time that you can enable the "archive data retention protection" is on a new installed TSM Server where there are no data in the database.

    If the "archive data retention protection" was not enable. Unlike backup, there are no rebinding with archives.
    You can not change the archive retention to affect previous archives.
    ie: Yesterday we archive a file for 180 days.
    The retention is too long, we reduce the archive retention to 60 days.
    We perform an archive today. Todays archive will have a retention for 60 days and we will still have the
    archive for 180 days.

    Several ways to change an archive retention.
    1. Retrive the data and rearchive the data with the archive mgmtclass with the retention that you need.
    2. Move the node into another domain where the archive mgmtclass have the retention that you need.

    Would have to run a select statement to see when the file was archived and count from that date.
     

Share This Page