Well the Borwse policy the shortest is by 2 days. I could be wrong but check
it out in man pages. As long as you are only recovering by ssid change the
browse to 1 day or even to min and see if this reduces you index size ( I
doubt it). extend the retention policy if you want to keep longer. Yo can
always get the data using the SSID.
-Venkat

On Sat, Mar 13, 2010 at 6:01 PM, Anacreo <anacreo AT gmail DOT com> wrote:

> Anyone here an MSSQL / NetWorker export?
>
> Here is our problem...
>
> We're bakcing up some instances with thousands and thousands of databases
> every 4 hours making our indexes quite large.  As a result we're only
> keeping our indexes on-line for 2 days.  Some how the full's are also going
> offline even though there are dependencies on them, which I'm not sure why
> this is happening.
>
> We'd like a way to bypass all this though and recover a table by using its
> SSID.  Even if we need to have the indexes online it would be faster for us
> to use scanner on the VTL with the specific SSID's then to use the "nsrck
> -L7" to bring the indexes back online.  Does anyone know a good way to do
> this?
>
> I'm going to work on the issue in the mean time, I'll post my results.
>
> Alec
>
> 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
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>



-- 
Venkat Tudi

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 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER