Re: [Networker] recover trying to using offsite volume

If you're using the 'recover' command then you can specify the -S switch
with the saveset id and clone id together as: 'recover -S ssid/cloneid'.
This will guarantee that NetWorker will ask for the clone volume.
Otherwise, NetWorker will default to the original. You can use 'mminfo
-S' to get the clone id for the affected savesets. Obviously, you'll
need to use -q and give it some criteria to narrow down the search.

Cloned savesets have their own id that is separate from the saveset id.
However, even if you do not create a clone of a given saveset, the
original is still considered a clone of itself, so you'll want to make
sure you specify the right clone id. The first one listed in the output
from 'mminfo  -S' is always the original.

Not sure how you specify when using nwrecover. I would think if you were
using saveset recover from the GUI then just selecting the clone saveset
would suffice.

Joel, what were you using to recover from the clone, e.g. nwrecover,
saveset recover, something else?

George


"Rohrich, James" wrote:
>
> One of the benefits of sending the originals offsite is that the tapes have
> been verified through the cloning process.
>
> -----Original Message-----
> From: Rutherford, Craig R. [mailto:Craig.Rutherford AT JHUAPL DOT EDU]
> Sent: Thursday, August 07, 2003 3:08 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] recover trying to using offsite volume
>
> Joel,
> We keep our originals onsite (in the tape library) and send the clone copies
> offsite (since Legato will always try a restore from the originals first).
> If you send your originals offsite, I'm surprised you haven't had to do this
> same procedure before.
> Craig
>
> -----Original Message-----
> From: Joel Fisher [mailto:jfisher AT WFUBMC DOT EDU]
> Sent: Thursday, August 07, 2003 3:35 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] recover trying to using offsite volume
>
> Hey Craig,
>
> Thanks for responding.  I'll try that for this ssid.
>
> We have recoveries going on a daily basis and they always use the cloned
> version, I'm not sure why this one wants the original.  Isn't it normal
> behavior to use the near volume?  Or is it normal to try and use the
> original volume?
>
> Thanks,
>
> Joel
>
> -----Original Message-----
> From: Rutherford, Craig R. [mailto:Craig.Rutherford AT JHUAPL DOT EDU]
> Sent: Thursday, August 07, 2003 2:39 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] recover trying to using offsite volume
>
> I think you need to mark the original save set as "Suspect" so Legato
> will
> request the clone save set instead.
>
> Suspect button -- click to change the save set's status to "suspect." A
> "suspect" save set cannot be used for recoveries. If NetWorker detects a
> suspect save set, it will then request a clone of the save set and its
> corresponding clone volume for the recovery (assuming that a cloned
> volume
> containing the cloned save set is available). This characteristic will
> continue until the save set is returned to "normal" status.
>
> -----Original Message-----
> From: Joel Fisher [mailto:jfisher AT WFUBMC DOT EDU]
> Sent: Thursday, August 07, 2003 2:26 PM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] recover trying to using offsite volume
>
> Hey All,
>
> Wondering if anyone knows what I can do about this...
>
> I have a saveset that is still within it's browse period that resides in
> 2 pools(backup and clone).  The clone is nearline in the Silo and the
> original is at offsite storage.  We are trying to do a recover, and
> networker keeps giving a "media waiting" message looking for the offsite
> volume.
>
> Anybody have any clue as to why it won't use the onsite volume?  Below
> is some info from mminfo.  The data we are trying to recover is in
> saveset 568401153.  I've run nsrck on the media database and on the
> client index without any results.
>
> ssflags created volume        ssid          clone id pool
> location       client     name
>
> vF      07/25/03 S01138        568401153   1059251748 OnlineCloneR30Days
> STK9310   ptcrcnt.nt.wfubmc.edu E:\
>
> vF      07/25/03 S01404        568401153   1059183971
> OffsiteB30DaysR30Days PP1-Vault ptcrcnt.nt.wfubmc.edu E:\
>
> vF      07/25/03 S01406        568401153   1059183971
> OffsiteB30DaysR30Days PP1-Vault ptcrcnt.nt.wfubmc.edu E:\
>
> vF      07/25/03 S01407        568401153   1059251748 OnlineCloneR30Days
> STK9310   ptcrcnt.nt.wfubmc.edu E:\
>
> vF      07/25/03 S01408        568401153   1059251748 OnlineCloneR30Days
> STK9310   ptcrcnt.nt.wfubmc.edu E:\
>
> vF      07/25/03 S01404        568418561   1059184039
> OffsiteB30DaysR30Days PP1-Vault ptcrcnt.nt.wfubmc.edu G:\
>
> vF      07/25/03 S01406        568418561   1059184039
> OffsiteB30DaysR30Days PP1-Vault ptcrcnt.nt.wfubmc.edu G:\
>
> vF      07/25/03 S01407        568418561   1059251761 OnlineCloneR30Days
> STK9310   ptcrcnt.nt.wfubmc.edu G:\
>
> vF      07/25/03 S01408        568418561   1059251761 OnlineCloneR30Days
> STK9310   ptcrcnt.nt.wfubmc.edu G:\
>
> vF      07/25/03 S01404        568400898   1059183970
> OffsiteB30DaysR30Days PP1-Vault ptcrcnt.nt.wfubmc.edu REPAIRDISK:\
>
> vF      07/25/03 S01407        568400898   1059251755 OnlineCloneR30Days
> STK9310   ptcrcnt.nt.wfubmc.edu REPAIRDISK:\
>
> Thanks,
>
> Joel
>
> E450/2.6/6.1.2
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via
> email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=