> On Mar 22, 2018, at 6:03 PM, Ryan, Lyle (US) <[email protected]> wrote: > > I've got an Amanda 3.4.5 server running on Centos 7 now, and am able to do > rudimentary backups of a remote client. > > But in spite of reading man pages, HowTo's, etc, I need help choosing config > params. I don't mind continuing to read and experiment, but if someone could > get me at least in the ballpark, I'd really appreciate it. > > The server has an 11TB filesystem to store the backups in. I should probably > be fancier and split this up more, but not now. So I've got my holding, > state, and vtapes directories all in there. > > The main client I want to back up has 4TB I want to backup. It's almost all > in one filesystem, but the HowTo for splitting DLE's with exclude lists is > clear, so it should be easy to split this into (say) 10 smaller individual > dumps. The bulk of the data is pretty static, maybe 10%/month changes. It's > hard to imagine 20%/month changing. > > For a start, I'd like to get a full done every 2 weeks, and > incrementals/differentials on the intervening days. If I have room to keep > 2 fulls (2 complete dumpcycles) that would be great. > > So I'm thinking: > - dumpcycle = 14 > - runspercycle = 0 (default) > - tapecycle = 30 > - runtapes = 1 (default) > > I'd break the filesystem into 10 pieces, so 400GB each. and make the vtapes > 400GB each (with tapetype length) relying on server-side compression to make > it fit. > The HowTo "Use pigz to speed compression" looks clear, and the DL380 G7 isn't > doing anything else, so server-side compression sounds good. > > Any advice on this or better ideas? Maybe I'm off in left-field. > > And one bonus question: I'm assuming Amanda will just make vtapes as > necessary, but is there any guidance as to how many vtape slots I should > create ahead of time? If my dumpcycle=14, maybe create 14 slots just to make > tapes easier to find? > > Thanks...Lyle
First pass, from a long time user. Those more expert, feel free to correct me. If you say tapecycle =30, then you ought to have 30 vtapes available. Were you going to swap in another 11TB disk or something, when the 14 in one dump cycle ran out? You’ve told it you have 30 total, so you need to have 30 somewhere. runspercycle — if you are doing incrementals on “the intervening days” then you are doing 14 runspercycle. Dumpcycle = 14 merely tells it how long it has to fit in a level 0 of everything, at least once. Now, if you aren’t running on weekends, you can have runspercycle=10 and still have dumpcycle= 14. If you want to keep at least 2 of each level 0, then tapecycle must be >= 2 x 14, so 30 is a nice number for tapecycle. I *think* you need to make the vtapes, and label them, in advance. ( Caveat: there is a way to have it “auto label” (v)tapes, so perhaps you don’t have to label them. But I sure don’t think it is going to create them for you. Deb Baddorf Fermilab
