NW 7.3.2 deletes indexes prematurely

[bchris]

Hello people.

I am facing a serious problem with NW 7.3.2.
I tried my luck with EMC via powerlink, but to no vail.
So here it is; you guys are my last resort.

The setup is NW 7.3.2 running on windows 2003.
It backs up four clients and of course the server itself. That's where the problem lays. The server keeps deleting it's own indexes.

If i run nsrck -L<up to 6> completes OK but no indexes. If i run nsrck -L7 then the indexes for the server are recovered only to be deleted again the next day.

Note that the browse policy is one year for all savesets.

That's it. Any ideas/thoughts are more than welcome.

Thanks in advance.

 

[mbw]

Isnt the expiration policy a combination of the BOTH the Browse and Retention policy? Also - if I recall correctly, policies arent on savesets, they are on Clients. Setting up networker to retain/expire media is the hardest part of the configuration, and tough to debug - good luck!

 

[605]

I assume that he does not delete them right after the backup.

When finished, have a look at your server save sets and verify the browse and retention date and see what they really have been set to:
mminfo -q "client=server_name" -r "name, ssbrowse, ssretent" -ot

 

[bchris]

605 you are correct.

bootstrap 16/12/2009 16/12/2018
bootstrap 16/12/2009 16/12/2018
SYSTEM DB:\ 17/12/2009 17/12/2018
SYSTEM DB:\ 17/12/2009 17/12/2018
SYSTEM DB:\ 17/12/2009 17/12/2018
SYSTEM DB:\ 17/12/2009 17/12/2018
SYSTEM DB:\ 17/12/2009 17/12/2018
ASR:\ 17/12/2009 17/12/2018
ASR:\ 17/12/2009 17/12/2018
SYSTEM STATE:\ 17/12/2009 17/12/2018
SYSTEM STATE:\ 17/12/2009 17/12/2018
C:\ 17/12/2009 17/12/2018
C:\ 17/12/2009 17/12/2018
SYSTEM FILES:\ 17/12/2009 17/12/2018
SYSTEM FILES:\ 17/12/2009 17/12/2018
index:server_name 17/12/2009 17/12/2018
index:server_name 17/12/2009 17/12/2018
bootstrap 17/12/2009 17/12/2018
bootstrap 17/12/2009 17/12/2018
ASR:\ 18/12/2009 18/12/2018
ASR:\ 18/12/2009 18/12/2018
C:\ 18/12/2009 18/12/2018
C:\ 18/12/2009 18/12/2018
SYSTEM DB:\ 18/12/2009 18/12/2018
SYSTEM DB:\ 18/12/2009 18/12/2018
SYSTEM DB:\ 18/12/2009 18/12/2018
SYSTEM DB:\ 18/12/2009 18/12/2018
SYSTEM DB:\ 18/12/2009 18/12/2018
SYSTEM STATE:\ 18/12/2009 18/12/2018
SYSTEM STATE:\ 18/12/2009 18/12/2018
SYSTEM FILES:\ 18/12/2009 18/12/2018
SYSTEM FILES:\ 18/12/2009 18/12/2018
index:server_name 18/12/2009 18/12/2018
index:server_name 18/12/2009 18/12/2018
bootstrap 18/12/2009 18/12/2018
bootstrap 18/12/2009 18/12/2018
SYSTEM DB:\ 19/12/2009 19/12/2018
SYSTEM DB:\ 19/12/2009 19/12/2018
SYSTEM DB:\ 19/12/2009 19/12/2018
SYSTEM DB:\ 19/12/2009 19/12/2018
SYSTEM DB:\ 19/12/2009 19/12/2018
C:\ 19/12/2009 19/12/2018
C:\ 19/12/2009 19/12/2018
SYSTEM STATE:\ 19/12/2009 19/12/2018
SYSTEM STATE:\ 19/12/2009 19/12/2018
ASR:\ 19/12/2009 19/12/2018
ASR:\ 19/12/2009 19/12/2018
SYSTEM FILES:\ 19/12/2009 19/12/2018
SYSTEM FILES:\ 19/12/2009 19/12/2018
index:server_name 19/12/2009 19/12/2018
index:server_name 19/12/2009 19/12/2018
bootstrap 19/12/2009 19/12/2018
bootstrap 19/12/2009 19/12/2018

C:\Program Files\Legato\nsr\mm>

So why is that networker disregards the browse time set in the GUI?

 

[605]

If the client's policies are fine, you obviously override them with another configuration. Could it be that you set the retention policy for a pool?

 

[bchris]

That could not be the case, because in the same group, writing to the same pool there are other clients as well. Their indexes are just fine.