Re: Simple backup tape encryption
Bruce Fletcher wrote: I would like to propose an idea for the Amanda wishlist. Assuming there aren't enough items on that list already... sigh ;) What I am imagining is putting a simple symmetric encryption key for perhaps AES encryption in the Amanda config file, and then perhaps enabling encryption in dumptype records. Assuming encryption is the last thing that happens before a DLE goes to tape and the first thing that happens on the way back, most of the Amanda chain would not need to know about the presence of any encryption. And for disaster recovery, you would presumably want to have a printout of your Amanda config offsite, so your password would be recoverable. As a start, is this idea conceptually sound? Maybe it could be implemented already with wrapper scripts? Good idea, this would add value to AMANDA. I am currently playing around with a wrapper-setup using aespipe (http://loop-aes.sourceforge.net/). Should be relatively easy to implement in a wrapper, yes. Maybe someone else wants to dig into this as well? Stefan. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: Simple backup tape encryption
Stefan G. Weichinger wrote: I am currently playing around with a wrapper-setup using aespipe (http://loop-aes.sourceforge.net/). Well, good news ... I hadn't expected that I would be able to get there so fast, but I have something working: I wrote a wrapper (modified and extended one, to be honest ;) for GNU-tar, which basically adds an option to the tar-call. This option tells tar to pipe through bz2aespipe, which is another wrapper, this time for the aespipe-binary. I had to patch bz2aespipe also to be able to store the Passphrase inside a file, so dumps can be done without manual intervention. Right now I have a vtape-setup, which does AES-encryption with amdump, and AES-decryption with amrestore. This works fine already. What is still missing, is the support of amrecover, seems like there's something wrong with the index-generation, the files are there, but no proper content ... And it has still to be tested with separated client/server-setups, yes. I think it should be possible to patch all this into AMANDA as well, I will see what I can do. But this is gonna be a topic for amanda-hackers then ;) I will try to write a small HOWTO about my steps soon. Stefan. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: amanda dumping salad of levels
Hi Jon, - I add "strategy nofull" to all incremental configs, and its work fine. - In full backup scripts is amadmin with force option. - All my daily incremental backups is flushing to the same tape. Thank you very much. Leonid Jon LaBadie wrote: On Sun, Jun 26, 2005 at 04:13:30PM +0300, Leonid Shulov wrote: Hi, My amanda configurations is: - DailySetPS - Fraiday weekly to tape (Full dump PS and servers) 00 0 * * 5 root /etc/amanda/amdumpPS.cron - DailySetL - Workday nightly (5 days) to holding disk (incremental dump PS and servers with Mandrake Linux PC) 30 1 * * 0-4 root /etc/amanda/amdump00.cron - DailySetTP - Monday weekly to tape (Full dump notebooks) /etc/amanda/amdumpTP.cron - DailySetY - Thuesday weekly to tape (Full dump boss notebooks) 00 10 * * 0-4 root /etc/amanda/amdump10.cron - DailySetE - Wednesday nightly to tape (Full dump Mandrake Linux PC) 00 20 * * 3 root /etc/amanda/amdumpPE.cron - DailySet2 - Workday (3 times X 5 days) to holding disk (12:00,15:00,18:00 incremental dump notebooks) 00 12 * * 0-4 root /etc/amanda/amdump12.cron 00 15 * * 0-4 root /etc/amanda/amdump15.cron 00 18 * * 0-3 root /etc/amanda/amdump18.cron - DailySetY - Workday (1 time X 5 days) to holding disk (10:00 incremental dump boss notebook) 00 10 * * 0-4 root /etc/amanda/amdump10.cron - DailySetF - Workday nightly (5 days) flush from holding disk to tape 00 20 * * 0-4 root /etc/amanda/amflush.cron Attached: 1. /etc/amanda/DailySet2/amanda.conf 2. /home/amanda/amd/ logfile Jon LaBadie wrote: On Thu, Jun 23, 2005 at 02:10:55PM +0300, Leonid Shulov wrote: Hi, I upgraded my amanda to 2.4.5 version, and after that sometimes amanda do backup with lev0 without any tape to holding disk. This broke all my work order. Before I do full PC dump once a week at Saturday nightly, incremental PC dump nightly in working days to holding disk. Daily incremental Notebook dump I do to holding disk. And now I don't know what to do, amanda dumping salad of levels: 0,1n The behavior you describe, a mixture of levels, is the 'normal' behavior for amanda. That amanda was behaving differently before suggests you had some aspect of your configuration set to force amanda to your desireed scheme. I'm surprised that a version change in the amanda executables would change its behavior with respect to an existing configuration. Let us know how your configuration tries to force amanda into the non-standard behavior you want. Maybe we will be able to notice something that is now apparent from what your posted. Leonid, amazingly complex setup. Seems like there could be a simpler, ?better? way to solve your requirements. But you know your needs better than we. It seems like you run many configs, with perhaps a total of about 40 amump runs per/work week. From what you present I can't tell if there is any overlap in config directories, disklists, log and index files, ... The one you show in more detail, DailySet2, seems to use the a subdir of the amanda user's home for its logs. Also this config uses tapes called DailySet1 despite the DailySet2 name. Do all your configs get flushed to the same tape? None of that addresses your stated problem, a changed behavior where you are now getting a mixture of full and incremental dumps when you want one or the other. But I see nothing in your DailySet2 amanda.conf file that would force one or the other behavior, no "increment only" type directives, so the behavior you are seeing is exactly the behavior I would expect, amanda's default of a mixture of levels. Is there something in your cron scripts that you expect would force this behavior? A common way to force amanda to behave the way you seem to want is to have a very long dumpcycle, a directive of increment only or no-full, and when you actually do want a full dump, use amadmin to "force" a level 0 dump on the next run.
Re: many dumps in parallel
many thanks to all, it was a problem with bandwidth definitions.
Alexc.
On Tue, 2005-06-21 at 12:32 +0200, Paul Bijnens wrote:
Vects wrote:
0 dumpers busy : 0:00:00 ( 0.00%)
1 dumper busy : 0:41:06 ( 70.46%)no-bandwidth: 0:41:06
(100.00%)
2 dumpers busy : 0:17:13 ( 29.53%)no-bandwidth: 0:17:13
(100.00%)
3 dumpers busy : 0:00:00 ( 0.00%)
4 dumpers busy : 0:00:00 ( 0.01%)
Here you got the reason why amanda did not start other dumpers:
you configured a too low value for bandwith.
define interface eth0 {
comment 10 Mbps ethernet
use 400 kbps
}
Amanda was already using more than 400kpbs when dumping a DLE
and here is specified to limit this.
Re: lvm and amanda?
Paul Bijnens wrote: Paul Bijnens wrote: Following up on myself... (as usual on mondays)... And again following up on myself... ;-) And again following up on myself -- hey it's monday again :-) Seems the bug was fixed in device-mapper 1.00.20 by making uid, gid, and mode a compile time option in device-mapper. See bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141050 That means: if you create the modules yourself, you have to: ./configure --with-device-gid=6 --with-device-mode=0660 ... each distributor should compile this themselves and use the correct number for gid. The default is uid=0, gid=0, mode=0600. So that means that the bug now shifts to the configurators of each distro :-) At least it is going forward -- a little. The Fedora 4 distro and Centos4.1 at least has the correct options in the .spec file. I don't understand (yet) why the permissions are still wrong on the original devices in my CentOS4.1 installation, while they are ok for the snapshot devices... -- 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 * ***
The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Hi all I have running amanda for a week but Fridays tape DailySet4 didn't get backed up because The DailySet4 tape is in the drive but my amanda doesn't think So. What is the best way to check what amanda tape it is as I assume when labelling I may of made a mistake. Is there a amanda program that will check what tape I have in the drive. *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet104. Here is the message when I run amverify Defects file is /tmp/amanda/amverify.20028/defects amverify DailySet1 Mon Jun 27 15:41:39 BST 2005 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... ** No amanda tape in slot So whats the best step to correct this. Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Chuck Amadi Systems Administrator wrote: Hi all I have running amanda for a week but Fridays tape DailySet4 didn't get backed up because The DailySet4 tape is in the drive but my amanda doesn't think So. What is the best way to check what amanda tape it is as I assume when labelling I may of made a mistake. Is there a amanda program that will check what tape I have in the drive. *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet104. Here is the message when I run amverify Defects file is /tmp/amanda/amverify.20028/defects amverify DailySet1 Mon Jun 27 15:41:39 BST 2005 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... ** No amanda tape in slot So whats the best step to correct this. Cheers I would try amtape [config] show. Vicki
Re: The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Hi I don't have no tpchanger specified in my ~amanda.conf As below # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. I am only using one tape per run that does a full backup onto tape. Thus is there a way to check my tapes I did orderly label them but need to verify which tape is DailySet4. Cheers On Mon, 2005-06-27 at 10:51 -0500, Vicki Stanfield wrote: Chuck Amadi Systems Administrator wrote: Hi all I have running amanda for a week but Fridays tape DailySet4 didn't get backed up because The DailySet4 tape is in the drive but my amanda doesn't think So. What is the best way to check what amanda tape it is as I assume when labelling I may of made a mistake. Is there a amanda program that will check what tape I have in the drive. *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet104. Here is the message when I run amverify Defects file is /tmp/amanda/amverify.20028/defects amverify DailySet1 Mon Jun 27 15:41:39 BST 2005 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... ** No amanda tape in slot So whats the best step to correct this. Cheers I would try amtape [config] show. Vicki -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: Simple backup tape encryption
Stefan G. Weichinger wrote: Stefan G. Weichinger wrote: I am currently playing around with a wrapper-setup using aespipe (http://loop-aes.sourceforge.net/). Well, good news ... I hadn't expected that I would be able to get there so fast, but I have something working: I wrote a wrapper (modified and extended one, to be honest ;) for GNU-tar, which basically adds an option to the tar-call. This option tells tar to pipe through bz2aespipe, which is another wrapper, this time for the aespipe-binary. I had to patch bz2aespipe also to be able to store the Passphrase inside a file, so dumps can be done without manual intervention. Right now I have a vtape-setup, which does AES-encryption with amdump, and AES-decryption with amrestore. This works fine already. What is still missing, is the support of amrecover, seems like there's something wrong with the index-generation, the files are there, but no proper content ... And it has still to be tested with separated client/server-setups, yes. I think it should be possible to patch all this into AMANDA as well, I will see what I can do. But this is gonna be a topic for amanda-hackers then ;) I will try to write a small HOWTO about my steps soon. Stefan. Wow, Stefan, that sounds great! I wasn't expecting such fast results. One thing I found looking at AES tools that you may find interesting is this: http://aescrypt.sourceforge.net/ It has one interesting property. You give it the name of a key file on the command line and it looks through it for a line like so: kk=hex key It ignores all other lines in the file. I was thinking that if Amanda could ignore the kk= line, then the key could be stored in the normal Amanda configuration file without any patching of the utility, and there would also be no need to have another separate configuration file. Anyway, just a thought. I should just get out of your way, though, and let you get those encrypted backups flowing. Thanks, - Bruce
Re: The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Chuck Amadi Systems Administrator wrote: Hi I don't have no tpchanger specified in my ~amanda.conf As below # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. I am only using one tape per run that does a full backup onto tape. Thus is there a way to check my tapes I did orderly label them but need to verify which tape is DailySet4. Cheers On Mon, 2005-06-27 at 10:51 -0500, Vicki Stanfield wrote: Chuck Amadi Systems Administrator wrote: Hi all I have running amanda for a week but Fridays tape DailySet4 didn't get backed up because The DailySet4 tape is in the drive but my amanda doesn't think So. What is the best way to check what amanda tape it is as I assume when labelling I may of made a mistake. Is there a amanda program that will check what tape I have in the drive. *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet104. Here is the message when I run amverify Defects file is /tmp/amanda/amverify.20028/defects amverify DailySet1 Mon Jun 27 15:41:39 BST 2005 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... ** No amanda tape in slot So whats the best step to correct this. Cheers I would try amtape [config] show. Vicki Sorry. I didn't notice that in your earlier email. How about using dd to read the header info off the tape? Vicki
Re: The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Vicki Stanfield wrote: Sorry. I didn't notice that in your earlier email. How about using dd to read the header info off the tape? Umm, please, no ... at least NOT YET ... Chuck, why not simply use amcheck -s conf? It checks if the inserted tape is the one to write to as well ... Stefan -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: Simple backup tape encryption
Bruce Fletcher wrote: Stefan G. Weichinger wrote: Right now I have a vtape-setup, which does AES-encryption with amdump, and AES-decryption with amrestore. This works fine already. What is still missing, is the support of amrecover, seems like there's something wrong with the index-generation, the files are there, but no proper content ... Update: amrecover works now as well, indexes are generated and read properly. The vtapes are encrypted AND (more important) decrypted now, works fine so far. I am going to add some more DLEs from some unpatched AMANDA-clients now to see what happens ... Wow, Stefan, that sounds great! I wasn't expecting such fast results. Same here ... http://aescrypt.sourceforge.net/ It ignores all other lines in the file. I was thinking that if Amanda could ignore the kk= line, then the key could be stored in the normal Amanda configuration file without any patching of the utility, and there would also be no need to have another separate configuration file. My preference is to have the passphrase separated as this enables to protect this file better. And you could put this passphrase onto some other media, say, a USB-stick or something ... There are many ways of securing things then ... Anyway, just a thought. I should just get out of your way, though, and let you get those encrypted backups flowing. ;) Greets, Stefan. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Interpreting Logs GNUTAR
Hi all,
I'm just getting my first Amanda setup working, and I've got a couple of
questions. First, is there documentation that tells how to interpret log
entries like the following?
SUCCESS dumper filename /files/share1 20050627 0 [sec 326.117 kb 550813
kps 1689.0 orig-kb 1843300]
SUCCESS taper fileserver /files/share1 20050627 0 [sec 34.484 kb 550814
kps 15972.6 {wr: writers 17214 rdwait 0.383 wrwait 29.156 filemark
2.233}]
That directory *should* contain 1.8 GB of files to backup, so I'm unsure
what I'm missing. However, I have a suspicion, and it ties into my next
question: how do you control dump levels when using GNUTAR?
I want to have individual directories in my disklist (ie, not individual
partitions, but subdirectories of those partitions), and dump just
chokes on this. I've switched to using GNUTAR, but I'm unsure how to
control when a full backup is done and when an incremental-style dump
level is done, or how it really works out when using GNUTAR.
Can anyone help me out on these points so I can get moving on my
testing? :)
Thanks!
--
Graeme Humphries ([EMAIL PROTECTED])
Linux Administrator
VCom Inc.
(306) 955-7075 ext 485
My views and comments do not necessarily reflect the views of my
employer.
Re: Simple backup tape encryption
Stefan G. Weichinger wrote: Update: amrecover works now as well, indexes are generated and read properly. The vtapes are encrypted AND (more important) decrypted now, works fine so far. I am going to add some more DLEs from some unpatched AMANDA-clients now to see what happens ... Was amrecover broken for vtapes in general or only encrypted vtapes? I have a vtape setup here but when I try to recover I get the following message from amrecover: Extracting files using tape drive file:/l/slots/ on host localhost. Load tape Ximbiot7 now Continue [?/Y/n/t]? y EOF, check amidxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n]? I also tried using amtape to load the correct tape before running amrecover with the same results. This is not covered in the HOWTO-FILE-DRIVER distributed with Amanda 2.4.4p3. Am I doing something wrong? I can't even find an amidxtaped.debug file. Thanks, Derek
Amanda and MacOS X and Exabyte autoloader
Dear All: First: forgive my terrible English. My mother language is Brasilian Portuguese. Second: is my first message. If this is not the best place to post like that, forgive me! I didn't find anything about put Amanda to work as client on MacOS X. Have anybody tried this yet? How can I determine if the Exabyte Autoloader VXA-2 1x10 1U will work perfectly with a linux machine with Amanda Server installed? What is, in your opinion, the best hardware equipment to work with Amanda? I will have to backup 100 GB every day, and I have to retain this information for one or two weeks. Thanks a lot, -- Artur F. Pimentel Analista de Suporte -- www.suam.edu.br www.unisuam.edu.br
Re: Simple backup tape encryption
Derek Price wrote: Stefan G. Weichinger wrote: Was amrecover broken for vtapes in general or only encrypted vtapes? It's not broken at all, my wrapper was broken. I have a vtape setup here but when I try to recover I get the following message from amrecover: Extracting files using tape drive file:/l/slots/ on host localhost. Really? I also tried using amtape to load the correct tape before running amrecover with the same results. This is not covered in the HOWTO-FILE-DRIVER distributed with Amanda 2.4.4p3. Am I doing something wrong? I can't even find an amidxtaped.debug file. http://www.amanda.org/docs/topten.html#id209 NO localhost inside disklist. You can easily find dozens of postings inside the archives. Use FQDNs for your hostnames ... - Just a few days ago I discussed this issue with some others and we agreed on the solution, that future AMANDA-releases should simply drop a big fat error when you use something like localhost or 127.0.0.1 ... There is a WARNING in recent releases, but this seems not enough ... (In AMANDA-releases newer than 2004-03-22 there is a WARNING issued ...) -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: Interpreting Logs GNUTAR
On Mon, 27 Jun 2005 at 1:37pm, Graeme Humphries wrote
I'm just getting my first Amanda setup working, and I've got a couple of
questions. First, is there documentation that tells how to interpret log
entries like the following?
SUCCESS dumper filename /files/share1 20050627 0 [sec 326.117 kb 550813
kps 1689.0 orig-kb 1843300]
SUCCESS taper fileserver /files/share1 20050627 0 [sec 34.484 kb 550814
kps 15972.6 {wr: writers 17214 rdwait 0.383 wrwait 29.156 filemark
2.233}]
That directory *should* contain 1.8 GB of files to backup, so I'm unsure
And that's how much amanda backed up -- orig-kb 1843300. It took
326.117 seconds, the compressed size of the backup was 550813 kb, and the
dump rate was 1689 kb/s.
what I'm missing. However, I have a suspicion, and it ties into my next
question: how do you control dump levels when using GNUTAR?
You don't -- amanda does.
I want to have individual directories in my disklist (ie, not individual
partitions, but subdirectories of those partitions), and dump just
chokes on this. I've switched to using GNUTAR, but I'm unsure how to
control when a full backup is done and when an incremental-style dump
level is done, or how it really works out when using GNUTAR.
Amanda manipulates tar to work just like dump. And with both, amanda
schedules level 0s or level 1s (and, if necessary, level 2s, level 3s,
etc) according to dumpcycle and runspercycle.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: Amanda and MacOS X and Exabyte autoloader
Artur F. Pimentel wrote: Dear All: First: forgive my terrible English. My mother language is Brasilian Portuguese. No problem ... Second: is my first message. If this is not the best place to post like that, forgive me! I forgive you, but please stop hi-jacking threads ... Simply write your new message to amanda-users@amanda.org ... I didn't find anything about put Amanda to work as client on MacOS X. Have anybody tried this yet? I hope this helps: http://www.amanda.org/docs/systemnotes.html#id2530998 Please let us know, if you find some OS-specific problems ... How can I determine if the Exabyte Autoloader VXA-2 1x10 1U will work perfectly with a linux machine with Amanda Server installed? Try it ;) AMANDA-tape-device-rule: If your OS supports it, AMANDA supports it. What is, in your opinion, the best hardware equipment to work with Amanda? I will have to backup 100 GB every day, and I have to retain this information for one or two weeks. I am sure you will get some feedback, but you might also browse the archives: http://marc.theaimsgroup.com/?l=amanda-usersr=1w=2 Stefan -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting implementation http://www.oops.co.at --
Re: Amanda and MacOS X and Exabyte autoloader
On Mon, 2005-06-27 at 17:03 -0300, Artur F. Pimentel wrote: How can I determine if the Exabyte Autoloader VXA-2 1x10 1U will work perfectly with a linux machine with Amanda Server installed? The easiest test is to use the commandline mtx utility. If mtx can manipulate your autoloader (which I'm guessing it can, given the success we've had with our new Exabyte Magnum 1x7 unit), then Amanda can be configured to use it as well. What is, in your opinion, the best hardware equipment to work with Amanda? I will have to backup 100 GB every day, and I have to retain this information for one or two weeks. Your VXA autoloader should be fine for this purpose. However, a better question would be, how much do you expect this data size to grow in the next year? It may be worth looking at some LTO solutions if your data size is going to double. Graeme -- Graeme Humphries ([EMAIL PROTECTED]) Linux Administrator VCom Inc. (306) 955-7075 ext 485 My views and comments do not necessarily reflect the views of my employer.
Re: Interpreting Logs GNUTAR
On Mon, 2005-06-27 at 16:16 -0400, Joshua Baker-LePain wrote:
SUCCESS dumper filename /files/share1 20050627 0 [sec 326.117 kb 550813
kps 1689.0 orig-kb 1843300]
SUCCESS taper fileserver /files/share1 20050627 0 [sec 34.484 kb 550814
kps 15972.6 {wr: writers 17214 rdwait 0.383 wrwait 29.156 filemark
2.233}]
That directory *should* contain 1.8 GB of files to backup, so I'm unsure
And that's how much amanda backed up -- orig-kb 1843300. It took
326.117 seconds, the compressed size of the backup was 550813 kb, and the
dump rate was 1689 kb/s.
Ahhh, I get it now. Thanks very much! :)
Amanda manipulates tar to work just like dump. And with both, amanda
schedules level 0s or level 1s (and, if necessary, level 2s, level 3s,
etc) according to dumpcycle and runspercycle.
Ok, so if I run another backup after this, presumably the dump level
should be higher, and kb should be much lower than 550814? I just want
to make sure I'm perfectly clear on this. :)
Re: Interpreting Logs GNUTAR
On Mon, 27 Jun 2005 at 2:22pm, Graeme Humphries wrote On Mon, 2005-06-27 at 16:16 -0400, Joshua Baker-LePain wrote: Amanda manipulates tar to work just like dump. And with both, amanda schedules level 0s or level 1s (and, if necessary, level 2s, level 3s, etc) according to dumpcycle and runspercycle. Ok, so if I run another backup after this, presumably the dump level should be higher, and kb should be much lower than 550814? I just want to make sure I'm perfectly clear on this. :) Yep, that's right. A level 1 is everything that's changed since the last level 0. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
What's the meaning of these logs?
Hi guys, I have a question about amanda logs. What's the meaning of promoted from no days ahead? this is the log: planner: Incremental of ns2:/data/back-up/rad-db/ bumped to level 2. planner: Incremental of radius:/var/back-up/rad-db/ bumped to level 3. planner: Full dump of ipass:/usr/ipass/ promoted from 6 days ahead. planner: Full dump of mail2:/etc/ promoted from 6 days ahead. planner: Full dump of ns2:/data/back-up/rad-db/ promoted from 3 days ahead. planner: Full dump of radius:/etc/ promoted from 4 days ahead. planner: Full dump of mg-rad:/etc/ promoted from 4 days ahead. Also why does amanda do that? Thanks, -- Ryan Pagquil Infodyne Inc. - PhilOnline.com 3603 Antel Global Corporate Center Doña Julia Vargas Ave. Ortigas Center Pasig City Web: www.philonline.com
Re: Amanda and MacOS X and Exabyte autoloader
Stefan and all: I forgive you, but please stop hi-jacking threads ... Simply write your new message to amanda-users@amanda.org ... I'm sorry. I thought just change the subject was enough. Laziness, what else can I say?? :(( I hope this helps: http://www.amanda.org/docs/systemnotes.html#id2530998 Please let us know, if you find some OS-specific problems ... This helps a lot, Thanks. I'll keep you informed with my progress.:-)) Try it ;) Unfortunely, I don't have this hardware to try, and if does not work, return it to the retailer. We will buy this product if I say OK. And will be my responsability if it not work. That's why I am asking to this list if someone knows this combination works. :(( AMANDA-tape-device-rule: If your OS supports it, AMANDA supports it. I quite sure the VXA-2 will work, but I'm very afraid about the autoloader (By the way, autoloader and tape changer is the same thing? I have already read something about it in Amanda documentation, but I'm not sure if I understand correctly...). If Autoloader does not work, I'll be throwing out thousands $$$. ;)) I am sure you will get some feedback, but you might also browse the archives: http://marc.theaimsgroup.com/?l=amanda-usersr=1w=2 OK! I'll do my home work! :))) But if someone have an opinion about this subject (best technology for backup), and thinks will not aggregate anything new to this list, feel free to mail me in PVT. ;)) Thanks for your time! Artur. PS: This MARC system rocks! Fantastic... Em Segunda 27 Junho 2005 17:16, Stefan G. Weichinger escreveu: Artur F. Pimentel wrote: Dear All: First: forgive my terrible English. My mother language is Brasilian Portuguese. No problem ... Second: is my first message. If this is not the best place to post like that, forgive me! I forgive you, but please stop hi-jacking threads ... Simply write your new message to amanda-users@amanda.org ... I didn't find anything about put Amanda to work as client on MacOS X. Have anybody tried this yet? I hope this helps: http://www.amanda.org/docs/systemnotes.html#id2530998 Please let us know, if you find some OS-specific problems ... How can I determine if the Exabyte Autoloader VXA-2 1x10 1U will work perfectly with a linux machine with Amanda Server installed? Try it ;) AMANDA-tape-device-rule: If your OS supports it, AMANDA supports it. What is, in your opinion, the best hardware equipment to work with Amanda? I will have to backup 100 GB every day, and I have to retain this information for one or two weeks. I am sure you will get some feedback, but you might also browse the archives: http://marc.theaimsgroup.com/?l=amanda-usersr=1w=2 Stefan -- Artur F. Pimentel Analista de Suporte -- www.suam.edu.br www.unisuam.edu.br
