Highlighted
JayJay9882
2 Iron

/nsr/index grows and grows and grows

Hello,

since weeks I'm trying to reduce the index (CFI) size of my NetWorker server (8.2.4.5). Currently it has a size of appr. 2,5 TB.

I have six clients which holds over 50% of this capacity. They are all NDMP clients. Three months ago browse policy and retention policy were set to "2 Years". I then changed the browse policy to "Quarter" and I also change the browse retention of every saveset from "2 Years" to "Quarter".

The plan was to reduce the index with this action which did not work. The index keeps growing and on a weekly basis I need to expand the /nsr on the server.

Has anyone an idea how to reduce the index size?

Cheers

Jan

Tags (2)
0 Kudos
12 Replies
bingo.1
4 Tellurium

Re: /nsr/index grows and grows and grows

Browse & Retention Policies are relative periods - when they are applied to a backup, they will be converted to absolute days/timestamps.

There are a few ways to reduce the indexes. They are all save set based operations using 'nsrmm'.

To get the ssid & cloneid (important when you have clones), use 'mminfo':

  mminfo -q "your_query_pameters" -r "ssid, cloneid" -xc/ > outfile

If you use mminfo to report more than 1 attribute, you must delete the headline of the output file before you proceed.

You then either redefine the browse date for the save set or set the save set to 'recoverable'.

For both methods it makes sense to use the command line to generate SSID which you then can process via scripts to the 'nsrmm' command (as a precaution, you cannot use SSID list files as input file).

   nsrmm –o recoverable  –y –S ssid[/cloneid]

   nsrmm –S ssid[/cloneid] –w browse-time –y

Then run 'nsrim' or wait until NW will do it by itself. 

0 Kudos
JayJay9882
2 Iron

Re: /nsr/index grows and grows and grows

Hi bingo,

three month back where I changed the browse policy from "2 Years" to "Quarter", I also changed every saveset with nsrmm. But I did not run the nsrim after that. I will do this now and see if the size of /nsr/index will get smaller.

Thanks!

0 Kudos
bingo.1
4 Tellurium

Re: /nsr/index grows and grows and grows

??? - index management should be started by the NW server itself (once a day, if I remember correctly).

Please verify the status of your save sets and their browse and retention dates.

0 Kudos
JayJay9882
2 Iron

Re: /nsr/index grows and grows and grows

Yes, you are right.

But still I don't why the index grows so much. The oldest save set which I can browse is 3 month (quarter) and my index is still getting bigger. I'm not backing up more data, even fewer (number of files) compared to three month ago. So the index should get smaller by itself. But it doesn't.

0 Kudos
bingo.1
4 Tellurium

Re: /nsr/index grows and grows and grows

Please run the following command:

   mminfo -q "client=your_client,savetime>-3months" -r "client,name,level,savetime(25),sumsize,sumflags,ssbrowse,ssretent,volume" -ot

and let us know the output.

0 Kudos
JayJay9882
2 Iron

Re: /nsr/index grows and grows and grows

Ok, I did that and the output brought back appr. 1000 lines.

So I'm gonna share a few lines. There are plenty of saveset which have a browse retention longer than three months from now (there should be no saveset with a browse retention longer than 01/30/2018).

name                        lvl date       time       size        fl       browse   retent
/bfv49_02_mi_0_ckpt         full    10/25/17 18:16:52 1476 GB cbNs 10/28/19 10/28/19
/bfv49_21_mi_0_ckpt         full    10/25/17 18:18:00 2948 GB cbNs 10/29/19 10/29/19
/bfv49_21_mi_0_ckpt         full    10/25/17 18:18:00 1376 GB tbNs 10/29/19 10/29/19
/bfv49_21_mi_0_ckpt         full    10/25/17 18:18:00 1572 GB hbNs 10/29/19 10/29/19
/bfv49_21_mi_0_ckpt         full    10/25/17 18:18:00 2948 GB cbNs 10/29/19 10/29/19
/bfv53_03_mi_0_ckpt         full    10/25/17 18:32:31  51 GB cbNs 01/25/18 10/25/19
/bfv53_03_mi_0_ckpt         full    10/25/17 18:32:31  51 GB cbNs 01/25/18 10/25/19
/bfv11_02_mi_0_ckpt         full    10/25/17 18:39:12 770 GB cbNs 10/28/19 10/28/19
/bfv11_02_mi_0_ckpt         full    10/25/17 18:39:12 770 GB cbNs 10/28/19 10/28/19
/bfv11_02_mi_0_ckpt         full    10/25/17 18:39:12 770 GB cbNs 10/28/19 10/28/19
/bfv65_07_mi_0_ckpt         full    10/25/17 19:05:38  36 GB cbNs 01/25/18 10/25/19
/bfv65_07_mi_0_ckpt         full    10/25/17 19:05:38  36 GB cbNs 01/25/18 10/25/19
/bfv71_02_do_0_ckpt         full    10/26/17 18:12:43  29 GB cbNs 01/26/18 10/26/19
/bfv71_02_do_0_ckpt         full    10/26/17 18:12:43  29 GB cbNs 01/26/18 10/26/19
/bfv61_01_do_0_ckpt         full    10/26/17 18:12:46 180 GB cbNs 01/26/18 10/26/19
/bfv61_01_do_0_ckpt         full    10/26/17 18:12:46 180 GB cbNs 01/26/18 10/26/19
/bfv49_01_do_0_ckpt         full    10/26/17 18:12:57 4066 GB cbNs 10/28/19 10/28/19
0 Kudos
bingo.1
4 Tellurium

Re: /nsr/index grows and grows and grows

So we now know that the brows/retention dates are in fact longer than expected.

Sometime they are equal but none of them passed the browse data yet.

Consequently their CFI has not been released yet.

So far only you might know why this is the case because only you know your configuration.

May I suggest you take one specific (older) save set and try to manipulate him with nsrmm as I suggested.

Let's see whether the 'cleanup' works at least.

0 Kudos
JayJay9882
2 Iron

Re: /nsr/index grows and grows and grows

So, I did find appr. 1000 save sets which had a browse retention with something going until 2019. I changed these 1000 save sets to quarter (01/30/2018) with nsrmm.

I the double checked with mminfo and all the save sets above are until 01/30/2018 now.

I hope this gives me a little air to breath on the /nsr/index.

0 Kudos
JayJay9882
2 Iron

Re: /nsr/index grows and grows and grows

I also discovered that I have thousands of save sets with a browse policy which is in the past. I do not understand this at all.

These save sets belong to backups which were cloned to a tape library.

0 Kudos