Maybe take a diff approach... Current Disk-Pool Next Stgpool=Data Domain
DD - Under Maint Disk pool >> next Stgpool (other media tape disk etc ) ex tapepool We do this often if we are upgrading a VTape appliance we will always have our backup and archive copy groups set to a destination of a disk pool even if it does not have disk associated, then we use the "nextstgpool" option to point to what ever other media we may use. Example - w have disk-pool1 with a next stgpool of vtape 1, we need to upgrade code on vtape one we just update the diskpool1 with a "Nextstgpool" of vtape2 (second vtape head) or a tape pool... This way your clients are not writing to the pool under maint, you may have a mediaw if a client is trying to do a restore ... Charles -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Thursday, April 28, 2011 9:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Stopping access to a filepool Taking the storage offline would work too but during a scheduled backup window the schedule may fail with an error of no storage available. ~Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 28, 2011 10:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Stopping access to a filepool Would like to keep clients accessing the diskpool to still keep running. That's the beauty of a diskpool . . .you can take your library offline ( or DataDomain) for some time and not effect backups that hit the diskpool. Rick From: Rick Adamson <rickadam...@winn-dixie.com> To: ADSM-L@VM.MARIST.EDU Date: 04/28/2011 09:48 AM Subject: Re: Stopping access to a filepool Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> What about "disable sessions client"? ~Rick Adamson Jacksonville, FL -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Thursday, April 28, 2011 9:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Stopping access to a filepool How do you offline/stop_access to a filepool? We have been implementing a DataDomain which is accessed as a filepool. Prior to the DD, most backups went to the diskpool with some very large backups going straight to tape. When we would want to take the library down, we would kill any processes/sessions writing to tape and then take the tape drives offline. This prevented any new sessions from trying to access tape until the library work was completed. Now were trying to figure out that the equivalent process is for the DD and it's filepool. Most backups still go into the diskpool, and the very large backups go straight into the DD filepool. If we want to take the DD down for some reason, we would kill any processes/sessions writing directly to the filepool, but we can't think of any way to prevent new sessions from trying to access the filepool. I guess I'm looking for some way to offline the filepool. Any thought/comments are most welcome! 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. This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.