Running Neworker 6.1.3 on Solaris.
I have a volume which contains savesets that have exceeded the browse policy but the volume is still listed in the media DB. The volume was created using a manual clone of various savesets, functioning as offsite disaster recovery media. The volume became full of data during cloning of a particular saveset and, at the time, a second volume was not used to complete the clone operation. Thus, the saveset status on this volume is listed as "abort", although nearly all of the saveset fit on this volume. Now, of course, I need to recover some of the files from this aborted saveset clone. Is it possible to use the scanner command to rebuild the client file index and recover some of the files that actually did get cloned onto this volume?
Thanks in advance for any help!
I have a volume which contains savesets that have exceeded the browse policy but the volume is still listed in the media DB. The volume was created using a manual clone of various savesets, functioning as offsite disaster recovery media. The volume became full of data during cloning of a particular saveset and, at the time, a second volume was not used to complete the clone operation. Thus, the saveset status on this volume is listed as "abort", although nearly all of the saveset fit on this volume. Now, of course, I need to recover some of the files from this aborted saveset clone. Is it possible to use the scanner command to rebuild the client file index and recover some of the files that actually did get cloned onto this volume?
Thanks in advance for any help!