retention policy and expiration date 1

[papad]

Hello,

I have a retention policy on my day-tapes for 1 week. But the tapes are geting a expiration date for over one year. I cheked the retention date of all clients several times. I cannont find any client with 1 year retention policy.
Any suggestions?
Thanks

 

[605]

Have you looked at your server's client as well? - If you have index and bootstrap save sets stored on the same media, then you migth see what you described if you did not change the default policies for your server's client resource.

Another way to find out which save sets have these long retention periods is via the mminfo command:

mminfo -a -r "savetime, ssretent, name"

Then find out the save set names and the client.

 

[papad]

Hi 605,
I tried: mminfo -a -r "savetime, ssretent, name" but I don't get the name of the clients. So I can't find the clients with the wrong retention policy.

I don't know if I understand goed what you are writing about the server's client.. Can you explain with more details? I have one day-group with several clients. Here is the backup-server also as client included. The retention policy of all savesets from these clients (included the server) is 1 week... Where else I must look?
Thanks!

 

[new2me]

Have you check the Browse Policy?

take one of the volume... mminfo -q "volume=vol001"

compare your retention and browse...

mminfo -r "savetime, sstent, ssbrowse

 

[605]

You are right - seeing the client name makes sense. So just tell the command appropriately:

mminfo -a -r "client, savetime, ssretent, name"

---------------------------------

Index backups are located at the NW server and of course they are backed up as well. In this case the NW server itself is a client.

If you
- only modify the policies for your remote clients
- but forget the local client (the NW server)
- AND you save all data to the same pool
you may see your effect.

Save sets with long retention policies should always be directed to a separate pool.

 

[papad]

Hello,

- new2me: The browse policy can never be longer than the retention policy. So my problem is somewhere in the retention policy...

- 605: I used the mminfo command you suggest. I see several clients with a retention policy of 1 year. The problem is that I cannot find the wrong configuration on my netw. administrator.
I have one "day-backup" with several clients, the nw-server as a client included. All of these clients have a retention policy of 1 week...

I still cannot find where the problem is...

 

[605]

Well, there are three potential problems which are not so easy to identify:

- with NW 5.x you could assign different policies to different save sets but
only the longest policy became effective
I hope that you run at least NW 6.

- a corrupted media database
You should be able to correct it (nsrck -X) or recover an earlier instance (mmrecov).

- a simple bug
In this case you should open an incident

 

[papad]

Hi 605,
-I am running NW 6.2.
- nsrck -X I had already used.
- I think that I can conclude that I have a bug.
Thanks a lot for the support.