[Networker] aborted savesets when cloning?
2003-05-06 16:58:19
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Networker] aborted savesets when cloning?,
George Sinclair <=
|
|
|