Networker vital data is backuped up every time you backup the particular client (backup of indexes) and bootstrap is backuped up every time you backup data from Networker server. You can also start boostrap/index backup by running group containing Networker server as a client:
savegrp -O group_name

Thanks a lot for the valuable information, but where should i run the savegrp -O group_name command (in the server"command line", or from the networker management console interface?and what should i write in the save set field in the client resource?

Hi,

When you launch backup for client Backup Server, and as save set you have added /nsr/index, only will backup tree, because there is a directive for every client, called nsr.dir, which, has value: +skip: * .?* , this way, the index are not solved when you backup Backup Server.

The index are solved when backup for clients have finished, but if you want to solve the index when you launch backup for Backup Server and it finishes, then you have to delete for every client the directive nsr.dir.

Regards.

Inma Bernabe.

Hi,

You have to launch #savegrp -O group_name for every group from command line Backup Server.

In save set field in the client resource, only you have to add the save set, which, you want to solve, remember that the index are in Backup Server.

Regards.

Inma Bernabe.

thanks much Inma and all,
another question, where in the administration guide 'or any other documentation" can i find such information about index, these special directives, and how to run a script "for example exprt database tables" as aprecommand in the networker and how to set the timeout of it?i have the course mannual but it is not so informative

thanks again

Administration guide and CLI manuals are good on that subject.

thanks alot,

actually i have the administration guide but where can i find those CLI manuals?i tried to search for networker CLI manuals but i got nothing

/nsr/index is the Client File Index, the database of files which Networker uses when you browse for file(s) you wish to restore. These are obviously pretty important so Networker backs them up everytime you run a backup as an index saveset for that client. Try running this command from the command line and you can see they have been backed up:

mminfo -q "name=index:myclient"

volume client date size level name
000001 myclient 02/09/08 1832 KB 9 index:myclient
etc...

index:myclient is in fact the /nsr/index/myclient directory.

You can also do just a backup of the client file indexes by using the -O switch from the command line:

savegrp -O -c myclient mygroup

- will only back up /nsr/index/myclient

Indexes are removed when they go outside of their browse time and you will need to restore the relevant /nsr/index subdirectory using the nsrck -L7 command:

nsrck -L7 -t "date when you want to see indexes from" myclient

Networker stops you backing up this data which already has its own backup mechanism by putting a file .nsr (nsr.dir on Windows) in the directory which is what is known as a local directive - this basically tells Networker at time of file system backup that this directory does not need backing up.

If you went on the course you should have been given a big thick book called Legato Networker Command Line Reference - take a look at the command savegrp in there. If you don't have it you can download it from Powerlink or you can check the man page, for example:

man savegrp

In docs section there should be something called Command Line Reference Guide.