ADSM-L

Re: [ADSM-L] Stopping access to a filepool

2011-04-28 10:19:38
Subject: Re: [ADSM-L] Stopping access to a filepool
From: "Prather, Wanda" <wPrather AT ICFI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 28 Apr 2011 14:05:43 +0000
Well if nothing else, this will surely do it:

update vol * wherestgpool=filepoolname access=readonly



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Rhodes
Sent: Thursday, April 28, 2011 9:17 AM
To: ADSM-L AT VM.MARIST DOT 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.