Re: [Networker] Device or resource busy during cloning?

Just tried creating another clone volume (Full_c.009) for a completely
different clone pool: Full Clone. This one is our normal clone pool. I
guess I'd never tried having more than one available clone volume for
this pool before. In this case, I tried cloning two ssids, same as with
the ARC Clone. First one is on ARC001 in library 1 and second is an
index on ARC002 located on primary server's library. Same thing happens,
but in this case the two clone volumes are not in the same library on
the storage node. Volume Full_c.008 is in library 1 and Full_c.009 is in
library2 on the storage node. Once again, it clones the first saveset to
Full_c.008 (was still appendable, so we'd expect this) and then clones
the second second saveset (an index) to Full_c.009. This is not what
we'd expect since there's still plenty of space on Full_c.008. I don't
get the device or resource busy message this time, but I'm thinkingt hat
might be because the two clone volumes are on separate libraries.
Strange, though, that is insists on wanting to load another clone volume
to clone the other saveset.
Shouldn't matter that the original savesets are on different tapes, but
apparently, if they are, and you have more than one clone volume
available, NetWorker will split them?
Weird! If you only have one clone volume available, then it writes both
to that one which is what you'd expect. If both original savesets are on
the same volume then it writes both to just the one clone volume, also
what you'd expect.

George


George Sinclair wrote:
>
> Noticed that if I re-label one of the two ARC Clone volumes as something
> else -- any other pool -- so I only have one ARC Clone pool tape
> available, NetWorker acts normal. It writes everything to just the one
> tape and never issues any device or resource messages. For some reason,
> though, having two available clone volumes causes the problem, and I
> have the sessions for each device set to 5, and the number I'm cloning
> is less than that. Strange!
>
> The thing is that I would like to have two clone volumes available so
> when one fills up, NetWorker will have another one to load. I can't rely
> on auto-media management because NetWorker will not necessarily select a
> tape that has the proper bar code.
>
> George
>
> George Sinclair wrote:
> >
> > Seeing strange problem when cloning, not sure what to think! Not seen
> > this before.
> >
> > I have two clone pool volumes: ARC_c001, ARC_c002. Both have plenty of
> > space. I try to clone 4 savesets. 2 are on volume: ARC001, and the other
> > 2 are client indexes located on volume: ARC002.
> >
> > ARC001, and both clone tapes are on storage node library. ARC002 is on
> > primary server's library.
> >
> > When I run clone command as: nsrclone -s server -b 'ARC Clone' -S ssid1
> > ssid2 ssid3 ssid4
> >
> > NetWorker clones two savesets to ARC_c001 (just what you'd expect), and
> > then when it starts to clone the two indexes it issues: Device or
> > resource busy message for the drive that has volume ARC0_c001. It then
> > loads ARC_c002 into another drive and clones the indexes to that tape,
> > not ARC_c001! If I then run the command again, using different ssids,
> > the same thing happens, but this time it writes the first two savesets
> > to ARC_c002 and then issues the Device or resource busy message on the
> > device containing ARC_c002 and then clones the indexes to ARC_c001.
> > Subsequent tests just keep producing the same swapping results. I don't
> > understand why NetWorker has to clone the last two savesets to another
> > volume member when there's plenty of space on the first one, and it
> > started on the first one. Makes no sense, and like I said, the results
> > change back and forth with every run. I even tried cloning just two
> > savesets, one on one tape (ARC001) and one index on another (ARC002) and
> > same results. This does not occur when both ssids are on the same tape,
> > however.
> >
> > I've cloned lots of stuff before to other clone pools (not ARC Clone),
> > and I've never seen this behavior. My experience was always been that
> > NetWorker didn't care how many ssids were contained on how many
> > different tapes. It would clone all of them to the same clone volume and
> > not to a different one until it ran out of space on the former then it
> > goes to the next.
> >
> > Anyone seen this? I tried re-labeling the tapes, still happens. We're
> > runnng 6.1.1. Storage node is using Linux Red Hat and primary server is
> > running Solaris 2.8. also 6.1.1. If I delete one of the clone volumes,
> > so I only have one, and try again, it just sits and waits for the second
> > volume after cloning the first ssid(s). Not good.
> >
> > Any help appreciated.
> >
> > George
> >
> > --
> > 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=