On Mon, Oct 25, 2010 at 10:26:42AM +0200, Thomas Marko wrote: > Thank you Jon, Brian and Charles for your answers! >
Just a couple of thoughts ... > Am 21.10.10 21:50, schrieb Jon LaBadie: > > > Even if you want Daily and Weekly to be different configs, rather > > than DLEs of one config, consider putting the DLEs from the four > > weekly configs into a single config. First benefit you get is > > 24 tapes of the current size. The dumptype could be set to > > "strategy nofull" (or is it "strategy incronly" ?) and use > > amadmin "force" commands (from cron) to specify when to do fulls. > > It's not that important to know when amanda is doing fulldumps (I think > amanda is much cleverer than me to decide when to do it ;-), but my goal > is to keep backup times and the vtape usage as small as possible and > reasonable. > > Will amanda be that "clever" to make the full dumps of each DLE on > different days? If not, is it possible to achieve this? Amanda tries to get balance things so that each days dump will backup the same amount of data (actually, if compressed, the same amount of "tape" is more accurate). But it can't get there until it has a history of dumps and compression rates. Even with a history, if you have a relatively small number of DLEs and very different sizes, it can never completely balance things. Under these conditions amanda seems to full-dump the small DLEs frequently. > > When I setup this new configuration and run it initially amanda will > make full dumps of all DLEs in the first run, right? > > Should I run this first backup manually (I think it'll take more than a > day) and after that set up the cron job? I recently reworked my backup setup, essentially started over. At first I started with small pieces. If you are configured to use timestamps (usetimestamps yes) you can run multiple amdumps in one day. So I commented out all the DLEs in the disklist file and gradually uncommented them over several dumps. First a server DLE. Next another server DLE and one or two client DLEs. Third one more DLE from each host. Then for each regularly schedulded dump I uncommented one or two additional DLEs from each host. In my case, this took about 3 days. I suspect others would suggest dumping everything right from the start. > When using a holding disk and amanda can dump multiple DLEs at a time, > will it be that clever to use DLEs from different hosts to do a bit load > balancing (I do the compressing on client side)? If not, is it possible > to achieve that? There are parameters that control how many total simultaneous dumps max and how many simultaneous from one client max. I think I have them set to 4 and 1. > > > Seriously consider moving to the 3.x versions. > > At the moment I would be happy to understand how amanda works and get > amanda running in a way I want it to. I do not want to mess up in a > selfcompiled installation and run into more troubles needed. > Are prebuilt binaries available for your OSs at zmanda.com? > > If you run your backups on the "ragged edge" of sufficient storage, > > I would say your (i.e. your mgmt) do not value highly the data > > that is being backed up. An extra pair of 1-2TB drives would cost > > about $125-$250. Isn't extra safety of your data worth it? > > You are completely right, but there is no management (maybe but my wife > ;-) and the problem is not the amount of $ it's the amount of SATA > controllers ;-) in my backup "server" ;-) Same as my setup. And I ran into the same situation, only one channel of SATA on my selected amanda server (a very old Pentium-3). I just spent $29 more for another controller so I could add two more disks. One isn't even in a cage, it is lying on the bottom of the case. I also moved from the previous amanda server, two external USB drives and the USB 2.0 interface card I previously purchased for the old host. Neither had USB 2 when purchased. jl -- Jon H. LaBadie [email protected] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
