Re: want only full dumps (strategy noinc)
From: Alexandre Oliva [EMAIL PROTECTED] Date: 19 Apr 2001 18:48:47 -0300 On Apr 18, 2001, Julian R C Briggs [EMAIL PROTECTED] wrote: How do others archive a set of large filesystems onto a set of small tapes? If filesystems are larger than tapes, telling Amanda to back them up as individual sub-directories with GNU tar. Thanks. I'll investigate that when I return from a break on 30th April. Julian -- Julian Briggs, System Administrator, Department of Computer Science, University of Sheffield, Regent Court, 211 Portobello St, Sheffield S1 4DP, UK Phone +44 (0) 114-222-1851. Fax +44 (0) 114-222-1810 [EMAIL PROTECTED] http://www.dcs.shef.ac.uk/~julian
Re: want only full dumps (strategy noinc)
John, Thanks for your further comments. Thanks. Yes I have upgraded to 2.4.2p2 (the advfs.patch is not applicable). The advfs.patch does more than just fix problems with advfs. It also deals with some Linux LABEL= issues in /etc/fstab. It may still not apply to your setup, but just in case. I am running Solaris-8. So the advfs patch really is not relevant. My reading of the amanda man page for runtapes is that it it only applicable when using a tape changer, which we are not. You can use chg-manual to emulate a changer with a human. Ahhh. Perhaps that's the way to go. I'll investigate. Also I will copy amdump to amdump0 and edit to stop at the planner output stage to speed up the testing cycle! Aside from not doing incrementals, what did you expect Amanda to do with the dumps that would not fit on your single tape? Defer them until the next run? Yes. I hope to do a run once a week each of which does a full backup of 20-25% of the filesystems. Is this feasible? I think you're going to have to split your configuration up by hand into groups of clients/disks that fit on a single tape. Or else use chg-manual. I really don't want to split my clients into groups like that. I see one of the great advantages of Amanda as letting it handle which filesystems to dump on which tapes. I am running 2.4.2p2 with strategy noinc but amstatus output appears to show incrementals :-(. You've backed Amanda into a corner by not giving it enough tape to do what you insist it does. It's doing the best it can :-). How do others archive a set of large filesystems onto a set of small tapes? I'd need to see the planner section of amdump.NN to dig more into why strategy noinc didn't do as expected. To avoid cloging the amanda mailing-list, I have put this on my website: http://www.dcs.shef.ac.uk/~julian/amdump.20010417 Thanks Julian -- Julian Briggs, System Administrator, Department of Computer Science, University of Sheffield, Regent Court, 211 Portobello St, Sheffield S1 4DP, UK Phone +44 (0) 114-222-1851. Fax +44 (0) 114-222-1810 [EMAIL PROTECTED] http://www.dcs.shef.ac.uk/~julian
Re: want only full dumps (strategy noinc)
John and Paul, Thanks for your responses.
Sadly the Amanda 2.4.1 change log (fragment appended) shows
"strategy noinc" is not implemented yet (see below).
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
But it does appear to be in 2.4.2.
Great. I will try upgrading to 2.4.2.
Using "dumpcycle 0" I still see incrementals in the archive backup.
Really?
Yes really, the appended amdump output shows incremental dumps.
Under what circumstances? This is usually all I do to get an
archive such as you're trying to do.
I have also appended the config. We have ~120Gb to dump, have an
18Gb holding disk and use software compression to dump to 12Gb
(native ie uncompressed) DDS3 DAT tapes.
From: "Bort, Paul" [EMAIL PROTECTED]
Date: Wed, 11 Apr 2001 15:48:02 -0400
Just to hazard a guess: You might have set dumpcycle 0 in one dumptype, and
then used another. I set dumpcycle 0 at the beginning of the amanda.conf
file, and all backups (for that configuration) always run level 0 backups.
I'm using a beta of 2.4.2 that I've heard is similar to 2.4.1.
I can confirm that I set dumpcycle 0 (both globally and in the
dumptype). I will try upgrading to 2.4.2.
I have appended config and amdump report:
Julian
--
Subject: archive AMANDA MAIL REPORT FOR April 12, 2001
...
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
cedar / 1 2079 448 21.51:185.70:00 1789.7
cedar /export2 FAILED
cedar /var 1 FAILED
cedar /var/mail 1 423039 192352 45.5 13:36 235.73:50 834.7
hazel / 08649530880 35.70:40 768.30:57 544.9
hazel /export425023 3392 13.62:14 25.40:04 878.4
hazel /export0 1 FAILED
hazel /export1 16166332672 53.05:31 98.70:38 869.5
hazel /usr 2 1023 224 21.90:20 11.10:00 2276.0
hazel /var 322815 2112 9.30:46 46.20:02 862.0
u2/ 1 1663 352 21.20:457.80:00 1887.1
u2/export338527 2880 7.53:11 15.10:03 916.4
u2/export0 4 426047 168384 39.5 16:07 174.23:18 850.3
u2/export1 36073529728 48.94:27 111.40:34 866.0
u2/export2 1 339 1952640 57.4 94:01 346.2 38:03 855.5
u2/export3 18303924736 29.82:01 204.90:29 847.1
u2/export4 1 FAILED
u2/export5 2 640447 260352 40.7 16:49 257.9N/AN/A
u2/export6 0 10603423 9977792 94.1 304:58 545.3N/AN/A
u2/var 348735 3648 7.50:57 64.20:04 996.3
--
bumpsizeinf #try to stop incremental dumps (JRCB11-apr-01)
bumpmult2 #factor by which bumpsize increases per level
dumpcycle 0 # Setting this to zero forces a full backup
each run
infofile"/var/adm/amanda/archive/curinfo"
inparallel 99 #ensure this not limiting
labelstr"archive[0-9]*"
logdir "/var/log/amanda/archive"
indexdir"/var/adm/amanda/archive/index"
mailto "backup"
maxdumps6 # low else connection to u2 fails
netusage10 mbps #Mbytes/s
org "archive"
tapedev "/dev/rmt/0bn" #bsd (see above), hardware compression off
tapetypeDDS3#tape params tuned with tapetype (JRCB
5-jun-00)
tapecycle 100 #at least 100, maybe more (JRCB 10-apr-01)
reserve 0 #use all holding-disk for level 0 dumps
holdingdisk sun3-6 {
directory "/dumps/archive"
chunksize inf #max file size is size of holding disk
}
#DUMPTYPE SECTION
define dumptype dcs {
# compress#use default (client fast)
dumpcycle 0 # Setting this to zero forces a full backup
each run
holdingdisk yes
index yes
record no #do not update /etc/dumpdates
}
#TAPETYPE SECTION
define tapetype DDS3 {
comment "HP C1537A: internal DDS3 DAT drive"
filemark 0 kbytes # integrated into data
length 11 gigabytes# 125 m tape (no hardware compression)
want only full dumps (strategy noinc)
Dear All, I want to use "strategy noinc" with an "archive" configuration, to get full dumps only. We run 2 configurations: 1. "normal" daily backup with a dumpcycle of 25 tapes (~1 month). 2. "archive" weekly backup with a dumpcycle of 150 tapes (~3 years). We dump ~120Gb onto With software compression onto 5 12Gb DAT3 tapes, ie ~20% of our data per week. We do not want incrementals in the archive as they would be against "normal" (daily) configuration backups which we reuse after a month. Sadly the Amanda 2.4.1 change log (fragment appended) shows "strategy noinc" is not implemented yet (see below). Using "dumpcycle 0" I still see incrementals in the archive backup. I have considered "bumpsize inf" to stop incrementals. I welcome help resolving this. Thanks Julian -- 1998-07-15 Alexandre Oliva [EMAIL PROTECTED] * configure.in: created Amanda 2.4.1 branch * example/amanda.conf.in: strategy noinc is not implemented yet -- Julian Briggs, System Administrator, Department of Computer Science, University of Sheffield, Regent Court, 211 Portobello St, Sheffield S1 4DP, UK Phone +44 (0) 114-222-1851. Fax +44 (0) 114-222-1810 [EMAIL PROTECTED] http://www.dcs.shef.ac.uk/~julian
