I agree. I have fallen into this situation where the original was damaged
and the primary copypool tape was also damaged, thus resulting is lost
data (long story about firewall and other issues).  I was able to recover
by having another copypool tape (belt, suspenders, nailgun).

On other systems, I don't have that luxury so if I delete the copypool
tape, I had better be absolutely sure to have a good primary.  Without
performing lots of long, tedious, audits of hundreds of tapes, this isn't
possible.

I feel the need for two new commands/processes.

1 - The ability to delete the copypool data by specific node(delete
nodedata type=copy stg=copypool?). I have had numerous times when I moved
a node to another server and would like to just delete it's copypool data
to free up the copypool tapes/space it occupied.

2- The ability to make another copypool copy of a single nodes data
(backup nodedata stg=copypool?), after the fact. For instance, if I have
nodes that have critical data and they want two copies of it, not another
copy of the whole primary stgpool.

We need more granularity/controls on the copypool process.

----------------------------------------------------
Zoltan Forray




Matthew Warren <matthew.warren AT UK.BNPPARIBAS DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/13/2007 10:10 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] deleting copypool volumes to be rebuilt by backup stgp






I recalled a point that has bothered me for ages after following the
recent
posts regarding splitting the copypool and technote 1222377.

There is a general acceptance that it's ok to do things like, delete the
volumes from the copypool and just let the backup storage pool recreate
them.

But, it's my understanding the copypool volumes are there to protect
against issues such as read errors or otherwise unusable primary pool
tapes.

Is it really a good idea to be relying on the fact you can read the only
copy of all your data once more? (Ok, we have read it once to make the
second copy, but there have perhaps been many movements of the data around
tapes and the file may not be on the piece of tape we know to have been
reliable once).

I think it would be much better of TSM to allow nodedata to be
specifically
deleted from a copypool, so long as TSM is aware there is another copy of
the file in another copypool. Perhaps something like delete nodedata
type=copy f=file,space,list? This would avoid the exposure in the first
place.


Matt.


This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in
the United Kingdom.

BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in
the United Kingdom.

BNP Paribas Fund Services UK Limited is authorised and
regulated by the Financial Services Authority