Amanda Backup
I have following queries in the amanda Backup 1) [EMAIL PROTECTED] amanda]$ amadmin DailySet1 balance new disk indus.mumbai.redhat.com://account.mumbai.redhat.com/C ignored. Why do i get this 2) I get this whwn i run amadmin DailySet1 due Overdue 12619 days: indus.mumbai.redhat.com://account.mumbai.redhat.com/D Overdue 12619 days: illusions.mumbai.redhat.com:/home/amit Can anyone clarify this on the above point -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. Tel : +91-22-22881326/27 Fax : +91-22-22881318 Cell : +91-9820367783 signature.asc Description: This is a digitally signed message part
Re: ideal amanda.conf configuration
Sergio A Lima Jr wrote: I'm have dificulties for create and manager back-up with amanda server. My problems: I not get ideal configuration for running back-up. My scenary: 1. Back-up server machine running GNU/Linux kerner 2.4 and file system type ext3. Tape device is SONY and model: SDT-2000E, with tapes of the 2GB uncompressed (single slot). 2. Is necessary running back-up 3 every time this week and incluind rotine of the back-up 3 servers. 3. The volum total of the files is approximate 22Gb. Unless I misunderstood, you seem to have a set of conflicting requirements here. You cannot backup 22 Gbyte to 2 GByte tapes running 3 times a week. Your tapecapacity is 2 GB, and you need to backup 22 GB. That means that you need 11 tapes to do a full backup (uncompressed). Let's assume the compression ratio is 50% (optimistic), then you still need 6 tapes to do the full backup. Amanda tries to spread the full backups over a dumpcycle. Each day, a few of the disklistentries are full backed up, the rest gets an incremental dump. That means we need a dumpcycle of at least 6 tapes in the case that no data changes and incremental dumps are minimal. If data does change, then the incremental backups need more space on the tapes too. So you need even more tapes in each cycle. Lets say 10 tapes fit. The total number of tapes is best double or more of the number of tapes in each dumpcycle. We spread the 10 tapes over 2 weeks, using one tape each working day: dumpcycle 14 days runspercycle 10 runtapes 1 tapecycle 20 tapes If you really really insist on running only 3 times each week, then you could try this: dumpcycle 21 days runspercycle 9 runtapes 1 tapecycle 18 tapes I already indicated this is very optimistic, and assumes the data does not change very much during the cycle. If you have less compressable data, or larger incrementals, you could set: dumpcycle 21 days runspercycle 15 runtapes 1 tapecycle 30 tapes Increasing the dumpcycle results in less full backups each run, but probably means that the average size of incrementals also increases. If you do have more tapes, just enlarge the tapecycle value. The idea is to keep the dumpcycle as small as possible, and the tapecycle as large as possible. There is probably another problem. Each disklistentry needs to fit completely on a tape. Your tapecapacity is 2 GByte. That means that, after compression, the full backup of a DLE should be less than 2 Gbyte. The same tape should also have enough space to hold all the other incrementals too! Given that those 22 GByte is divided over 3 hosts, you probably need to use GNUTAR plus include/exclude mechanisms to split larger partitions up into smaller ones. Have a look at the last example in $SRCS/example/disklist file. One final remark: it takes a few cycles before amanda can spread the backups more or less optimal over the dumpcycle. This gets done faster if you add DLE's a few at a time each run. -- 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: Amanda Backup
Kaushal Shriyan wrote: I have following queries in the amanda Backup 1) [EMAIL PROTECTED] amanda]$ amadmin DailySet1 balance new disk indus.mumbai.redhat.com://account.mumbai.redhat.com/C ignored. Why do i get this Because amanda never did a full backup of that DLE, it cannot predict when it will be scheduled, nor how much data that will add to the size of full backups that day. 2) I get this whwn i run amadmin DailySet1 due Overdue 12619 days: indus.mumbai.redhat.com://account.mumbai.redhat.com/D Overdue 12619 days: illusions.mumbai.redhat.com:/home/amit Can anyone clarify this on the above point $ perl -M'Date::Calc :all' \ -e 'print join(-, Add_Delta_Days(2004, 7, 26, -12619)), \n' 1970-1-7 I guess you got that result 6 days ago :-) January 1, 1970 is the beginning of the epoch in Unix. I'm not 100% sure, but I think that some older version of Amanda says this when this is a new disk, or you did a amadmin config force on that DLE to force a full dump. What version is this? Otherwise you somehow got a zero in the field of last-full-dump in the info files. Don't know how that could get there (except if your CMOS battery is broken, and you booted that computer 6 days ago?) -- 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 * ***
Tapes filling up
Hi, I'm fairly new to all this so please bear with me. I am currently backing up 150Gb nightly split over 3 partitions (1x8Gb, 2x71Gb). These are dumping straight to a 100/200Gb LTO changer. No compression is used for the backup because most files are jpgs / pdfs and no holding disk is used because there isn't one big enough. The problem I have is that when amanda gets round to backing up the last 71Gb partition there is only 20Gb left on the first tape, which it tries to write before failing and starting the dump again on a second tape. Everyting eventually gets backed up ok, but 3+ hours are wasted writing to the first tape. Is there a way to tell amanda to use a new tape for the last partition? Thanks.
Planner problems
Hi guys I am using amanda installed in a FReBSD 5.1 BOx, it is runnig fine when I run amdump in a local basis, but when I try to make the buckups from other computers in my network I got planner errors: SETTING UP FOR ESTIMATES... planner: time 0.007: setting up estimates for fslim951-2.pe.yr.com:/home/arosales fslim951-2.pe.yr.com:/home/arosales overdue 12624 days for level 0 setup_estimate: fslim951-2.pe.yr.com:/home/arosales: command 0, options: last_level -1 next_level0 -12624 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) planner: time 0.008: setting up estimates for fslim951-1.pe.yr.com:/home/arosales fslim951-1.pe.yr.com:/home/arosales overdue 12624 days for level 0 setup_estimate: fslim951-1.pe.yr.com:/home/arosales: command 0, options: last_level -1 next_level0 -12624 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) driver: pid 715 executable /usr/local/libexec/amanda/driver version 2.4.4 driver: send-cmd time 0.019 to taper: START-TAPER 20040724 planner: time 0.019: setting up estimates took 0.001 secs and then I get a Failed QUEUE:empty amcheck gives me no errors. Any ideas would be greatly appreciated - Original Message - From: Paul Bijnens [EMAIL PROTECTED] Date: Mon, 26 Jul 2004 10:57:05 +0200 To: Kaushal Shriyan [EMAIL PROTECTED] Subject: Re: Amanda Backup Kaushal Shriyan wrote: I have following queries in the amanda Backup 1) [EMAIL PROTECTED] amanda]$ amadmin DailySet1 balance new disk indus.mumbai.redhat.com://account.mumbai.redhat.com/C ignored. Why do i get this Because amanda never did a full backup of that DLE, it cannot predict when it will be scheduled, nor how much data that will add to the size of full backups that day. 2) I get this whwn i run amadmin DailySet1 due Overdue 12619 days: indus.mumbai.redhat.com://account.mumbai.redhat.com/D Overdue 12619 days: illusions.mumbai.redhat.com:/home/amit Can anyone clarify this on the above point $ perl -M'Date::Calc :all' \ -e 'print join(-, Add_Delta_Days(2004, 7, 26, -12619)), \n' 1970-1-7 I guess you got that result 6 days ago :-) January 1, 1970 is the beginning of the epoch in Unix. I'm not 100% sure, but I think that some older version of Amanda says this when this is a new disk, or you did a amadmin config force on that DLE to force a full dump. What version is this? Otherwise you somehow got a zero in the field of last-full-dump in the info files. Don't know how that could get there (except if your CMOS battery is broken, and you booted that computer 6 days ago?) -- 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 * *** -- _ Web-based SMS services available at http://www.operamail.com. From your mailbox to local or overseas cell phones. Powered by Outblaze
Re: Planner problems
On Mon, Jul 26, 2004 at 11:17:10PM +0100, Alvaro Rosales enlightened us: guys I am using amanda installed in a FReBSD 5.1 BOx, it is runnig fine when I run amdump in a local basis, but when I try to make the buckups from other computers in my network I got planner errors: SETTING UP FOR ESTIMATES... planner: time 0.007: setting up estimates for fslim951-2.pe.yr.com:/home/arosales fslim951-2.pe.yr.com:/home/arosales overdue 12624 days for level 0 setup_estimate: fslim951-2.pe.yr.com:/home/arosales: command 0, options: last_level -1 next_level0 -12624 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) planner: time 0.008: setting up estimates for fslim951-1.pe.yr.com:/home/arosales fslim951-1.pe.yr.com:/home/arosales overdue 12624 days for level 0 setup_estimate: fslim951-1.pe.yr.com:/home/arosales: command 0, options: last_level -1 next_level0 -12624 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) driver: pid 715 executable /usr/local/libexec/amanda/driver version 2.4.4 driver: send-cmd time 0.019 to taper: START-TAPER 20040724 planner: time 0.019: setting up estimates took 0.001 secs and then I get a Failed QUEUE:empty amcheck gives me no errors. Any ideas would be greatly appreciated Likely a firewall problem. amcheck usually passes the firewall without a problem, but amdump fails. I would check to see if there are any firewalls on the server, client, or somewhere in between. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Planner problems
On Tue, Jul 27, 2004 at 12:09:50AM +0100, Alvaro Rosales enlightened us: Thank you, but there are no firewalls running in the client computers. I have noticed that there is one line tahat says: overdue 12624 days for level 0 is that ok ? That just means that a level 0 has never been done for that client. 12624 days ago is likely January 1, 1970. I would look at the debug files on the clients to ensure that the estimate requests are making it through as a next step. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Planner problems
On Tue, Jul 27, 2004 at 12:55:30AM +0100, Alvaro Rosales enlightened us: thank you , I get this error in sendsize.debug, but the directory exist.Any hint? sendsize[25120]: time 0.084: dump: /home/arosales: unknown file system That's an error from dump. My guess is that /home is a filesystem that is not supported by dump. You didn't say what OS you are using, but if it's linux, it must be an ext2/3 file system for dump to work. What OS and filesystem is it? Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Planner problems
On Tue, Jul 27, 2004 at 01:55:44AM +0100, Alvaro Rosales enlightened us: I am using Freebsd, and I am trying to backup a directoy inside my filesystem /home , I am using the filesystem of Freebsd Ah, ok. If you are trying to back up a subdirectory, you must use tar, not dump. Some versions of dump will allow you to do level 0 backups of subdirectories, but it looks like FreeBSD may not...perhaps someone who knows that OS better than I can answer that. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
