1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Delete files from a stg pool

Discussion in 'TSM Operation' started by gernthefish, Sep 13, 2017.

  1. gernthefish

    gernthefish ADSM.ORG Member

    Joined:
    Mar 3, 2005
    Messages:
    102
    Likes Received:
    0
    I'm having a senior moment and can't find a way to delete a nodes files from 1 specific stg pool. In the following example, is there a way to delete just SERVER1's files from POOL2 only?

    Protect: TSM-TEST>q occ server1

    Node Name Type Filespace FSID Storage Po Number of F Physical Sp Logical Spa
    Name ol Name iles ace Occupie ce Occupied
    d (MB) (MB)
    ---------- ---- ---------- ---- ---------- ----------- ----------- -----------
    SERVER1 Bkup / 2 POOL2 8,816 - 249.71
    SERVER1 Bkup / 2 DISKPOOL 2,772 216.34 208.90
    SERVER1 Bkup / 2 TAPEPOOL 99,637 5,476.90 3,314.85
    SERVER1 Bkup / 2 TAPEPOOL_C 99,775 4,130.80 3,325.17
    OPY
    SERVER1 Bkup /boot 3 POOL2 1 - 0.00
    SERVER1 Bkup /boot 3 TAPEPOOL 56 173.33 133.57
    SERVER1 Bkup /boot 3 TAPEPOOL_C 56 133.57 133.57
    OPY
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,608
    Likes Received:
    370
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    You're not having a senior moment, you can't do it. At least not easily.

    You can delete a filespace, but that deletes the files in that filespace regardless in which pool they are.

    Option 1:
    This is the prefered method, ff you know which files are in the pool in question, go on that client and use the "delete backup" command to delete that data. Typically, we decide what data to keep or delete based on the actual files on the client, not where they are stored. Most of us don't know where the data is stored, we can find out, but we don't keep track of it. Why would we, the server tracks it for us.

    Option 2:
    I guess an awkward alternative would be to create a new temporary storage pool, do a MOVE NODEDATA to move the data in question to that new pool, then delete the volumes in that.

    Option 3:
    If you are using collocation, you could do Q NODEDATA and delete the stgpool volumes that node has data on. BE EXTREMELY CAREFUL THAT THE VOLUMES DON'T CONTAIN DATA FROM OTHER NODES.
     
  4. gernthefish

    gernthefish ADSM.ORG Member

    Joined:
    Mar 3, 2005
    Messages:
    102
    Likes Received:
    0
    Thanks marclant. This is very helpful.
     

Share This Page