How do you Shred a document from TSM?
We have the need to be able to completely delete (shred) a document. Once shredded, it can't be restored. I need to be able to remove it from all the tape pools, disk pools, off site tapes, off site databases, archive tapes etc. Is this possible? If I delete the document from the database (how is this done), how do I then delete it from the seven backup databases that are stored off site? I do not want to wait a week until they are replaced with new database backup tapes. Is deleting it from the database enough? Is there anyway to get the document off of a tape (or disk pool) once removed from the database? Once a tape is assigned to a scratch pool, but not used, can it be returned to its previous status or is it effectively erased? Thanks for any help, Scott Foley Part time TSM admin
Re: How do you Shred a document from TSM?
Given your requirement, you probably should not back up the file to TSM in the first place. TSM is not designed for the kind of absolute destruction you need; for example, your file is (theoretically; let's not reopen this discussion!) recoverable from the onsite primary tape and offsite copypool tape until is it physically overwritten. In addition, it will be cumbersome to properly rebind the file so that all of the versions expire off. _ William Mansfield Senior Consultant Solution Technology, Inc Scott Foley sfoley@NETDOCUMETo: [EMAIL PROTECTED] NTS.COM cc: Sent by: ADSM: Subject: How do you Shred a document from TSM? Dist Stor Manager [EMAIL PROTECTED] .EDU 02/20/2002 04:48 PM Please respond to ADSM: Dist Stor Manager We have the need to be able to completely delete (shred) a document. Once shredded, it can't be restored. I need to be able to remove it from all the tape pools, disk pools, off site tapes, off site databases, archive tapes etc. Is this possible? If I delete the document from the database (how is this done), how do I then delete it from the seven backup databases that are stored off site? I do not want to wait a week until they are replaced with new database backup tapes. Is deleting it from the database enough? Is there anyway to get the document off of a tape (or disk pool) once removed from the database? Once a tape is assigned to a scratch pool, but not used, can it be returned to its previous status or is it effectively erased? Thanks for any help, Scott Foley Part time TSM admin
Re: How do you Shred a document from TSM?
some thoughts... delete archive delete backup perhaps delete filesystem expire inventory it will not be removed from any of your db backups... and, I think, scratch tape reuse(how quick are tapes returned to scratch status...this IS a parm...and settable...if you reuse tapes quicker than 7 days, then your 7 day old db backup is not very useful...if the data is moved around...(migration? reclaimation?). FYI -Original Message- From: Scott Foley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 4:49 PM To: [EMAIL PROTECTED] Subject: How do you Shred a document from TSM? We have the need to be able to completely delete (shred) a document. Once shredded, it can't be restored. I need to be able to remove it from all the tape pools, disk pools, off site tapes, off site databases, archive tapes etc. Is this possible? If I delete the document from the database (how is this done), how do I then delete it from the seven backup databases that are stored off site? I do not want to wait a week until they are replaced with new database backup tapes. Is deleting it from the database enough? Is there anyway to get the document off of a tape (or disk pool) once removed from the database? Once a tape is assigned to a scratch pool, but not used, can it be returned to its previous status or is it effectively erased? Thanks for any help, Scott Foley Part time TSM admin
Re: How do you Shred a document from TSM?
My feeling is that backups are required to do exactly the opposite of this, i.e., to protect against the accidental shred -r * command. Any backup product that would be able to do this would need, I think, a two key locking system, voice recognition, and retinal scans from at least one VP before deleting files from backups. Anything else just wouldn't be safe and in the spirit of recovery. And for situations like the Enron shredding parties, maybe it should also have a tie to the Judicial branch's computers for authorization there. However, if you're going to try to jerry rig it with TSM, I think it would be too risky to let any volumes from that pool remain (unless collocated). And if you're going to go through this effort, why bother taking the risk? I mean, even if you don't KNOW that file was on a certain volume, it might have been on a dbbackup 20 days ago. 1 Bind the file(s) to a mgmtclass with verdel=0, retonly=0 2 Delete the file(s) 3 Back up again so TSM knows it's (they're) inactive/expired/gone 4 Run expiration to get it (them) out of your current database 5 Create a new copypool 6 Populate it by backing up your primary storagepool to it 7 Create a new primary pool 8 Move all data from your old primary pools to the new primary pool 9 Delete your disk volumes 10 Reformat your disk volumes 11 Redefine your disk volumes 12 Backup the database 13 Send new copypool and the dbbackup offsite. 14 Retrieve ALL volumes that were offsite before this most recent batch 15 Destroy the data old primary and old offsite volumes - overwrite, degauss, or my favorite, bonfire with a nice old-fashioned crab bake (I wonder if the crab would taste like plastic?) Voila, gone, and the rest of your data is still offsite. Notice, don't destroy the offsite backups until after you expire, recreate, and offsite your new copypool, unless the SEC or a Congressional hearing is REALLY breathing down your neck. If a disaster happens, ok, OTHER than a legal disaster, had you destroyed your offsite volumes first, you could be SOL. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail ** My only explanation is Insanity -Original Message- From: Scott Foley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 2:49 PM To: [EMAIL PROTECTED] Subject: How do you Shred a document from TSM? We have the need to be able to completely delete (shred) a document. Once shredded, it can't be restored. I need to be able to remove it from all the tape pools, disk pools, off site tapes, off site databases, archive tapes etc. Is this possible? If I delete the document from the database (how is this done), how do I then delete it from the seven backup databases that are stored off site? I do not want to wait a week until they are replaced with new database backup tapes. Is deleting it from the database enough? Is there anyway to get the document off of a tape (or disk pool) once removed from the database? Once a tape is assigned to a scratch pool, but not used, can it be returned to its previous status or is it effectively erased? Thanks for any help, Scott Foley Part time TSM admin
Re: How do you Shred a document from TSM?
YEPPER, there is a way to do this. This is how. 1. Determine the tapes/volumes the filespace is stored on that contains the document. 2. Change the include/exclude on the client to exclude that file from backup. When you do this the file will be expired if you run a backup and even removed as an inactive file. You are not supposed to be managing this file anymore is what you are telling TSM. 3. TSM will remove all entries in the database. 4. Issue move data commands for each tape volume to the same storage pool with the reconstruct=yes option. The onsite and offsite will be rebuilt from the primary pool. This will put the original tapes in an empty status unless a file spans a tape, then you have to do the one before or after or both in the sequence of tapes. You can figure that out from the filespace and volume history information. 5. Once the move data commands are complete no one can access the tapes if you take control of them. But, you must rerun your offsite database backups when you rotate these offsite. This is also how we avoid open storage at our offsite storage facility. We cycle our tapes trough over a 6 week period. Anthing that is coming back within 8 days gets a move data command to the same pool as part of the cycle because we do weekly rotations. If you do daily you would probably do every 2 or 3 days. But, the point is we never do reclamation of the offsite pool because we are forcing reclamation. This keeps fresh tapes offsite and continually churns the mix. We use sealed boxes to rotate the tapes. This process has many benefits, but we have a lot of hardware to do the forced reclaims. -Original Message- From: Scott Foley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 5:49 PM To: [EMAIL PROTECTED] Subject: How do you Shred a document from TSM? We have the need to be able to completely delete (shred) a document. Once shredded, it can't be restored. I need to be able to remove it from all the tape pools, disk pools, off site tapes, off site databases, archive tapes etc. Is this possible? If I delete the document from the database (how is this done), how do I then delete it from the seven backup databases that are stored off site? I do not want to wait a week until they are replaced with new database backup tapes. Is deleting it from the database enough? Is there anyway to get the document off of a tape (or disk pool) once removed from the database? Once a tape is assigned to a scratch pool, but not used, can it be returned to its previous status or is it effectively erased? Thanks for any help, Scott Foley Part time TSM admin
Re: How do you Shred a document from TSM?
Who knows, maybe he is taking care of some END-RUN Accounting. -Original Message- From: Alex Paschal [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 7:27 PM To: [EMAIL PROTECTED] Subject: Re: How do you Shred a document from TSM? My feeling is that backups are required to do exactly the opposite of this, i.e., to protect against the accidental shred -r * command. Any backup product that would be able to do this would need, I think, a two key locking system, voice recognition, and retinal scans from at least one VP before deleting files from backups. Anything else just wouldn't be safe and in the spirit of recovery. And for situations like the Enron shredding parties, maybe it should also have a tie to the Judicial branch's computers for authorization there. However, if you're going to try to jerry rig it with TSM, I think it would be too risky to let any volumes from that pool remain (unless collocated). And if you're going to go through this effort, why bother taking the risk? I mean, even if you don't KNOW that file was on a certain volume, it might have been on a dbbackup 20 days ago. 1 Bind the file(s) to a mgmtclass with verdel=0, retonly=0 2 Delete the file(s) 3 Back up again so TSM knows it's (they're) inactive/expired/gone 4 Run expiration to get it (them) out of your current database 5 Create a new copypool 6 Populate it by backing up your primary storagepool to it 7 Create a new primary pool 8 Move all data from your old primary pools to the new primary pool 9 Delete your disk volumes 10 Reformat your disk volumes 11 Redefine your disk volumes 12 Backup the database 13 Send new copypool and the dbbackup offsite. 14 Retrieve ALL volumes that were offsite before this most recent batch 15 Destroy the data old primary and old offsite volumes - overwrite, degauss, or my favorite, bonfire with a nice old-fashioned crab bake (I wonder if the crab would taste like plastic?) Voila, gone, and the rest of your data is still offsite. Notice, don't destroy the offsite backups until after you expire, recreate, and offsite your new copypool, unless the SEC or a Congressional hearing is REALLY breathing down your neck. If a disaster happens, ok, OTHER than a legal disaster, had you destroyed your offsite volumes first, you could be SOL. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail ** My only explanation is Insanity -Original Message- From: Scott Foley [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 2:49 PM To: [EMAIL PROTECTED] Subject: How do you Shred a document from TSM? We have the need to be able to completely delete (shred) a document. Once shredded, it can't be restored. I need to be able to remove it from all the tape pools, disk pools, off site tapes, off site databases, archive tapes etc. Is this possible? If I delete the document from the database (how is this done), how do I then delete it from the seven backup databases that are stored off site? I do not want to wait a week until they are replaced with new database backup tapes. Is deleting it from the database enough? Is there anyway to get the document off of a tape (or disk pool) once removed from the database? Once a tape is assigned to a scratch pool, but not used, can it be returned to its previous status or is it effectively erased? Thanks for any help, Scott Foley Part time TSM admin
