Re: Christoph Pospiech/Germany/IBM is out of the office.
Can list admin please remove this user from the mailing list? I complained several times both the user and the postmasters, to no avail. Out of office autoresponders on mailing list, and a repeat offense at that. Christoph Pospiech wrote: I will be out of the office starting February 16, 2004 and will not return until February 17, 2004. No access to email. In urgent case please call my mobile +49-171-7655871
Re: how to fit backup on 1 tape
Madhvi Gokool wrote: I have a18G filesystem that needs to be backed up and do not have a tape changer. I have tried the following :- [...] When I run amdump WeeklySet1, it asks me to load tapes repeatedly. Fine, just as expected. But does it make any backups? Or what exactly is your problem? Since 2 tapes of 12G should be enough for the backup ( no hardware compression and using tar) , I am not sure what I'm doing wrong. can anyone help me with this config??? In the normal way of using amanda, you don't need chg-manual to backup a large disk. You could divide your big filesystem in smaller subdirectories, use a dumpcycle of several days, and spread the full backups over each run. Together with the incrementals, you can always restore up to the last day. See in docs/disklist for the last example how split up a large directory. Apology if this is not an answer to your question. -- 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: how to fit backup on 1 tape
On Mon, Feb 16, 2004 at 10:35:08AM +0400, Madhvi Gokool wrote: Hello I have a18G filesystem that needs to be backed up and do not have a tape changer. I have tried the following :- runtapes 2 # number of tapes to be used in a single run of amdump tpchanger chg-manual # the tape-changer glue script tapedev /dev/nst0 # the no-rewind tape device to be used changerfile /usr/adm/amanda/WeeklySet1/changer When I run amdump WeeklySet1, it asks me to load tapes repeatedly. 3 files were created in the log directory and are as follows :- changer-status-access, changer-status-clean, changer-status-slot with following contents : - changer-status-access :: 2 :: changer-status-clean :: 0 :: changer-status-slot :: 1 Since 2 tapes of 12G should be enough for the backup ( no hardware compression and using tar) , I am not sure what I'm doing wrong. can anyone help me with this config??? From the name of your amanda config, Weekly..., I'm guessing this is the do a full, level 0 backup on the weekend config. That you do not do incremental backup in this configuration. You say you have 18GB to backup. How many entries in your disklist (DLE's) are there? Each DLE must fit by itself on a `single' tape. The total collection of DLE's can exceed a tape, but no single DLE. Also, what is the length specified in your tapetype. If you have just a one big 18GB DLE and properly specified your tapelength as 12GB, I'm surprised it even attempted to do a dump. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: script to calculate tape parameters
Kurt Yoder said: Hello list I wasn't sure I understood how to set the Amanda dumpcycle, runspercycle, runtapes, and tapecycle correctly, so I wrote a small perl script to check my logic. It asks a few questions about the number of backups within a certain time period, whether a changer will be used, etc, and then prints the values one should set for dumpcycle, runspercycle, runtapes, and tapecycle. Assuming my thinking is correct, perhaps others on this list could benefit from the script as well, so I am attaching it... I refined the script a bit based on feedback from the list. I've posted the updated script to the faq-o-matic at http://amanda.sourceforge.net/fom-serve/cache/391.html since the mailing list archive strips attachments. If there's interest, I can set up a Sourceforge project, though this is such a small script it hardly seems worth it. -- Kurt Yoder Sport Health network administrator
Re: Making two copies of a backup -- CONCLUSION
On Mon, Feb 09, 2004 at 03:01:21PM -0500, Eric Siegerman wrote: I want to make two identical copies of an Amanda backup. I have enough holding-disk space to hold all of the client's DLEs at once, so what I'm thinking is this: 1. Build a new Amanda configuration that backs up only the client in question (reserve=0; also record=no to be on the safe side) 2. Run the configuration with no tape in the drive, forcing all the (full) backups to holding disk 3. Hard-link the holding-disk files to another directory that Amanda doesn't know about 4. Run amflush 5. Hard-link the holding-disk files back to the Amanda spool directory (it's pure paranoia that I choose not to mv them instead and thus dispense with step 7) 6. Run amflush again 7. Delete the holding-disk files from the other directory Does this look like a reasonable approach? Since nobody raised any red flags, I went ahead and tried this. It worked flawlessly. My main worry is that the curinfo database and multiple amflush's of the same data won't get along with each other. Is that likely to be a problem? This didn't turn out to be an issue. The only effect I could find on the database was that when I amflushed the second copy (step 6), amadmin info forgot about the first one. But this is a minor quibble, and I'm *not* suggesting that anything needs to be done about it. amserver 3# amadmin archive info foo c0t4d0s4 Current info for foo c0t4d0s4: Stats: dump rates (kps), Full: 629.0, -1.0, -1.0 Incremental: -1.0, -1.0, -1.0 compressed size, Full: 94.8%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20040209 archive.foo_before_reinstall.20040210.copy_2.tape_1 2 1308351 1240741 1972 amadmin find gets it right -- it reports both tapes: amserver 4# amadmin archive find foo c0t4d0s4 | more Scanning /var/spool/amanda/holding-disk-archive... date host disk lv tape or file file status 2004-02-09 fooc0t4d0s4 0 archive.foo_before_reinstall.20040210.copy_1.tape_1 2 OK 2004-02-09 fooc0t4d0s4 0 archive.foo_before_reinstall.20040210.copy_2.tape_1 2 OK In summary, I wouldn't recommend doing it this way on a regular basis -- RAIT and a second drive would be easier and less error-prone. But I only needed to do a single two-copy backup; in that situation, if you have enough holding-disk space, this approach is hard to beat. (And no, my regular backup tapes don't have weird names like that; they're Weekly.[0-9][0-9][0-9]. But for permanent archival tapes, I thought, why not make them as self-identifying as possible?) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
