Solstice Backup Server Recovery (pre 6.x)

This procedure is used in recovering from the loss or corruption of a Solstice Backup (SBU) server's critical files including the server's index, the media index, and the server's resource files. Typical events causing such disasters are accidental removal of these files by a user or a disk crash on the SBU server itself.

NOTE: This procedure is for Solstice Backup version 4.x and 5.x only!

  1. Stop (SBU) daemons
    # /usr/sbin/nsr/nsr_shutdown -aq
  2. Move the OLD SBU configuration and index files out of the way
    # mv /nsr /nsr.old
  3. Start SBU daemons
    # /etc/init.d/networker start
  4. Recreate client index (server)
    # /usr/sbin/nsr/nsrck -c
    NOTE: You may get messages that the client index already exists for the SBU server, if so you can ignore this message.
  5. Rewind the tape
    # mt -f /dev/rmt/0 rewind
    (replace 0 with whatever tape device you use)
  6. Get bootstrap information from tape If you already have the bootstrap information to hand (ie from the SBU bootstrap reports) you can skip to step 7 You will manually need to mount the volume with the bootstrap into the tape drive

    Note: If you are using an autoloader or jukebox, you'll need to use the front panel on the library to manually load the desired tape, see your libraries user guide for detilas on how to perform this operation.

    # /usr/sbin/nsr/scanner -B /dev/rmt/0bn
    (replace 0 with whatever tape device you use) NOTE: Always specify a non-rewind device Example output ...
    scanner: no `NSR device' with the name of `/dev/rmt/0hbn' found
            scanner: scanning 8mm 5GB tape merrin.022 on /dev/rmt/0hbn
            scanner: done with 8mm 5GB tape merrin.022
            scanner: Bootstrap 25348 of 10/06/99  3:32:06 located on volume
            merrin.022, file 90.
    Where SSID (SaveSet ID) is: 25348 File Number: 90
  7. Recover the servers online and media indexes
    # /usr/sbin/nsr/mmrecov
    - specify the 'bootstrap save set id' from the scanner output - specify the 'file number' from the scanner output - leave the 'starting record number' as default
  8. Monitor nsrindexasm processes Once the mmrecov has finished it passes control to the index daemon, which in turn rebuilds the indexes ... NOTE: YOU MUST LET THIS PROCESS FINISH PRIOR TO CONTINUING
  9. Stop SBU daemons
    # /usr/sbin/nsr/nsr_shutdown -aq
  10. Recover the resource files
    # cd /nsr
    # rm -rf res
    # mv res.R res
  11. Restart SBU daemons
    # /etc/init.d/networker start
    If your SBU Server also backs up clients, then the following steps are needed to recover the CLIENT indexes
  12. Start nwrecover program Select and mark the NetWorker directory for recovery Deselect the following directories and files before starting the recover
    • /nsr/index/
    • /nsr/res
    • /nsr/mm
    Click the Start speedbar button to begin recovery Once the client recovery has completed, stop and restart the SBU daemons to give the recovered data a clean start.
  13. Stop SBU daemons
    # /usr/sbin/nsr/nsr_shutdown -aq
  14. Restart SBU daemons
    # /etc/init.d/networker start