[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

425.0. "not in an active group / bootstrap" by BRSDVP::DUPLICY (Bruno DUPLICY) Wed Feb 19 1997 11:21

	Hello,


I am installing CA unicenter Workload(scheduler) at a customer site.

Now every backups are scheduled via that product. It means that the Group
attribute is set to disable for every group.

Since this moment I get the followinf in the log file:

  -- Successful Save Set --
  nsrclient: list of saveset
              ...
              ...
              ...
 *nsrserver:index Saving server index because server is not in active group
  nsrserver: /var/nsr/index/nsrserver level 1 ... 6files
  nsrserver: bootstrap level ... 13files


Is it normal that the server is saving his bootstrap and index for each
client ?

How can I disable that, and disable the printing of the bootstrap for each 
client completion ?
(actually the PRINT field for each client is set to a non-existing printer)


        Thanks and regards,             Bruno
[End of file]
T.RTitleUserPersonal
Name		DateLines
425.1NetWorker is designed that wayDECWET::EVANSNSR EngineeringWed Feb 19 1997 12:4824
>Is it normal that the server is saving his bootstrap and index for each
>client ?
>
    yes.

>How can I disable that, and disable the printing of the bootstrap for each 
>client completion ?
>(actually the PRINT field for each client is set to a non-existing printer)

 by doing manual saves from each client (via cron perhaps). Unfortunately,
 should you/customer do this, there will be no index images saved to tape,
 thus should *anything* happen to the disk index images, you are toast.

  To disable the "printing" of the bootstrap info is ill advised because
 here is what you would have to do when the index files got blown up:
   find the latest bootstrap saved by using scanner, and waiting for
   (perhaps) hours for one number to appear on the listing. Start a
   recoverindex with that number to get the server index file back, then 
   do recovers to get the various client index files back.
 versus:
   look up the bootstrap number from email/printout. Start recoverindex...

 Howver, if you *really* wanted to disable this, then perhaps alter the
 savegroup completion notification to do *nothing*, or go to /dev/null...
425.2Advice...DECWET::FARLEEInsufficient Virtual um...er....Thu Feb 20 1997 11:4122
Alternatively, you could perhaps create a savegroup containing
*only* the server, and allow that to be scheduled by NetWorker.
This way, the bootstrap save will happen as part of that savegroup,
and will not happen on any of the others which you are scheduling.


The saving of the "bootstrap", or server index files is a very important
operation for disaster recovery.  That is why the server goes to such trouble
to make sure it happens.  If the server is part of an active savegroup, then
the bootstrap save will happen at that time.  Otherwise, savegroup will
save it whenever it gets a chance, because it cannot assume that whatever
external event is causing the savegroup to run will ever cause the bootstrap 
to run.

I would urge you in the strongest possible terms *NOT* to disable the
savegroup completion messages. *EVER*.  If you do this, you will have NO way
of finding out if some of your saves start failing.

Believe me, finding out that your saves haven't been running correctly
by attempting an emergency disaster recovery is *NO FUN*.

Kevin