Edit tapelist to change tape order
Title: Edit tapelist to change tape order I have a problem with tapelist file (shown below) 20051123 bkalfa-all07 reuse 20051123 bkalfa-all06 reuse 20051116 bkalfa-all04 reuse 20051110 bkalfa-all03 reuse 20051110 bkalfa-all02 reuse 20051109 bkalfa-all00 reuse 0 bkalfa-all05 reuse 0 bkalfa-all01 reuse As you can see, during the next run amanda expect to use the tapes labelled bkalfa-all01 - bkalfa-all05 (i have runtapes = 2 with chg-manual). If amanda run i suppose that tapelist will result something like this: 20051207 bkalfa-all05 reuse 20051207 bkalfa-all01 reuse 20051123 bkalfa-all07 reuse 20051123 bkalfa-all06 reuse 20051116 bkalfa-all04 reuse 20051110 bkalfa-all03 reuse 20051110 bkalfa-all02 reuse 20051109 bkalfa-all00 reuse This is not an ordered tapelist file (as i want, to make tape changing every night more simple). There's a way to force amanda to use tape in the order shown below? 20051123 bkalfa-all07 reuse 20051123 bkalfa-all06 reuse 0 bkalfa-all05 reuse 20051116 bkalfa-all04 reuse 20051110 bkalfa-all03 reuse 20051110 bkalfa-all02 reuse 0 bkalfa-all01 reuse 20051109 bkalfa-all00 reuse I have tapecycle = 8 but i've also tried with a lower value (4 or less) and nothing has changed, amadmin claim that amanda want tapes labelled bkalfa-all01 - bkalfa-all05. Thanks in advance. Giovanni -- Il contenuto della presente comunicazione riservato e destinato esclusivamente ai destinatari indicati. Nel caso in cui sia ricevuto da persona diversa dal destinatario sono proibite la diffusione, la distribuzione e la copia. Nel caso riceveste la presente per errore, Vi preghiamo di informarci e di distruggerlo e/o cancellarlo dal Vostro computer, senza utilizzare i dati contenuti. La presente comunicazione (comprensiva dei documenti allegati) non avr valore di proposta contrattuale e/o accettazione di proposte provenienti dal destinatario, n rinuncia o riconoscimento di diritti, debiti e/o crediti, n sar impegnativa, qualora non sia sottoscritto successivo accordo da chi pu validamente obbligarci. Non deriver alcuna responsabilit precontrattuale a ns. carico, se la presente non sia seguita da contratto sottoscritto dalle parti. -- The contents of the present communication is strictly confidential and reserved solely to the referred addressees. In the event was received by person different from the addressee, it is forbidden the diffusion, distribution and copy. In the event you have received it mistakenly we ask you to inform us and to destroy and/or to delete it by your computer, without using the data herein contained. The present message (eventual annexes inclusive) shall not be considered any contractual proposal and/or acceptance of offer coming from the addressee, nor waiver neither recognizance of rights, debts and/or credits, and it shall not be binding, when it is not executed a subsequent agreement by person who could lawfully represent us. No pre-contractual liability shall derive to us, when the present communication is not followed by any binding agreement between the parties.
Re: Tapetype definition for Quantum DLT-V4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, 29.11.2005 at 11:09 +, Dave Ewart wrote:
Hello all,
Does anyone have a tapetype definition for a Quantum DLT-V4? This is a
160GB native capacity drive and is connected to an Adaptec 29160
Ultra160 SCSI adapter.
I would like to encourage people to add their tapetype definitions to
http://wiki.zmanda.com/index.php/Tapetype_definitions - this will be a
very useful resource.
Well, I ran the 'tapetype' program and came up with the following
definition, which I've added to the Wiki too, for reference:
define tapetype Quantum-DLT-V4 {
comment Quantum-DLT-V4 on Adaptec 29160
length 157284 mbytes
filemark 0 kbytes
speed 9936 kps
}
Cheers,
Dave.
- --
Dave Ewart
[EMAIL PROTECTED]
Computing Manager, Cancer Epidemiology Unit
Cancer Research UK / Oxford University
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
Get key from http://www.ceu.ox.ac.uk/~davee/davee-ceu-ox-ac-uk.asc
N 51.7518, W 1.2016
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDjssObpQs/WlN43ARAsVkAJ44ETN0geo/SSc24MA7ymwZiGvC4QCgrDjG
Jatxq+1VdaklRJ+1/Gby4Vs=
=DPbD
-END PGP SIGNATURE-
Re: please check your config and use a config file for chg-scsi
Richard Pyne wrote: I am STILL trying to get amanda set up to run with an adic Scalar 458 changer with three DLT4000 drives. [...] I decided to try to label a tape. After that failed miserably, I decided to take a step back and just try to get chg-scsi to work. Is there a reason you cannot use chg-zd-mtx? If your changer works with mtx, that might be simpler to set up. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
Re: Edit tapelist to change tape order
On Thu, Dec 01, 2005 at 09:53:26AM +0100, Montagni, Giovanni wrote: I have a problem with tapelist file (shown below) 20051123 bkalfa-all07 reuse 20051123 bkalfa-all06 reuse 20051116 bkalfa-all04 reuse 20051110 bkalfa-all03 reuse 20051110 bkalfa-all02 reuse 20051109 bkalfa-all00 reuse 0 bkalfa-all05 reuse 0 bkalfa-all01 reuse Please note that it is YOU, you as a human, that has a problem with this. Amanda cares nothing about the number sequence being in order. However, most of your tapes are in numeric sequence and the two out of sequence are unused, new in amanda terminology. As you can see, during the next run amanda expect to use the tapes labelled bkalfa-all01 - bkalfa-all05 (i have runtapes = 2 with chg-manual). There's a way to force amanda to use tape in the order shown below? ... I have tapecycle = 8 but i've also tried with a lower value (4 or less) and nothing has changed, amadmin claim that amanda want tapes labelled bkalfa-all01 - bkalfa-all05. Leave your tapecycle at 4, or at least below 7. That will allow amanda to use tape 00 (it is the olded used tape within the cycle) and it will always accept a new tape. Amanda requires new tapes up to the tapecycle, but after it is reached, it will reuse the oldest used, or a new tape. So after it uses tape 00 tonight, present it with tape new tape 01. Then let it use tape 02 and tape 03 the next run of amdump. And finally, after tape 04 is used, present next tape 05. After that you can reset tapecycle to 8 or leave it at the lower setting. You can cycle more, but not less, than tapecycle tapes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Edit tapelist to change tape order
On Thu, Dec 01, 2005 at 09:53:26AM +0100, Montagni, Giovanni enlightened us: I have a problem with tapelist file (shown below) 20051123 bkalfa-all07 reuse 20051123 bkalfa-all06 reuse 20051116 bkalfa-all04 reuse 20051110 bkalfa-all03 reuse 20051110 bkalfa-all02 reuse 20051109 bkalfa-all00 reuse 0 bkalfa-all05 reuse 0 bkalfa-all01 reuse snip -- snip -- snip This is not an ordered tapelist file (as i want, to make tape changing every night more simple). What's more simple than putting in the tapes amcheck lists in the e-mail to you? Amanda has no concept of order. I have tapecycle = 8 but i've also tried with a lower value (4 or less) and nothing has changed, amadmin claim that amanda want tapes labelled bkalfa-all01 - bkalfa-all05. That said, it looks like you could do the following: * Change your tapecycle to something low. 4 should be fine. * On your next run, bkalfa-all00 should be old enough to be used again. Put bkalfa-all00 and bkalfa-all01 in the drive. * On the next run, use bkalfa-all02 and bkalfa-all03 * On the next run, use bkalfa-all04 and bkalfa-all05 * Return your tapecycle to 8, continue life as normal Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Next tape?
How do I query amanda for the next tape? I run my backups on my home server; at times I am away from home so I can't feed the tapes in daily. I would like to be emailed a reminder telling me which tape is next. Right now amanda tells me which tape it expects when it completes a successful backup; I want to query it so it tells me on demand Thanks, --Yan
R: Edit tapelist to change tape order
-Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Matt Hyclak Inviato: giovedì 1 dicembre 2005 14.42 A: amanda-users@amanda.org Oggetto: Re: Edit tapelist to change tape order On Thu, Dec 01, 2005 at 09:53:26AM +0100, Montagni, Giovanni enlightened us: I have a problem with tapelist file (shown below) 20051123 bkalfa-all07 reuse 20051123 bkalfa-all06 reuse 20051116 bkalfa-all04 reuse 20051110 bkalfa-all03 reuse 20051110 bkalfa-all02 reuse 20051109 bkalfa-all00 reuse 0 bkalfa-all05 reuse 0 bkalfa-all01 reuse snip -- snip -- snip This is not an ordered tapelist file (as i want, to make tape changing every night more simple). What's more simple than putting in the tapes amcheck lists in the e-mail to you? Amanda has no concept of order. We had a strange internal organization about changing tapes for backups so i need to take tapelist in a human order to be sure that the correct tape is inserted every night. I have tapecycle = 8 but i've also tried with a lower value (4 or less) and nothing has changed, amadmin claim that amanda want tapes labelled bkalfa-all01 - bkalfa-all05. That said, it looks like you could do the following: * Change your tapecycle to something low. 4 should be fine. * On your next run, bkalfa-all00 should be old enough to be used again. Put bkalfa-all00 and bkalfa-all01 in the drive. * On the next run, use bkalfa-all02 and bkalfa-all03 * On the next run, use bkalfa-all04 and bkalfa-all05 * Return your tapecycle to 8, continue life as normal Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 Thanks a lot for your help (and Jon LaBadie too!) I haven't understood what's the real meaning of tapecycle. But now i know :-) Giovanni -- Il contenuto della presente comunicazione è riservato e destinato esclusivamente ai destinatari indicati. Nel caso in cui sia ricevuto da persona diversa dal destinatario sono proibite la diffusione, la distribuzione e la copia. Nel caso riceveste la presente per errore, Vi preghiamo di informarci e di distruggerlo e/o cancellarlo dal Vostro computer, senza utilizzare i dati contenuti. La presente comunicazione (comprensiva dei documenti allegati) non avrà valore di proposta contrattuale e/o accettazione di proposte provenienti dal destinatario, nè rinuncia o riconoscimento di diritti, debiti e/o crediti, nè sarà impegnativa, qualora non sia sottoscritto successivo accordo da chi può validamente obbligarci. Non deriverà alcuna responsabilità precontrattuale a ns. carico, se la presente non sia seguita da contratto sottoscritto dalle parti. -- The contents of the present communication is strictly confidential and reserved solely to the referred addressees. In the event was received by person different from the addressee, it is forbidden the diffusion, distribution and copy. In the event you have received it mistakenly we ask you to inform us and to destroy and/or to delete it by your computer, without using the data herein contained. The present message (eventual annexes inclusive) shall not be considered any contractual proposal and/or acceptance of offer coming from the addressee, nor waiver neither recognizance of rights, debts and/or credits, and it shall not be binding, when it is not executed a subsequent agreement by person who could lawfully represent us. No pre-contractual liability shall derive to us, when the present communication is not followed by any binding agreement between the parties.
Re: Next tape?
On Thu, Dec 01, 2005 at 06:53:31AM -0800, Yan Seiner enlightened us: How do I query amanda for the next tape? I run my backups on my home server; at times I am away from home so I can't feed the tapes in daily. I would like to be emailed a reminder telling me which tape is next. Right now amanda tells me which tape it expects when it completes a successful backup; I want to query it so it tells me on demand amcheck will tell you, or alternatively amadmin CONFIGNAME tape Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Next tape?
Yan Seiner wrote: How do I query amanda for the next tape? I run my backups on my home server; at times I am away from home so I can't feed the tapes in daily. I would like to be emailed a reminder telling me which tape is next. Right now amanda tells me which tape it expects when it completes a successful backup; I want to query it so it tells me on demand On demand: amadmin config tape or for the next five runs: amadmin config tape -days 5 Also amcheck verifies if the tape inserted is ok, and sends mail with the label of the tape it expects. -- 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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
R: Next tape?
I suppose you have to run an Amadmin yourconf tape From the amadmin manual: tape Display the tape(s) Amanda expects to write to during the next run. Giovanni -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Yan Seiner Inviato: giovedì 1 dicembre 2005 15.54 A: amanda-users@amanda.org Oggetto: Next tape? How do I query amanda for the next tape? I run my backups on my home server; at times I am away from home so I can't feed the tapes in daily. I would like to be emailed a reminder telling me which tape is next. Right now amanda tells me which tape it expects when it completes a successful backup; I want to query it so it tells me on demand Thanks, --Yan -- Il contenuto della presente comunicazione è riservato e destinato esclusivamente ai destinatari indicati. Nel caso in cui sia ricevuto da persona diversa dal destinatario sono proibite la diffusione, la distribuzione e la copia. Nel caso riceveste la presente per errore, Vi preghiamo di informarci e di distruggerlo e/o cancellarlo dal Vostro computer, senza utilizzare i dati contenuti. La presente comunicazione (comprensiva dei documenti allegati) non avrà valore di proposta contrattuale e/o accettazione di proposte provenienti dal destinatario, nè rinuncia o riconoscimento di diritti, debiti e/o crediti, nè sarà impegnativa, qualora non sia sottoscritto successivo accordo da chi può validamente obbligarci. Non deriverà alcuna responsabilità precontrattuale a ns. carico, se la presente non sia seguita da contratto sottoscritto dalle parti. -- The contents of the present communication is strictly confidential and reserved solely to the referred addressees. In the event was received by person different from the addressee, it is forbidden the diffusion, distribution and copy. In the event you have received it mistakenly we ask you to inform us and to destroy and/or to delete it by your computer, without using the data herein contained. The present message (eventual annexes inclusive) shall not be considered any contractual proposal and/or acceptance of offer coming from the addressee, nor waiver neither recognizance of rights, debts and/or credits, and it shall not be binding, when it is not executed a subsequent agreement by person who could lawfully represent us. No pre-contractual liability shall derive to us, when the present communication is not followed by any binding agreement between the parties.
Re: please check your config and use a config file for chg-scsi
On 1 Dec 2005 at 13:25, Alexander Jolk wrote: Richard Pyne wrote: I am STILL trying to get amanda set up to run with an adic Scalar 458 changer with three DLT4000 drives. [...] I decided to try to label a tape. After that failed miserably, I decided to take a step back and just try to get chg-scsi to work. Is there a reason you cannot use chg-zd-mtx? If your changer works with mtx, that might be simpler to set up. Alex No reason at all other than there is nothing in the documentation that would indicate that it is a better choice. The docs seem to indicate that the chg-scsi is a more direct interface, especially for the Linux 2.6 kernel that has changer support. I am still baffled that my earlier request for configuration suggestions only got one reply and that was to say read the wiki which provided no more insight than the other docs. Is no one out there using an adic Scalar tape library? It seems odd that if no one is using it that chg-scsi recognizes it specifically. I'll give chg-zd-mtx a try. --Richard
Re: Next tape?
On Thu, 1 Dec 2005 at 6:53am, Yan Seiner wrote How do I query amanda for the next tape? I run my backups on my home server; at times I am away from home so I can't feed the tapes in daily. I would like to be emailed a reminder telling me which tape is next. Right now amanda tells me which tape it expects when it completes a successful backup; I want to query it so it tells me on demand 2 ways: amadmin $CONFIG tape amcheck -t $CONFIG -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
Hi Testing a restore on the above config i have found this error. Backups run fine but this is the error when trying to do a restore on it - Anyone seen it before as i have not come accross this - Restore is being attempted NOT on the same server that did the backup amrestore: 53: restoring x1._dev_sda2.20051130.1 Input block size is 32 Dump date: Wed Nov 30 03:06:53 2005 Dumped from: Tue Nov 29 03:11:26 2005 Level 1 dump of / on x1:/dev/sda2 Label: / Extract directories from tape Mangled directory: reclen not multiple of 4 reclen less than DIRSIZ (2 12) Mangled directory: reclen less than DIRSIZ (0 12) Mangled directory: reclen less than DIRSIZ (0 12) Mangled directory: reclen less than DIRSIZ (0 12) Mangled directory: reclen not multiple of 4 reclen less than DIRSIZ (2 12) Mangled directory: reclen less than DIRSIZ (0 12) Mangled directory: reclen less than DIRSIZ (0 12) Mangled directory: reclen less than DIRSIZ (0 12) Mangled directory: reclen not multiple of 4 thanks
Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
Tom, What OS and dump version was the data backed up from? What OS and dump version are you trying to restore to? In general, the dump type (xfsdump, vdump, etc.) and sometimes even the version must be the same for backup and restore. This is an unfortunate consequence of Amanda's use of native tools. Cheers, --Ian -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
What OS and dump version was the data backed up from? What OS and dump version are you trying to restore to? In general, the dump type (xfsdump, vdump, etc.) and sometimes even the version must be the same for backup and restore. This is an unfortunate consequence of Amanda's use of native tools. the clients that i'm testing at the moment are running CentOS4.2 and the server that did this backup is running CentOS 3.something 6 i think - I'm testing this restore on a server running RH7.3 and this is chucking the error. I'm currently running a test restore on the same server that did the backup to see if that works - I'll confirm dump versions shortly
Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
What OS and dump version was the data backed up from? What OS and dump version are you trying to restore to? In general, the dump type (xfsdump, vdump, etc.) and sometimes even the version must be the same for backup and restore. This is an unfortunate consequence of Amanda's use of native tools. server that ran the backup Linux 2.4.21-27.0.2.ELsmp dump 0.4b37 client that got backed up Linux 2.6.9-22.ELsmp dump 0.4b39 and i can confirm that even on the server that did the backup i get the same garbage when trying to restore - Is the dump version difference the issue do you think?
Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
On Thu, Dec 01, 2005 at 04:15:09PM +, Tom Brown wrote: What OS and dump version was the data backed up from? What OS and dump version are you trying to restore to? In general, the dump type (xfsdump, vdump, etc.) and sometimes even the version must be the same for backup and restore. This is an unfortunate consequence of Amanda's use of native tools. server that ran the backup Linux 2.4.21-27.0.2.ELsmp dump 0.4b37 client that got backed up Linux 2.6.9-22.ELsmp dump 0.4b39 and i can confirm that even on the server that did the backup i get the same garbage when trying to restore - Is the dump version difference the issue do you think? I wonder about the info in your original post, Input block size is 32. If that is related to the amanda blocksize, it is normally 32KB. Is the program just implying KB or might there be a blocksize mismatch between how it was dumps and how it is being recovered? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
server that ran the backup Linux 2.4.21-27.0.2.ELsmp dump 0.4b37 client that got backed up Linux 2.6.9-22.ELsmp dump 0.4b39 sorry to reply to myself here but on another test client Linux 2.4.20 dump 0.4b27 and the same server did a succesful restore so it seems that if the client version of dump is higher than the server the restore barfs however the opposite appears to give a good restore - Looks like i'm going to have to install myself a new server box with dump 0.4b39 so get around this - Unless anyone has any other suggestions? thanks
Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
and i can confirm that even on the server that did the backup i get the same garbage when trying to restore - Is the dump version difference the issue do you think? Well, if you're getting this issue on the original server, then version differences are probably not the problem. Amrecover should have told you which tape and filemark your backup was at. Yes? If so, try restoring the dump manually with amrestore, and feed it to the file command, like so: $ amrestore -p -f fileno -l tapelabel tapedevice hostname diskname | file - And see what type of archive you are looking at. -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: Files garbages after restore :-(
Jehan PROCACCIA wrote: Hello I've been saving partitions with amanda (dumps) for weeks now ... unfortunaltly while needing to restore a file I got garbage :-( For exemple, here's what I expected from the file I needed: [EMAIL PROTECTED] /var/www/html/server/settings/siteaccess/site_unite_server_en] $ cat site.ini.append.php ?php /* #?ini charset=iso-8859-1? [DatabaseSettings] DatabaseImplementation=ezpostgresql etc ... And here's what I got from an amrecover (same with amrestore !) [EMAIL PROTECTED] /data1/restore-server/21-11-2005/www/html/server/settings/siteaccess/site_unite_server_en] $ cat site.ini.append.php $var3, 'templateValue' ) ) $var3 = $var3-templateValue(); $var2 = ( ( $var3 ) == ( 'enabled' ) ); unset( $var3 ); while ( is_object( $var2 ) and method_exists( $var2, 'templateValue' ) ) $var2 = $var2-templateValue(); unset( $var3 ); etc You can see that it's completly different ! source codes have replaces the initial php configuration code . It's as if one file was replaced with an other one, perhaps inodes were mismatched or something ...? Is this problem already occured to someone on this list ? Is amanda in cause , dump part, restore part ? , or it comes from outsite amanda tools , from the system (here redhat 4 running amanda-2.4.4p3-1) ? This is also a typical effect of using dump on a busy filesystem. Or, even worse, using dump on a corrupted filesystem... That's one of the reasons I use gnutar instead of dump. It could also be a tapedrive that is out of warranty of course. Or Harry Potter training new magic. I'am really confused about that problem, and cannot be confident on my backups as long as I am not sure of what was the problem. Since then, I fsck.ext3 -f the /var partition which caused me the problems, it works fine now (last 3 days) , but I'am afraid of beeing once again confronted to that problem. Thanks of any help / sugestions . -- 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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
How long lasts a backup image?
Hi, How long does amanda keep in its catalog a backup image? I mean, what is the oldest backup I can restore for a specific client? Is this configurable (for example, keep only the backups not older than 2 months) or does this depend exclusively on the number of tapes amanda knows? Thanks
Files garbages after restore :-(
Hello I've been saving partitions with amanda (dumps) for weeks now ... unfortunaltly while needing to restore a file I got garbage :-( For exemple, here's what I expected from the file I needed: [EMAIL PROTECTED] /var/www/html/server/settings/siteaccess/site_unite_server_en] $ cat site.ini.append.php ?php /* #?ini charset=iso-8859-1? [DatabaseSettings] DatabaseImplementation=ezpostgresql etc ... And here's what I got from an amrecover (same with amrestore !) [EMAIL PROTECTED] /data1/restore-server/21-11-2005/www/html/server/settings/siteaccess/site_unite_server_en] $ cat site.ini.append.php $var3, 'templateValue' ) ) $var3 = $var3-templateValue(); $var2 = ( ( $var3 ) == ( 'enabled' ) ); unset( $var3 ); while ( is_object( $var2 ) and method_exists( $var2, 'templateValue' ) ) $var2 = $var2-templateValue(); unset( $var3 ); etc You can see that it's completly different ! source codes have replaces the initial php configuration code . It's as if one file was replaced with an other one, perhaps inodes were mismatched or something ...? Is this problem already occured to someone on this list ? Is amanda in cause , dump part, restore part ? , or it comes from outsite amanda tools , from the system (here redhat 4 running amanda-2.4.4p3-1) ? I'am really confused about that problem, and cannot be confident on my backups as long as I am not sure of what was the problem. Since then, I fsck.ext3 -f the /var partition which caused me the problems, it works fine now (last 3 days) , but I'am afraid of beeing once again confronted to that problem. Thanks of any help / sugestions .
Re: Files garbages after restore :-(
Hi Jehan What do you mean by Since then, I fsck.ext3 -f the /var partition which caused me the problems, it works fine now (last 3 days) , What works fine? The restore? Are you not seeing the file corruption anymore? Thanks tk Jehan PROCACCIA wrote: Hello I've been saving partitions with amanda (dumps) for weeks now ... unfortunaltly while needing to restore a file I got garbage :-( For exemple, here's what I expected from the file I needed: [EMAIL PROTECTED] /var/www/html/server/settings/siteaccess/site_unite_server_en] $ cat site.ini.append.php ?php /* #?ini charset=iso-8859-1? [DatabaseSettings] DatabaseImplementation=ezpostgresql etc ... And here's what I got from an amrecover (same with amrestore !) [EMAIL PROTECTED] /data1/restore-server/21-11-2005/www/html/server/settings/siteaccess/site_unite_server_en] $ cat site.ini.append.php $var3, 'templateValue' ) ) $var3 = $var3-templateValue(); $var2 = ( ( $var3 ) == ( 'enabled' ) ); unset( $var3 ); while ( is_object( $var2 ) and method_exists( $var2, 'templateValue' ) ) $var2 = $var2-templateValue(); unset( $var3 ); etc You can see that it's completly different ! source codes have replaces the initial php configuration code . It's as if one file was replaced with an other one, perhaps inodes were mismatched or something ...? Is this problem already occured to someone on this list ? Is amanda in cause , dump part, restore part ? , or it comes from outsite amanda tools , from the system (here redhat 4 running amanda-2.4.4p3-1) ? I'am really confused about that problem, and cannot be confident on my backups as long as I am not sure of what was the problem. Since then, I fsck.ext3 -f the /var partition which caused me the problems, it works fine now (last 3 days) , but I'am afraid of beeing once again confronted to that problem. Thanks of any help / sugestions . -- Ram TK Krishnamurthy http://www.zmanda.com
Re: Alternating dump cycles for offsite storage
On Wed, 30 Nov 2005 at 8:05pm, C Shore wrote I'm wondering if amanda can handle having two different configurations which are used on alternating two week periods. I know I could set up DailySet1 and DailySet2 and a crontab that ran DailySet1 for the first two weeks of the month and DailySet2 for the next two, but I'm not how well amanda will deal with the two week gap between dumps. Hrm. It seems like: dumpcycle 4 weeks runspercycle 12 tapecycle 14 e.g., may work, but I've never tried anything of the sort. Note that I set runspercycle 2 less than tapecycle for a little bit of leeway. The reason I want to do this is that I want to have offsite storage in which I deposit one tapecyle's worth of tapes, and pull out the other tapecylce's tapes. (The dumpcycle would end up being 13 days because the tapecycle must be greater than the dumpcycle). And I like more than just 1 tape worth of extra space, just in case. I'm interested in this as well -- if you find a scheme that works well, definitely let the list and/or Wiki know. tape on a given day. Actually the dumps seems to be taking about 22 hours which is another problem for this approach. I'm hoping the time is reduced when I upgrade and divide out the server's tasks. amplot can show you where all the time is being spent (in addition, of course, to just reading it in the report). Are your estimates really long? Is there just that much data to move? Are you hitting disk and/or network bottlenecks that you could iron out? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: How long lasts a backup image?
Edson Noboru Yamada wrote: Hi, How long does amanda keep in its catalog a backup image? I mean, what is the oldest backup I can restore for a specific client? Amanda keeps the online info and index of a tape until it is reused, or until you label a tape (with force flag) with the same label, or until you amrmtape the tape. You need the index to use amrecover, but without the index, you can still use amrestore, or even dd plus gnutar or restore to recover anything from the tape. -- 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 * ***
** resolved ** Re: Restore error - centos 3/amanda-2.4.5 server - centos4/amanda-2.4.5 client
and the same server did a succesful restore so it seems that if the client version of dump is higher than the server the restore barfs however the opposite appears to give a good restore - Looks like i'm going to have to install myself a new server box with dump 0.4b39 so get around this - Unless anyone has any other suggestions? thanks OK - I have managed to resolve this issue. I had to install a newer version of dump that was higher than the client version and then re-compile amanda so that it picked up this new version of dump. It appears that dump/restore is a bit picky regarding version numbers - the client version must be the same or lower than the server version otherwise restores may not work. thanks
amverify shows invalid sparse archive member errors
Hi there, I need a little help. I've installed Amanda server with clients through a firewall. Everything is OK except when the disklist includes the AIX client the amverify command on the server produces hundreds of these errors: /bin/gtar: ./987366/cred: invalid sparse archive member /bin/gtar: ./987366/sigact: invalid sparse archive member /bin/gtar: ./991470/sigact: invalid sparse archive member /bin/gtar: ./995570/cred: invalid sparse archive member /bin/gtar: ./995570/sigact: invalid sparse archive member /bin/gtar: ./999676/sigact: invalid sparse archive member The tar version from both machines: AIX Client: (/)- which tar /usr/bin/tar (/)- /usr/bin/tar --version tar (GNU tar) 1.15.1 (/)- RedHat Server: (/root)- which tar /bin/tar (/root)- /bin/tar --version tar (GNU tar) 1.15.1 (/root)- amverify does not write to the /tmp/amanda place like its supposed to either. Any ideas?
Re: amverify shows invalid sparse archive member errors
--On December 1, 2005 7:12:30 PM -0500 Ed Kenny [EMAIL PROTECTED] wrote: Hi there, I need a little help. I've installed Amanda server with clients through a firewall. Everything is OK except when the disklist includes the AIX client the amverify command on the server produces hundreds of these errors: Known tar 1.15 ish bugDebian tar 1.15.1-2 has a patch for it atleast, though I thought that 1.15.1 upstream had it patched, it showed up in or around 1.14 and persisted for quite a while. Debian Sarge's default tar has the issue. 1.13.25 is known to me to be good,. though i thought it was fixed in 1.15.1 as well, but maybe only in debians. Try finding an older or newer tar package. 1.13.25ish, or go after 1.15.1, 1.14 definitely has the bug. /bin/gtar: ./987366/cred: invalid sparse archive member /bin/gtar: ./987366/sigact: invalid sparse archive member /bin/gtar: ./991470/sigact: invalid sparse archive member /bin/gtar: ./995570/cred: invalid sparse archive member /bin/gtar: ./995570/sigact: invalid sparse archive member /bin/gtar: ./999676/sigact: invalid sparse archive member The tar version from both machines: AIX Client: (/)- which tar /usr/bin/tar (/)- /usr/bin/tar --version tar (GNU tar) 1.15.1 (/)- RedHat Server: (/root)- which tar /bin/tar (/root)- /bin/tar --version tar (GNU tar) 1.15.1 (/root)- amverify does not write to the /tmp/amanda place like it’s supposed to either. Any ideas? -- Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds. -- Samuel Butler
Re: amverify shows invalid sparse archive member errors
Ed Kenny wrote: /bin/gtar: ./987366/cred: invalid sparse archive member ... (/)- /usr/bin/tar --version tar (GNU tar) 1.15.1 ... (/root)- /bin/tar --version tar (GNU tar) 1.15.1 But you restored with /bin/gtar. Is that the same binary as /usr/bin/tar on the AIX? What does /bin/gtar --version say? -- 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 * ***
Re: Alternating dump cycles for offsite storage
On Thu, Dec 01, 2005 at 03:15:04PM -0500, Joshua Baker-LePain wrote: On Wed, 30 Nov 2005 at 8:05pm, C Shore wrote I'm wondering if amanda can handle having two different configurations which are used on alternating two week periods. I know I could set up DailySet1 and DailySet2 and a crontab that ran DailySet1 for the first two weeks of the month and DailySet2 for the next two, but I'm not how well amanda will deal with the two week gap between dumps. Hrm. It seems like: dumpcycle 4 weeks runspercycle 12 tapecycle 14 What does two identical configs buy you that you don't get from a single config where 1/2 the tapes are moved offsite bi-weekly? Or even better (IMNSHO) a dumpcycle of 1 week with 1/4 of the tapes moved offsite weekly. As to how well amanda will handle the 2 week gap, I'd guess badly. I base that on reports of people who have things like a 1 week dumpcycle, but dump only 3 (MWF) or 5 (M-F) times a week. After the weekend gap, the Monday dump is always unbalanced. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Which ports to open in which direction...
Thanks! There is a document called PORT.USAGE. Available in the source docs directory or at amanda.org. Actually, the precise URL is: http://www.amanda.org/docs/portusage.html Ok, well, I've tried to decipher the doc, but I'm not quite sure about a few things. I started writing a simplified doc on the wiki for people who need to set up a network like mine. http://wiki.zmanda.com/index.php/Configuration_with_iptables It would be really great to get a little advice on how the traffic is passed around. I read the doc, but it's still a bit unclear to me. The page above says which program uses what port, but there seem to be a few holes that require more research. If anybody is interested in editing this article on the wiki, please do so! I think (hope) that this doc could be useful for others, too. Thank you! Dave
Re: Alternating dump cycles for offsite storage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon LaBadie wrote: What does two identical configs buy you that you don't get from a single config where 1/2 the tapes are moved offsite bi-weekly? Or even better (IMNSHO) a dumpcycle of 1 week with 1/4 of the tapes moved offsite weekly. Erm. Good point. If I use a dumpcycle of two weeks the planner will ensure there is at least one full dump of all DLE's within each two week period, right? (I have a small tape drive relative to what I'm dumping so I'm out of luck as far as a one week dumpcycle goes). Amanda is cool, must remember it can do things other backup systems can't... :-) Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDj8wCeVDHer2Nu1QRAobnAJ9fLZV79Zr+aPW8L4SNPWN7TiDAIgCgoGu9 Rg+OeDqcCooIZ5XBYOeKAwk= =WtPG -END PGP SIGNATURE-
