| 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 | 
    Hello,
    
    I've configured one group with two clients. The clients use the same
    pool and schedule policy.
    
    In the customize - Groups I've defined:
    
    	Autostar: Enable
    	Start time: 11:12
    
    The schedule has full backup on monday and skip on thuesday.
    If I enable the group on thuesday I see the following messages:
    
    Mon 11:12:02 savegroup info: starting group2 (with 2 clients)
    Mon 11:12:03 savegroup info:
    opale.mln.dec.com:/usr/var/nsr/index/opale.mln.dec.com no cycles found
    in media db; doing full save
    Mon 11:12:05 opale.mln.dec.com:/usr/var/nsr/index/opale.mln.dec.com
    saving to pool 'pool2' (label2.003)
    Mon 11:12:09 opale.mln.dec.com:/usr/var/nsr/index/opale.mln.dec.com
    done saving to pool 'pool2' (label2.003)
    Mon 11:12:14 opale.mln.dec.com:bootstrap saving to pool 'pool2'
    (label2.003)
    Mon 11:12:17 opale.mln.dec.com:bootstrap done saving to pool 'pool2'
    (label2.003)
    Mon 11:12:23 savegroup notice: group2 completed, 2 clients (All
    Succeeded)
    Mon 11:12:24 index notice: nsrim has finished checking the media db
    
    
    The directory isn't saved but the index is.
    
    I expected nsr to completely skip the backup without doing any
    activity.
    
    Thanks,
    Gea
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 449.1 | info needed | MLNCSC::VOCI | Thu Mar 06 1997 08:05 | 7 | |
|     Any news on this?
    
    The customer is wondering if this will delay his backups since he has
    about 120 clients.
    
    Thanks,
    Gea
 | |||||
| 449.2 | what verson of NetWorker, please. | DECWET::EVANS | NSR Engineering | Thu Mar 06 1997 11:24 | 0 | 
| 449.3 | versions | MLNCSC::VOCI | Fri Mar 07 1997 00:59 | 2 | |
|     Digital Unix 4.0b
    Networker 4.2B
 | |||||
| 449.4 | hmmm, next version does nothing | DECWET::EVANS | NSR Engineering | Fri Mar 07 1997 11:04 | 20 | 
| I created a "skip always" schedule, and applied it to my client, and did a group start-now for that 1 client. Nothing happened. This is using the next version of NetWorker. With V4.2B, I get: Fri 10:57:38 savegroup info: starting mrcofe (with 1 client) Fri 10:57:39 savegroup notice: mrcofe completed, 1 client (All Succeeded) Fri 10:57:41 index notice: nsrim has finished checking the media db in the GUI, and in the savegroup completion I get: --- Successful Save Sets --- mrcofe.zso.dec.com: All level=skip, 0 KB 00:00:00 0 files mrcofe.zso.dec.com: /var/nsrCQ/index/mrcofe.zso.dec.com level=skip,0 KB 00:00:00 0 files (all successful). Can you post your savegroup completion (part that applies?) | |||||
| 449.5 | MLNCSC::VOCI | Mon Mar 10 1997 00:58 | 4 | ||
|     You'll find my savegroup completition in the original note.
    I tested only the GUI interface.
    
    Gea
 | |||||
| 449.6 | Was this the first time you saved the client? | DECWET::GRAHAM | Mon Mar 10 1997 09:45 | 9 | |
| If you had not saved the client before, it may have ignored the save level because it didn't have anything in the client's index. I know that if a level 1-9 save is specified in the schedule the first time a client is saved, a full will be forced. You can further check this by doing a full savgroup of a new client before specifying a skip in the schedule. Debbie | |||||