| 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 | 
    Hi,
    
    I'm doing a recovery test and I'm in a loop.
    
    recover> add /
    recover> delete /vmunix
    recover> force 
    recover> recover
    
    This is as per the docs..
    
    The problem comes when it is recovering /var/nsr/mm/mmvolume. It looks
    as if mmvolume is spread across 2 tapes. So, nsr starts to recover
    mmvolume (overwriting the existing file), gets halfway, asks for the
    next tape; but when it goes to mount this tape it checks it media database 
    , which is mmvolume (and now corrupt) and so bombs out saying that the
    new tape is not inn it's mmvolume file.....catch22.
    
    The recovery screen says:
    nsrmmdbasm -r ./var/nsr/mm/mmvolume
    ./var/nsr/mm/mmvolume:file exists, overwriting
    >then stops.
    
    ls /var/nsr/mm/
    -rw-r--r--  1 root  system  835584  Mar 11 18:51  mmvolume
    -rw-------  1 root  system  565248  Mar 11 18:37  mmvolume.r
    -rw-r--r--  1 root  system 1318912  Mar 11 18:30  mmvolume.I_SAVED
    
    nwadmin says:
    volume I_UNIX.001 ssid (12216) NOT in media index
    
    Is this just bad luck or can I exclude mmvolume from the recvoery?
    
    Itried this:
    recover>delete /var/nsr
    '/var/nsr' not marked for recovery
    
    Any thoughts???
    
    Regards,
    Richard Carter. ([email protected])
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 476.1 | DECWET::RWALKER | Roger Walker - Media Changers | Tue Mar 11 1997 11:35 | 2 | |
| Refer to the procedures documented in the nsr_crash man page and use mmrecov to get your media indexs back. | |||||
| 476.2 | exclude /var/nsr/index/<nsr_server> from recover? | CHEFS::CARTERR | Bemused of Basingstoke | Thu Mar 13 1997 01:33 | 11 | 
|     Hi,
    
    I'm using 3.2 and mmrecov isn't available.
    
    I've used recoverindex to get back my indexes O.K.; but I'm wondering
    if it's a good idea to exclude the nsr server index directory from the
    complete recovery?  I didn't see this mentioned in nsr_crash.
    
    Regards,
    Richard.
    
 | |||||
| 476.3 | Yes | DECWET::RWALKER | Roger Walker - Media Changers | Thu Mar 13 1997 09:55 | 10 | 
| You should either skip or relocate any files under /nsr. It's been too long since I played with 3.2 so I'm not sure what is documented in which manual. I'm fairly sure that the disaster recovery process is in the one of the manuals, user, admin, or adendum. You might want to relocate a file like nsr.res if your current one doesn't have all the configuration that the one on tape does. After the recovery shutdown NetWorker and move the recovered files, then restart NetWorker. | |||||
| 476.4 | Thanks! | CHEFS::CARTERR | Bemused of Basingstoke | Fri Mar 14 1997 01:04 | 2 | 
|     Thanks!
    Richard.
 | |||||