Conference decwet::networker

662.0. " bootstrap question" by EVTAI1::POUSSARD () Wed May 07 1997 03:53

	Hi,


	I would ask for a confirmation of what I say is true.


	When we save several group, and only one group contains the server
itself, it is important that this group is the last one, because bootstrap 
information must be that last information saved.

	Let's assume we have 2 groups:

		- group A containing a group of clients, but server is not in 
this group

		- group B contains the server itself

	When we saves group A, so after the data's client save completion, 
the server itself saves the clients db files on the tape ( savegrp -O ), 
so put the /nsr/index/"server"/db on the disk up_to_date to reflect the client 
databases saves.
	
	So, the group containing the server itself ( group B ) must be the 
last one,because we save the bootstrap information, and in this bootstrap 
information, we have the /nsr/index/"server"/db up_to_date file.


	If we triggers group B before group A, we will not put up_to_date
/nsr/index/"server"/db in the bootstrap information, and after, if the /nsr 
disk crash, we will not be able to recover the up_to_date clients db files.


	I think I do some confusion, but I don't know where ??



	Any clarification appreciated.


    			Gilles.

yes

It's very simple:

A bootstrap save (like any other) will create an up-to-date backup
of whatever is being backed up as of the time it is run.

If what is being backed up (in this case the indexes) changes
after you do the backup, then those changes cannot be in the
backup.

So, you are correct.  In order to make sure that you have the most
complete possible bootstrap, the savegroup containing the server
should be scheduled to run last.

Also remember that a bootstrap save cannot contain itself, as the bootstrap
saveset did not exist when the bootstrap save was performed.  Thus, after
recovery from a bootstrap save, you will not see the bootstrap which you
just recovered from.

Kevin