Expiration of index bothers me

Please make sure that you use the correct NW terms:
- the default Browse Prolicy expires after a month
- the default Retention Policy expires after a year
NW does not now the term "expiration policy".
For the index, the Retention Policy is the key.

Do not forget, to make a media become recyclable, ALL save sets must have the status recyclable (their retention policies must have passed). This could also become an issue.

Yes, I undestand you.. I know what th epolicies are (retention & browse). with "expiration policy" I mean that save sets get the retention policy (save set has expired)..

Anyway, I resolve it... As you said, the default policy is browse: 1 month, retention: 1 year. But if you modify the default client (the server itself as a client) who has the save set "All" to 1 week both policies (retention & browse) you fix it and you get the indexes with their retention and browse policy as you need. So if you have some save sets (resource clients) with retention/browse policy with less time (only days, less than 7) you should set the default client with save set "All" to the minimum (same as the less retention policy).

Hope this helps to other who ahs the same problem.

Cheers.

You can also create your server as a new client with different browse and retention policies, and add it into group, where short browse and retention policy should be used.
For example:
client SERVER with save set "All" and browse and retention policy "OneMonth" in group "OneMonth clients"
client SERVER with save set C:\TEMP (you can set schedule to "Skip") and browse and retention policy "OneWeek" in group "OneWeek clients"
With this configuration, indexes of clients from group "OneMonth clients" (including SERVER) will expire after one month and indexes of clients from group "OneWeek clients" (including directory C:\TEMP of SERVER) will expire after one week.
One disadvantage is, that after every backup of client SERVER, bootstrap is generated - after backup of group "OneMonth clients" and group "OneWeek clients" too.

your solution sounds good, but what I did was put the SERVER client with the "All" save set with retention/browse policy of 1 week in the "default" group.. so I don't back it up. I backup what I want of the SERVER in another group with specific save sets. With this I avoid to backup the bootstrap always.. just once with group different than "default".

Thanks anyway..

You may also send index and bootstrap backups to a separate media (a special pool).

Simply create a pool with this configuration:
groups ----
clients ----
save sets index
bootstrap
level ----

and isolate these backups from your others.

yeah, thanks... it can be confortable in order to recover a disaster. But my problem was the retention of indexes... they were of 1 month and not 1 week as I wanted... but I resolve it.

Thanks!