ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
I'm very confused here about which command is used when and/or if there are occasions where it's recommended to run both.
[ Question 1 of 4 ]
If you have a primary pool tape that you're a little nervous about (maybe you've seen some errors), and "query content copied=no" reports nothing, and you have a copy pool, then what is the preferred approach?
If you run audit volume fix=no, and no discrepancies are reported, then should you simply:
1. Run a "move data" to copy the data to another tape, and keep running it until "query content" on the original tape reports nothing?
Note: we collocate primary pool tapes by groups of nodes. We do no collocate copy pools tapes. Thought I'd read that when moving data where collocation is used that it only moves data for that node (or group?) so t he move data might require multiple runs?
OR
2. Run a "restore volume" with preview=yes? Then load all the off-site copy pool tapes required, set read-only, and then rerun "restore volume" without preview option?
[ Question 2 of 4 ]
Are there cases wherein you should do both a "move data" and a "restore volume"?
Looks like someone did that a while back on a tape wherein they did this:
update volume ABC123L6 access=readonly
move data ABC123L6
update volume ABC123L6 access=destroyed
restore volume ABC123L6
But I don't know what if any errors were reported on the original tape or if an audit volume was run. Regardless, if there's a copy in a copy pool then this seems like it would potentially result in 3 copies of the data. 1. The original data on the copy pool, 2. the "new" tape that the data gets copied to with the "move data" command and 3. the "new" tape that gets created from the "restore volume".
[ Question 3 of 4 ]
Do I have that right about that resulting in 3 copies?
But then again, maybe running a "move data" is a precaution so in a worst case scenario, you now at least have a "new" copy with whatever you can salvage from the original "suspect" tape before you move on to the "restore volume", and that way if that goes awry, at least you still have something? I'm thinking, though, that you probably would not use the "move data" unless the audit reported inconsistencies in which case you'd run it again with "fix=yes" and then move the data? Completely confused or probably wrong here.
[ Question 4 of 4 ]
Does the "restore volume" use the same tape that the "move data" used, or does each of those use a new "scratch" tape?
[ Question 1 of 4 ]
If you have a primary pool tape that you're a little nervous about (maybe you've seen some errors), and "query content copied=no" reports nothing, and you have a copy pool, then what is the preferred approach?
If you run audit volume fix=no, and no discrepancies are reported, then should you simply:
1. Run a "move data" to copy the data to another tape, and keep running it until "query content" on the original tape reports nothing?
Note: we collocate primary pool tapes by groups of nodes. We do no collocate copy pools tapes. Thought I'd read that when moving data where collocation is used that it only moves data for that node (or group?) so t he move data might require multiple runs?
OR
2. Run a "restore volume" with preview=yes? Then load all the off-site copy pool tapes required, set read-only, and then rerun "restore volume" without preview option?
[ Question 2 of 4 ]
Are there cases wherein you should do both a "move data" and a "restore volume"?
Looks like someone did that a while back on a tape wherein they did this:
update volume ABC123L6 access=readonly
move data ABC123L6
update volume ABC123L6 access=destroyed
restore volume ABC123L6
But I don't know what if any errors were reported on the original tape or if an audit volume was run. Regardless, if there's a copy in a copy pool then this seems like it would potentially result in 3 copies of the data. 1. The original data on the copy pool, 2. the "new" tape that the data gets copied to with the "move data" command and 3. the "new" tape that gets created from the "restore volume".
[ Question 3 of 4 ]
Do I have that right about that resulting in 3 copies?
But then again, maybe running a "move data" is a precaution so in a worst case scenario, you now at least have a "new" copy with whatever you can salvage from the original "suspect" tape before you move on to the "restore volume", and that way if that goes awry, at least you still have something? I'm thinking, though, that you probably would not use the "move data" unless the audit reported inconsistencies in which case you'd run it again with "fix=yes" and then move the data? Completely confused or probably wrong here.
[ Question 4 of 4 ]
Does the "restore volume" use the same tape that the "move data" used, or does each of those use a new "scratch" tape?