Beginning with NetWorker 6.2, Legato introduced a reorganisation of NetWorker's configuration database. It will be used for all NetWorker versions in the future.
Prior to 6.2, NetWorker stores all configuration information in three files:
||The NetWorker client configuration file
||The NetWorker storage node configuration file
||The NetWorker server configuration file
In a larger NetWorker environment, the last RAP databases can become very large and potentially impact NetWorker server performance, as the time needed to update the RAP files increases linearly with the number and size of the resources.
In NetWorker 6.2, each resource of the
\nsr\res\nsrjb.res entries are saved as individual files instead of within a single, expanding file. However, \nsr\res\nsrla.res will not change. There are good reasons for these changes:
- It enables multiple database reads,
- It eliminates access delays during modification of resource information,
- It ensures that database queries are fast, regardless of how large the database grows as client resources are added,
- The reading of a resource is faster because the exact resource can be addressed. There is no need to read through a very large
*.res file any longer.
Here is an example to explain the speed improvement of a NetWorker data zone with 1130 resources:
- Shutdown using NetWorker 6.1.1 44.86 s
- Shutdown using NetWorker 6.2.0 6.93 s
Please not that the startup may take a bit longer as more files need to be read. Here are the values for the same configuration:
- Startup using NetWorker 6.1.1 0.40 s
- Startup using NetWorker 6.2.0 1.13 s
The new directory structure looks like this:
Here is how it looks under windows explorer
The structure of the resources themselves did not change at all, each file represents a single resource and it is nothing else but a text file. Their contents is visible using a text editor that can deal with UNIX type text files (for example
write.exe). However, as before, you usually configure the resource using the NetWorker Administrator GUI (
As new resources are added (for example, clients, groups, pools, etc.) a new file is created in one of these directories. There are some notes with respect to this new database:
- The filenames seem to be random. As a consequence, the filename will not tell you which resource it defines.
- You cannot follow a structure any more that lets you predict, in which directory a new resource will be saved.
- Limited tests did not show new directories created.
Reviewing resource configuration
There are several options available to reviewing the contents of the RAP configuration
- Use the NetWorker Administrator GUI as before
nsradmin has been modified to work with the new nsrdb structure
nsrsup.bat has been modified to use nsradmin to automatically include the resource configuration in the nsr_support output file.
nsrsup.bat has been modified to use
nsradmin -s localhost when the NetWorker server is up, and it will use
nsradmin -d <path> when the NetWorker server is down.
- Use the windows copy command to append all of the files together into one file that could be search:
copy .\00\*.* + .\01\*.* + .\02\*.* + .\03\*.* + .\04\*.* + \\
.\05\*.* + .\06\*.* + .\07\*.* + .\08\*.* + .\09\*.* res.txt
NOTE: With all of the above methods, the listing of resources in the output file is always in the order that these resource files appear in the directories.
Searching the resource files
If you need to determine which resource file relates to a specific resource you will need to use the native tools for the OS to relate a specific file to a resource.
Under Windows, use the Search...Files or Folders utility.
- Enter what you want to search for in the Containing text field
- Modify the Look in field to specify to only search the ..\nsr\res\nsrdb directory tree.
Here is an example
You will see the search results like this:
Corrupted Resource file
If NetWorker detects (upon startup) that it cannot read one of the resource files (ie: it is corrupt), the following proess flow occurs:
There is no procedure or utility provided that would take the converted nsrdb directory and recreate the nsr.res and nsrjb.res files. You must recover the bootstrap if this is required.
Also, please keep in mind, that customized scripts using nsradmin to modify the resource files will not work any longer.