Amanda-Users

Re: Sizes don't fit?

2006-03-16 07:52:53
Subject: Re: Sizes don't fit?
From: listrcv <listrcv AT condor-werke DOT com>
To: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Thu, 16 Mar 2006 13:48:20 +0100
Paul Bijnens wrote:
On 2006-03-16 12:02, listrcv wrote:

planner: prometheus /home 20060315 0 [dump larger than tape, 101387063 KB, full dump delayed]


Backups should automatically spread across multiple tapes in case they don't fit onto one tape. That's why we are using a tape changer.


In 2.4.X a single dump may not be larger than your tape capacity.
In 2.5.0 (currently in beta) that limitation is removed.

Hm, I cannot upgrade the software on the server until Etch is out because I need a somewhat more stable and reliable state of things with AMD64. An upgrade will screw up the server, and it's not a good idea to try that now ... The system is still only a few days after the state of Sarge, so an upgrade to Etch might be possible.

From what I've been reading, I was afraid it won't work and decided to solve the problem once it occured.

Can I make entries in the disklist that do not represent mount points? I could, for example, make seperate entries for some users who are using a lot of disk space or even one for each user. But I would want to keep an entry for /home so that I won't forget to make an entry in the disklist for newly created users and have them in the backup nonetheless.


Yes:  http://www.amanda.org/docs/topten.html#id2553034

Thanks! But tar -T doesn't work, I tried that out with a couple test directories:


prometheus:/tmp/xxx# ls -la
total 60
drwxr-xr-x  14 root root 4096 2006-03-16 13:26 .
drwxrwxrwt   8 root root 4096 2006-03-16 13:24 ..
drwxr-xr-x   2 root root 4096 2006-03-16 11:41 aa
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 ab
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 ac
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 ba
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 bb
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 bc
drwxr-xr-x   2 root root 4096 2006-03-16 11:40 ca
drwxr-xr-x   2 root root 4096 2006-03-16 11:40 cb
drwxr-xr-x   2 root root 4096 2006-03-16 11:40 cd
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 da
drwxr-xr-x   2 root root 4096 2006-03-16 11:39 db
drwxr-xr-x   2 root root 4096 2006-03-16 11:41 dc
-rw-r--r--   1 root root    5 2006-03-16 11:53 include
prometheus:/tmp/xxx# cat include
./aa
prometheus:/tmp/xxx# tar -cf test.tar -T include .
tar: ./test.tar: file is the archive; not dumped
prometheus:/tmp/xxx# tar -tvf test.tar
drwxr-xr-x root/root         0 2006-03-16 13:27:10 ./
drwxr-xr-x root/root         0 2006-03-16 11:41:08 ./aa/
-rw-r--r-- root/root         0 2006-03-16 11:41:08 ./aa/0-aa
drwxr-xr-x root/root         0 2006-03-16 11:39:28 ./ab/
drwxr-xr-x root/root         0 2006-03-16 11:39:31 ./ac/
drwxr-xr-x root/root         0 2006-03-16 11:39:37 ./ba/
drwxr-xr-x root/root         0 2006-03-16 11:39:38 ./bb/
drwxr-xr-x root/root         0 2006-03-16 11:39:40 ./bc/
drwxr-xr-x root/root         0 2006-03-16 11:39:46 ./da/
drwxr-xr-x root/root         0 2006-03-16 11:39:49 ./db/
drwxr-xr-x root/root         0 2006-03-16 11:41:20 ./dc/
-rw-r--r-- root/root         0 2006-03-16 11:41:20 ./dc/0-dc
drwxr-xr-x root/root         0 2006-03-16 11:40:01 ./ca/
drwxr-xr-x root/root         0 2006-03-16 11:40:02 ./cb/
drwxr-xr-x root/root         0 2006-03-16 11:40:04 ./cd/
-rw-r--r-- root/root         5 2006-03-16 11:53:49 ./include
drwxr-xr-x root/root         0 2006-03-16 11:41:08 ./aa/
-rw-r--r-- root/root         0 2006-03-16 11:41:08 ./aa/0-aa
prometheus:/tmp/xxx#


Only the directory ./aa should have been included in the archive, but tar cowardly includes everything, and ./aa even twice. Only excluding (-X) works, but it doesn't work the other way round, either:


prometheus:/tmp/xxx# tar -cf test.tar --exclude "*" -T include .
prometheus:/tmp/xxx# tar -tvf test.tar


An empty archive is created by that, with no warning about contradictory options. (It is imho rather questionable having the exclude option override the explicit include option. That should be the other way round.) Do the exclude and include options in the disklist or in the dumptypes work otherwise?

To backup /home/[a-c]*, /home/[d-f]* etc., I would have to set up like 10 exclude files or so many disklist entries --- I just posted another mail about it to the list because it doesn't have to do with the problem of the dump sizes not corresponding to the allocated space.

Maybe I just have to try it out ... :/


GH

<Prev in Thread] Current Thread [Next in Thread>