I am confused about the pathnames you mentioned. On a NW 8.2.4. server they should read
/nsr/logs/sg
/nsr/res//statistics
Even if you have another version they should reside under their appropriate subdirectory.
But yes, deleting that information will not harm your configuration.
However, before you do that you should check/verify why they became so big:
- Obsolete but not yet deleted information
I do not remember each detail with respect to the behaviour of older versions. However, I would urge you to install a new NW software version, if possible.
I don't know exactly. But I think these values are controlled by NMC:
These are the obvious default values:
To compare jobs before and after updates, I have set our jobsdb retention to 30 days.
We are running about 9-10k jobs daily - the jobs db is only about 880MB in size.
/nsr/logs/sg about 785MB
/nsr/res/statistics 2GB
Also be aware that with the upgrade NW will begin a new jobs db - the old directory will be renamed an a timestamp will be appended. With a retention of 24 hours you might not even have noticed the difference:
The NMC data retention refers to the data that is stored in the NMC database.
This is the data that is collected from the NetWorker servers that NMC is used to connect to, and this data is stored under the NMC path... not the NetWorker path. Whenever this NMC data is collected or removed has no impact on the space that is used by the NSR subdirectories... (unless you actually installed NMC under /nsr)
Suggest taking a detailed look at the /nsr structure to see how much space each subdirectory is consuming.
You can move some or all of the client file index database directories to different local or SAN partitions. Caveat here is that if you want to recover a CFI, the nsrck process will recover back to the location that it was backed up from.
/nsr/res/statistics:
You did not mention what NetWorker you are using. Prior to 8.2.4, this directory was used to collect and store statistical information. This database would keep growing, and only recourse was to delete this database.
Between 8.2.5 and 9.0.x, this database was not used.
With NetWorker 9.1.x, NetWorker set a one year retention on this data, so this database would grow up to a certain size before stabilizing.
/nsr/logs:
Here, there will be some log files that can grow endlessly until deleted or renamed. Example: /nsr/logs/messages. To remove these files, stop the NetWorker services first. Alternatively, convert these to compressed files and move them so that these logs can be saved for future review.
/nsr/tmp:
This directory is used by the NetWorker application for a number of different functions. For this reason, in my opinion and experience, please do not delete this directory unless you know what you are deleting and why. This directory can contain, and not limited to:
database lock files
Certain versions will have the savegroup (progress files and completion reports) logs stored under /nsr/logs/sg and /nsr/logs/sec. If this is deleted, then you will lose the ability to look at the recent savegroup completion reports.
NDMP index temp files... created during NDMP backups. eg) /nsr/tmp/FileIndex[ssid]. These subdirectories can consume a lot of space, and can be deleted if NetWorker is not running.
/nsr/res/jobsdb
This is the NetWorker Jobs database. This size is controlled by the number of days the data is retained. Default is 3 days. Also, depending on version, you can also control the maximum size.
I have noticed some users would make backup copies of this database, and then keep it indefinitely. These older copies are not useful and can be deleted.
I have noticed that some users will make backup copy or copies of this folder. Which is good practice before making or adding changes to how NetWorker is configured. However, since the jobs database is located within /nsr/res (plus any other back up copies of jobsdb), these old jobsdb is just consuming space, since it is unlikely you would replace the current jobsdb with an older copy.
If you have backup copies of /nsr/res, take a look at their sub-directories and remove what is unneeded, such as the older copies of jobsdb. Check the current /nsr/res for backup copies of jobsdb too.
/nsr/tmp (revisited)
Some users will also rename /nsr/tmp so that NetWorker will create a new /nsr/tmp directory. These older copies can almost certainly be deleted.
If you are unsure if you should delete, then convert to a compressed file so that uses minimal space, and move to a different disk.
I'm on NetWorker v8.2.4 and think that /nsr/res/statistics is a relict from a previous version. I renamed it and created a new directory named staistics which is empty since then.
bingo.1
2.4K Posts
0
May 3rd, 2017 03:00
I am confused about the pathnames you mentioned. On a NW 8.2.4. server they should read
/nsr/logs/sg
/nsr/res//statistics
Even if you have another version they should reside under their appropriate subdirectory.
But yes, deleting that information will not harm your configuration.
However, before you do that you should check/verify why they became so big:
- Obsolete but not yet deleted information
I do not remember each detail with respect to the behaviour of older versions. However, I would urge you to install a new NW software version, if possible.
JayJay9882
2 Intern
•
161 Posts
0
May 3rd, 2017 05:00
Hi,
you are absolutely t know why I collect so many historic informations. I just upgraded to v8.2 SP4 and during that I recognised the large folders.
My JobDB retention is set to 24 hours. Where else can I configure how long statistics etc. should be kept?
bingo.1
2.4K Posts
0
May 3rd, 2017 06:00
I don't know exactly. But I think these values are controlled by NMC:
These are the obvious default values:
To compare jobs before and after updates, I have set our jobsdb retention to 30 days.
We are running about 9-10k jobs daily - the jobs db is only about 880MB in size.
/nsr/logs/sg about 785MB
/nsr/res/statistics 2GB
Also be aware that with the upgrade NW will begin a new jobs db - the old directory will be renamed an a timestamp will be appended. With a retention of 24 hours you might not even have noticed the difference:
wlee
263 Posts
0
May 3rd, 2017 07:00
The NMC data retention refers to the data that is stored in the NMC database.
This is the data that is collected from the NetWorker servers that NMC is used to connect to, and this data is stored under the NMC path... not the NetWorker path. Whenever this NMC data is collected or removed has no impact on the space that is used by the NSR subdirectories... (unless you actually installed NMC under /nsr)
wlee
263 Posts
0
May 3rd, 2017 08:00
Suggest taking a detailed look at the /nsr structure to see how much space each subdirectory is consuming.
You can move some or all of the client file index database directories to different local or SAN partitions. Caveat here is that if you want to recover a CFI, the nsrck process will recover back to the location that it was backed up from.
/nsr/res/statistics:
/nsr/logs:
Here, there will be some log files that can grow endlessly until deleted or renamed. Example: /nsr/logs/messages. To remove these files, stop the NetWorker services first. Alternatively, convert these to compressed files and move them so that these logs can be saved for future review.
/nsr/tmp:
This directory is used by the NetWorker application for a number of different functions. For this reason, in my opinion and experience, please do not delete this directory unless you know what you are deleting and why. This directory can contain, and not limited to:
/nsr/res/jobsdb
wlee
263 Posts
0
May 3rd, 2017 19:00
/nsr/res
I have noticed that some users will make backup copy or copies of this folder. Which is good practice before making or adding changes to how NetWorker is configured. However, since the jobs database is located within /nsr/res (plus any other back up copies of jobsdb), these old jobsdb is just consuming space, since it is unlikely you would replace the current jobsdb with an older copy.
If you have backup copies of /nsr/res, take a look at their sub-directories and remove what is unneeded, such as the older copies of jobsdb. Check the current /nsr/res for backup copies of jobsdb too.
/nsr/tmp (revisited)
Some users will also rename /nsr/tmp so that NetWorker will create a new /nsr/tmp directory. These older copies can almost certainly be deleted.
If you are unsure if you should delete, then convert to a compressed file so that uses minimal space, and move to a different disk.
JayJay9882
2 Intern
•
161 Posts
0
May 4th, 2017 03:00
Hi guys,
thanks for the replies.
I'm on NetWorker v8.2.4 and think that /nsr/res/statistics is a relict from a previous version. I renamed it and created a new directory named staistics which is empty since then.
Cheers
Jan