When I say reported as "aborted" I mean running something like:
'mminfo -av -s server clone_volume_name'
shows them as having an "aborted" status. Also, they show up in the
volumes window with a status of "aborted". You may be right, though,
because it did in fact run out and was requesting another tape, but
here's where I have a problem with this theory as the culprit. The drive
has a max sessions value of 4. There were 10 pathnames listed in my
input file. The first 5 are rather small, about 4 GB, and the next 5 are
much larger at around 30 GB. The first 5 completed with no problems. I
know that because these all were listed with a status of "recoverable"
by the time the cloning process began the first of the big guns. Now,
this was a brand new LTO tape with 100 GB of native capacity. 5 savesets
at 4 GB each only adds up to 20 GB. That still leaves at least 80 GB
remaining. I have a hard time believing that the next saveset at 30 GB
could not fit on that tape. It should have, in which case the space
problem should not have been an issue with the first of the large
savesets, so I wouldn't have expected this to be a cause of the problem.
On the other hand, I do only see 4 of the larger savesets listed for the
volume, along with the 5 small ones for a total of 9. Obviously, it
never started on the 5th large one. So, it would appear that all 4 of
the larger ones were multi-plexed to the tape, in which case I guess it
could not finish any "one" before it ran out of space. Maybe I'll try
again, and only list two of the large savesets and see what happens. I'm
sure you're right about the "out of space" theory causing the aborted
problem, but since I'd seen this before when cloning several small
savesets, where space on the tape was never an issue, I became
concerned. I find it odd that NetWorker doesn't report these as
"in-progress" or something more meaningful.
Thanks for your response! I will re-test.
George
Carl Farnsworth wrote:
>
> What do you mean by "reported as aborted"? You also mentioned the tape is
> filled up. Is it possible the clone session is still active and waiting
> for a second tape?
>
> I also got confused by this my first time using scripted cloning. The
> volumes disply GUI for the clone volume will show an "a" flag for the
> savesets that are currently being cloned. At first I thought this
> meant "a" for active, but I later realized that NetWorker is setting the
> flag as "a" for aborted, until it's succesfully completed!
>
> (P.S. This is how I first realized that the cloning operation was not de-
> multiplexing the savesets).
>
> HTH
> Carl Farnsworth
> DigiDyne Inc.
>
> On Tue, 6 May 2003 16:58:11 -0400, George Sinclair
> <George.Sinclair AT NOAA DOT GOV> wrote:
>
> >Hi,
> >
> >I've noticed that whenever I create a file containing a list of ssids,
> >and I run the clone command as:
> >
> >nsrclone -s server -b 'Clone Pool Name' -S -f input_file
> >
> >or if I pass them in as:
> >
> >nsrclone -s server -b 'Clone Pool Name' -S ssid1 ssid2 ....
> >
> >then the operation works, but there's always one, and sometimes several,
> >that are reported as "aborted". Deleting them and re-running them
> >wouldn't be so bad except that in this case, they're like 30 GB
> >savesets! I can't reclaim my space on the tape. The last time I tried to
> >clone 9 savesets, 5 of them were aborted when I came back. I'm going to
> >have to just end up re-labeling the tape because it's filled up, and the
> >only ones that were not aborted are only like 7 GB each, for a total of
> >maybe 35 Gb. Not really worth sacrificing the whole tape just for those
> >few. Anyone have any ideas what causes this abort business?
> >
> >I notice that if I run them one at a time, I don't see this problem. I'm
> >not seeing problems during backups, and I'm not seeing errors on the
> >devices.
> >
> >Thanks.
> >
> >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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
