NAME

fdp − create, or restore from, a full file system archive

SYNOPSIS

fdp −B [−dovAENS] [−c count] bkjobid odpname odpdev odplab descript

fdp −RC [−dovAENS] [−c count] odpname odpdev redpname redev rsjobid descript

DESCRIPTION

The fdp command is invoked as a child process by other shell commands.  The command name, fdp, is read either from the bkhist.tab file or the bkreg -m command and option.  The -B, -R, and -C options are passed to fdp by the shell commands backup, and restore.  The other options are passed from the bkhist.tab file or the bkreg -p command and option.  The arguments are sent to fdp from various locations in the backup service. 

fdp −B is invoked as a child process by the backdaemon command to perform a backup of the data slice odpdev (the originating data slice).  All blocks in the data slice are archived.  The resulting backup is created in the format described on dd(1).  The backup is recorded in the backup history log, /etc/bkup/bkhist.tab. 

fdp −RC is invoked as a child process by the rsoper command to restore the entire data slice from an archive created by fdp −B.  The data slice archive is assumed to be in the format described on dd(1).  dd(1) format. 

The arguments to fdp are defined as follows:

bkjobid the job id assigned by backup.  The method uses the bkjobid when it creates history log entries. 

odpname the name of the data slice that is to be backed up.  Unused by fdp, but supplied by backup for command-line compatibility with other archiving methods. 

odpdev the name of the block special device on which the data slice resides. 

odplab the volume name on the file system [see labelit(1M)].  Unused by fdp, but supplied by backup for command-line compatibility with other archiving methods. 

descript is a description for a destination device in the form:

dgroup:dname:dchar:dlabels

dgroup specifies a device group [see devgroup.tab(4)]. 
dname specifies a particular device name [see device.tab(4)]. 
dchars specifies characteristics associated with the device.  If specified, dchar overrides the defaults for the specified device and group.  [See device.tab(4) for a further description of device characteristics]. 
dlabels specifies the volume names for the media to be used for reading or writing the archive. 

rsjobid the job id assigned by restore. 

redev if non-null, the slice to be restored to instead of ofsdev.

redpname unused, but provided for consistency with other methods. 

Options

Some options are only significant during fdp −B invocations; they are accepted but ignored during fdp −R invocations because the command is invoked and options are specified automatically by restore.  These options are flagged with an asterisk (∗). 

c∗count Archives or restores only the first count (512 byte) blocks of data in the data slice. 

d∗ Inhibits recording the archive in the backup history log. 

o Permits the user to override media insertion requests [see getvol(1M) and the description of the −o option]. 

v∗ Validates 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 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 Establishes automated mode, (that is, does not prompt the user to insert or remove media). 

E∗ Reports an estimate of media usage for the archive; then performs the backup. 

N∗ Reports an estimate of media usage for the archive; does not perform the backup. 

S Displays 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 is more complex than a simple fork/exec or pipe.  The backup command is responsible for all interactions with the user, either directly, or through the bkoper command.  Therefore, fdp 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, filenames, periods, status, and so on) to backup. 

DIAGNOSTICS

The exit codes for fdp are the following:

0 successful completion of the task

1 one or more parameters to fdp are invalid. 

2 an error has occurred which caused fdp to fail to complete all portions of its task. 

FILES

/etc/bkup/bkexcept.tab
lists the files that are to be excluded from an incremental file system backup.

/etc/bkup/bkhist.tab lists the labels of all volumes that have been used for backup operations. 

/etc/bkup/rsstatus.tab
tracks the status ofall restore requests from users.

/etc/bkup/bklog logs errors generated by the backup methods and the backup command

/etc/bkup/rslog logs errors generated by the restore methods and the restore command

$TMP/filelist$$ temporarily stores a table of contents for a backup archive. 

SEE ALSO

backup(1M), device.tab(4), fdp(1), ffile(1), fimage(1), getvol(1M), incfile(1), labelit(1M), libbrmeth(3), prtvtoc(1M), rsoper(1M)

  —  System Administration Utilities