ADSM-L

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

2007-07-13 10:51:22
Subject: Re: [ADSM-L] deleting copypool volumes to be rebuilt by backup stgp
From: "Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 13 Jul 2007 10:22:16 -0400
I've been there -- and in reality, the process is to create TWO new
copypools. One for the new primary pool and a new pool for the original
primary pool. Start doing backups to both copypools, and THEN delete the
volumes from the old, no longer needed copypool.

Tom Kauffman
NIBCO, Inc

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Matthew Warren
Sent: Friday, July 13, 2007 9:51 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: 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
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.