Re: [Networker] Clone of a clone

Hi Jeffrey,


as you have attempted to do this via nsrclone by specifying the exact 
ssid/cloneid of the savesets on the clone RO volume, then the problem cannot 
be that only the ssid is picked up. NW knows what instance is to be cloned. 
It looks more like a problem related to the SN and devices configuration.


If by storage node affinity you mean the "clone storage nodes" attribute 
configured on the source SN client definition, then that seems to be right. 

Do you have any device restrictions on the clone pool configuration?

Does the manual nsrclone command show what devices are not available and on 
what host? If not, Is it possible to use dbgcommand to raise the debug level 
of nsrexecd on the source and target SN during the time the cloning is 
attempted? (debug level 5 should suffice)


If the target pool P2 (specified with -b ) doesn't have any device 
restrictions AND the "clone storage nodes" attribute on the client 
configuration of  SN1 contains SN2, THEN you should be able  to clone from 
pool P1, and the devices connected to SN1,  and write to pool P2 and the 
drives on SN2 (if I got the design right...)


jee


On Tuesday 31 May 2011 13:47:24 Morton, Jeffrey wrote:
> OK, so here's my situation.
>
> I am currently attempting to use the clone controlled replication
> capability of DD Boost to move data to a remote site for tape output
> using scheduled cloning.
>
> This works well.
>
> The problem I am encountering now is with attempting to move that data
> to tape at the remote site.  Despite several attempts to specify storage
> node affinity, clone volume pool, etc.. the scheduled clone just appears
> to hang without any specific reason. I'll assume at this point that it
> is picking just the SSID on the clone volume pool and reverting to the
> original copy at the source location.
>
> I've also attempted to do this via nsrclone by specifying the exact
> ssid/cloneid of the savesets on the clone RO volume and I get an error
> stating that the device is not available.
>
> Anyone have any suggestions?
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of bingo
> Sent: Monday, May 30, 2011 4:42 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Clone of a clone
>
> By default, NW will always choose the first instance of a save set - the
> one with the lowest cloneid.
> BTW - the cloneid is nothing else but the UNIX timestamp which you can
> verify by displaying the cloneid along with the nsavetime parameter
> within an mminfo command.
>
> NW can however choose any other instance. You have two possibilities to
> do that:
>   - You either specify "ssid/cloneid" - this means you usually switch to
> the command line.
>     However, the tab "Save Set Filters" in the "Clones" resource also
> has this capability - use the option "Clone specific save sets ..."
>
>   - You simply set all other save set in question to "suspect".
>
> +----------------------------------------------------------------------
>
> |This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
>
> +----------------------------------------------------------------------
>
> 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
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
>
> NOTICE OF CONFIDENTIALITY: This message and any attachments contains
> confidential information belonging to the sender intended only for the use
> of the individual or entity named above. If you are not the intended
> recipient, be advised that copying, disclosure or reliance upon the
> contents is strictly prohibited. If you have received this message in error
> please notify the sender immediately.
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> 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