Re: Config file upgrade from 2.4.2p2 to 2.5.1p3
> # ls -la /etc/amandapass > -rw--- 1 amanda disk 950 Apr 18 10:19 /etc/amandapass > > I am wondering if the new amanda server 2.5.1p3 if offering a way to > > hide the contents of amandapass file. > Why won't try hiding it, because of settings the rights so that > nobody except amanda and root can read it? Because this file contains clear text high priviledge password for the Windows machines. Any leakage of this file would provide access to any Windows machine in the network, so it is better to have the password not clear. Bests, Olivier
Re: Config file upgrade from 2.4.2p2 to 2.5.1p3
> Then you better think about your security policy, instead of doing > obscoure things with long passwords. It someone can read the content > of the file, then it doesn't matter if you have a 8 or 100 character > password. Sorry, I was not clear enough, that is not 100 character long password, but some kind of scrambling of "normal length" password, that is why I used the word obscurity. Ideally, I'd like a crypted file for amandapass. Olivier
Re: Config file upgrade from 2.4.2p2 to 2.5.1p3
Olivier Nicole schrieb: Because this file contains clear text high priviledge password for the Windows machines. But it also contains cleartext passwords if you use a 100 character password. There's nothing more secure by doing that. Any leakage of this file would provide access to any Windows machine in the network, so it is better to have the password not clear. Then you better think about your security policy, instead of doing obscoure things with long passwords. It someone can read the content of the file, then it doesn't matter if you have a 8 or 100 character password. What about having a special backup user in your domain, that is inserted in the workstations "Backup operators" group when it's a workstation you wanna backup (not all). Also set up a policy to disallow local logon for that group/user. Also make sure that no one can access your backup server except the administrators. Also sometimes change the password of that backup domain user (and in that file). I think, that are much better ways to secure your system instead of a long plain text password that also everybody can read. Regards Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: Config file upgrade from 2.4.2p2 to 2.5.1p3
Olivier Nicole schrieb: Sorry, I was not clear enough, that is not 100 character long password, but some kind of scrambling of "normal length" password, that is why I used the word obscurity. Ideally, I'd like a crypted file for amandapass. But also, I think there's nothing more secure, because amanda must know the cleartext password to connect to samba/windows. And even if it's encrypted or scrambled, there have to be a way to count back for that reason. And then every other tool can do this too. -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: suggestion for a disk-to-disk backup server
Dustin J. Mitchell wrote: > Folks -- I looked into this '-o' question, and have some answers for > you. > > On Mon, Jul 02, 2007 at 03:44:55PM -0400, Chris Hoogendyk wrote: > >> Jon LaBadie wrote: >> >>> On Mon, Jul 02, 2007 at 01:48:59PM -0400, Chris Hoogendyk wrote: >>> I checked the documentation & man pages and the documentation of the -o option is pretty sparse. All references say "see the configuration override section in amanda(8)". That section is only a few lines long and makes no reference to the syntax with a comma separating multiple parameter=value pairs. So, possibilities ... 1. The syntax is wrong? And I need to use "amdump daily -o reserve=100 -o tapedev=/dev/rmt/0n"? (In either case, this should be documented, since one would typically want to override more than one parameter if any at all.) > > The documentation could use some help there, for sure. FWIW, it doesn't > seem that comma-separated options are supported, from my look at the > source. > > The basic problem is that, since you're using a changer, tapedev is > actually supplied by the *changer*, which looks directly in amanda.conf. > There's no provision to hand configuration overrides (-o) to changers. > Furthermore, many changers (e.g., chg-multi) supply their own tapedev. > > The best solution, in this case, is to completely disable the changer, > too: > > amdump -o tapedev=/no/such/dev -o tpchanger= > > I hope that helps. I'll work on the documentation. > Thanks, Dustin. I set that up in crontab yesterday and it ran this morning. Worked. 45 0 * * 2-6 /usr/local/sbin/amdump daily -o reserve=100 -o tapedev=/dev/rmt/0n -o tpchanger="" Now, I'll change that entry back so it doesn't do it on weekdays. Anyway, it gave me a tape error at the top of the report and then fell back to incrementals on the holding disk -- mostly level 1, but some level 2. The one thing that is annoying is that on /var/mail an incremental is essentially the same as a full. Those mail files (one per account) are just like a database file -- add or remove one message and you have to back up the whole file. It would be interesting to write a wrapper to do incremental mail dumps sort of like the sql database programs that do incremental dumps. I wonder if there would be any demand for such a thing. It could get a little messy, and would probably require the Application API. In our case, we have about 1200 accounts/files. It would require reading headers and doing proper locking so as not to collide with the mail programs. - Comment & Question on the need for the changer script to tell amdump what is in amanda.conf (thus overriding the override): This behavior seems rather contrary. I can see that it is reasonable to override tpchanger as well as tapedev to provide a sort of clean slate. I can also see the possibility of some thrashing if amanda tries to read a tape, fails, and asks the changer to bring up the next tape. But reversing an override is just weird behavior. I'm guessing that for those changers where it's all tied up in one scsi address, and/or where there are multiple drives in a library, it might be desirable to have changer handle it. Then my case becomes the special case -- the changer is set up in sgen.conf and has a scsi device address, and the tape drive is set up in st.conf and is /dev/rmt/1 -- so the changer does not know how the drive got set up. This special case might require the changer to look somewhere else, e.g. amanda.conf, to find out. But, then, couldn't it also tell somehow if there had been an override? Or does that get too messy? Ok, maybe we just need to document that when someone overrides tapedev they should also override tpchanger if they have one. --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst <[EMAIL PROTECTED]> --- Erdös 4
Re: suggestion for a disk-to-disk backup server
On Thu, Jul 05, 2007 at 10:35:21AM -0400, Chris Hoogendyk wrote: > The one thing that is annoying is that on /var/mail an incremental is > essentially the same as a full. Those mail files (one per account) are > just like a database file -- add or remove one message and you have to > back up the whole file. It would be interesting to write a wrapper to do > incremental mail dumps sort of like the sql database programs that do > incremental dumps. I wonder if there would be any demand for such a > thing. It could get a little messy, and would probably require the > Application API. In our case, we have about 1200 accounts/files. It > would require reading headers and doing proper locking so as not to > collide with the mail programs. Yes, I think there would be demand for that (there are a lot of application-specific things that could use better backups). And yes, it will be a lot easier after the Application API is in place :) > I'm guessing that for those changers where it's all tied up in one scsi > address, and/or where there are multiple drives in a library, it might > be desirable to have changer handle it. Then my case becomes the special > case -- the changer is set up in sgen.conf and has a scsi device > address, and the tape drive is set up in st.conf and is /dev/rmt/1 -- so > the changer does not know how the drive got set up. This special case > might require the changer to look somewhere else, e.g. amanda.conf, to > find out. But, then, couldn't it also tell somehow if there had been an > override? Or does that get too messy? That's basically the answer -- the current changer interface has no provision for passing along overrides, and adding one would potentially break a lot of custom changer scripts. You've hit the nail on the head as to why changers provide devices to Amanda, rather than leaving her to use tapedev. > Ok, maybe we just need to document that when someone overrides tapedev > they should also override tpchanger if they have one. See the attached patch. Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/ Index: man/xml-source/amanda.8.xml === --- man/xml-source/amanda.8.xml (revision 423) +++ man/xml-source/amanda.8.xml (working copy) @@ -1221,15 +1221,36 @@ CONFIGURATION OVERRIDE -Most command allow to overwrite any configuration parameter on -the command line with the -o option. --o NAME=value -eg. -o runtapes=2 -eg. -o DUMPTYPE:no-compress:compress="server fast" -eg. -o TAPETYPE:HP-DAT:length=2000m -eg. -o INTERFACE:local:use="2000 kbps" +Most commands allow the override of specific +configuration options on the command line, using the -o option. This option has the form -oname=value. +An optional space is allowed after the -o. +Each configuration option should be specified in a separate +command-line option. +For global options, name is simply the name of the option, e.g., + +amdump -oruntapes=2 + +For options in a named section of the configuration, name has the +form SECTION:section_name:name, where SECTION is one of TAPETYPE, DUMPTYPE, HOLDINGDISK, or INTERFACE, and section_name is the name of the tapetype, dumptype, holdingdisk, or interface. Examples: + +amdump -o TAPETYPE:HP-DAT:length=2000m +amdump -o DUMPTYPE:no-compress:compress="server fast" +amdump -o HOLDINGDISK:hd1:use="-100 mb" +amdump -o INTERFACE:local:use="2000 kbps" + + +Note that configuration overrides are not effective for tape +changers, which supply a tapedev based on their own configuration. In order to +override tapedev, you must also disable any changer: + +amdump -otapedev=/dev/nst1 -otpchanger='' + + + AUTHOR
Re: more restore problems with tape spanning...
* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 09:08]: > Try the attached patch for amrestore and amfetchdump. patch applied, hmm, still getting the 'no space left on device': /opt/amanda/amanda2/sbin/amrestore /hw/tape/tps22d2nrnsv nosuchhost amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 amrestore: 2: skipping yorick._.20070630.1 amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 amrestore: 12: skipping yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 amrestore: could not fsf /hw/tape/tps22d2nrnsv: No space left on device amrestore.*.debug: amrestore: debug 1 pid 53730507 ruid 0 euid 0: start at Thu Jul 5 10:48:53 2007 amrestore: time 723.545: could not fsf /hw/tape/tps22d2nrnsv: No space left on device amrestore: time 723.545: pid 53730507 finish time Thu Jul 5 11:00:56 2007 jf > > Jean-Louis > > Jean-Francois Malouin wrote: > >* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070704 08:04]: > > > >>Jean-Francois Malouin wrote: > >> > >>>Following on my previous post: here's what I get > >>> > >>>/opt/amanda/amanda2/sbin/amfetchdump -p -l stk_80-conf2 yorick > >>>/data/ipl/ipl10 > >>>20070630 -o stk_80-conf2 | /usr/freeware/bin/tar -xvGpf - > >>>"(null)", line 0: Must specify a value for stk_80-conf2. > >>> > >>> > >>You can remove the '-o stk_80-conf2' argument. > >> > >>>amfetchdump: time 2425.149: could not fsf /hw/tape/tps22d2nrnsv: No > >>>space left on device > >>> > >>> > >>I don't understand the 'No space left on device' error. > >> > >>Can you put the stk_40-conf2-17 tape in the drive and run: > >> mt -f /hw/tape/tps22d2nrnsv rewind > >> amrestore /hw/tape/tps22d2nrnsv nohost > >> > > > >here's what I got: > > > >amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 > >amrestore: 2: skipping yorick._.20070630.1 > >amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 > >amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 > >amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 > >amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 > >amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 > >amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 > >amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 > >amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 > >amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 > >amrestore: 12: skipping > >yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 > >amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 > >amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 > >amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 > >amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 > >amrestore: could not fsf /hw/tape/tps23d3nrnsv: No space left on device > > > >jf > > > -- <° ><
Re: more restore problems with tape spanning...
Try amfetchdump. Jean-Louis Jean-Francois Malouin wrote: * Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 09:08]: Try the attached patch for amrestore and amfetchdump. patch applied, hmm, still getting the 'no space left on device': /opt/amanda/amanda2/sbin/amrestore /hw/tape/tps22d2nrnsv nosuchhost amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 amrestore: 2: skipping yorick._.20070630.1 amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 amrestore: 12: skipping yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 amrestore: could not fsf /hw/tape/tps22d2nrnsv: No space left on device amrestore.*.debug: amrestore: debug 1 pid 53730507 ruid 0 euid 0: start at Thu Jul 5 10:48:53 2007 amrestore: time 723.545: could not fsf /hw/tape/tps22d2nrnsv: No space left on device amrestore: time 723.545: pid 53730507 finish time Thu Jul 5 11:00:56 2007 jf Jean-Louis Jean-Francois Malouin wrote: * Jean-Louis Martineau <[EMAIL PROTECTED]> [20070704 08:04]: Jean-Francois Malouin wrote: Following on my previous post: here's what I get /opt/amanda/amanda2/sbin/amfetchdump -p -l stk_80-conf2 yorick /data/ipl/ipl10 20070630 -o stk_80-conf2 | /usr/freeware/bin/tar -xvGpf - "(null)", line 0: Must specify a value for stk_80-conf2. You can remove the '-o stk_80-conf2' argument. amfetchdump: time 2425.149: could not fsf /hw/tape/tps22d2nrnsv: No space left on device I don't understand the 'No space left on device' error. Can you put the stk_40-conf2-17 tape in the drive and run: mt -f /hw/tape/tps22d2nrnsv rewind amrestore /hw/tape/tps22d2nrnsv nohost here's what I got: amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 amrestore: 2: skipping yorick._.20070630.1 amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 amrestore: 12: skipping yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 amrestore: could not fsf /hw/tape/tps23d3nrnsv: No space left on device jf
Re: more restore problems with tape spanning...
* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 14:02]: > Try amfetchdump. I've put the 7 tapes needed in the library and loaded the first one needed (stk_40-conf2-17) with amtape: # /opt/amanda/amanda2/sbin/amfetchdump -p -a stk_80-conf2 \ yorick /data /ipl/ipl10 20070630 | /usr/freeware/bin/tar -xvpf - 7 tape(s) needed for restoration cc dd (null) The following tapes are needed: stk_40-conf2-17 stk_40-conf2-18 stk_40-conf2-19 stk_40-conf2-20 stk_40-conf2-14 stk_40-conf2-15 stk_40-conf2-01 ee (null) ff (null) gg (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape hh (null) Looking for tape stk_40-conf2-17... ii (null) no tapedev specified amfetchdump: error reading file header: Bad file number Not an amanda tape jj (null) Insert tape labeled stk_40-conf2-17 in device (null) and press enter, ^D to finish reading tapes Not the first time I'm there. I reported this a while ago. Something funky is happening for sure. jf > > Jean-Louis > > Jean-Francois Malouin wrote: > >* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 09:08]: > > > >>Try the attached patch for amrestore and amfetchdump. > >> > > > >patch applied, hmm, still getting the 'no space left on device': > > > >/opt/amanda/amanda2/sbin/amrestore /hw/tape/tps22d2nrnsv nosuchhost > >amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 > >amrestore: 2: skipping yorick._.20070630.1 > >amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 > >amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 > >amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 > >amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 > >amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 > >amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 > >amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 > >amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 > >amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 > >amrestore: 12: skipping > >yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 > >amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 > >amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 > >amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 > >amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 > >amrestore: could not fsf /hw/tape/tps22d2nrnsv: No space left on device > > > >amrestore.*.debug: > > > >amrestore: debug 1 pid 53730507 ruid 0 euid 0: start at Thu Jul 5 > >10:48:53 2007 > >amrestore: time 723.545: could not fsf /hw/tape/tps22d2nrnsv: No space > >left on device > >amrestore: time 723.545: pid 53730507 finish time Thu Jul 5 11:00:56 2007 > > > >jf > > > > > >>Jean-Louis > >> > >>Jean-Francois Malouin wrote: > >> > >>>* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070704 08:04]: > >>> > >>> > >>>>Jean-Francois Malouin wrote: > >>>> > >>>> > >>>>>Following on my previous post: here's what I get > >>>>> > >>>>>/opt/amanda/amanda2/sbin/amfetchdump -p -l stk_80-conf2 yorick > >>>>>/data/ipl/ipl10 > >>>>>20070630 -o stk_80-conf2 | /usr/freeware/bin/tar -xvGpf - > >>>>>"(null)", line 0: Must specify a value for stk_80-conf2. > >>>>> > >>>>> > >>>>> > >>>>You can remove the '-o stk_80-conf2' argument. > >>>> >
Re: more restore problems with tape spanning...
Hold on to answer this one Jean-Louis. I think I've found the problem and I'm doing a amfetchdump run and it went through the first tape and resumed the restore with the second tape. I'll post later when it completes. jf * Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 14:02]: > Try amfetchdump. > > Jean-Louis > > Jean-Francois Malouin wrote: > >* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 09:08]: > > > >>Try the attached patch for amrestore and amfetchdump. > >> > > > >patch applied, hmm, still getting the 'no space left on device': > > > >/opt/amanda/amanda2/sbin/amrestore /hw/tape/tps22d2nrnsv nosuchhost > >amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 > >amrestore: 2: skipping yorick._.20070630.1 > >amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 > >amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 > >amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 > >amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 > >amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 > >amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 > >amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 > >amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 > >amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 > >amrestore: 12: skipping > >yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 > >amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 > >amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 > >amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 > >amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 > >amrestore: could not fsf /hw/tape/tps22d2nrnsv: No space left on device > > > >amrestore.*.debug: > > > >amrestore: debug 1 pid 53730507 ruid 0 euid 0: start at Thu Jul 5 > >10:48:53 2007 > >amrestore: time 723.545: could not fsf /hw/tape/tps22d2nrnsv: No space > >left on device > >amrestore: time 723.545: pid 53730507 finish time Thu Jul 5 11:00:56 2007 > > > >jf > > > > > >>Jean-Louis > >> > >>Jean-Francois Malouin wrote: > >> > >>>* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070704 08:04]: > >>> > >>> > >>>>Jean-Francois Malouin wrote: > >>>> > >>>> > >>>>>Following on my previous post: here's what I get > >>>>> > >>>>>/opt/amanda/amanda2/sbin/amfetchdump -p -l stk_80-conf2 yorick > >>>>>/data/ipl/ipl10 > >>>>>20070630 -o stk_80-conf2 | /usr/freeware/bin/tar -xvGpf - > >>>>>"(null)", line 0: Must specify a value for stk_80-conf2. > >>>>> > >>>>> > >>>>> > >>>>You can remove the '-o stk_80-conf2' argument. > >>>> > >>>> > >>>>>amfetchdump: time 2425.149: could not fsf /hw/tape/tps22d2nrnsv: No > >>>>>space left on device > >>>>> > >>>>> > >>>>> > >>>>I don't understand the 'No space left on device' error. > >>>> > >>>>Can you put the stk_40-conf2-17 tape in the drive and run: > >>>>mt -f /hw/tape/tps22d2nrnsv rewind > >>>>amrestore /hw/tape/tps22d2nrnsv nohost > >>>> > >>>> > >>>here's what I got: > >>> > >>>amrestore: 1: skipping yorick._data_mril_mril5_bojana_images.20070630.0 > >>>amrestore: 2: skipping yorick._.20070630.1 > >>>amrestore: 3: skipping yorick._data_noel_noel1.20070630.0 > >>>amrestore: 4: skipping yorick.noel1_neda_03.20070630.1 > >>>amrestore: 5: skipping yorick._data_mril_mril5_tardif.20070630.2 > >>>amrestore: 6: skipping yorick._data_mril_mril5_leili.20070630.0 > >>>amrestore: 7: skipping yorick._data_mril_mril5_vivian.20070630.0 > >>>amrestore: 8: skipping yorick._data_mril_mril5_mferre.20070630.0 > >>>amrestore: 9: skipping yorick._data_mril_mril5_ives.20070630.0 > >>>amrestore: 10: skipping yorick._data_mril_mril5_jcampbel.20070630.1 > >>>amrestore: 11: skipping yorick._data_mril_mril5_vanela.20070630.0 > >>>amrestore: 12: skipping > >>>yorick._data_mril_mril5_mgriffin_Experimental_data.20070630.1 > >>>amrestore: 13: skipping yorick._data_mril_mril5_bojana.20070630.1 > >>>amrestore: 14: skipping yorick._data_ipl_ipl10.20070630.0.001 > >>>amrestore: 15: skipping yorick._data_ipl_ipl10.20070630.0.002 > >>>amrestore: 16: skipping yorick._data_ipl_ipl10.20070630.0.003 > >>>amrestore: could not fsf /hw/tape/tps23d3nrnsv: No space left on device > >>> > >>>jf > >>> > >>> > > > > > > > > -- <° ><
Re: more restore problems with tape spanning...
* Jean-Francois Malouin <[EMAIL PROTECTED]> [20070705 16:05]: > Hold on to answer this one Jean-Louis. > I think I've found the problem and I'm > doing a amfetchdump run and it went > through the first tape and resumed the > restore with the second tape. > I'll post later when it completes. OK here it goes: I had somehow 2 config recompiled most probably without doing a 'make distclean' between the configure. The hint was that the debug files for this one were not located in the right place and once I found them I realized that amfetchdump could not find the chg-zd-mtx script. The amfetchdump debug file (in /tmp/amanda-spantest/server/stk_80-conf2 it should have been /tmp/amanda-conf2/server/stk_80-conf2): ... search_tapes(prompt_out=2, prompt_in=0, use_changer=1, tapelist=100873f8, match_list=10025758, flags=10016550, features=0) could not exec "/opt/amanda/spantest/libexec/chg-zd-mtx": No such file or directory changer: got exit: 1 str: could not read result from "/opt/amanda/spantest/libexec/chg-zd-mtx" num_entries(tapelist=100873f8)=7 could not exec "/opt/amanda/spantest/libexec/chg-zd-mtx": No such file o r directory changer: got exit: 1 str: could not read result from "/opt/amanda/spantest/libexec/chg-zd-mtx" So I recompiled making sure to start with a clean slate and now I get: # /opt/amanda/amanda2/sbin/amfetchdump -p -a stk_80-conf2 \ yorick /data/ipl/ipl10 20070630 | /usr/freeware/bin/tar -xpf - 7 tape(s) needed for restoration cc dd (null) The following tapes are needed: stk_40-conf2-17 stk_40-conf2-18 stk_40-conf2-19 stk_40-conf2-20 stk_40-conf2-14 stk_40-conf2-15 stk_40-conf2-01 ee (null) ff /hw/tape/tps22d2nrnsv gg /hw/tape/tps22d2nrnsv Label mismatch, got stk_40-conf2-18 and expected stk_40-conf2-17 hh /hw/tape/tps22d2nrnsv Looking for tape stk_40-conf2-17... amfetchdump: slot 26: date 20070630 label stk_40-conf2-17 (exact label match) ii /hw/tape/tps22d2nrnsv Scanning stk_40-conf2-17 (slot 26) amfetchdump: 14: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 1/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 15: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 2/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: Search of stk_40-conf2-17 complete gg /hw/tape/tps22d2nrnsv Label mismatch, got stk_40-conf2-17 and expected stk_40-conf2-18 hh /hw/tape/tps22d2nrnsv Looking for tape stk_40-conf2-18... amfetchdump: slot 28: date 20070630 label stk_40-conf2-18 (exact label match) ii /hw/tape/tps22d2nrnsv Scanning stk_40-conf2-18 (slot 28) amfetchdump: 1: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 3/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 2: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 4/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 3: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 5/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 4: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 6/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 5: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 7/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 6: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 8/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 7: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 9/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 8: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 10/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 9: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 11/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 10: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 12/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: 11: restoring split dumpfile: date 20070630 host yorick disk /data/ipl/ipl10 part 13/UNKNOWN lev 0 comp N program /usr/freeware/bin/tar amfetchdump: error reading file header: No space left on device amfetchdump: Search of stk_40-conf2-18 complete /usr/freeware/bin/tar: Unexpected EOF in archive /usr/freeware/bin/tar: Unexpected EOF in archive /usr/freeware/bin/tar: Error is not recoverable: exiting now amfetchdump.*.debug attached. jf > jf > > * Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 14:02]: > > Try amfetchdump. > > > > Jean-Louis > > > > Jean-Francois Malouin wrote: > > >* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070705 09:08]: >
Re: suggestion for a disk-to-disk backup server
> > The one thing that is annoying is that on /var/mail an incremental is > > essentially the same as a full. Those mail files (one per account) are > > just like a database file -- add or remove one message and you have to > > back up the whole file. It would be interesting to write a wrapper to do > > incremental mail dumps sort of like the sql database programs that do > > incremental dumps. I wonder if there would be any demand for such a > > thing. It could get a little messy, and would probably require the > > Application API. In our case, we have about 1200 accounts/files. It > > would require reading headers and doing proper locking so as not to > > collide with the mail programs. Another advantage of maildir format over mailbox :) Only one message per file and no need for locking :) OK, I am still using mailbox, but I will change that :) > > I'm guessing that for those changers where it's all tied up in one scsi > > address, and/or where there are multiple drives in a library, it might > > be desirable to have changer handle it. Then my case becomes the special > > case -- the changer is set up in sgen.conf and has a scsi device > > address, and the tape drive is set up in st.conf and is /dev/rmt/1 -- so > > the changer does not know how the drive got set up. This special case > > might require the changer to look somewhere else, e.g. amanda.conf, to > > find out. But, then, couldn't it also tell somehow if there had been an > > override? Or does that get too messy? > > That's basically the answer -- the current changer interface has no > provision for passing along overrides, and adding one would potentially > break a lot of custom changer scripts. You've hit the nail on the head > as to why changers provide devices to Amanda, rather than leaving her to > use tapedev. An idea for the next release of Amanda: Add one config parameter that says "use the device povided by the tape changer" and that default to YES. So it would not break any existing customized changer script. When set to NO, use the device explicitely defined by tapedev. No need to change any script, all the changes are inside Amanda only. Best regards, Olivier
