Re: Reusable
On 11/26/18 2:32 PM, J Chapman Flack wrote: > Jean-Louis mentioned the amraw application as one that can be used on > a single file: http://wiki.zmanda.com/man/3.5.1/amraw.8.html > > In the pending pull request #11, there are some others as well: > > amooraw:... amgrowingfile:... amgrowingzip:... I've realized I gave the wrong PR number here, it is pull request #78. Sorry. https://github.com/zmanda/amanda/pull/78 I was looking at the number saying it's currently the 11th open PR. -Chap
Re: Configuration Rollback [Was: Reusable]
On Mon, Nov 26, 2018 at 20:00:09 +, Debra S Baddorf wrote: > promoting a DLE to do an early level 0. Doing 21 runs in NN minutes > will use up all your vtapes, but will not force more than 1 level 0. (Yes, you are correct -- that's why I was asking about the output of "amoverview" for him last week, etc) On Mon, Nov 26, 2018 at 20:19:06 +, Cuttler, Brian R (HEALTH) wrote: > Based on the latest emails I think Chris may have moved on, but he has > these additional answers for when he cycles back. > (Note that the emails today are from a different Chris -- I don't believe we've heard back from Chris Miller since last week) Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
RE: Configuration Rollback [Was: Reusable]
Depending on what I'm testing and its importance I may just # cp tapelist.yesterday tapelist or manually alter it. -Original Message- From: Debra S Baddorf Sent: Monday, November 26, 2018 3:25 PM To: Cuttler, Brian R (HEALTH) Cc: Debra S Baddorf ; Debra S Baddorf ; amanda-users Subject: Re: Configuration Rollback [Was: Reusable] ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. > On Nov 26, 2018, at 2:19 PM, Cuttler, Brian R (HEALTH) > wrote: > > Deb, > > I'm with you, periodically I have to test something, or will start an > additional backup to help move data after a failure of some sort but in > general I allow cron to start # amdump once/day. My understanding matches > yours, balance will get thrown off, amanda may advance dumps but you chew up > a lot of tape and do a lot of I/O for little overall gain if you are running > multiple dumps as a matter of course. When I have something that failed/was missed OR a new node or DLE to add, I do amdump config —no-taper node DLE so test the dump, but leave the results on my holding disk. It’ll be flushed when tonight’s backup starts. So I don’t HAVE to chew up tape, just to test things. :) Deb Baddorf > > I have even gone so far as run run multiple dumps across a very small > (perhaps "1") DLE to test include/exclude or get a new dumptype (snapshot) or > compress(pig/parallel zip) tested, but do not run multiple dumps as a matter > of routine. > > In my mind running many small DLEs can be self-defeating, as can running very > few very large once, each hitting a different set of constraints. > > My samba shares are on separate ZFS mount points and I snapshot them. My home > directories are also on separate ZFS mount points but individual backups were > untenable so I glob them by letter, but that means I can't do snapshots. > > Based on the latest emails I think Chris may have moved on, but he has these > additional answers for when he cycles back. > > Thanks, > Brian > > > -Original Message- > From: Debra S Baddorf > Sent: Monday, November 26, 2018 3:00 PM > To: amanda-users > Cc: Debra S Baddorf ; Debra S Baddorf > ; Cuttler, Brian R (HEALTH) > > Subject: Re: Configuration Rollback [Was: Reusable] > > ATTENTION: This email came from an external source. Do not open attachments > or click on links from unknown senders or unexpected emails. > > >> >> -Original Message- >> From: owner-amanda-us...@amanda.org >> On Behalf Of Debra S Baddorf >> Sent: Monday, November 26, 2018 2:04 PM >> To: amanda-users >> Cc: Debra S Baddorf >> Subject: Re: Configuration Rollback [Was: Reusable] >> >> ATTENTION: This email came from an external source. Do not open attachments >> or click on links from unknown senders or unexpected emails. >> >> >>> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger >>> wrote: >>> >>> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: >>> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: >>>> Hi Folks, >>>> >>>> I have written some very small DLEs so I can rip through weeks of >>>> backups in minutes. I've learned some things. >>> >> >> Am I wrong in thinking that you cannot do extra backups, to get to the end >> of your “dumpcycle” faster? >> Dumpcycle is explicitly in days, not number of times run. Isn’t it? >> >> Deb Baddorf >> Fermilab >> >> >> >> On Nov 26, 2018, at 1:21 PM, Cuttler, Brian R (HEALTH) >> wrote: >> >> Deb, >> >> Not sure if I'm understanding your question. If so I believe Amanda was >> built with the concept of a once/day run schedule taking into account >> runs/cycle as well as days/dumpcycle (for instance 5 run days in a one week >> dump cycle). >> >> Brian > > Yes, I agree. At one point, Chris was trying to speed this up by doing 21 > runs in 10 minutes or so. > Perhaps he has stopped that, and people are just continuing to quote that > line (above). It’s that line that’s bothering me. > > He did ask "Can I specify "dumpcycle" as an elapsed count rather than an > elapsed time?” > Per the wiki help files, dumpcycle seems to be explicitly in “days” and > cannot be changed or sped up. > ( > https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye. > com_url-3Fk-3D42d018d223e76922.42d2e1e7-2D4a9f6eb7b4f1e3bb-26u-3Dhttps > -3A__wiki.zmanda.com_index.php_Dumpcycle=DwIGaQ=gRgGjJ3BkIsb5y6s49 > QqsA=HMrKaRiCv4jddln9fLPIOw=
Re: Configuration Rollback [Was: Reusable]
> On Nov 26, 2018, at 2:19 PM, Cuttler, Brian R (HEALTH) > wrote: > > Deb, > > I'm with you, periodically I have to test something, or will start an > additional backup to help move data after a failure of some sort but in > general I allow cron to start # amdump once/day. My understanding matches > yours, balance will get thrown off, amanda may advance dumps but you chew up > a lot of tape and do a lot of I/O for little overall gain if you are running > multiple dumps as a matter of course. When I have something that failed/was missed OR a new node or DLE to add, I do amdump config —no-taper node DLE so test the dump, but leave the results on my holding disk. It’ll be flushed when tonight’s backup starts. So I don’t HAVE to chew up tape, just to test things. :) Deb Baddorf > > I have even gone so far as run run multiple dumps across a very small > (perhaps "1") DLE to test include/exclude or get a new dumptype (snapshot) or > compress(pig/parallel zip) tested, but do not run multiple dumps as a matter > of routine. > > In my mind running many small DLEs can be self-defeating, as can running very > few very large once, each hitting a different set of constraints. > > My samba shares are on separate ZFS mount points and I snapshot them. My home > directories are also on separate ZFS mount points but individual backups were > untenable so I glob them by letter, but that means I can't do snapshots. > > Based on the latest emails I think Chris may have moved on, but he has these > additional answers for when he cycles back. > > Thanks, > Brian > > > -Original Message- > From: Debra S Baddorf > Sent: Monday, November 26, 2018 3:00 PM > To: amanda-users > Cc: Debra S Baddorf ; Debra S Baddorf ; > Cuttler, Brian R (HEALTH) > Subject: Re: Configuration Rollback [Was: Reusable] > > ATTENTION: This email came from an external source. Do not open attachments > or click on links from unknown senders or unexpected emails. > > >> >> -Original Message- >> From: owner-amanda-us...@amanda.org On >> Behalf Of Debra S Baddorf >> Sent: Monday, November 26, 2018 2:04 PM >> To: amanda-users >> Cc: Debra S Baddorf >> Subject: Re: Configuration Rollback [Was: Reusable] >> >> ATTENTION: This email came from an external source. Do not open attachments >> or click on links from unknown senders or unexpected emails. >> >> >>> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger >>> wrote: >>> >>> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: >>> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: >>>> Hi Folks, >>>> >>>> I have written some very small DLEs so I can rip through weeks of >>>> backups in minutes. I've learned some things. >>> >> >> Am I wrong in thinking that you cannot do extra backups, to get to the end >> of your “dumpcycle” faster? >> Dumpcycle is explicitly in days, not number of times run. Isn’t it? >> >> Deb Baddorf >> Fermilab >> >> >> >> On Nov 26, 2018, at 1:21 PM, Cuttler, Brian R (HEALTH) >> wrote: >> >> Deb, >> >> Not sure if I'm understanding your question. If so I believe Amanda was >> built with the concept of a once/day run schedule taking into account >> runs/cycle as well as days/dumpcycle (for instance 5 run days in a one week >> dump cycle). >> >> Brian > > Yes, I agree. At one point, Chris was trying to speed this up by doing 21 > runs in 10 minutes or so. > Perhaps he has stopped that, and people are just continuing to quote that > line (above). It’s that line that’s bothering me. > > He did ask "Can I specify "dumpcycle" as an elapsed count rather than an > elapsed time?” > Per the wiki help files, dumpcycle seems to be explicitly in “days” and > cannot be changed or sped up. > ( > https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D42d018d223e76922.42d2e1e7-2D4a9f6eb7b4f1e3bb-26u-3Dhttps-3A__wiki.zmanda.com_index.php_Dumpcycle=DwIGaQ=gRgGjJ3BkIsb5y6s49QqsA=HMrKaRiCv4jddln9fLPIOw=l_nUa8ln6_AcIwhv7dPsFLOJjoUvcO0FZC_Go-Kk0_Q=jgJt912esNKK5Qjd43o1uniBJyWyfB4otVSX4o4CDL8= > ) > > Chris also asked "Are "dumpcycle" and "runspercycle" conflicting with each > other?” > Even if you occasionally do extra amdump runs (I do), that doesn’t bother > the “runspercycle” count. It still results in “at least one level 0 within > dumpcycle days”.Runspercycle just lets amanda gauge numbers for balance > adjusting, and maybe promoting a DLE to do an early level 0. > Doing 21 runs in NN minutes will use up all your vtapes, but will not force > more than 1 level 0. > > Maybe I’m being pedantic, and he’s looking at other issues now. If so, > nevermind me! > :) > > Deb Baddorf > > >
RE: Configuration Rollback [Was: Reusable]
Deb, I'm with you, periodically I have to test something, or will start an additional backup to help move data after a failure of some sort but in general I allow cron to start # amdump once/day. My understanding matches yours, balance will get thrown off, amanda may advance dumps but you chew up a lot of tape and do a lot of I/O for little overall gain if you are running multiple dumps as a matter of course. I have even gone so far as run run multiple dumps across a very small (perhaps "1") DLE to test include/exclude or get a new dumptype (snapshot) or compress(pig/parallel zip) tested, but do not run multiple dumps as a matter of routine. In my mind running many small DLEs can be self-defeating, as can running very few very large once, each hitting a different set of constraints. My samba shares are on separate ZFS mount points and I snapshot them. My home directories are also on separate ZFS mount points but individual backups were untenable so I glob them by letter, but that means I can't do snapshots. Based on the latest emails I think Chris may have moved on, but he has these additional answers for when he cycles back. Thanks, Brian -Original Message- From: Debra S Baddorf Sent: Monday, November 26, 2018 3:00 PM To: amanda-users Cc: Debra S Baddorf ; Debra S Baddorf ; Cuttler, Brian R (HEALTH) Subject: Re: Configuration Rollback [Was: Reusable] ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. > > -Original Message- > From: owner-amanda-us...@amanda.org On > Behalf Of Debra S Baddorf > Sent: Monday, November 26, 2018 2:04 PM > To: amanda-users > Cc: Debra S Baddorf > Subject: Re: Configuration Rollback [Was: Reusable] > > ATTENTION: This email came from an external source. Do not open attachments > or click on links from unknown senders or unexpected emails. > > >> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger >> wrote: >> >> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: >> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: >>> Hi Folks, >>> >>> I have written some very small DLEs so I can rip through weeks of >>> backups in minutes. I've learned some things. >> > > Am I wrong in thinking that you cannot do extra backups, to get to the end > of your “dumpcycle” faster? > Dumpcycle is explicitly in days, not number of times run. Isn’t it? > > Deb Baddorf > Fermilab > > > > On Nov 26, 2018, at 1:21 PM, Cuttler, Brian R (HEALTH) > wrote: > > Deb, > > Not sure if I'm understanding your question. If so I believe Amanda was built > with the concept of a once/day run schedule taking into account runs/cycle as > well as days/dumpcycle (for instance 5 run days in a one week dump cycle). > > Brian Yes, I agree. At one point, Chris was trying to speed this up by doing 21 runs in 10 minutes or so. Perhaps he has stopped that, and people are just continuing to quote that line (above). It’s that line that’s bothering me. He did ask "Can I specify "dumpcycle" as an elapsed count rather than an elapsed time?” Per the wiki help files, dumpcycle seems to be explicitly in “days” and cannot be changed or sped up. ( https://protect2.fireeye.com/url?k=42d018d223e76922.42d2e1e7-4a9f6eb7b4f1e3bb=https://wiki.zmanda.com/index.php/Dumpcycle ) Chris also asked "Are "dumpcycle" and "runspercycle" conflicting with each other?” Even if you occasionally do extra amdump runs (I do), that doesn’t bother the “runspercycle” count. It still results in “at least one level 0 within dumpcycle days”.Runspercycle just lets amanda gauge numbers for balance adjusting, and maybe promoting a DLE to do an early level 0. Doing 21 runs in NN minutes will use up all your vtapes, but will not force more than 1 level 0. Maybe I’m being pedantic, and he’s looking at other issues now. If so, nevermind me! :) Deb Baddorf
Re: Reusable
On 11/21/18 2:55 PM, Chris Miller wrote: > AMANDA can't backup a file; only directories. Is there any way around > that? Suppose I need to backup a large file in a directory with many > other large files, so backing up the complete directory or moving / > copying my target would be inconvenient, not to mention > administratively cumbersome when it comes to restoring. Jean-Louis mentioned the amraw application as one that can be used on a single file: http://wiki.zmanda.com/man/3.5.1/amraw.8.html In the pending pull request #11, there are some others as well: amooraw: this is just the same as amraw but implemented in the OO style made possible in PR#11, to show how the development is simplified. Like amraw, it only supports full backups. amgrowingfile: this is specific to the case where the single file is something that grows very large and only by appending (think audit or log files, etc). It can do efficient incremental backups of the single file (an increment is just what has been appended since the last one). A level 0 has to be forced any time the file is rewritten any other way than appending. amgrowingzip: like amgrowingfile but for the special case where the single file is a large zip archive that is only grown by appending new members at the end. It also supports increments. A level 0 must be forced any time the file is modified any other way than adding new zip members at the end. In the preliminary man pages with the pull request, amooraw is on page 12, amgrowingfile on page 9, and amgrowingzip on page 10. https://github.com/zmanda/amanda/files/1265069/AppScriptWithAbstractClasses.pdf -Chap
Re: Configuration Rollback [Was: Reusable]
> > -Original Message- > From: owner-amanda-us...@amanda.org On Behalf > Of Debra S Baddorf > Sent: Monday, November 26, 2018 2:04 PM > To: amanda-users > Cc: Debra S Baddorf > Subject: Re: Configuration Rollback [Was: Reusable] > > ATTENTION: This email came from an external source. Do not open attachments > or click on links from unknown senders or unexpected emails. > > >> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger >> wrote: >> >> On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: >> On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: >>> Hi Folks, >>> >>> I have written some very small DLEs so I can rip through weeks of >>> backups in minutes. I've learned some things. >> > > Am I wrong in thinking that you cannot do extra backups, to get to the end > of your “dumpcycle” faster? > Dumpcycle is explicitly in days, not number of times run. Isn’t it? > > Deb Baddorf > Fermilab > > > > On Nov 26, 2018, at 1:21 PM, Cuttler, Brian R (HEALTH) > wrote: > > Deb, > > Not sure if I'm understanding your question. If so I believe Amanda was built > with the concept of a once/day run schedule taking into account runs/cycle as > well as days/dumpcycle (for instance 5 run days in a one week dump cycle). > > Brian Yes, I agree. At one point, Chris was trying to speed this up by doing 21 runs in 10 minutes or so. Perhaps he has stopped that, and people are just continuing to quote that line (above). It’s that line that’s bothering me. He did ask "Can I specify "dumpcycle" as an elapsed count rather than an elapsed time?” Per the wiki help files, dumpcycle seems to be explicitly in “days” and cannot be changed or sped up. ( https://wiki.zmanda.com/index.php/Dumpcycle ) Chris also asked "Are "dumpcycle" and "runspercycle" conflicting with each other?” Even if you occasionally do extra amdump runs (I do), that doesn’t bother the “runspercycle” count. It still results in “at least one level 0 within dumpcycle days”.Runspercycle just lets amanda gauge numbers for balance adjusting, and maybe promoting a DLE to do an early level 0. Doing 21 runs in NN minutes will use up all your vtapes, but will not force more than 1 level 0. Maybe I’m being pedantic, and he’s looking at other issues now. If so, nevermind me! :) Deb Baddorf
RE: Configuration Rollback [Was: Reusable]
Deb, Not sure if I'm understanding your question. If so I believe Amanda was built with the concept of a once/day run schedule taking into account runs/cycle as well as days/dumpcycle (for instance 5 run days in a one week dump cycle). Brian -Original Message- From: owner-amanda-us...@amanda.org On Behalf Of Debra S Baddorf Sent: Monday, November 26, 2018 2:04 PM To: amanda-users Cc: Debra S Baddorf Subject: Re: Configuration Rollback [Was: Reusable] ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. > On Nov 24, 2018, at 9:47 AM, Chris Nighswonger > wrote: > > On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: > On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: > > Hi Folks, > > > > I have written some very small DLEs so I can rip through weeks of > > backups in minutes. I've learned some things. > Am I wrong in thinking that you cannot do extra backups, to get to the end of your “dumpcycle” faster? Dumpcycle is explicitly in days, not number of times run. Isn’t it? Deb Baddorf Fermilab
Re: Configuration Rollback [Was: Reusable]
> On Nov 24, 2018, at 9:47 AM, Chris Nighswonger > wrote: > > On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: > On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: > > Hi Folks, > > > > I have written some very small DLEs so I can rip through weeks > > of backups in minutes. I've learned some things. > Am I wrong in thinking that you cannot do extra backups, to get to the end of your “dumpcycle” faster? Dumpcycle is explicitly in days, not number of times run. Isn’t it? Deb Baddorf Fermilab
Configuration Rollback [Was: Reusable]
On Fri, Nov 23, 2018 at 6:47 PM Jon LaBadie wrote: > On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: > > Hi Folks, > > > > I have written some very small DLEs so I can rip through weeks > > of backups in minutes. I've learned some things. > > When I'm experimenting with amanda after I create the > test configuration, before the first amdump run, I > copy or tar the entire configuration. > > Then I write a little shell script so that after I've > run a few test dumps, I can delete the entire config > and restore it to the original state from the copy or > tarball. > I use Git and create a repo at the root of each configuration. Every change gets a commit. Rolling back to any point in time is super easy in that way. It has saved my skin on several occasions. Kind regards, Chris
Re: Reusable
On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: > Hi Folks, > > I have written some very small DLEs so I can rip through weeks > of backups in minutes. I've learned some things. When I'm experimenting with amanda after I create the test configuration, before the first amdump run, I copy or tar the entire configuration. Then I write a little shell script so that after I've run a few test dumps, I can delete the entire config and restore it to the original state from the copy or tarball. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: Reusable
On Wed, Nov 21, 2018 at 11:55:21AM -0800, Chris Miller wrote: > Hi Folks, > > I have written some very small DLEs so I can rip through weeks > of backups in minutes. I've learned some things. AMANDA can't > backup a file; only directories. Is there any way around that? > Suppose I need to backup a large file in a directory with many > other large files, so backing up the complete directory or > moving / copying my target would be inconvenient, not to mention > administratively cumbersome when it comes to restoring. Create a DLE that would backup the entire directory. Then add the command "include list " in the DLE and it will exclude all others. > > I'm also still fighting AMANDA about how to manage vtapes, but I'm developing > more focused questions. For example, my test runs are reporting: > jl -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: Reusable
On Wed, Nov 21, 2018 at 12:09:50 -0800, Chris Miller wrote: > There is a new question, however. AMANDA warned me as I approached the > overwrite of slot0, which was the first backup, and consequently a > level 0 dump. Apparently AMANDA thought it was my only level 0 dump. > > My config defines: > dumpcycle 1week > runspercycle 7 > tapecycle 21 > > I thought I was requesting level 0 once every seven, but apparently not. > (What's the exact text of the warning in question? Knowing that would help give more precise explanations.) Note that dumpcycle is specified in days, but if you are running multiple runs per day then it would be possible to fill up 21 tapes in less than 7 days, and Amanda might not have scheduled a second level 0 for some DLEs in that period of time. The "amoverview" command can show you if in fact your tape .0 is the only one with a level 0 dump for some DLE(s). Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: Reusable
On Wed, Nov 21, 2018 at 11:55:21 -0800, Chris Miller wrote: > Hi Folks, > > I have written some very small DLEs so I can rip through weeks of > backups in minutes. I've learned some things. AMANDA can't backup a [...] (Do you mean so you can do some test runs quickly, running multiple runs in a day? This can definitily be useful, but keep in mind that 1) it won't give you accurate results for the full dump for the "balance" stuff we've been discussing in that recent thread on this list, and 2) if you are manually running more than one run per day, you are going to mess up your dumpcycle v.s. tapecycle calculations, etc.) > I'm also still fighting AMANDA about how to manage vtapes, but I'm > developing more focused questions. For example, my test runs are > reporting: > > NOTES: > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > > So, how do I designate a slot as having a volume that is re-usable? This overlaps with the email I just sent in your other thread, but I just wanted to make sure you have figured out by now that the message "... is not resuable" does not mean "the administrator has configured this tape as one that cannot be reused" (though it is possible for you do do such a thing). Rather, the message means "due to some constraint or other, I cannot use this tape right this minute". Hopefully the output of "amtape ... inventory" and/or "amadmin ... retention" will tell us exactly why. Nathan Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: Reusable
On Wednesday 21 November 2018 15:09:50 Chris Miller wrote: > Hi Folks, > > > From: "Chris Miller" > > To: "amanda-users" > > Sent: Wednesday, November 21, 2018 11:55:21 AM > > Subject: Reusable > > > > I'm also still fighting AMANDA about how to manage vtapes, but I'm > > developing more focused questions. For example, my test runs are > > reporting: > > > > NOTES: > > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > > > > So, how do I designate a slot as having a volume that is re-usable? > > This is a "Type II" error, meaning that the error is my thinking that > it is an error. Apparently this message means something other then I > thought, because as I continue my blitz, these tapes cycle just fine. > > There is a new question, however. AMANDA warned me as I approached the > overwrite of slot0, which was the first backup, and consequently a > level 0 dump. Apparently AMANDA thought it was my only level 0 dump. > My config defines: dumpcycle 1week > runspercycle 7 > tapecycle 21 > > I thought I was requesting level 0 once every seven, but apparently > not. > That is not how amanda works. And its unique among backup tools, having orginally been written when a 200 meg qic drive was a luxury. After it has done an initial level 0 backup it will make an estimate for each succeeding backup, advanceing level 0's in order to more evenly fill the tapes, "making room in the future" to backup the big ones before that 7 days of age occurs. That is so you could both fill the tape more efficiently, and guarantee amanda will also do the level 0's a bit more frequently than dumpcycle. Look at that as a guarantee of the maximum time between level 0's. Each time amanda does a level 0, the dumpcycle timer for that DLE is reset. > Thanks for the help, NP. Copyright 2018 by Maurice E. Heskett -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Reusable
On Wednesday 21 November 2018 14:55:21 Chris Miller wrote: > Hi Folks, > > I have written some very small DLEs so I can rip through weeks of > backups in minutes. I've learned some things. AMANDA can't backup a > file; only directories. Is there any way around that? Suppose I need > to backup a large file in a directory with many other large files, so > backing up the complete directory or moving / copying my target would > be inconvenient, not to mention administratively cumbersome when it > comes to restoring. > > I'm also still fighting AMANDA about how to manage vtapes, but I'm > developing more focused questions. For example, my test runs are > reporting: > > NOTES: > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > > So, how do I designate a slot as having a volume that is re-usable? > > Thanks for the help, Please see your example/disklist file in the src tree. Something I have done for years to get a consistent build that just works after an upgrade. There are recipes there, near the top of the file that can do or do not, an individual file. I'm using such a scheme to break up the huge directories here. I might point out that using a compressing dumptype is by and large a waste of time when dealing with really big files like a .iso or .gz, bz2, etc is generally lost time trying to compress already compressed data. Copyright 2018 by Maurice E. Heskett -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Reusable
Hi Deb, > From: "Debra S Baddorf" > To: "Chris Miller" > Cc: "Debra S Baddorf" , "amanda-users" > Sent: Wednesday, November 21, 2018 12:20:57 PM > Subject: Re: Reusable >> dumpcycle 1week >> runspercycle 7 >> tapecycle 21 >> >> I thought I was requesting level 0 once every seven, but apparently not. > > I agree that I think you are requesting level 0 once every week. Have you run > for 21 days? Even if you manually did extra runs, it looks at the date > stamp. Well, that makes perfect sense. Can I specify "dumpcycle" as an elapsed count rather than an elapsed time? Are "dumpcycle" and "runspercycle" conflicting with each other? > (At least, I don’t recall that this conversation has taken more than 3 weeks). I can be tedious, but I doubt I have exhausted anyone's patience yet. (-: Thanks for the help, Deb. -- Chris. V:916.974.0424 F:916.974.0428
Re: Reusable
> On Nov 21, 2018, at 2:09 PM, Chris Miller wrote: > > Hi Folks, > From: "Chris Miller" > To: "amanda-users" > Sent: Wednesday, November 21, 2018 11:55:21 AM > Subject: Reusable > I'm also still fighting AMANDA about how to manage vtapes, but I'm developing > more focused questions. For example, my test runs are reporting: > > NOTES: > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > > So, how do I designate a slot as having a volume that is re-usable? > This is a "Type II" error, meaning that the error is my thinking that it is > an error. Apparently this message means something other then I thought, > because as I continue my blitz, these tapes cycle just fine. > > There is a new question, however. AMANDA warned me as I approached the > overwrite of slot0, which was the first backup, and consequently a level 0 > dump. Apparently AMANDA thought it was my only level 0 dump. My config > defines: > dumpcycle 1week > runspercycle 7 > tapecycle 21 > > I thought I was requesting level 0 once every seven, but apparently not. > > Thanks for the help, > -- > Chris. > I agree that I think you are requesting level 0 once every week. Have you run for 21 days? Even if you manually did extra runs, it looks at the date stamp. So it hasn’t been tricked into doing extra level 0’s. (At least, I don’t recall that this conversation has taken more than 3 weeks). Try setting tapecycle to 7 while you are testing. Or even lower, but then change the other numbers too. Deb
Re: Reusable
> On Nov 21, 2018, at 1:55 PM, Chris Miller wrote: > > Hi Folks, > > I have written some very small DLEs so I can rip through weeks of backups in > minutes. I've learned some things. AMANDA can't backup a file; only > directories. Is there any way around that? Suppose I need to backup a large > file in a directory with many other large files, so backing up the complete > directory or moving / copying my target would be inconvenient, not to mention > administratively cumbersome when it comes to restoring. > > I'm also still fighting AMANDA about how to manage vtapes, but I'm developing > more focused questions. For example, my test runs are reporting: > > NOTES: > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > > So, how do I designate a slot as having a volume that is re-usable? > > Thanks for the help, > -- > Chris. > > V:916.974.0424 > F:916.974.0428 1) You can always “amrecover” a single file, even if you’ve restored a whole directory. That’s only a half answer to what you asked. 2) amadmin config reuse TAPENAME man amadmin to check this option, but I think I’ve written it right 3) You still cannot reuse a tape until your “tapecycle” number of tapes is re-used. That’s how you told it how many tapes to use before writing over contents. 4) However, you can remove those contents by “amrmtape” removing the tape, and then relabelling it. This nominally blanks it. It also removes the record of what it contained … because you just told it you never want to use those contents; you threw them out. amrmtape config TAPENAME it erases it from the tapelist, and erases the contents from the currinfo (and etc) directories. Then re-label it with the same name & number as before. Deb Baddorf Fermilab
Re: Reusable
Use the amraw application to backup a single file. it backup on;y the data, not the meta-data: filename permission, stat, ... man amraw Le mer. 21 nov. 2018, à 15 h 01, Chris Miller a écrit : > Hi Folks, > > I have written some very small DLEs so I can rip through weeks of backups > in minutes. I've learned some things. AMANDA can't backup a file; only > directories. Is there any way around that? Suppose I need to backup a large > file in a directory with many other large files, so backing up the complete > directory or moving / copying my target would be inconvenient, not to > mention administratively cumbersome when it comes to restoring. > > I'm also still fighting AMANDA about how to manage vtapes, but I'm > developing more focused questions. For example, my test runs are reporting: > > NOTES: > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > > So, how do I designate a slot as having a volume that is re-usable? > > Thanks for the help, > -- > Chris. > > V:916.974.0424 > F:916.974.0428 >
Re: Reusable
Hi Folks, > From: "Chris Miller" > To: "amanda-users" > Sent: Wednesday, November 21, 2018 11:55:21 AM > Subject: Reusable > I'm also still fighting AMANDA about how to manage vtapes, but I'm developing > more focused questions. For example, my test runs are reporting: > NOTES: > taper: Slot 13 with label Mail.TCLC.org-13 is not reusable > So, how do I designate a slot as having a volume that is re-usable? This is a "Type II" error, meaning that the error is my thinking that it is an error. Apparently this message means something other then I thought, because as I continue my blitz, these tapes cycle just fine. There is a new question, however. AMANDA warned me as I approached the overwrite of slot0, which was the first backup, and consequently a level 0 dump. Apparently AMANDA thought it was my only level 0 dump. My config defines: dumpcycle 1week runspercycle 7 tapecycle 21 I thought I was requesting level 0 once every seven, but apparently not. Thanks for the help, -- Chris. V:916.974.0424 F:916.974.0428
Reusable
Hi Folks, I have written some very small DLEs so I can rip through weeks of backups in minutes. I've learned some things. AMANDA can't backup a file; only directories. Is there any way around that? Suppose I need to backup a large file in a directory with many other large files, so backing up the complete directory or moving / copying my target would be inconvenient, not to mention administratively cumbersome when it comes to restoring. I'm also still fighting AMANDA about how to manage vtapes, but I'm developing more focused questions. For example, my test runs are reporting: NOTES: taper: Slot 13 with label Mail.TCLC.org-13 is not reusable So, how do I designate a slot as having a volume that is re-usable? Thanks for the help, -- Chris. V:916.974.0424 F:916.974.0428
more than one tape reusable
This is probably something trivial. in my amanda.conf I have dumpcycle 1 week# the number of days in the normal dump cycle runspercycle 5 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just # weekdays) tapecycle 25 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the # previous # cycle runtapes1 I have indeed 25 tapes in my tapelist. Now when I do an amadmin myconfig tape it tells me The next Amanda run should go onto tape LTO020 or a new tape. Meaning there's only one specific tape amanda will overwrite. Im lazy, and Id like to have a list of 5 tapes (so that I can take the tapes for a whole week, stack them, next to the tapedrive, and use them in whatever order I please. What is the trick to get this done ? Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __O This parrot wouldn't voom if I put 4000 volts through it. It's bleeding =`\, demised. This parrot is no more. It has ceased to be. It's expired (=)/(=) gone to meet it's maker. This is a late parrot. It's a stiff. Bereft of life, it rests in peace. It's rung down the curtain joined the choir invisible. This is an EX-parrot.
Re: more than one tape reusable
On Feb 13, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
I have indeed 25 tapes in my tapelist.
Im lazy, and Id like to have a list of 5 tapes (so that I can take the
tapes for a whole week, stack them, next to the tapedrive, and use them in
whatever order I please.
What is the trick to get this done ?
Set tapecycle to 21. Then, any of the 5 oldest tapes will be
overwritable.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: more than one tape reusable
* Alexandre Oliva [EMAIL PROTECTED] (Tue, Feb 13, 2001 at 08:39:21AM -0200) On Feb 13, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote: I have indeed 25 tapes in my tapelist. Im lazy, and Id like to have a list of 5 tapes (so that I can take the tapes for a whole week, stack them, next to the tapedrive, and use them in whatever order I please. What is the trick to get this done ? Set tapecycle to 21. Then, any of the 5 oldest tapes will be overwritable. I just did that, and then I get this: # amadmin lto tape The next Amanda run should go onto tape LTO020 or a new tape. Am I missing something ? My tapelist file counts 25 tapes (LTO001 to LTO025) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: more than one tape reusable
Gerhard den Hollander wrote: * Alexandre Oliva [EMAIL PROTECTED] (Tue, Feb 13, 2001 at 08:39:21AM -0200) On Feb 13, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote: I have indeed 25 tapes in my tapelist. Im lazy, and Id like to have a list of 5 tapes (so that I can take the tapes for a whole week, stack them, next to the tapedrive, and use them in whatever order I please. What is the trick to get this done ? Set tapecycle to 21. Then, any of the 5 oldest tapes will be overwritable. I just did that, and then I get this: # amadmin lto tape The next Amanda run should go onto tape LTO020 or a new tape. Am I missing something ? My tapelist file counts 25 tapes (LTO001 to LTO025) I had a similar (understanding) problem, but without a changer. Just run amcheck with one of the tapes you want to overwrite. Amanda only *expects* lto020, but will overwrite any non-active tape, according to your tapecycle setting. Simon
Re: more than one tape reusable
On Feb 13, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
# amadmin lto tape
The next Amanda run should go onto tape LTO020 or a new tape.
Am I missing something ?
Just because Amanda tells you it wants LTO020, it doesn't mean it
won't accept one of the other 4 recyclable tapes. Just load one of
them into the tape drive and run `amcheck -t'.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
