Thanks Thierry and Davina for your feedback.

I was hoping for a simple procedure. The restores will be done primarily
by our DBAs and server administrators, who need to keep things quick and
simple. Blocking write access during the restore is a big potential
problem, as well. I know this limitation was present on advfs, but I am
surprised it occurs with Data Domain Boost devices too.

On 5/10/2011 11:36 AM, "Davina Treiber" <Davina.Treiber AT PEEVRO.CO DOT UK>
wrote:

>On 10/05/11 15:28, Thierry Faidherbe wrote:
>> Earlier, by change, I found "a way" to recover during
>> clone/stage on an AFD dev at same time :
>> 
>> The trick is not to restore using client file index
>> (recoveries browsing files) but recovering using
>> SSID/Cloneid :
>> 
>> Query the SSID/CloneID of the SS you need to recover.
>> If the SSID copy has not be staged and purged yet
>> (in other word, still on AFD), you will get at least
>> 2 different cloneid, one for each copy of the ssid
>> (one on the write enabled AFD volume,
>>  one for the read-only AFD volume).
>> 
>> eg :
>> 
>> SSID      CLONE ID    Name  Volume
>> 12345678  123456789   c:\   Test
>> 12345678  123456790   c:\   Test.RO
>> 
>> When AFD read-only part is reading (for recover,clone or stage, doesn't
>> matter), 
>> if you recover using SSID/Cloneid and use Cloneid of the SSID copy from
>> the Write-enabled volume like
>> "recover -S 12345678/123456789 [-d <alternate_loc>] path_to_recover"
>> it will read from write-enabled AFD device while the
>> read-only one is reading.
>> 
>> I discovered it by chance, when scripting new staging batch
>> when I did forget to specify ".RO" in <volume>.RO name in
>> piped mminfo for staging cmd during operators did recover using GUI.
>> 
>> Not using that trick very often but it worked each time in
>> case of emergency recover.
>
>Yeah it's a good trick, but don't forget that doing this will block any
>writes to this device.
>
>To sign off this list, send email to listserv AT listserv.temple DOT edu and
>type "signoff networker" in the body of the email. Please write to
>networker-request AT listserv.temple DOT edu if you have any problems with this
>list. You can access the archives at
>http://listserv.temple.edu/archives/networker.html or
>via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER