X-Git-Url: https://git.gag.com/?a=blobdiff_plain;ds=sidebyside;f=man%2Fxml-source%2Famadmin.8.xml;h=9f70828bf2bf0d7d104b5f2b25d5b6633c66e290;hb=fd48f3e498442f0cbff5f3606c7c403d0566150e;hp=64153d43b970890120b24af8f511ae62fffaa845;hpb=96f35b20267e8b1a1c846d476f27fcd330e0b018;p=debian%2Famanda diff --git a/man/xml-source/amadmin.8.xml b/man/xml-source/amadmin.8.xml index 64153d4..9f70828 100644 --- a/man/xml-source/amadmin.8.xml +++ b/man/xml-source/amadmin.8.xml @@ -3,7 +3,7 @@ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - + %global_entities; ]> @@ -20,7 +20,7 @@ amadmin -administrative interface to control &A; backups +administrative interface to control Amanda backups &author.jds; @@ -33,7 +33,7 @@ config command command_options - configoption + &configoverride.synopsis; @@ -42,11 +42,11 @@ Amadmin performs various administrative tasks on the config -&A; configuration. +Amanda configuration. See the -amanda8 -man page for more details about &A;. + +man page for more details about Amanda. COMMANDS @@ -57,13 +57,13 @@ parameter pair operate on all disks in the &disklist; for that the command operates on all hosts and disks in the &disklist;. Both hostname and disks are special expressions; see the "HOST & DISK EXPRESSION" section -of amanda8 +of for a description. Commands that take one or more dumpspec parameters operate on the set of dumps specified by all of the expressions. See the "DUMP SPECIFICATIONS" section of -amanda8 + for a description. @@ -74,6 +74,37 @@ for a description. The config parameter must be present but is ignored. + + + + estimate [ hostname [ disks ]* ]* + +Print the server estimate for the dles, each output lines have the following format: + + hostname diskname level size + + + +hostname +The quoted hostname + + + +diskname +The quoted diskname + + + +level +The level of the estimate + + + +size +The estimate size in kbytes + + + @@ -83,7 +114,7 @@ parameter must be present but is ignored. disks on hostname -to bump to a new incremental level during the next &A; run. +to bump to a new incremental level during the next Amanda run. @@ -93,7 +124,7 @@ to bump to a new incremental level during the next &A; run. disks on hostname -to not bump to a new incremental level during the next &A; run. +to not bump to a new incremental level during the next Amanda run. @@ -113,7 +144,7 @@ command. disks on hostname -to do a full (level 0) backup during the next &A; run. +to do a full (level 0) backup during the next Amanda run. @@ -139,7 +170,7 @@ will not be reused when their turn comes up again in the tape cycle. Note that if this causes the number of reusable tapes to drop below the amanda.conf tapecycle -value, &A; will request new tapes until the count is satisfied again. +value, Amanda will request new tapes until the count is satisfied again. Tape marked no-reuse are available for recovery, marking them no-reuse is a security to be sure amanda will not overwrite them. @@ -213,9 +244,9 @@ The default sort order is hkdlpbfw. disks on hostname -from the &A; database. +from the Amanda database. If you do not also remove the disk from the &disklist; -file, &A; will treat it as a new disk during the next run. +file, Amanda will treat it as a new disk during the next run. @@ -223,9 +254,9 @@ file, &A; will treat it as a new disk during the next run. tape -Display the tape(s) &A; expects to write to during the next run. +Display the tape(s) Amanda expects to write to during the next run. See also -amcheck8. +. @@ -244,8 +275,8 @@ levels. export [ hostname [ disks ]* ]* -Convert records from the &A; database -to a text format that may be transmitted to another &A; machine and +Convert records from the Amanda database +to a text format that may be transmitted to another Amanda machine and imported. @@ -254,7 +285,7 @@ to a text format that may be transmitted to another &A; machine and Convert exported -records read from standard input to a form &A; uses +records read from standard input to a form Amanda uses and insert them into the database on this machine. @@ -283,13 +314,7 @@ Mostly used for debugging. - - -o configoption - -See the "CONFIGURATION OVERRIDE" - section in amanda8. - - + &configoverride.varlistentry; @@ -297,7 +322,7 @@ Mostly used for debugging. EXAMPLES Request three specific file systems on machine-a -get a full level 0 backup during the next &A; run. +get a full level 0 backup during the next Amanda run. $ amadmin daily force machine-a / /var /usr @@ -308,7 +333,7 @@ amadmin: machine-a:/usr is set to a forced level 0 tonight. Request all file systems on machine-b -get a full level 0 backup during the next &A; run. +get a full level 0 backup during the next Amanda run. $ amadmin daily force machine-b @@ -370,7 +395,7 @@ date host disk lv tape or file file part status disk on machine-d. If you do not also remove the disk from the &disklist; -file, &A; will treat it as a new disk during the next run. +file, Amanda will treat it as a new disk during the next run. $ amadmin daily delete machine-d /workspace @@ -378,11 +403,11 @@ amadmin: machine-d:/workspace deleted from database. amadmin: NOTE: you'll have to remove these from the &disklist; yourself. -Find the next tape &A; will use (in this case, 123456). +Find the next tape Amanda will use (in this case, 123456). $ amadmin daily tape -The next &A; run should go onto tape 123456 or a new tape. +The next Amanda run should go onto tape 123456 or a new tape. Show how well full backups are balanced across the dump cycle. @@ -401,17 +426,17 @@ before and after any compression, respectively. balance column shows how far off that night's backups are from the average size (shown at the bottom of the balance column). -&A; tries to keep the backups within +/- 5%, +Amanda tries to keep the backups within +/- 5%, but since the amount of data on each filesystem is always changing, -and &A; will never delay backups just to rebalance the schedule, +and Amanda will never delay backups just to rebalance the schedule, it is common for the schedule to fluctuate by larger percentages. In particular, in the case of a tape or backup failure, a bump will occur the following night, which will not be smoothed out until the next pass through the schedule. -The last line also shows an estimate of how many &A; runs will be +The last line also shows an estimate of how many Amanda runs will be made between full backups for a file system. In the example, a file system will probably have a full backup done -every eight times &A; is run (e.g. every eight days). +every eight times Amanda is run (e.g. every eight days). $ amadmin daily balance @@ -436,13 +461,12 @@ TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle) /usr/local/etc/amanda/config/amanda.conf -SEE ALSO -amanda8, -amcheck8, -amdump8, -amrestore8, -amfetchdump8, - - - + +, +, +, +, + + +