Rick, About a year ago we implemented the Data Domain system just as you described and after having some time to study its operation and design I would urge you to think long and hard about it and debate the design with DD and TSM Support. My concern is this, as recommended by Data Domain we removed all copy pools and replicate a duplicate copy of our entire primary sequential (file) storage to our DR site. The problem is; what do you do if you incur corruption or some other issue in the primary pool that would normally be resolved by marking the volume as destroyed and recovering the data from the copy pool (which is now non-existent). While I have not begun the discussion yet I think a better design approach may be to either use the DDR as a copy pool resource or incorporate the resources at the DR site to add copy pools. Think about it in terms of "what if" something happened to the data at the primary facility and it got replicated to the DR site, what would be your option to resolve? I don't see any.
Feedback anyone? ~Rick Adamson Jacksonville, Fl. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Tuesday, March 22, 2011 9:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] draining a diskpool when using a DD and no copypool Hello everyone, An interesting problem . . . we are implementing a Data Domain system. It will be configured as a file device via NFS mount. DD replication of the primary file device pool to the DR site will be use so there will be no copypool. We will still use a diskpool with migration into the file device pool, and this brings up a problem. The majority of backups come in over night into diskpool and get migrated. But some backups (Oracle archive logs, long running backups from remote sites and some others) come in at any time around the clock. Since DR relies on DD replication of the primary file device pool, we MUST make sure that at some point every file in diskpool gets migrated. With ongoing backups coming into diskpool, migration to 0% may never complete. The one thought we had was to once a day (after migration completed) run movedata on each diskpool volume. We've asked DD this question, but so far they haven't provided an answer. Thanks! Rick ----------------------------------------- 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.
