• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • 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.

  • 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 all data related to a specific filespace?

tivolimistery

ADSM.ORG Member
Joined
Oct 10, 2009
Messages
58
Reaction score
0
Points
0
Hi All,

we are going to destroy an HSM managed GPFS file system.
But, first, we would like delete all data (about 1PB) related to this GPFS file system and free up a lot of tapes (assigned to the primary storage pool and to the copy storage pool).

This is our first "massive deletion" and I would ask you some suggestion about the right way to do it.

In particular, I would know if I have to delete all files from file system and wait for reclamation effects or:

- simply remove related filespace from TSM server;
- delete related storage pool from TSM server;
- delete each single tape from storage pool.

Thank you in advance.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,774
Reaction score
624
Points
0
Location
Canada
Website
www.ibm.com
- simply remove related filespace from TSM server;
- delete related storage pool from TSM server;
- delete each single tape from storage pool.
You don't need to delete the volumes if you delete the filespace and vice-versa.

You can do it in one of 2 ways.
Method 1 is if you don't know which volumes are owned by that node
1 - delete the filespace(s)
2 - wait for reclamation to run (both onsite and offsite) or kick it off manually
3 - delete the stgpool(s) if empty
This method will have less commands because don't need to touch every volume


Method 2 if you know which volumes are vor that node
1 - delete each primary volume individually with the option discarddata=yes
2 - delete the stgpool(s)
This method will have a large number of commands because do need to touch every volume.
 

tivolimistery

ADSM.ORG Member
Joined
Oct 10, 2009
Messages
58
Reaction score
0
Points
0
Thank you very much for your support.
So (just for confirmation), if I understand we can do it in one of 2 ways you suggested or deleting all files from GPFS file system waiting for reclamation, right?

Thank you again.
Have a great day
 

teeraw

Active Newcomer
Joined
Nov 29, 2010
Messages
8
Reaction score
0
Points
0
You don't need to delete the volumes if you delete the filespace and vice-versa.

You can do it in one of 2 ways.
Method 1 is if you don't know which volumes are owned by that node
1 - delete the filespace(s)
2 - wait for reclamation to run (both onsite and offsite) or kick it off manually
3 - delete the stgpool(s) if empty
This method will have less commands because don't need to touch every volume


Method 2 if you know which volumes are vor that node
1 - delete each primary volume individually with the option discarddata=yes
2 - delete the stgpool(s)
This method will have a large number of commands because do need to touch every volume.
Do any ways impacted to plenty of db log will fill-in during processing?
And, how about interval time to do this by 2 ways?
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,774
Reaction score
624
Points
0
Location
Canada
Website
www.ibm.com
Do any ways impacted to plenty of db log will fill-in during processing?
And, how about interval time to do this by 2 ways?
It won't be hard on the active log because those will all be relatively short transactions. Depending on how many million files there are to delete, it could potentially have an impact if the archive log is small and the number of files to delete is extremely large.
And, how about interval time to do this by 2 ways?
It depends. Option 1 is much less work for you, less typing, just kick off the delete and grab a coffee. Option 2 is more work for you as you have to issue every delete command manually unless you are good as scripting. Option 2 could potentially be faster because you can delete multiple volumes in parallel, but not too many as to not overload the server. Can't tell you how many in parallel your server can handle, too many variables, start small and increase slowly if you feel it can handle more. Thins to monitor before adding more: CPU, memory, DB/log disks response time, and archive log free space.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

DigitalOcean $100 Credit

Support ADSM.ORG and get DigitalOcean FREE credit. DigitalOcean currently offer a $100, 60-day Free Credit for new accounts. Sign-up here:

DigitalOcean Referral Badge

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 20 18.3%
  • Keep using TSM for Spectrum Protect.

    Votes: 65 59.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.8%
  • Other (please comement)

    Votes: 9 8.3%

Forum statistics

Threads
31,811
Messages
134,819
Members
21,786
Latest member
marwo
Top