Recovering from archive volume

We are still on 8.2.x (moving to 9.x hopefully by the end of the year) and
I am testing command-line recover from an archive to make sure the archive
worked. I entered the command from the recovery directory as follows:

recover -b "LTO archive pool" -d /path/to/relocation

I then used the interactive session to add certain specific files, and when
I entered "volumes" it told me

Volumes needed (all had errors):
Unknown

The only way I was able to recover the archive was to recover the entire
archive using the -S ssid switch. Is this by design, or is there something
else I'm missing in my recover command?

jim


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module

Hi Jim,

I have seen similar problem (also on 8.2.x) after scanning an expired tape:

recover> recover
        Recovering 1 file from /home/XXX/ into /tmp/YYY
        Volumes needed:
                Unknown

- Fix for this was to run these commands in order to reconcile index
databases:

# nsrim -V volume -X
# nsrck -L6 client

Hope this helps,
Adnan



On 2019-08-09 1:35 p.m., Jim Weill wrote:
> We are still on 8.2.x (moving to 9.x hopefully by the end of the year)
> and I am testing command-line recover from an archive to make sure the
> archive worked.  I entered the command from the recovery directory as
> follows:
>
> recover -b "LTO archive pool" -d /path/to/relocation
>
> I then used the interactive session to add certain specific files, and
> when I entered "volumes" it told me
>
> Volumes needed (all had errors):
>         Unknown
>
> The only way I was able to recover the archive was to recover the
> entire archive using the -S ssid switch.  Is this by design, or is
> there something else I'm missing in my recover command?
>
> jim
>
> -- This list is hosted as a public service at Temple University by
> Stan Horwitz If you wish to sign off this list or adjust your
> subscription settings, please do so via
> http://listserv.temple.edu/archives/emc-dataprotection-l.html If you
> have any questions regarding management of this list, please send
> email to owner-emc-dataprotection-l@listserv.temple.edu
> <mailto:owner-emc-dataprotection-l@listserv.temple.edu>
>



--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module

Just a quick note about the following:

On 8/10/2019 6:00 AM, EMC-DATAPROTECTION-L automatic digest system wrote:
> We are still on 8.2.x (moving to 9.x hopefully by the end of the year)


That will be too late. Support for 9.x ends 31 December 2019. You
"hopefully" go to 18.x (2021), better yet 19.x (2022).

Cheers.


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module