We implemented a switchover from Veritas to NW and now we are looking to move
off NW after 2 months. We found yet another bug that causes data loss. We are
running 7.3.2 Jumbo 11.
Below is the stdout from the nsrclone command on one ssid, run from the command
line. As you can see it encountered an error but then verbally says that the
clone finished successfully and the return code is zero indicating success. We
tried to restore from this clone and it was missing 9GB's of 16GB's. We have
opened a case with EMC and submitted a bug report but after looking through the
daemon logs there are other instances of this happening. We were using scripts
to automate the cloning. The script checked the return code of each clone to
verify and ran an mminfo to check flags too but there is a major bug in the
Starting cloning operation...
...from storage node: socdlsvra
nsrclone: error, Bad or missing record in save set 2838334395, lost 9861698379
bytes starting from offset 6935989492.
nsrclone: Cannot open nsrclone session with soslxbkp01.howost.strykercorp.com
nsrclone: Cannot open nsrclone session with soslxbkp01.howost.strykercorp.com.
Error is 'Bad or missing record in save set 2838334395, lost 9861698379 bytes
starting from offset 6935989492.'
nsrclone: Successfully cloned all requested save sets
nsrclone: Clones were written to the following volume(s):
[email protected]:/nsr/scripts> echo $?
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
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER