Displays the dump hierarchy from the Backup Database
Synopsis
bak lsdumps [-help]
Options
-help
Prints the online help for this command.
Description
The bak lsdumps command displays the dump hierarchy from the Backup Database. A dump hierarchy can contain more than one full dump level, each of which
defines a separate subhierarchy of dump levels. The bak lsdumps command displays the multiple subhierarchies if the Backup Database contains more than one full dump level.
Privilege Required
The issuer must be listed in the admin.bak files on all Backup Database machines.
Output
The output depicts the parent/child relationships between full and incremental dump levels in the dump hierarchy. The names of full dump levels are displayed at the far
left margin. There can be more than one full dump in the hierarchy; each defines a subhierarchy of dump levels, each of which would presumably be used for dumping different fileset families.
Incremental dump levels are displayed below and indented to the right from their parent dump level, which can be either full or incremental. Incremental dump levels need not be directly below their parent; the amount of indentation alone indicates the parent/child relationship.
Examples
The following example displays a dump hierarchy with two subhierarchies. One subhierarchy starts with the full dump level /month, the other with the full dump
level /monday (their positions at the left margin indicate they are full dump levels).
$ bak lsdumps
/month
/week1
/tuesday
/thursday
/week2
/tuesday
/thursday
/monday
/tuesday
/wednesday
/thursday
/friday
/saturday
In the first subhierarchy, /month serves as the parent for the /month/week1 and /month/week2 dump levels, as indicated by the indentation (/month/week2 is an example of how an incremental level need not be directly below its parent). The /month/week1 dump level serves as the parent for the /month/week1/tuesday dump level, which serves as the parent for the /month/week1/tuesday/thursday level. These within-week relationships are repeated under /month/week2.
Dump sets created at the /month level are full dumps. Dumps performed at the /month/week1 level include all files modified since the fileset family was dumped at the /month level. Dumps performed at the /month/week1/tuesday level include all files modified since the fileset family was dumped at the /month/week1 level, and dumps done at the /month/week1/tuesday/thursday level include all files modified since the dump done at the /month/week1/tuesday level.
Dumps done at the /month/week2 level would include all files modified since the fileset family was dumped at the /month level. Thus, dumps done at the/month/week2 level serve as a summary of dumps done since the dump at the /month/week1 level (they contain all files modified since a full dump was performed at the /month level).
The second subhierarchy, starting with /monday, is similarly constructed. The /monday dump level represents a full dump (it is at the far left margin); it is the parent for the /monday/tuesday level. The /monday/tuesday level is the parent for /monday/tuesday/wednesday, and so on. The /monday/saturday level's parent is /monday, so dumps performed at that level represent a summary of all the dumps performed at the intervening levels.
Related Information
Commands: bak adddump(8dfs)