Re: Dump larger than available tape space
On 2006-12-13 11:08, imacat wrote: On Wed, 13 Dec 2006 09:09:14 +0100 (CET) Marc Muehlfeld [EMAIL PROTECTED] wrote: Marc Muehlfeld schrieb: Amanda is filling tapes almost to 100% with this option, but if I want to backup a mountpoint that is compressed larger then the space of an empty tape, I get a Dump larger than available tape space-Error. As far as I know, it is not possible to dump a disk that is larger than the tape after compress. The split-tape only span multiple-tapes on the boundary of each individual resulted dump file. It won't split the resulted dump file itself. A compressed dump result has to be entirely on one tape. Amanda can do that since 2.5.0, more than a year old now. See: http://wiki.zmanda.org/index.php/Splitting_dumps_across_tapes This is due to the fact that Amanda is a manager/wrapper of complex tar operations. It does not do binary things like splitting files at all. Well, actually, it does :-) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Excluding with Samba
Hello!
I just tried to add our Windows server to our Amanda backup.
Basically everything is working, the nightly dump fails
because of dumps way to big.
I want to backup this disklist entry:
hugo10.ka.punkt.de //hugo11/c$ samba-tar
The samba-tar definition looks like this:
define dumptype samba-tar {
root-tar
comment user partitions dumped with tar
priority medium
exclude ./Virtual Machines
}
Obviously this does *not* correctly exclude the Virtual Machines
directory on drive C:, because otherwise the dumps would definitely
fit on the tape.
How to specify exclusions if one is using Samba? The above syntax
I tried is correct for Unix hosts with gnutar, but I could not
find an example for Windows.
Thanks,
Patrick M. Hausen
Leiter Netzwerke und Sicherheit
--
punkt.de GmbH Internet - Dienstleistungen - Beratung
Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100
76137 Karlsruhe http://punkt.de
Re: Problem after years of backing up successful: data timeout
On 2006-12-13 01:48, Jobst Schmalenbach wrote: All over sudden I get a data timeout, e.g.: adminserver /var lev 0 FAILED [data timeout] adminserver /home lev 3 FAILED [data timeout] [...] Looking at the sendbackup..debug I can see the following message: ... index tee cannot write [Broken pipe] ... Is the problem described here: http://wiki.zmanda.com/index.php/Amdump:_mesg_read:_Connection_reset_by_peer -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Dump larger than available tape space
Note that amanda-hackers is for developers. This is clearly a user question. So I redirected the answer to the amanda-users list. On 2006-12-05 14:29, Marc Muehlfeld wrote: Hi, I use amanda 2.5.1p2 and setup tape_splitsize 3072M fallback_splitsize 32M Amanda is filling tapes almost to 100% with this option, but if I want to backup a mountpoint that is compressed larger then the space of an empty tape, I get a Dump larger than available tape space-Error. What I am doing wrong? That should work, if the parameters you gave are on the right tapetype definition, and you use a changer and you set runtapes 1. And ofcourse the total size of the dump should not be larger than runtapes times tapecapacity (the one you specified, not the one physical capacity of the tape). What is the size? What is runtapes? What is the result of: amadmin yourconfig disklist thehost /the/large/disk Des it show the tape_splitsize parameter above? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Problem after years of backing up successful: data timeout
Jobst, if your data grows you may actually run into an estimate timeout after a long period of success, I did just the other day, had a 20 minute timeout and checking the /tmp/amanda logs on the client I found that the estimate didn't finish for nearly 23 minutes. I'm not saying you had the same problem I did, but the log files on the client are a great place to confirm or disprove. On Wed, Dec 13, 2006 at 11:48:19AM +1100, Jobst Schmalenbach wrote: Hi. All over sudden I get a data timeout, e.g.: ... ... adminserver /var lev 0 FAILED [data timeout] adminserver /home lev 3 FAILED [data timeout] ... ... I havent changed a thing on the machines involved for a while (I work on the basic principle if aint broken, dont fix) Now I have searched the net and found a few pointers, but all those I found do not help: * I do not use compression (I use hardware compression) * its NOT backing up another host, its the LOCAL machine backing up itself, and I have never had any problems with this * the dtimeout already is 1800 * since the last reboot of the machine I have done lots of successfull backups. * I havent installed anything new for a while on that machine. * I havent hanged anything (xinet, hosts.allow, .amandahost, directories, amanda, whatever). Looking at the sendbackup..debug I can see the following message: ... index tee cannot write [Broken pipe] ... The index file for the latest ones are missing, that is correct. I checked all the permissions on the amanda based directories, and they look fine to me. What can be the cause for the errors popping up? jobst -- Learn the rules so you know how to break them properly. -F1 | |0| | Jobst Schmalenbach, [EMAIL PROTECTED], Technical Director | | |0| Barrett Consulting Group P/L The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
hacker's digest 1104
An interesting but confusing (for me) read, but the wiki page was very helpful. http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes We are will likely be implementing this shortly, I have a number of jukeboxes with large DLE or many small DLE where I'm only partially filling multiple tapes, I have a related question. Is there a value in trying to match the tape_slitsize to the chunksize ? thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: hacker's digest 1104
Brian Cuttler schreef: An interesting but confusing (for me) read, but the wiki page was very helpful. http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes We are will likely be implementing this shortly, I have a number of jukeboxes with large DLE or many small DLE where I'm only partially filling multiple tapes, I have a related question. Is there a value in trying to match the tape_slitsize to the chunksize ? They are completely unrelated, and can be used orthogonal. chunksize is a holdingdisk parameter mainly to overcome filesize limitations on certain filesystems. One additional benefit is that when using many holdingdisk areas, one dump one holdingdisk can be spread over all these disks, even if each of them would be too small to hold one complete image. tapesplit_size is the size of chunk on tape. When writing such a chunk to tape, and the tape bumps into EOT, the next tape is loaded, and the complete chunk is rewritten again. Compare this to the alternative to restart the complete dumpimage on that tape: it avoids wasting too much tape (and time writing it). Note also that tapesplit_size is a dumptype parameter: you may specify which DLE's should be split, and which not (e.g. not splitting the DLE's that contain the amanda software makes restores easier, when that disk itself was lost). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
