Mismatch with data and index retention dates

[dwindle]

I am getting a curious result when backing up clients to a Windows 2000 server running Networker 6.1. I have a client set up with both the browse and retention policies for the set to 4 weeks. When I backup this client, the data backup receives the correct browse and retention dates but the index file gets the browse and retention dates defined for one of the backup server clients. This only happens for clients in a different group to the backup server clients.

(Note:I have several clients defined for the backup server each with different browse and retention policies).

Is this a feature or bug? It currently selects the backup server client with the longest retention date (5 years) which means that most of my backup tapes won't be recyclable for a long time. Is there a way of forcing the index files to follow the retention policy set for the client not the backup server?

 

[nandfred]

I have the exact same problem, and my spupport told it it was quit logical, go figure, what I've done is to create the server as client in the group, and just backup one single files for the server in that group, it does mean I get some extra bootstrap saves, but I can live with that, compared to the work with correcting retention times.

 

[dwindle]

nandfred-
As the index file resides on the backup server than I guess it makes some sense but it seems more logical to me to have the index files backed up with the same retention policy as the client or what?

Anyway thanks for the tip. It worked. In fact I created the backup server client with a schedule that does a skip every day and this still works (i.e. you don't need to backup anything)