Events During a Scheduled Backup

When you configure a backup group on the Backup server, you schedule a start time for the backup group. The nsrd server daemon starts the server's savegrp program for the backup group at the scheduled time.

The savegrp program queries the client resources configured on the Backup server to determine:

• Which clients configured on the server are members of the scheduled group

• What level of backup (save) to perform

  How many save sets to run concurrently, determined by the parallelism value set on the Backup server

• When the most recent backup of the group occurred

If any of this information is not available on the Backup server, savegrp sends a request to the nsrexecd client-side daemon to run savefs on each client assigned to the backup group to gather the necessary details.

The savefs program tells savegrp which objects to back up for the client. After savegrp receives information about the objects to back up, savegrp assembles a work list for the server. The work list specifies the order in which clients are contacted for backup. The order of the work list is determined by the Client Priority attribute in the Clients resource. The client with the lowest value in the Client Priority attribute is contacted first.

If problems were encountered with the client file index during the previous backup session, nsrd invokes the nsrck daemon to check the consistency and state of the Backup server's client file indexes and media database. Then, nsrd starts the nsrindexd client file index insertion daemon.

The savegrp program contacts the first client on the server's work list. The client's nsrexecd is invoked and starts a save session of the first save set listed on the server's work list. The save program passes to nsrd all save criteria, such as group, client, save sets, storage node affinity, and level of the save data. With this information, nsrd determines the pool of volumes that will store the data and forwards the information to the appropriate media daemon, on either the Backup server or on a storage node controlled by the Backup server.

The nsrmmd media daemon:

• Sends a message to the console of the Backup server, requesting a mount of the media assigned to the volume pool indicated by nsrd

• Writes the data sent by save to storage media

• Forwards storage information to nsrmmdbd for recording in the Backup server's media database

Any time there is a lull in save set activity from the client, the Backup server attempts to find another save set in the group to keep the process moving. The savegrp program attempts to concurrently back up as many save sets as possible, up to the limit set by the parallelism attribute in the Backup server's configuration, to use the backup devices to their maximum potential.

The savegrp program repeats the process for each item on the server's work list until all clients in the group are backed up. Before the savegrp is completed, if the Backup server is part of the group being backed up or the server is not part of any enabled group, nsrim is invoked and the Backup server's bootstrap file is backed up. When the bootstrap backup is completed, a bootstrap printout is sent to the default printer configured for the Backup server. Keep the bootstrap printout in a safe place in case you need to restore the Backup server.

The final results of the savegrp execution are sent back to the server and are included in the savegroup completion report, which is sent through email to root.

Figure A-1 shows how all the Backup client and server daemons and programs interact during a scheduled save.

Figure A-1 How Backup Daemons and Programs Interact During a Scheduled Save