Defines a dump level in the dump hierarchy
Synopsis
bak adddump -level dump_level... [-expires date...] [-help]
Options
-level dump_level
Names each new dump level to be added to the dump hierarchy. Specify a full pathname for each dump level. Precede the name of each level by a /
(slash); the / (slash) is a metacharacter that separates each level in a dump level name. When defining a full dump level, precede the name of the level with a / (slash). When defining an
incremental dump level, precede the name of each dump level in name with a / (slash); the elements in the pathname preceding the last one must already exist in the dump hierarchy. The complete
pathname of each dump level must be unique within the Backup Database of the local cell.
Dump level names can have any number of elements. Each element cannot contain more than 28 characters. Complete dump level names cannot contain more than 256 characters. They can include any characters. (To avoid confusion when dump set names are created, the name should not include a period. When a dump set is transferred to tape, the fileset family name and the last component of the dump level name are joined by a period to form the name of the dump set.) When including regular expression characters, escape each character with a \ (backslash) or " " (double quotes).
-expires date
Defines the expiration date to be associated with each new dump level. Expiration dates can be specified as absolute or relative values. Absolute
expiration dates have the format
at mm/dd/yy [hh:mm]
The word at is followed by a date (month/day/year) and, optionally, a time (hours:minutes). When the system creates a dump set at this level, it assigns the specified date as the expiration date of the tape that contains the dump set. Valid values for yy are 00 to 37, which are interpreted as the years 2000-2037, and 70 to 99, which are interpreted as 1970-1999. Values between 38 and 69 cannot be interpreted because the years to which they correspond (2038-2069) exceed the capacity of the standard UNIX representation of dates (the number of seconds since 12:00 a.m. on 1 January 1970). Values between 38 and 69 are reduced to 2038.
If specified, the time must be in 24-hour format (for example, 20:30 for 8:30 p.m.). The default time is 00:00 (12:00 a.m.).
Relative expiration dates have the format
in [integery] [integerm] [integerd]
The word in is followed by a number of years (maximum 9999), months (maximum 11), and days (maximum 30), or a combination of these arguments. When the system creates a dump set at this level, it adds the specified values to the current date to calculate the expiration date of the tape that contains the dump set. At least one of the three values must be specified, and the appropriate unit abbreviation (y, m, or d) must always accompany a value. If more than one of the three is specified, they must appear in the order shown. As with absolute dates, a number of years that causes the relative time to exceed the year 2038 is effectively truncated to the number of years remaining until 2038.
If you omit this option, tapes created at the specified dump levels have no expiration dates, meaning they can be overwritten by appropriately named dump sets at any time. Although the -expires option is followed by an ellipsis, you can specify only one expiration date. (The ellipsis is included to accommodate the DFS command parser.)
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The bak adddump command defines one or more dump levels in the dump hierarchy that is stored in the Backup Database and names them as specified by
-level. Precede each different level in a dump level name with a / (slash) metacharacter. If a dump level is for full dumps, provide only its name preceded by a / (slash)
(for example, /full).
If a dump level is for incremental dumps, its name resembles a pathname listing the dump levels that serve as its parents, starting with a full dump level and proceeding (in order) down the hierarchy. The dump level's immediate parent (named by the next-to-last element in the pathname) is the reference point that determines which files are included in dump sets made at the dump level. Files with modification time stamps later than the date and time when the volume was dumped at the parent dump level are included.
The optional -expires option associates an expiration date with each dump level. The expiration date is applied to tapes containing dump sets made at the dump level; after the specified date, the Backup System overwrites the tape's contents with acceptably named dump sets without question.
An attempt to overwrite an unexpired tape fails until the issuer relabels the tape with the bak labeltape command. (Because the label records the unexpired expiration date or unacceptable name, erasing the label removes the obstacle to overwriting.) If no expiration date is defined for a tape, the Backup System overwrites the dump set on the tape with a dump set of the same name without question. Expiration dates can be either absolute or relative; see the Options section for details.
Privilege Required
The issuer must be listed in the admin.bak files on all Backup Database machines.
Examples
The following command defines a full dump called /yearly with a relative expiration date of one year:
$ bak addd -level /yearly -expires in 1y
The following command defines an incremental dump called /full/incr1 with a relative expiration date of 3 months and 15 days:
$ bak addd -l /full/incr1 -e in 3m 15d
The following command defines two dump levels, week1 and week2; both are incremental from the parent, monthly, and both are defined to expire at 12:00 a.m. on 1 January 1992:
$ bak adddump -l /monthly/week1 /monthly/week2 -e at 01/01/92
Related Information
Commands: bak dump(8dfs)