migration(1M)                                                 migration(1M)


   NAME
         migration - move an archive from one set of volumes to another

   SYNOPSIS
         migration -B [ -dlmotuvAENS ] bkjobid ofsname ofsdev ofslab descript

   DESCRIPTION
         migration is invoked as a child process by bkdaemon(1M) to move an
         existing archive made by some other arbitrary method to a new set of
         volumes.  The existing backup history log entry of the archive is
         updated to reflect the new volumes and destination information of the
         archive.

         bkjobid is the job id assigned by backup(1M).  ofsdev is the name of
         the UNIX raw (character) device on which the archive resides.  ofslab
         is the volume label on the archive [see labelit(1M)].  descript is a
         description for a destination device in the form:

               dgroup:dname:dchar:dlabels

         dgroup specifies a device group.  dname specifies a device name.
         dchars specifies characteristics for the specified device and group
         (see device.tab(4) for a further description of device
         characteristics).  dlabels specifies the media names for the media to
         be used for the archive.

      Options
         d*        Do not update the backup history log entry for the archive.

         l*        Create a long form of the backup history log that includes
                   a table-of-contents for the archive.  This includes the
                   data used to generate an ls -l-like listing of each file in
                   the archive.

         m*        Mount the originating filesystem read-only before starting
                   the backup and remount it with its original permissions
                   after completing the backup.

         o         Permit the user to override media insertion requests (see
                   getvol(1M) -o).

         t*        Create a table of contents for the backup on additional
                   media instead of in the backup history log.

         u*        Unmount the originating filesystem before performing the
                   backup and remount it with its original permissions after
                   completing the backup.

         v*        Validate the archive as it is written.  A checksum is
                   computed as the archive is being written; as each medium is
                   completed, it is re-read and the checksum recomputed to


   8/91                                                                 Page 1

   migration(1M)                                                 migration(1M)


                   verify that each block is readable and correct.  If either
                   check fails, the medium is considered unreadable.  If -A
                   has been specified, the archiving operation fails;
                   otherwise, the operator is prompted to replace the failed
                   medium.

         A         Do not prompt the user for removable media operations
                   (automated operation).

         E*        Report an estimate of media usage for the archive; then
                   perform the backup.

         N*        Report an estimate of media usage for the archive; do not
                   perform the backup.

         S*        Generate a period (.) for every 100 (512 byte) blocks
                   read-from or written-to the archive on the destination
                   device.

      User Interactions
         The connection between an archiving method and backup(1M) is more
         complex than a simple fork/exec or pipe.  backup(1M) is responsible
         for all interactions with the user, either directly, or through
         bkoper(1M).  Therefore, migration neither reads from standard-input
         nor writes to standard-output or standard-error.  A method library
         must be used [see libbrmeth(3)] to communicate reports (estimates,
         periods, status, etc.) to backup(1M).

   DIAGNOSTICS
         If migration successfully completes its task, it exits with a 0
         status.  If any of the parameters to migration are invalid, it exits
         with a 1 status.  If any error occurs which causes migration to fail
         to complete all portions of its task, it exits with a 2 status.

         Errors are reported if any of the following occur:

         1.   -t is specified together with -A.

         2.   -A is specified together with -o.

         3.   -t is specified and the destination device does not support
              removable media.

         4.   -A is specified and more than one removable medium is required.

         5.   Unrecoverable errors occurred in trying to read or write the
              destination device.

         6.   -m is specified and the originating filesystem could not be
              mounted read-only.



   Page 2                                                                 8/91

   migration(1M)                                                 migration(1M)


         7.   -m is specified and the originating filesystem could not be
              unmounted.

         8.   -o is not specified and insufficient media names are supplied in
              descript.

         9.   -u is specified and the filesystem could not be unmounted.

         10.  -u is specified and the filesystem could not be remounted.

   FILES
         /usr/oam/bkrs/tables/bkhist.tab
         $TMP/filelist$$

   SEE ALSO
         awk(1), backup(1M), device.tab(4), getvol(1M), grep(1), labelit(1M),
         libbrmeth(3), ls(1), prtvtoc(1M), restore(1M), rsoper(1M), sed(1),
         time(2), urestore(1M).



































   8/91                                                                 Page 3