Re: some suggested config parameters for backups to local disk

[Debra S Baddorf]

> On Mar 22, 2018, at 6:03 PM, Ryan, Lyle (US)  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

some suggested config parameters for backups to local disk

[Ryan, Lyle (US)]

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

Re: Community ZWC Issue

[Chris Nighswonger]

Ping.


On Sun, Mar 18, 2018 at 1:34 PM, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:

> No takers? To be sure someone who works on the ZWC can comment on what
> sorts of issues might cause this change in behavior.
>
> Kind regards,
>
> Chris
>
> On Mar 14, 2018 3:24 PM, "Chris Nighswonger" 
> wrote:
>
>> Thanks Paddy. I also had to restart the ZWC service to make the log level
>> change effective.
>>
>> So maybe someone who works on the ZWC code can explain what operation
>> might account for the following differences in log entries. Both are from
>> the same machine. The backup began failing with the 18/1/2018 run. I wonder
>> if ZWC is doing some sort of name resolution here which suddenly began to
>> fail? On the client, nslookup results are correct both ways (see below).
>> This same failure occurs on all of my ZWC installs.
>>
>> ZWC working fine:
>>
>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Entering
>> ExecuteValidateServerJob
>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Server address to be
>> validated from the list of authentic server = 192.168.x.x
>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Server name =
>> scriptor.foo.bar
>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Authentic Server name
>> = scriptor.foo.bar
>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Leaving
>> ExecuteValidateServerJob
>>
>> ZWC borking:
>>
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Entering
>> ExecuteValidateServerJob
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Server address to be
>> validated from the list of authentic server = 192.168.x.x
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Server name =
>> 192.168.x.x
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Authentic Server name
>> = scriptor.foo.bar
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Server Validation
>> Failed - Server 192.168.x.x With IP 192.168.x.x is not registered
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Leaving
>> ExecuteValidateServerJob
>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler:: Exiting ExecuteJob
>> with status = 65535
>>
>> Client-side nslookup:
>>
>> PS C:\Program Files\Zmanda\Zmanda Client for Windows Community
>> Edition(x64)\bin> nslookup 192.168.x.x
>> Server:  UnKnown
>> Address:  192.168.y.y
>>
>> Name:scriptor.foo.bar
>> Address:  192.168.x.x
>>
>> PS C:\Program Files\Zmanda\Zmanda Client for Windows Community
>> Edition(x64)\bin> nslookup scriptor.foo.bar
>> Server:  UnKnown
>> Address:  192.168.x.x
>>
>> Name:scriptor.foo.bar
>> Address:  192.168.x.x
>>
>> PS C:\Program Files\Zmanda\Zmanda Client for Windows Community
>> Edition(x64)\bin>
>>
>> Kind regards,
>> Chris
>>
>>
>> On Fri, Mar 9, 2018 at 10:46 AM, Paddy Sreenivasan <
>> paddy.sreeniva...@gmail.com> wrote:
>>
>>>
>>>1. Open the ZWC Config Utility: Start Menu → All Programs → Zmanda → 
>>> Zmanda
>>>Client for Windows → ZWC Config Utility
>>>2. Select the Logging tab
>>>3. Set Log Level to 5
>>>4. Click Save
>>>5. Click Exit
>>>
>>>
>>>
>>> On Fri, Mar 9, 2018 at 5:59 AM, Chris Nighswonger <
>>> cnighswon...@foundations.edu> wrote:
>>>
 Jean-Louis can you help with this? Is there a way to up the verbosity
 level of the ZWC log?


 On Tue, Feb 27, 2018 at 10:43 AM, Chris Nighswonger <
 cnighswon...@foundations.edu> wrote:

> No takers?
>
> The ZWC is always a hard one to gin up help for.
>
> An additional piece of information: DNS resolution seems to be working
> fine both server and client side.
>
>
>
> On Fri, Feb 23, 2018 at 8:34 AM, Chris Nighswonger <
> cnighswon...@foundations.edu> wrote:
>
>> Any thoughts on what might be going on here?
>>
>> Last week I began to have numerous Win10 clients failing in this
>> fashion:
>>
>> backup@scriptor:/home/manager amcheck -c campus shipping.foo.bar
>>
>> Amanda Backup Client Hosts Check
>> 
>> ERROR: shipping.foo.bar: Server validation Failed. Please register
>> server with client.
>> Client check: 1 host checked in 0.072 seconds.  1 problem found.
>>
>> Taking a look at the ZWC debug log on that client, I see the
>> following:
>>
>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Entering
>> ExecuteValidateServerJob
>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Server address to
>> be validated from the list of authentic server = 192.168.x.x
>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Server name =
>> 192.168.x.x
>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Authentic Server
>> name = scriptor.foo.bar
>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Server Validation
>> Failed - Server 192.168.x.x With IP 192.168.x.x is not registered
>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Leaving
>>