Prev Part IV. Various Information Next
-------------------------------------------------------------------------------
Prev Part IV. Various Information Next
-------------------------------------------------------------------------------
It has become very common for regular mailinglist-participants to use the
abbreviation DLE, which means in its long form
DiskList Entry
It has become very common for regular mailinglist-participants to use the
abbreviation DLE, which means in its long form
DiskList Entry
usage was to describe them as partitions, or file systems. But in fact they do
not have to be either. They can be directory trees, or multiple trees, or trees
with some branches cut off. So the more generic term DLE was coined.
usage was to describe them as partitions, or file systems. But in fact they do
not have to be either. They can be directory trees, or multiple trees, or trees
with some branches cut off. So the more generic term DLE was coined.
SHORT ANSWER:
DO NOT USE "localhost" as host entry in your disklist entries (aka DLEs). Use
the FQDN (Fully Qualified Domain Name) instead.
SHORT ANSWER:
DO NOT USE "localhost" as host entry in your disklist entries (aka DLEs). Use
the FQDN (Fully Qualified Domain Name) instead.
something like "localhost" or localhost.localdomain.net in your disklist.
Example (applies to Linux, syntax may be different on other systems):
something like "localhost" or localhost.localdomain.net in your disklist.
Example (applies to Linux, syntax may be different on other systems):
The first thing to understand is how to read this message. When it says "access
as amanda ..." it is telling you the client side ( amandad) is running as user
"amanda". The "... from amanda@some.amanda.server" part tells you the server
The first thing to understand is how to read this message. When it says "access
as amanda ..." it is telling you the client side ( amandad) is running as user
"amanda". The "... from amanda@some.amanda.server" part tells you the server
or amdump) is running as user "amanda".
The user names are typically the same on both client and server, but some
situations use different names and it is important to understand which is
which. For instance, amrecover connects as root ("... from
or amdump) is running as user "amanda".
The user names are typically the same on both client and server, but some
situations use different names and it is important to understand which is
which. For instance, amrecover connects as root ("... from
lists in the message. It does not try to look up abbreviations.
The only exception to this is that the lookup is case insensitive.
* The user name listed in ~amanda/.amandahosts is not the one trying to connect
from the server. In particular, watch out for the "root" case listed above
lists in the message. It does not try to look up abbreviations.
The only exception to this is that the lookup is case insensitive.
* The user name listed in ~amanda/.amandahosts is not the one trying to connect
from the server. In particular, watch out for the "root" case listed above
name, not "localhost". The sethost command inside amrecover can "fix" this, but
why not just set it up right in the first place?
Another reason to not use "localhost" is because it helps with future changes.
name, not "localhost". The sethost command inside amrecover can "fix" this, but
why not just set it up right in the first place?
Another reason to not use "localhost" is because it helps with future changes.
make it a client of a new, larger, server. But now "localhost" does not point
to the same machine it used to. If the FQDN of the machine had been used all
along, this upgrade would have been much easier.
make it a client of a new, larger, server. But now "localhost" does not point
to the same machine it used to. If the FQDN of the machine had been used all
along, this upgrade would have been much easier.
"My backup screwed up on tuesday and now it keeps asking for the tuesday tape
even though it is wednesday!"
ANSWER:
The short answer is: You can't.
The longer answer is: You can. But you should not.
"My backup screwed up on tuesday and now it keeps asking for the tuesday tape
even though it is wednesday!"
ANSWER:
The short answer is: You can't.
The longer answer is: You can. But you should not.
-The reason: AMANDA is designed to schedule your backups. Let "her" do it.
-When you want to make the best use of AMANDA, you have to let go the classic
+The reason: Amanda is designed to schedule your backups. Let "her" do it.
+When you want to make the best use of Amanda, you have to let go the classic
schedule where one used to have one tape dedicated to each day of the week, and
one for the friday.
The main difference in concept is this:
In the classic backup scheme you said:
"I want to have incremental backups from Mo-Th and a full backup on Fr."
schedule where one used to have one tape dedicated to each day of the week, and
one for the friday.
The main difference in concept is this:
In the classic backup scheme you said:
"I want to have incremental backups from Mo-Th and a full backup on Fr."
"I want to have at least one full backup in 5 days."
So you don't have to specify exactly WHEN the full backup should happen. You
"I want to have at least one full backup in 5 days."
So you don't have to specify exactly WHEN the full backup should happen. You
There are several advantages in this:
Imagine that you have your classic backup-schedule running fine. Everything is
calculated and designed well, so your tape gets filled well each night.
There are several advantages in this:
Imagine that you have your classic backup-schedule running fine. Everything is
calculated and designed well, so your tape gets filled well each night.
So the size of the directory raises within one day, maybe for multiple GBs.
Would your classic backup-scheme catch that? Or would it run out of tape,
simply because it was not calculated to have that filesystem with that size?
So the size of the directory raises within one day, maybe for multiple GBs.
Would your classic backup-scheme catch that? Or would it run out of tape,
simply because it was not calculated to have that filesystem with that size?
-AMANDA would try to catch it (and most of the time succeed ...).
-As there is the estimate-phase before actually dumping something, AMANDA can
+Amanda would try to catch it (and most of the time succeed ...).
+As there is the estimate-phase before actually dumping something, Amanda can
look at the DLEs and determine the actual size at the time. It also determines
the size of an incremental backup so it can test for the Plan B to just run a
level-1 if it does not work out to do a level-0 for that DLE.
look at the DLEs and determine the actual size at the time. It also determines
the size of an incremental backup so it can test for the Plan B to just run a
level-1 if it does not work out to do a level-0 for that DLE.
still tries to meet your goals. It just reschedules stuff, combining full and
incremental backups to meet the goals as good as possible.
still tries to meet your goals. It just reschedules stuff, combining full and
incremental backups to meet the goals as good as possible.
-So you can think of it as some algorithm which lets AMANDA adapt to your data.
-If you set the goals in a reasonable way, AMANDA will just do the rest.
+So you can think of it as some algorithm which lets Amanda adapt to your data.
+If you set the goals in a reasonable way, Amanda will just do the rest.
Use another backup scheduler.
This question is most often asked by individual computer users as a cost
consideration.
Use another backup scheduler.
This question is most often asked by individual computer users as a cost
consideration.
moderately sized computer centers. That it can be used by users of small
computers is a testament to its designers and maintainers.
While it may seem cost effective to put as many dumps as possible on a single
tape, in a computing center that would be considered a very risky decision. The
loss of, or damage to, a single tape would be the loss of many days worth of
dumps. That is too much to chance.
moderately sized computer centers. That it can be used by users of small
computers is a testament to its designers and maintainers.
While it may seem cost effective to put as many dumps as possible on a single
tape, in a computing center that would be considered a very risky decision. The
loss of, or damage to, a single tape would be the loss of many days worth of
dumps. That is too much to chance.
-Thus, AMANDA was designed to never overwrite a non-AMANDA tape, nor an AMANDA
-tape from a different configuration, nor an AMANDA tape from the current
+Thus, Amanda was designed to never overwrite a non-Amanda tape, nor an Amanda
+tape from a different configuration, nor an Amanda tape from the current
configuration that is still "active", i.e. has backups on the tape more recent
than the dumpcycle length.
configuration that is still "active", i.e. has backups on the tape more recent
than the dumpcycle length.
is a crude way to accomplish your goal.
But first ask yourself, "If my data is worth so little that I can not afford a
few more tapes, why am I backing it up?"
is a crude way to accomplish your goal.
But first ask yourself, "If my data is worth so little that I can not afford a
few more tapes, why am I backing it up?"
tape out for a week. Then stick it in and run amflush.
(Better make sure you have sufficient disk space on your holding disk.)
Note, a slight variant of this is to have the parameter autoflush in
tape out for a week. Then stick it in and run amflush.
(Better make sure you have sufficient disk space on your holding disk.)
Note, a slight variant of this is to have the parameter autoflush in
their version already supports that parameter.)
Then after several dumps have collected in the holding disk, put the tape in
before that day's amdump is scheduled. amdump will both flush the holding disk
their version already supports that parameter.)
Then after several dumps have collected in the holding disk, put the tape in
before that day's amdump is scheduled. amdump will both flush the holding disk
contained:
>Welcome to the amanda-users mailing list!
>Please save this message for future reference. Thank you.
contained:
>Welcome to the amanda-users mailing list!
>Please save this message for future reference. Thank you.
-packages of AMANDA-servers and -clients.
-Due to the design of the AMANDA source code, in which MANY features can be
+packages of Amanda-servers and -clients.
+Due to the design of the Amanda source code, in which MANY features can be
configured at compile-time, it is heavily and heartily recommended to take the
effort and roll your own special flavour.
configured at compile-time, it is heavily and heartily recommended to take the
effort and roll your own special flavour.
-configurations right into your AMANDA-binaries. You also get the benefit of a
-much more improved understanding of the way AMANDA does backups.
+configurations right into your Amanda-binaries. You also get the benefit of a
+much more improved understanding of the way Amanda does backups.
"Which device is my changer?"
" amtapetype is broken, it says my 200GB tape only holds 65GB."
"My file marks are HUGE, 1.3MB (on a 200GB tape, i.e. about 0.05% of the total
capacity, or expressed another way, maybe 2 mm of a 125000 mm tape ...)"
ANSWER:
"Which device is my changer?"
" amtapetype is broken, it says my 200GB tape only holds 65GB."
"My file marks are HUGE, 1.3MB (on a 200GB tape, i.e. about 0.05% of the total
capacity, or expressed another way, maybe 2 mm of a 125000 mm tape ...)"
ANSWER:
-It is crucial to tell AMANDA the truth about the tape-device(s) you want to
-use. Given the wrong values, AMANDA can't calculate proper dumpsizes, free
+It is crucial to tell Amanda the truth about the tape-device(s) you want to
+use. Given the wrong values, Amanda can't calculate proper dumpsizes, free
tape-space or make valuable use of compression.
Before you consider running amtapetype, think twice. Twice.
As tapedrives tend to be produced by not-so-small companies and as those not-
tape-space or make valuable use of compression.
Before you consider running amtapetype, think twice. Twice.
As tapedrives tend to be produced by not-so-small companies and as those not-
is very likely that someone else has the same device you have or at least one
that uses the same technology.
Many people have already run amtapetype to determine the proper values to fill
is very likely that someone else has the same device you have or at least one
that uses the same technology.
Many people have already run amtapetype to determine the proper values to fill
-in their amanda.conf-files. Browse the example amanda.conf in your AMANDA-
-tarball for various tapetypes. Browse the AMANDA-FAQ on http://www.amanda.org.
+in their amanda.conf-files. Browse the example amanda.conf in your Amanda-
+tarball for various tapetypes. Browse the Amanda-FAQ on http://www.amanda.org.
Chances are high that you find just your device described.
As in every other topic discussed in internet mailing lists, please try finding
Chances are high that you find just your device described.
As in every other topic discussed in internet mailing lists, please try finding
-an answer there before asking on the AMANDA-users list.
-If your device is so exotic that even the AMANDA-users can't help you, you
+an answer there before asking on the Amanda-users list.
+If your device is so exotic that even the Amanda-users can't help you, you
still have your copy of amtapetype.
Before you start running it, note this:
still have your copy of amtapetype.
Before you start running it, note this:
-* AMANDA supports using more than one tape in a single run of amdump
-* AMANDA does not support splitting a dump image across tapes
+* Amanda supports using more than one tape in a single run of amdump
+* Amanda does not support splitting a dump image across tapes
The first rule lets you make use of two or more tapes for a single amdump when
using a tapechanger-robot or a tape-library. You could even use multiple tapes
The first rule lets you make use of two or more tapes for a single amdump when
using a tapechanger-robot or a tape-library. You could even use multiple tapes
The trick is to form several chunks of data of which each fits on tape. In the
example above the chunks are formed by regular expressions matching files named
like file00, file123 and file9999. You have to look at your DLEs to find the
patterns describing your chunks.
The trick is to form several chunks of data of which each fits on tape. In the
example above the chunks are formed by regular expressions matching files named
like file00, file123 and file9999. You have to look at your DLEs to find the
patterns describing your chunks.
to schedule your backups more flexible. Having more and smaller DLEs, the
planner has more variations to possibly schedule your backups, so this will
help getting nice output from amadmin <conf> balance, too.
Note
to schedule your backups more flexible. Having more and smaller DLEs, the
planner has more variations to possibly schedule your backups, so this will
help getting nice output from amadmin <conf> balance, too.
Note
-Actually there are people working on GUIs for AMANDA. Aside from that the
-question really is: "Does anyone need a GUI for AMANDA?"
+Actually there are people working on GUIs for Amanda. Aside from that the
+question really is: "Does anyone need a GUI for Amanda?"
Given the fact that backups tend to be run at night while people tend to sleep,
who would need a fancy GUI showing 3D-backup-diagrams via X11? The only part of
backups where GUIs maybe could add some comfort is recovery for unexperienced
Given the fact that backups tend to be run at night while people tend to sleep,
who would need a fancy GUI showing 3D-backup-diagrams via X11? The only part of
backups where GUIs maybe could add some comfort is recovery for unexperienced
Please feel free to suggest additions and corrections. Write to the amanda-
users-mailinglist at mailto://amanda-users@amanda.org.
Please feel free to suggest additions and corrections. Write to the amanda-
users-mailinglist at mailto://amanda-users@amanda.org.