amadmin
-Prev Chapter 35. The AMANDA Manual Pages. Next
+Prev Chapter 36. The Amanda Manual Pages. Next
-------------------------------------------------------------------------------
Name
-amadmin \14 administrative interface to control AMANDA backups
+amadmin \14 administrative interface to control Amanda backups
Synopsis
-amadmin config command [ command options ]
+amadmin config command [command options] [ -o | configoption ]*
DESCRIPTION
-Amadmin performs various administrative tasks on the config AMANDA
+Amadmin performs various administrative tasks on the config Amanda
configuration.
-See the amanda(8) man page for more details about AMANDA.
+See the amanda(8) man page for more details about Amanda.
COMMANDS
force-bump [ hostname [ disks ]* ]+
Force the disks on hostname to bump to a new incremental level during the
- next AMANDA run.
+ next Amanda run.
force-no-bump [ hostname [ disks ]* ]+
Force the disks on hostname to not bump to a new incremental level during
- the next AMANDA run.
+ the next Amanda run.
unforce-bump [ hostname [ disks ]* ]+
Undo a previous force-bump or force-no-bump command.
force [ hostname [ disks ]* ]+
Force the disks on hostname to do a full (level 0) backup during the next
- AMANDA run.
+ Amanda run.
unforce [ hostname [ disks ]* ]+
Undo a previous force command.
no-reuse tapelabel [ ... ]
The tapes listed 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, AMANDA will request new tapes
+ below the amanda.conf tapecycle value, Amanda will request new tapes
until the count is satisfied again.
due [ hostname [ disks ]* ]*
Show when the next full dump is due.
- find [ --sort hkdlb ] [ hostname [ disks ]* ]*
+ find [ --sort hkdlpb ] [ hostname [ disks ]* ]*
Display all backups currently on tape or in the holding disk. The tape
label or holding disk filename, file number, and status are displayed.
The --sort option changes the sort order using the following flags:
- hhost name kdisk name ddump date lbackup level btape label
+ hhost name kdisk name ddump date lbackup level p dump part btape label
An uppercase letter reverses the sort order for that key. The default
- sort order is hkdlb.
+ sort order is hkdlpb.
delete [ hostname [ disks ]* ]+
- Delete the specified disks on hostname from the AMANDA database.
+ Delete the specified disks on hostname from the Amanda database.
Note
- If you do not also remove the disk from the disklist file, AMANDA will
+ If you do not also remove the disk from the disklist file, Amanda will
treat it as a new disk during the next run.
tape
- Display the tape(s) AMANDA expects to write to during the next run. See
+ Display the tape(s) Amanda expects to write to during the next run. See
also amcheck(8).
bumpsize
Display the distribution of full backups throughout the dump schedule.
export [ hostname [ disks ]* ]*
- Convert records from the AMANDA database to a text format that may be
- transmitted to another AMANDA machine and imported.
+ Convert records from the Amanda database to a text format that may be
+ transmitted to another Amanda machine and imported.
import
- Convert exported records read from standard input to a form AMANDA uses
+ Convert exported records read from standard input to a form Amanda uses
and insert them into the database on this machine.
disklist [ hostname [ disks ]* ]*
Display the database record for each of the disks on hostname (or all
hosts). Mostly used for debugging.
+ -o configoption
+ See the "CONFIGURATION OVERWRITE" section in amanda(8).
+
EXAMPLES
Request three specific file systems on machine-a get a full level 0 backup
-during the next AMANDA run.
+during the next Amanda run.
$ amadmin daily force machine-a / /var /usr
amadmin: machine-a:/ is set to a forced level 0 tonight.
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
-AMANDA run.
+Amanda run.
$ amadmin daily force machine-b
amadmin: machine-b:/ is set to a forced level 0 tonight.
had some type of error.
$ amadmin daily find machine-c /var
- date host disk lv tape or file file status
- 2000-11-09 machine-c /var 0 000110 9 OK
- 2000-11-08 machine-c /var 2 000109 2 OK
- 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
- 2000-11-06 machine-c /var 2 000107 2 OK
- 2000-11-05 machine-c /var 2 000106 3 OK
- 2000-11-04 machine-c /var 2 000105 2 OK
- 2000-11-03 machine-c /var 2 000104 2 OK
- 2000-11-02 machine-c /var 2 000103 2 OK
- 2000-11-01 machine-c /var 1 000102 5 OK
- 2000-10-31 machine-c /var 1 000101 3 OK
+ date host disk lv tape or file file part status
+ 2000\-11\-09 machine\-c /var 0 000110 9 -- OK
+ 2000\-11\-08 machine\-c /var 2 000109 2 -- OK
+ 2000\-11\-07 machine\-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
+ 2000\-11\-06 machine\-c /var 2 000107 2 -- OK
+ 2000\-11\-05 machine\-c /var 2 000106 3 -- OK
+ 2000\-11\-04 machine\-c /var 2 000105 2 -- OK
+ 2000\-11\-03 machine\-c /var 2 000104 2 -- OK
+ 2000\-11\-02 machine\-c /var 2 000103 2 -- OK
+ 2000\-11\-01 machine\-c /var 1 000102 5 -- OK
+ 2000\-10\-31 machine\-c /var 1 000101 3 -- OK
Forget about the /workspace disk on machine-d. If you do not also remove the
-disk from the disklist file, AMANDA will treat it as a new disk during the next
+disk from the disklist file, Amanda will treat it as a new disk during the next
run.
$ amadmin daily delete machine-d /workspace
amadmin: machine-d:/workspace deleted from database.
amadmin: NOTE: you'll have to remove these from the disklist yourself.
-Find the next tape AMANDA will use (in this case, 123456).
+Find the next tape Amanda will use (in this case, 123456).
$ amadmin daily tape
- The next AMANDA 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. The due-date
column is the day the backups are due for a full backup. #fs shows the number
estimated total size of the backups before and after any compression,
respectively.
The balance column shows how far off that night's backups are from the average
-size (shown at the bottom of the balance column). AMANDA tries to keep the
+size (shown at the bottom of the balance column). Amanda tries to keep the
backups within +/- 5%, but since the amount of data on each filesystem is
-always changing, and AMANDA will never delay backups just to rebalance the
+always changing, 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 AMANDA runs will be made
+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 AMANDA is run (e.g. every
+probably have a full backup done every eight times Amanda is run (e.g. every
eight days).
$ amadmin daily balance
AUTHOR
James da Silva, <jds@amanda.org> : Original text
-Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the AMANDA-documentation:
+Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the Amanda-documentation:
XML-conversion
SEE ALSO
-amanda(8), amcheck(8), amdump(8), amrestore(8)
+amanda(8), amcheck(8), amdump(8), amrestore(8), amfetchdump(8)
-------------------------------------------------------------------------------
-Prev Up Next
-Chapter 35. The AMANDA Manual Pages. Home amanda
+Prev Up Next
+Chapter 36. The Amanda Manual Pages. Home amaespipe
projects / debian / amanda / blobdiff