logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

backup_interactive - Enters interactive mode

Description

       The backupinteractive initiates an interactive session for issuing backup commands. As indicated in the
       syntax statement, the operation code (interactive) is optional.

       Several features of interactive mode distinguish it from regular mode:

       •   In  interactive  mode,  the  "backup"> prompt replaces the system (shell) prompt. The operator enters
           only a command's operation code (omitting the command suite name, backup).

       •   If the -localauth flag or the -cell argument is included  on  the  backupinteractive  command,  the
           settings  apply  to  all commands issued during that interactive session. The issuer does not need to
           type them on every command. Another consequence is that the flag and argument do not  appear  in  the
           syntax  statement  generated  by the help subcommand or -help flag on an individual command issued at
           the "backup"> prompt.

       •   The backupjobs and backupkill commands are available only in interactive mode. It is  not  possible
           to track and terminate backup operations as cleanly in non-interactive mode.

       •   It  is  not  necessary  to  enclose  strings  that  include  metacharacters in double quotes or other
           delimiters.

       •   The backup command interpreter establishes a connection to  the  Backup  Server,  Volume  Server  and
           Volume Location (VL) Server processes as it enters interactive mode, and uses the same connection for
           all commands during the session. Execution time can therefore be faster than in non-interactive mode,
           in which the command interpreter must establish a new connection for each command.

       To exit an interactive session, issue the backupquit command.

Examples

       The following example shows how the -localauth flag and -cell argument do not appear when the  helpdump
       subcommand is issued in interactive mode.

          % backup
          backup> help dump
          dump: start dump
          Usage: dump [-volumeset <volume set name>] [-dump <dump level name>]
          [-portoffset <TC port offset>] [-at <Date/time to start dump>+]
          [-append ] [-n ] [-file <load file>] [-help ]

Name

       backup_interactive - Enters interactive mode

Options

-localauth
           Constructs  a  server  ticket using a key from the local /etc/openafs/server/KeyFile file. The backup
           command interpreter presents it to the Backup Server, Volume  Server  and  VL  Server  during  mutual
           authentication. Do not combine this flag with the -cell argument. For more details, see backup(8).

       -cell <cellname>
           Names  the  cell  in which to run the command. Do not combine this argument with the -localauth flag.
           For more details, see backup(8).

       -help
           Prints the online help for this command. All other valid options are ignored.

Privilege Required

       None.  However,  backup  commands  that require privilege in regular mode still require it in interactive
       mode.

See Also

backup(8), backup_jobs(8), backup_kill(8), backup_quit(8), butc(8)

Synopsis

backup [interactive] [-localauth] [-cell <cellname>]
           [-help]

       backup [i] [-l] [-c <cellname>] [-h]

See Also