I guess I don't see the difference. If logical corruption (rm -r * in the filepool or tsm screws up and deletes vols), the copy pool could be just as corrupt as the main pool. if the copy pool is in the same dd, then a dd failure would trash both anyway and you're in a DR situation. The snapshot is only over the local dd, so we cut snapshots on both dd's at the same time.
Rick From: Steven Langdale <steven.langd...@gmail.com> To: ADSM-L@VM.MARIST.EDU Date: 06/17/2011 01:22 PM Subject: Re: tsm and data domain Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > We debated having a copy pool when doing our DD setup. We finally decided > that using a daily DD snapshot was an acceptable solution. We take a Rick The problem with that is that you'd just be replicating a logical corruption. So unless you noticed it before your last snapshot expired, you be stuck. Obvoliusly a simple solution would be to have a copy stpool on exactly the same DD - inefficient copying wize, but it would dedupe down to nothing. ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
