The important issue for the index is that the expiration will not take place when the policy expires but at the end when the first full of the next backup cycle (=full-to-full) will be run.
Consequently, suppose you run a full once per week, you might need to wait up to 6 more days before the index for the oldest backup cycle will be deleted. The same of course is true for the retention policy.
NW should only delete client file index information if the save set is either 'recoverable' or 'recyclable'. Keeping this in mind, it is impossible to keep the file index info when the associated save set status is still browsable.
With respect to auto-labeling: Obviously you have 'Auto Media Management' activated for the device or jukebox. In such case, NW will pick a 'recyclable' media and will relabel it before it will take an empty one. This is NW's default behaviour.
ww1977,
the index will expire when the server retention is reach.
Find the client with the 'red quote' (with the server name)
and set the browse policy/retention policy to 30 days.
You have to understand that an index is a save-set of the server.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.