RE: Configuration confusion
I suppose you could have a small modification to your config file every day.
(scripted to run dynamically, # date has very useful output formatting)
# amdump config-type-1-day-${dayname}
With 7 dumps/week and three configs he can have 21 different backup files,
completely defeating the scheduling but getting exactly the result he wants.
-Original Message-
From: Debra S Baddorf
Sent: Thursday, November 15, 2018 1:39 PM
To: Cuttler, Brian R (HEALTH)
Cc: Debra S Baddorf ; Charles Curley
; amanda-users
Subject: Re: Configuration confusion
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
If you’ve disable level 0 backups in the setup, *WILL* it do a level 0, even
if you try to force it?
I have one hge config that is set up this way. I have to edit the
amanda.conf and REMOVE the “incr-only” lines
when I want to force a level 0. Specially since you HAVE to start with a
level 0, initially.
I’m pretty sure I’ve tried to force some level 0’s and found they failed, till
I removed the “incr-only” bits.
Deb Baddorf
> On Nov 15, 2018, at 12:16 PM, Cuttler, Brian R (HEALTH)
> wrote:
>
> Alternatively - configure all DLE to be non-fulls, disable level 0 backups
> entirely and run cron jobs to force level 0 dumps on particular DLEs.
> That way you can get level 0 when you want it to occur an no other DLE will
> advance to a level 0 on its own.
>
> # amadmin config force client DLE
>
> -Original Message-
> From: owner-amanda-us...@amanda.org On
> Behalf Of Charles Curley
> Sent: Thursday, November 15, 2018 12:31 PM
> To: amanda-users
> Subject: Re: Configuration confusion
>
> ATTENTION: This email came from an external source. Do not open attachments
> or click on links from unknown senders or unexpected emails.
>
>
> On Thu, 15 Nov 2018 09:03:00 -0800 (PST) Chris Miller wrote:
>
>> If I run three backups, serial or otherwise, then do they know about
>> each other? Meaning, is AMANDA smart enough to know not to run more
>> than one level 0 dump per night? The problem is that level 0 backups
>> take several hours and if I run multiple then I will still be
>> completing last nights backup when everybody comes in the next
>> morning. That would be embarrassing. "Sorry, I didn't complete my
>> work last night, so you can't continue yours."
>
> Ah, that helps. My experience is in a SOHO environment, so take with the salt
> shaker handy.
>
> The different configurations don't know about each other at all. So you could
> in theory have a night in which all three run level 0 backups.
> The only way I know to get that kind of co-ordination is to have one
> configuration which then backs up all three machines. Unfortunately your
> requirement not to mix the backups due to custodial and security requirements
> may kill that idea.
>
> Another thing to look at is to break your DLEs up into lots of smaller DLEs.
> You'll get more level 0 backups, but they'll be spread around the week more
> evenly.
>
> Or consider having a longer tape cycle. That means fewer level 0 backups in
> any one week.
>
> --
> "When we talk of civilization, we are too apt to limit the meaning of the
> word to its mere embellishments, such as arts and sciences; but the true
> distinction between it and barbarism is, that the one presents a state of
> society under the protection of just and well-administered law, and the other
> is left to the chance government of brute force."
> - The Rev. James White, Eighteen Christian Centuries, 1889 Key
> fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
> https://urldefense.proofpoint.com/v2/url?u=https-3A__charlescurley.com
> =DwIDAg=gRgGjJ3BkIsb5y6s49QqsA=HMrKaRiCv4jddln9fLPIOw=fnbC4Yi7
> 6_5ky_32Tf9A5Geluildi-avCP3JC0hU2RA=oia-zSsMzlRk8WRCNW_-9vpn6VWUX7Vm
> XSyeRVdmgcM=
>
Re: Configuration confusion
If you’ve disable level 0 backups in the setup, *WILL* it do a level 0, even if you try to force it? I have one hge config that is set up this way. I have to edit the amanda.conf and REMOVE the “incr-only” lines when I want to force a level 0. Specially since you HAVE to start with a level 0, initially. I’m pretty sure I’ve tried to force some level 0’s and found they failed, till I removed the “incr-only” bits. Deb Baddorf > On Nov 15, 2018, at 12:16 PM, Cuttler, Brian R (HEALTH) > wrote: > > Alternatively - configure all DLE to be non-fulls, disable level 0 backups > entirely and run cron jobs to force level 0 dumps on particular DLEs. > That way you can get level 0 when you want it to occur an no other DLE will > advance to a level 0 on its own. > > # amadmin config force client DLE > > -Original Message- > From: owner-amanda-us...@amanda.org On Behalf > Of Charles Curley > Sent: Thursday, November 15, 2018 12:31 PM > To: amanda-users > Subject: Re: Configuration confusion > > ATTENTION: This email came from an external source. Do not open attachments > or click on links from unknown senders or unexpected emails. > > > On Thu, 15 Nov 2018 09:03:00 -0800 (PST) Chris Miller wrote: > >> If I run three backups, serial or otherwise, then do they know about >> each other? Meaning, is AMANDA smart enough to know not to run more >> than one level 0 dump per night? The problem is that level 0 backups >> take several hours and if I run multiple then I will still be >> completing last nights backup when everybody comes in the next >> morning. That would be embarrassing. "Sorry, I didn't complete my work >> last night, so you can't continue yours." > > Ah, that helps. My experience is in a SOHO environment, so take with the salt > shaker handy. > > The different configurations don't know about each other at all. So you could > in theory have a night in which all three run level 0 backups. > The only way I know to get that kind of co-ordination is to have one > configuration which then backs up all three machines. Unfortunately your > requirement not to mix the backups due to custodial and security requirements > may kill that idea. > > Another thing to look at is to break your DLEs up into lots of smaller DLEs. > You'll get more level 0 backups, but they'll be spread around the week more > evenly. > > Or consider having a longer tape cycle. That means fewer level 0 backups in > any one week. > > -- > "When we talk of civilization, we are too apt to limit the meaning of the > word to its mere embellishments, such as arts and sciences; but the true > distinction between it and barbarism is, that the one presents a state of > society under the protection of just and well-administered law, and the other > is left to the chance government of brute force." > - The Rev. James White, Eighteen Christian Centuries, 1889 Key fingerprint = > CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB > https://urldefense.proofpoint.com/v2/url?u=https-3A__charlescurley.com=DwIDAg=gRgGjJ3BkIsb5y6s49QqsA=HMrKaRiCv4jddln9fLPIOw=fnbC4Yi76_5ky_32Tf9A5Geluildi-avCP3JC0hU2RA=oia-zSsMzlRk8WRCNW_-9vpn6VWUX7VmXSyeRVdmgcM= >
Re: Configuration confusion
Hi Brian and Deb, > Alternatively - configure all DLE to be non-fulls, disable level 0 backups > entirely and run cron jobs to force level 0 dumps on particular DLEs. > That way you can get level 0 when you want it to occur an no other DLE will > advance to a level 0 on its own. This is a very good solution, I think. I already have the requirement that I collect a disk image once per cycle, which AMANDA can't schedule, so I am already in "self-scheduling" territory. Can you tell me how I disable level 0 backups? Thanks for the help, -- Chris. V:916.974.0424 F:916.974.0428
RE: Configuration confusion
From: owner-amanda-us...@amanda.org On Behalf
Of Chris Miller
Sent: Thursday, November 15, 2018 12:29 PM
To: amanda-users
Subject: Re: Configuration confusion
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
Hi Brian,
From: "Cuttler, Brian R (HEALTH)"
mailto:brian.cutt...@health.ny.gov>>
To: "Cuttler, Brian R (HEALTH)"
mailto:brian.cutt...@health.ny.gov>>, "Chris
Miller" mailto:c...@tryx.org>>, "amanda-users"
mailto:amanda-users@amanda.org>>
Sent: Wednesday, November 14, 2018 9:08:26 AM
Subject: RE: Configuration confusion
Tape custody – means what, retention policy or storage of the tape when not in
the drive/juke?
Yes. Simplest is local custody. Off site custody comes in two media flavors --
local media and cloud. Off site costs, so we want to minimize this, as well as
increases the response time for restorations. You get the idea. I don't use
tapes; I use removable disks, optical media,and usb keydrives. General this is
determined by the client, so when I plan this, I simply consider which client
backups need to be sequestered where. This gives me a configuration where I can
think in terms of "client gets backedup to NAS ", where NAS has
different properties and different dispositions.
* Yes, I understand. I have worked at sites where offsite was someone’s
house (tapes never came back in the right cycle, seems if you use them as hills
under your train set you might not return the oldest tapes but bring back a
mix). Other sites had tapes stored in the fire protected computer room, still
others had them in a room in another part of the building, but it is a very big
building.
Amanda is not an archiver in the sense that the tapes are cycled on a regular
basis. You are able to tape a tape out of rotation and replace it, or create a
unique tape label and perform level 0 backups to it and then mark it as
no-reuse in the tapelist, but the primary function is not long term archiving,
though the tools exist to do that very well.
You can use the same tape pool for all three Amanda configs, but they will need
to have a common tapelist file. But if you are doing that then you are
selecting a single set of standards for your data-at-rest security, in which
case there is little reason to maintain 3 different configs.
Each Amanda config will look to level nightly data, but you will have nights
with relatively little and nights with relatively large data volume swings, er
think wave interference from physics. You eliminate a lot of that by combining
disklists into a single configuration.
Yes! "Each Amanda config will look to level nightly data ..." This is my
principle question, and I seek to level the nightly data across all configs on
a given night, which I recognize can't be done, so I seek to combine my
multiple configs into a single config which specifies multiple sets of DLEs
being mapped to multiple tapedev, if that can be done. For example, if the
definition of tapedev had a "DLE ..." argument, and AMANDA were capable of this
additional dimension of scheduling.
* See reply I put in subsequent email by Charles Curley that was a response
to you.
Amanda will backup a new DLE at level 0 the first time it sees it. If you are
worried about running long you will want to phase in the DLEs across several
evenings. You may want to add the largest on Friday night, assuming that no one
cares how late Amanda runs into Saturday. You will want to avoid adding
multiple large DLEs on a single night, add a large and a small each night until
they are all added.
"Phasing" my backup jobs may be my only choice, as that is exactly the problem
I seek to avoid and I have been admonished to not try to subvert the scheduler
by forcing level 0 backups to happen on my schedule. As I continue to discuss
this, I am more and more convinced that AMANDA cannot schedule in two
dimensions {(backups / night) X (nights / cycle)}
So, suppose I wanted to force my level 0 backups to happen at my discretion, so
I can level my nightly run times. How would I do that?
Thanks for the help, Brian.
--
Chris.
V:916.974.0424
F:916.974.0428
RE: Configuration confusion
Alternatively - configure all DLE to be non-fulls, disable level 0 backups entirely and run cron jobs to force level 0 dumps on particular DLEs. That way you can get level 0 when you want it to occur an no other DLE will advance to a level 0 on its own. # amadmin config force client DLE -Original Message- From: owner-amanda-us...@amanda.org On Behalf Of Charles Curley Sent: Thursday, November 15, 2018 12:31 PM To: amanda-users Subject: Re: Configuration confusion ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. On Thu, 15 Nov 2018 09:03:00 -0800 (PST) Chris Miller wrote: > If I run three backups, serial or otherwise, then do they know about > each other? Meaning, is AMANDA smart enough to know not to run more > than one level 0 dump per night? The problem is that level 0 backups > take several hours and if I run multiple then I will still be > completing last nights backup when everybody comes in the next > morning. That would be embarrassing. "Sorry, I didn't complete my work > last night, so you can't continue yours." Ah, that helps. My experience is in a SOHO environment, so take with the salt shaker handy. The different configurations don't know about each other at all. So you could in theory have a night in which all three run level 0 backups. The only way I know to get that kind of co-ordination is to have one configuration which then backs up all three machines. Unfortunately your requirement not to mix the backups due to custodial and security requirements may kill that idea. Another thing to look at is to break your DLEs up into lots of smaller DLEs. You'll get more level 0 backups, but they'll be spread around the week more evenly. Or consider having a longer tape cycle. That means fewer level 0 backups in any one week. -- "When we talk of civilization, we are too apt to limit the meaning of the word to its mere embellishments, such as arts and sciences; but the true distinction between it and barbarism is, that the one presents a state of society under the protection of just and well-administered law, and the other is left to the chance government of brute force." - The Rev. James White, Eighteen Christian Centuries, 1889 Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB https://charlescurley.com
Re: Configuration confusion
> On Nov 15, 2018, at 11:29 AM, Chris Miller wrote:
>
> Hi Brian,
> From: "Cuttler, Brian R (HEALTH)"
> To: "Cuttler, Brian R (HEALTH)" , "Chris Miller"
> , "amanda-users"
> Sent: Wednesday, November 14, 2018 9:08:26 AM
> Subject: RE: Configuration confusion
> Tape custody – means what, retention policy or storage of the tape when not
> in the drive/juke?
> Yes. Simplest is local custody. Off site custody comes in two media flavors
> -- local media and cloud. Off site costs, so we want to minimize this, as
> well as increases the response time for restorations. You get the idea. I
> don't use tapes; I use removable disks, optical media,and usb keydrives.
> General this is determined by the client, so when I plan this, I simply
> consider which client backups need to be sequestered where. This gives me a
> configuration where I can think in terms of "client gets backedup to NAS
> ", where NAS has different properties and different dispositions.
>
>
>
> Amanda is not an archiver in the sense that the tapes are cycled on a regular
> basis. You are able to tape a tape out of rotation and replace it, or create
> a unique tape label and perform level 0 backups to it and then mark it as
> no-reuse in the tapelist, but the primary function is not long term
> archiving, though the tools exist to do that very well.
>
> You can use the same tape pool for all three Amanda configs, but they will
> need to have a common tapelist file. But if you are doing that then you are
> selecting a single set of standards for your data-at-rest security, in which
> case there is little reason to maintain 3 different configs.
>
> Each Amanda config will look to level nightly data, but you will have nights
> with relatively little and nights with relatively large data volume swings,
> er think wave interference from physics. You eliminate a lot of that by
> combining disklists into a single configuration.
> Yes! "Each Amanda config will look to level nightly data ..." This is my
> principle question, and I seek to level the nightly data across all configs
> on a given night, which I recognize can't be done, so I seek to combine my
> multiple configs into a single config which specifies multiple sets of DLEs
> being mapped to multiple tapedev, if that can be done. For example, if the
> definition of tapedev had a "DLE ..." argument, and AMANDA were capable of
> this additional dimension of scheduling.
>
>
>
> Amanda will backup a new DLE at level 0 the first time it sees it. If you are
> worried about running long you will want to phase in the DLEs across several
> evenings. You may want to add the largest on Friday night, assuming that no
> one cares how late Amanda runs into Saturday. You will want to avoid adding
> multiple large DLEs on a single night, add a large and a small each night
> until they are all added.
> "Phasing" my backup jobs may be my only choice, as that is exactly the
> problem I seek to avoid and I have been admonished to not try to subvert the
> scheduler by forcing level 0 backups to happen on my schedule. As I continue
> to discuss this, I am more and more convinced that AMANDA cannot schedule in
> two dimensions {(backups / night) X (nights / cycle)}
>
> So, suppose I wanted to force my level 0 backups to happen at my discretion,
> so I can level my nightly run times. How would I do that?
>
> Thanks for the help, Brian.
> --
> Chris.
>
Well, you *can* do
amadminforce node [dles]
Do man amadmin to get details on the FORCE command.
I have a separate configuration, using the same disklist, which I run once a
month to get an archive tape,
with all the level 0’s on the same tape. I have it set to do no-incr but I
also tell it “amadmin archive force *.full.ipname “
to make sure they are only level 0. You know - belt *and* suspenders.
PS the phasing in (adding a few disks each night) is only at the beginning,
when they all need to do a level 0 backup.
If they’re ALL in the disklist file, then they’ll ALL get a level 0 backup the
first time you run amdump.
If you only add a few DLEs each night, then you are manually balancing it —
but only until all are added. After that,
amanda uses it’s leveling to proceed.
Deb Baddorf
Re: Configuration confusion
On Thu, 15 Nov 2018 09:03:00 -0800 (PST) Chris Miller wrote: > If I run three backups, serial or otherwise, then do they know about > each other? Meaning, is AMANDA smart enough to know not to run more > than one level 0 dump per night? The problem is that level 0 backups > take several hours and if I run multiple then I will still be > completing last nights backup when everybody comes in the next > morning. That would be embarrassing. "Sorry, I didn't complete my > work last night, so you can't continue yours." Ah, that helps. My experience is in a SOHO environment, so take with the salt shaker handy. The different configurations don't know about each other at all. So you could in theory have a night in which all three run level 0 backups. The only way I know to get that kind of co-ordination is to have one configuration which then backs up all three machines. Unfortunately your requirement not to mix the backups due to custodial and security requirements may kill that idea. Another thing to look at is to break your DLEs up into lots of smaller DLEs. You'll get more level 0 backups, but they'll be spread around the week more evenly. Or consider having a longer tape cycle. That means fewer level 0 backups in any one week. -- "When we talk of civilization, we are too apt to limit the meaning of the word to its mere embellishments, such as arts and sciences; but the true distinction between it and barbarism is, that the one presents a state of society under the protection of just and well-administered law, and the other is left to the chance government of brute force." - The Rev. James White, Eighteen Christian Centuries, 1889 Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB https://charlescurley.com
Re: Configuration confusion
Hi Brian,
> From: "Cuttler, Brian R (HEALTH)"
> To: "Cuttler, Brian R (HEALTH)" , "Chris Miller"
> , "amanda-users"
> Sent: Wednesday, November 14, 2018 9:08:26 AM
> Subject: RE: Configuration confusion
> Tape custody – means what, retention policy or storage of the tape when not in
> the drive/juke?
Yes. Simplest is local custody. Off site custody comes in two media flavors --
local media and cloud. Off site costs, so we want to minimize this, as well as
increases the response time for restorations. You get the idea. I don't use
tapes; I use removable disks, optical media,and usb keydrives. General this is
determined by the client, so when I plan this, I simply consider which client
backups need to be sequestered where. This gives me a configuration where I can
think in terms of "client gets backedup to NAS ", where NAS has
different properties and different dispositions.
> Amanda is not an archiver in the sense that the tapes are cycled on a regular
> basis. You are able to tape a tape out of rotation and replace it, or create a
> unique tape label and perform level 0 backups to it and then mark it as
> no-reuse in the tapelist, but the primary function is not long term archiving,
> though the tools exist to do that very well.
> You can use the same tape pool for all three Amanda configs, but they will
> need
> to have a common tapelist file. But if you are doing that then you are
> selecting a single set of standards for your data-at-rest security, in which
> case there is little reason to maintain 3 different configs.
> Each Amanda config will look to level nightly data, but you will have nights
> with relatively little and nights with relatively large data volume swings, er
> think wave interference from physics. You eliminate a lot of that by combining
> disklists into a single configuration.
Yes! " Each Amanda config will look to level nightly data ..." This is my
principle question, and I seek to level the nightly data across all configs on
a given night, which I recognize can't be done, so I seek to combine my
multiple configs into a single config which specifies multiple sets of DLEs
being mapped to multiple tapedev, if that can be done. For example, if the
definition of tapedev had a "DLE ..." argument, and AMANDA were capable of this
additional dimension of scheduling.
> Amanda will backup a new DLE at level 0 the first time it sees it. If you are
> worried about running long you will want to phase in the DLEs across several
> evenings. You may want to add the largest on Friday night, assuming that no
> one
> cares how late Amanda runs into Saturday. You will want to avoid adding
> multiple large DLEs on a single night, add a large and a small each night
> until
> they are all added.
"Phasing" my backup jobs may be my only choice, as that is exactly the problem
I seek to avoid and I have been admonished to not try to subvert the scheduler
by forcing level 0 backups to happen on my schedule. As I continue to discuss
this, I am more and more convinced that AMANDA cannot schedule in two
dimensions {(backups / night) X (nights / cycle)}
So, suppose I wanted to force my level 0 backups to happen at my discretion, so
I can level my nightly run times. How would I do that?
Thanks for the help, Brian.
--
Chris.
V:916.974.0424
F:916.974.0428
Re: Configuration confusion
Hi Charles, > I think the simplest solution to your problem is to take Gene's advice > and run the three backups in sequence, using a simple shell script. > That is what I do. All these issues go away. I don't think I understand your advice, via Gene. To refresh your memory, I have three configs for three clients which effectively backup each to it's own vtape pool: c0.tclc.org --> nas0.tclc.org c1.tclc.org --> nas1.tclc.org c2.tclc.org --> nas2.tclc.org I am working with a one week backup cycle -- seven backups, during which each of the three clients must complete a level 0 backup. If I run three backups, serial or otherwise, then do they know about each other? Meaning, is AMANDA smart enough to know not to run more than one level 0 dump per night? The problem is that level 0 backups take several hours and if I run multiple then I will still be completing last nights backup when everybody comes in the next morning. That would be embarrassing. "Sorry, I didn't complete my work last night, so you can't continue yours." It seems like I should be able to combine my several configs into a single config so AMANDA will actually know the full scope of the problem and schedule accordingly, but I don't understand enough of the configuration discipline to describe multiple DLE --> vtape mappings to run in a single AMANDA execution. I think this comes from "disklist" having a list, but amanda.conf having only one tapedev. Even if there were latitude to define multiple tapedev, I don't see syntax that would map a set of DLEs to each tapedev. For example, can I specify the "disklist" in the definition of the tapedev? Unfortunately "man tapedev" does not produce anything. Is there, for example a BNF definition of syntax for tapedev anywhere? Thanks for the help, Charles. -- Chris. V:916.974.0424 F:916.974.0428
RE: Configuration confusion
Tape custody – means what, retention policy or storage of the tape when not in
the drive/juke?
Amanda is not an archiver in the sense that the tapes are cycled on a regular
basis. You are able to tape a tape out of rotation and replace it, or create a
unique tape label and perform level 0 backups to it and then mark it as
no-reuse in the tapelist, but the primary function is not long term archiving,
though the tools exist to do that very well.
You can use the same tape pool for all three Amanda configs, but they will need
to have a common tapelist file. But if you are doing that then you are
selecting a single set of standards for your data-at-rest security, in which
case there is little reason to maintain 3 different configs.
Each Amanda config will look to level nightly data, but you will have nights
with relatively little and nights with relatively large data volume swings, er
think wave interference from physics. You eliminate a lot of that by combining
disklists into a single configuration.
Amanda will backup a new DLE at level 0 the first time it sees it. If you are
worried about running long you will want to phase in the DLEs across several
evenings. You may want to add the largest on Friday night, assuming that no one
cares how late Amanda runs into Saturday. You will want to avoid adding
multiple large DLEs on a single night, add a large and a small each night until
they are all added.
You may want to think about your dumpcycle, 1 week, 2 weeks? Depends on your
tapecycle (number of tapes in the pool) as well as your business requirements.
You want multiple level 0 dumps of each DLE in the pool, you want the level 0
dumps to be relatively frequent as it simplifies the restore process should you
need to run it (you remember the text book procedure for restoring TAR/DUMP
backups).
From: owner-amanda-us...@amanda.org On Behalf
Of Cuttler, Brian R (HEALTH)
Sent: Wednesday, November 14, 2018 11:44 AM
To: Chris Miller ; amanda-users
Subject: RE: Configuration confusion
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
You can run amanda multiple times per night, and each config can specify a
different, MUST specify a different set of tape labels, different tape pools.
But I don’t believe you can run multiple amanda servers concurrently.
Could you run your tapes with the highest security level so that DLEs can
intermix on the output tape?
I believe that selection of encryption data-in-motion (vs on tape data-at-rest)
can be configured per DLE, if not then certainly by host.
From: owner-amanda-us...@amanda.org<mailto:owner-amanda-us...@amanda.org>
mailto:owner-amanda-us...@amanda.org>> On Behalf
Of Chris Miller
Sent: Wednesday, November 14, 2018 11:33 AM
To: amanda-users mailto:amanda-users@amanda.org>>
Subject: Configuration confusion
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
Hi Folks,
I now have three working configs, meaning that my test configuration can backup
three clients. I still can't tell what is happening, but that is a topic for a
different thread. There is not much difference among the configs; in fact the
only difference is the src (contents of "disklist") and the dst ("tapedev").
So, I have three clients, but the way I have configured AMANDA, I am running
three copies of AMANDA, none of which knows what any other is doing. They will
quite probably schedule level 0 backups on the same run, meaning I lose the
smoothing benefit of the scheduler, which wants to try to make the nightly
backup task approximately equal in terms of storage and network bandwidth
consumption. However, I recognize that I'm asking a single copy of AMANDA to do
multiple backups each night, and this might not be something AMANDA was
designed to do. I don't know, being relatively inexperienced.
The config specifies the src and dst of the backup where src is a set of DLEs
and dst is single tapedev. I think I want a single config that recognizes
multiple (src to dst) mappings, and AMANDA can make backup level decisions
knowing the full scope of the problem for that cycle. Given that I have fewer
clients than backup-cycles, I can space my level 0 backups so that I never do
more than one on any given night. I can fear that AMANDA will schedule everyone
for level 0 and backups are still proceeding the next day! That would be
disruptive and embarrassing.
I think what I'm asking is if I can backup a set of DLEs to a single tapedev,
and have a single copy of AMANDA run multiple backups each night? I can't mix
clients on the backup media, since each has different security and custody
requirements, and I think I'd like AMANDA to be aware of the complete set of
tasks for any given night without coming into conflict with AMANDA
doppelgangers, un
RE: Configuration confusion
You can run amanda multiple times per night, and each config can specify a
different, MUST specify a different set of tape labels, different tape pools.
But I don’t believe you can run multiple amanda servers concurrently.
Could you run your tapes with the highest security level so that DLEs can
intermix on the output tape?
I believe that selection of encryption data-in-motion (vs on tape data-at-rest)
can be configured per DLE, if not then certainly by host.
From: owner-amanda-us...@amanda.org On Behalf
Of Chris Miller
Sent: Wednesday, November 14, 2018 11:33 AM
To: amanda-users
Subject: Configuration confusion
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
Hi Folks,
I now have three working configs, meaning that my test configuration can backup
three clients. I still can't tell what is happening, but that is a topic for a
different thread. There is not much difference among the configs; in fact the
only difference is the src (contents of "disklist") and the dst ("tapedev").
So, I have three clients, but the way I have configured AMANDA, I am running
three copies of AMANDA, none of which knows what any other is doing. They will
quite probably schedule level 0 backups on the same run, meaning I lose the
smoothing benefit of the scheduler, which wants to try to make the nightly
backup task approximately equal in terms of storage and network bandwidth
consumption. However, I recognize that I'm asking a single copy of AMANDA to do
multiple backups each night, and this might not be something AMANDA was
designed to do. I don't know, being relatively inexperienced.
The config specifies the src and dst of the backup where src is a set of DLEs
and dst is single tapedev. I think I want a single config that recognizes
multiple (src to dst) mappings, and AMANDA can make backup level decisions
knowing the full scope of the problem for that cycle. Given that I have fewer
clients than backup-cycles, I can space my level 0 backups so that I never do
more than one on any given night. I can fear that AMANDA will schedule everyone
for level 0 and backups are still proceeding the next day! That would be
disruptive and embarrassing.
I think what I'm asking is if I can backup a set of DLEs to a single tapedev,
and have a single copy of AMANDA run multiple backups each night? I can't mix
clients on the backup media, since each has different security and custody
requirements, and I think I'd like AMANDA to be aware of the complete set of
tasks for any given night without coming into conflict with AMANDA
doppelgangers, unless I'm inventing problems that don't exist and there is no
problem running multiple copies of AMANDA.
I may be looking to solve a non-problem, meaning that running multiple copies
of AMANDA each night is not a problem and hearing, "That is not a problem."
from those who know would be comforting.
Thanks for the help,
--
Chris.
V:916.974.0424
F:916.974.0428
