It's not always such a good idea to use a file device as the primary storage device for backups. It all depends on the amount of clients, if you're using multi-session backups and the size of your file volumes.
Remember that even though TSM has concurrent access to file volumes, only 1 session is actually allowed to write to the volume. This means that backup sessions, migration TO a file device and such will effectively lock up that specific volume for write access. So basicallly, if you run 1000 sessions against a filedevice pool, you will be creating 1000 volumes. -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- Till: ADSM-L@VM.MARIST.EDU Från: "Prather, Wanda" <wprat...@icfi.com> Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Datum: 03/22/2011 15:25 Ärende: Re: draining a diskpool when using a DD and no copypool Curious as to why you are using the disk pool with migration to DD instead of having your backups write directly to the DD. Wanda -----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.
