


MMRECOV(8)                                             MMRECOV(8)


NNAAMMEE
       mmrecov  -  recover a NetWorker server's on-line index and
       media index

SSYYNNOOPPSSIISS
       mmmmrreeccoovv [ --qq | --vv ]

DDEESSCCRRIIPPTTIIOONN
       The mmmmrreeccoovv command is used in recovering from the loss of
       a NetWorker 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
       NetWorker  server  itself.  The mmmmrreeccoovv command is used to
       recover the indexes and other files.  See nnssrr__ccrraasshh(8) for
       a  discussion  of  general  issues and procedures for Net-
       Worker client and server crash recovery.

       MMmmrreeccoovv is used to recover the NetWorker server's  on-line
       file  and  media  index  from  the  media (backup tapes or
       disks) when either of the server's online  file  or  media
       index  has  been  lost or damaged.  Note that this command
       _o_v_e_r_w_r_i_t_e_s the server's existing  online  file  and  media
       index.  The  MMmmrreeccoovv  command  is not used to recover Net-
       Worker clients' online indexes; you can use normal recover
       procedures for this purpose.

       The NetWorker system must be fully installed and correctly
       configured prior to using this command.   If  any  of  the
       NetWorker  software is lost, re-install NetWorker from the
       distribution files before you run mmmmrreeccoovv.  Use  the  same
       release  of NetWorker, and install it in the same location
       as it was before the software was lost.   MMmmrreeccoovv  program
       works in two phases.  First, it extracts the contents of a
       _b_o_o_t_s_t_r_a_p save set, which contains the  media  and  online
       file  indexes.   The  online  file index only contains one
       entry, for the online file index itself.   In  the  second
       phase,  mmmmrreeccoovv  will run rreeccoovveerr(8) to completely recover
       the server's online file index.  This last phase  is  per-
       formed  in  the background, so the operator can respond to
       subsequent media mount requests.

       When mmmmrreeccoovv is started, it will ask for the  device  from
       which  the bootstrap save set will be extracted.  Next, it
       will ask for the _b_o_o_t_s_t_r_a_p save set identifier.  This num-
       ber  is  found  in the fourth column (labeled _s_s_i_d) of the
       last line of the bootstrap information  sheet  printed  by
       ssaavveeggrrpp, an example of which is shown below:

       Jun 17  22:21 1992  mars's NetWorker bootstrap information Page 1

          date    time    level       ssid  file  record   volume
        6/14/92 23:46:13   full   17826163    48       0   mars.1
        6/15/92 22:45:15      9   17836325    87       0   mars.2



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        1





MMRECOV(8)                                             MMRECOV(8)


        6/16/92 22:50:34      9   17846505   134       0   mars.2 mars.3
        6/17/92 22:20:25      9   17851237    52       0   mars.3


       In  the  example  above, the _s_s_i_d of the most recent boot-
       strap save set is `1177885511223377'.  If  you  are  cloning  save
       sets, your bootstrap save set is also cloned, and you need
       to use the _s_e_c_o_n_d to last save set.   See  the  RREECCOOVVEERRIINNGG
       FFRROOMM CCLLOONNEE MMEEDDIIAA section for an example of boostrap infor-
       mation with cloned save sets.  Next, mmmmrreeccoovv  prompts  for
       the  file  and  record location of the bootstrap save set.
       Both values may default to zero if  they  are  not  known.
       The  file  and  record  locations  are the fifth and sixth
       columns of the bootstrap information sheet.  In the  exam-
       ple  above,  the  values for the file and record locations
       are 52 and 0, respectively.   Finally,  mmmmrreeccoovv  will  ask
       that the volume (`mmaarrss..33' in the example above) containing
       the selected _b_o_o_t_s_t_r_a_p save set be inserted into the spec-
       ified  device.   All  of  the  _s_s_i_d, file location, record
       location, and the physical volume must  be  determined  by
       the  user from the printed sheet, since mmmmrreeccoovv has no way
       of determining this information.  On the  other  hand,  if
       the  volume  containing the bootstrap is not known, the --BB
       option of ssccaannnneerr(8) can be used to determine the file and
       record locations.

       If the _b_o_o_t_s_t_r_a_p save set spans more than one volume, mul-
       tiple volume names are printed.  The order printed is  the
       order  required  by  mmmmrreeccoovv.   In  the example above, the
       third save  set  produced  on  6/16/92  begins  on  volume
       `mmaarrss..22'  and  spans  to  volume `mmaarrss..33'.  If a bootstrap
       save set spans volumes, mmmmrreeccoovv will ask for the  name  of
       the  device  where the next volume has been loaded when an
       end-of-volume occurs.  The volume is then scanned, and the
       bootstrap save set extracted.

       After the volume scan completes, mmmmrreeccoovv will complete.  A
       rreeccoovveerr will be running in the background,  reconstructing
       a  complete  index  from  the  save  sets generated by the
       server's save schedule.  Since the save sets may be spread
       across  multiple volumes, nnwwaaddmmiinn(8) or nnssrrwwaattcchh(8) should
       be run, and the volumes mounted as they are requested.

       When the rreeccoovveerr completes, the message "TThhee iinnddeexx iiss  nnooww
       ffuullllyy rreeccoovveerreedd" is displayed.  rreeccoovveerr can now be used in
       its normal interactive browsing  mode,  to  recover  other
       server  files,  including  other  NetWorker client on-line
       file indexes.  Once a NetWorker client's index  is  recov-
       ered, that client can start recovering its files.

       As  stated earlier, the NetWorker resource files are saved
       as part of the bootstrap save set.  If your resource files
       were also deleted, you may quickly replace them by copying
       or  moving  them  from  /nsr/res.R  to  /nsr/res.   Before



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        2





MMRECOV(8)                                             MMRECOV(8)


       restoring  them to /nsr/res, the daemons must be shut down
       (see nnssrr__sshhuuttddoowwnn(8)).

       Sometimes, it  is  neccessary  to  recover  the  NetWorker
       server  onto  a  new  machine,  for example, after a major
       hardware failure.  When this occurs, the NetWorker Licens-
       ing  software  will  detect  the move.  Once the NetWorker
       server has been moved to a new machine, it must be re-reg-
       istered  with Customer Support within 15 days of the move,
       or  the  server  will  disable  itself.   After  disabling
       itself,  you will only be able to recover files; new back-
       ups cannot be performed until the server is re-registered.
       Notifications will be sent by the NSR Registration notifi-
       cation, warning of the need to re-register the product.

RREECCOOVVEERRIINNGG FFRROOMM CCLLOONNEE MMEEDDIIAA
       If you are running mmmmrreeccoovv  with  clone  media  only,  for
       example,  at  a  remote site, you will need to perform the
       recovery using a slightly different method.  When  select-
       ing the bootstrap identifier, make sure that you are using
       the information associated with the cloned save  set:  the
       last  save  set  listed in the bootstrap output.  Consider
       the following list of save sets:

       Jun 17  22:21 1996  mars's NetWorker bootstrap information Page 1

          date    time    level       ssid  file  record   volume
        6/14/96 23:46:13   full   17826163    48       0   mars.1
        6/14/96 23:46:13   full   17826163    12       0   mars_c.1
        6/15/96 22:45:15      9   17836325    87       0   mars.2
        6/15/96 22:45:15      9   17836325    24       0   mars_c.2
        6/17/96 22:20:25      9   17851237    52       0   mars.3
        6/17/96 22:20:25      9   17851237     6       0   mars_c.3

       In the example above, the _s_s_i_d of the  most  recent  boot-
       strap save set is `1177885511223377'.  The cloned save set resides
       on _m_a_r_s___c_._3 and the values for the file and  record  loca-
       tions are 6 and 0, respectively.

       Once  mmmmrreeccoovv  recovers  the  bootstrap  save set, it will
       start pursuing other pieces of the server's  client  index
       to  complete  the  recovery.   The  cloned bootstrap knows
       about the original and cloned volumes.  If all clone  vol-
       umes  needed  are online when the index recovery proceeds,
       mmmmrreeccoovv will complete on its own.

       If some of the volumes are not online, then  mmmmrreeccoovv  will
       attempt  to  recover the index from the original volume it
       was backed up  to,  and  therefore  request  the  original
       media.   In  the  example bootstrap output above, _m_a_r_s___c_._1
       _a_n_d mars_c.3 would all  need  to  be  online.   If  volume
       _m_a_r_s___c_._3  was  the  only volume online, then mmrecov would
       also request _m_a_r_s_._1.  To finish  recovering  the  server's
       index  in  this  case,  you  need to perform the following



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        3





MMRECOV(8)                                             MMRECOV(8)


       steps:

       1.     Note what  volumes  are  needed  for  recovery  and
              delete them from the media database.

              nnwwaaddmmiinn(8)  or  nnssrrwwaattcchh(8)  lists  out the volumes
              needed for recovery in the _P_e_n_d_i_n_g messages  panel.
              Use  nnwwaaddmmiinn(8)  or  nnssrrmmmm(8) to delete the volumes
              from the media database.

              Given the scenario in the example bove  where  only
              _m_a_r_s___c_._3  was  mounted,  we  would  have  to delete
              _m_a_r_s_._1 from the  media  database,  i.e.   _n_s_r_m_m  _-_d
              _m_a_r_s_._1.

       2.     Restart  the  server to kill off the index recovery
              in progress.

              Use nnssrr__sshhuuttddoowwnn(8) to bring the server down.   Run
              nnssrrdd(8) to start the server again.

       3.     Recover the server's index via recover by save set.

              Use mmmmiinnffoo(8) to determine the save set id  of  the
              last index backup, for example

              _m_m_i_n_f_o _-_s _s_e_r_v_e_r _-_c _s_e_r_v_e_r _-_N _/_n_s_r_/_i_n_d_e_x_/_s_e_r_v_e_r _-_v _-_o _t

              Note  that  the  _-_N option should be given the full
              path to the index if it is located in  a  different
              location. For example, if _/_n_s_r_/_i_n_d_e_x_/_s_e_r_v_e_r
               is a symlink to _/_d_i_s_k_1_/_n_s_r_/_i_n_d_e_x_/_s_e_r_v_e_r_,
               you  should  specify  _-_N  _/_d_i_s_k_1_/_n_s_r_/_i_n_d_e_x_/_s_e_r_v_e_r.
              The save set id to use for recover by save set fol-
              lows  the  size  field in the mmmmiinnffoo(8) output.  In
              the following example output from mmmmiinnffoo, the  save
              set id is `1188119966'

              mars_c.002    mars       12/27/96 14:06:32  138 KB      18196 cb    9 /nsr/index/mars

              Once  you  have  the  save  set  id,  you  can  run
              rreeccoovveerr(8).  Given the information above, one would
              run the following command:

              _r_e_c_o_v_e_r _-_s _s_e_r_v_e_r _-_S _1_8_1_9_6

         When  the  rreeccoovveerr  completes, the message "TThhee iinnddeexx iiss
         nnooww ffuullllyy rreeccoovveerreedd" is displayed.

OOPPTTIIOONNSS
       --qq     Quiet.  Display only error messages.

       --vv     Verbose.  Generates debugging information.




NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        4





MMRECOV(8)                                             MMRECOV(8)


FFIILLEESS
       //nnssrr   If this was a symbolic link when the bootstrap save
              set was created, it is recovered (recreated) uncon-
              ditionally by mmmmrreeccoovv.

       //nnssrr//rreess
              This directory and its contents are saved  as  part
              of  the  bootstrap save set.  MMmmrreeccoovv restores this
              directory, and then renames it to //nnssrr//rreess..RR.   The
              original   directory   is  temporarily  renamed  to
              //nnssrr//rreess..oorrgg while the bootstrap save set is  being
              recovered.

       //nnssrr//mmmm//mmmmvvoolluummee
              The NetWorker server's media index saved as part of
              the bootstrap save set, and unconditionally  recov-
              ered by mmmmrreeccoovv.

       //nnssrr//iinnddeexx//_s_e_r_v_e_r_n_a_m_e//ddbb
              The  NetWorker server's on-line file index saved as
              part of the bootstrap save set, and unconditionally
              recovered by mmmmrreeccoovv.

BBUUGGSS
       The  name  mmmmrreeccoovv  is  misleading, as a result mmrecov is
       often  used  when  it  is  not  needed.    A   name   like
       "recover_server_index_or_media_index_when_either_is_miss-
       ing" is more descriptive.  Note that any part of the boot-
       strap  save  set  contents  are  recoverable  using normal
       recover procedures  provided  that  the  server's  on-line
       index and media index are intact.

       To  recover  files  that are not in the on-line file index
       (for example, files saved after the last run of  ssaavveeggrrpp),
       ssccaannnneerr must be used to rebuild the media and on-line file
       indexes from the contents of the volumes generated between
       the  time  of  the last run of ssaavveeggrrpp and the loss of the
       original index.

SSEEEE AALLSSOO
       mmmmiinnffoo(8), nnssrr__ccrraasshh(8), nnssrr(8), nnssrrdd(8), nnssrr__cclliieenntt(5),
       nnssrr__sscchheedduullee(5), nnssrr__sshhuuttddoowwnn(8), rreeccoovveerr(8), ssaavvee(8),
       ssaavveeffss(8), ssaavveeggrrpp(8), ssccaannnneerr(8), nnssrriinnddeexxaassmm(8),
       nnssrrmmmm(8), nnssrrmmmmddbbddaassmm(8), nnwwaaddmmiinn(8), nnssrrwwaattcchh(8),
       nnssrr__ggeettddaattee(3)

DDIIAAGGNNOOSSTTIICCSS
       TThhee iinnddeexx ffoorr _s_e_r_v_e_r wwaass NNOOTT ffuullllyy rreeccoovveerreedd
              There was an error recovering all or  part  of  the
              _s_e_r_v_e_r's  index.   Look  back through the output to
              find out what was not recovered (one or more  addi-
              tional  error  messages will be mixed in with other
              mmmmrreeccoovv status messages).  You may  need  to  retry
              the   mmmmrreeccoovv,  for  example,  in  the  case  of  a



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        5





MMRECOV(8)                                             MMRECOV(8)


              temporary resource limitation or  media  error,  or
              you  may need to resort to recovering an older ver-
              sion of the index, in the case  a  permanent  media
              error.





















































NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        6


