ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 228
- Reaction score
- 4
- Points
- 0
While the subject of moving data from one tape to another has been discussed many times, I'm coming up a bit short here on tracking this information down in regards to a primary pool tape.
[ Question 1 ]
After the move data command has completed for a primary pool tape, I presume the source tape will be returned to scratch, following the reusedelay period for the storage pool. Is that right ?
[ Question 2 ]
If there are bad files on the source tape (perhaps marked from audit volume fix=no), and there's a copy then I would expect that TSM will only move (logically) the good files. But what happens then to the source tape once the move is done ? Is TSM still tracking those bad files on that source tape ? If so then how can TSM return that tape to scratch, even after the resusedelay?
[ Question 3 ]
Or will TSM not return it to scratch, in which case you'd have to run audit with fix=yes before running move data ? What if you didn't run it first ?
I ask this because I thought that if you have both the primary and a copy, and TSM marked bad files on the primary (for example, from an audit with fix=no) then 1. audit with fix=yes won't be any different than fix=no due to the copy as opposed to if there was no copy, in which case 2. it deletes that information from its database (no point in keeping it if they're in fact bad), and the affected data would be rebacked up on the next backup of the client, assuming it still exists on the client, of course.
I might have misunderstood there, however, on point 1 of 2 (here in question 3).
[ Question 4 ]
Following along from question 2, what if you then run a restore volume to restore those damaged files. Will that work if you did not first run audit with fix=yes ? If so, what then becomes of those files on that source tape ?
I would expect that maybe TSM would simply no longer be tracking them on that original tape (due to the restore) and would now instead be tracking them on whatever primary pool volume the files were recopied to from the copy pool. And then the original tape would still get returned to scratch despite the bad files not having been deleted with fix=yes ?
I guess what I'm really asking here is if there's a difference between:
a. audit volume fix=no
b. move data
c. restore volume
vesus:
a. audit volume fix=yes
b. move data
c. restore volume
[ Question 1 ]
After the move data command has completed for a primary pool tape, I presume the source tape will be returned to scratch, following the reusedelay period for the storage pool. Is that right ?
[ Question 2 ]
If there are bad files on the source tape (perhaps marked from audit volume fix=no), and there's a copy then I would expect that TSM will only move (logically) the good files. But what happens then to the source tape once the move is done ? Is TSM still tracking those bad files on that source tape ? If so then how can TSM return that tape to scratch, even after the resusedelay?
[ Question 3 ]
Or will TSM not return it to scratch, in which case you'd have to run audit with fix=yes before running move data ? What if you didn't run it first ?
I ask this because I thought that if you have both the primary and a copy, and TSM marked bad files on the primary (for example, from an audit with fix=no) then 1. audit with fix=yes won't be any different than fix=no due to the copy as opposed to if there was no copy, in which case 2. it deletes that information from its database (no point in keeping it if they're in fact bad), and the affected data would be rebacked up on the next backup of the client, assuming it still exists on the client, of course.
I might have misunderstood there, however, on point 1 of 2 (here in question 3).
[ Question 4 ]
Following along from question 2, what if you then run a restore volume to restore those damaged files. Will that work if you did not first run audit with fix=yes ? If so, what then becomes of those files on that source tape ?
I would expect that maybe TSM would simply no longer be tracking them on that original tape (due to the restore) and would now instead be tracking them on whatever primary pool volume the files were recopied to from the copy pool. And then the original tape would still get returned to scratch despite the bad files not having been deleted with fix=yes ?
I guess what I'm really asking here is if there's a difference between:
a. audit volume fix=no
b. move data
c. restore volume
vesus:
a. audit volume fix=yes
b. move data
c. restore volume