Maintenance of backup index cycles in nwadmin v5.1 1

[Roadster]

Legato Networker v5.1.Build.264 on Solaris v5.5.1; one workstation configured as backup server, another as a client.
We have a problem where /var on the backup server repeatedly fills up to >95%, and (what I believe is known as) the browse policy (set up by someone else) is supposed to maintain the number of daily backup cycles at 2 for the client system, but this grows to 4, leading to excessive usage of /var. So far, the only way we can manage this is to manually remove unwanted cycles from the indexes, then reclaim free space. This is effective, but painfully slow and intensive.
I don't yet know enough about nwadmin to be able to examine or modify the policies, although if what I've been told is correct, the set policy appears not be enforced.

Any ideas? Does anyone know, is this known behaviour? Is there a fix or workaround for it?

 

[MoshiachNow]

Hi,

If my browse policy is 1 week,and i'm running full backup once a week adn incrementalls daily,Legato normally will keep a 2 week cycles prior to deleting the old ones,since the last incremental done 6 days after the full backup,still requires the previous full to be able to restore the data completely.

That's how it works - the solution is either to decrease the policy twice or run the full backups more often. "Long live king Moshiach !"
h

http://www.noahide.com/movement.htm