Date: Sat, 30 Nov 1996 14:03:55 +0200 (IST) From: Yuri Gindin <yuri@aebeard.technion.ac.il> To: Andreas Klemm <andreas@klemm.gtn.com> Cc: gpalmer@FreeBSD.org, Michael Reifenberger <root@totum.plaut.de>, FreeBSD-Ports <freebsd-ports@FreeBSD.org> Subject: Re: amanda 2.3.0 anyone under current? Message-ID: <Pine.BSI.3.95.961130135848.11593A-100000@aebeard.technion.ac.il> In-Reply-To: <Pine.BSF.3.95.961124120253.5481B-100000@klemm.gtn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 Nov 1996, Andreas Klemm wrote: Andreas, > -----BEGIN PGP SIGNED MESSAGE----- >=20 > On Mon, 4 Nov 1996, Yuri Gindin wrote: >=20 > > On Thu, 31 Oct 1996, Michael Reifenberger wrote: > >=20 > > > Hi, > > > The subject says it. > > > I tried it with no success. > > > I suspect a changed DUMP format but > > > before digging into it I would like to ask If > > > anyone had success... > > > Thanks. > > >=20 > > >=20 > > Michael, > > It works fine for me. >=20 > I send some patches to Gary Palmer (the port maintainer of amanda) > some time ago, but didn't receive a response. >=20 > I found out, that one has to fiddle around much with amanda. >=20 > The docu doesn't fit FreeBSD paths and devices much and such things. > Additionally I found out, that some paths could be configured more > suitable to BSD 4.4 paths. >=20 > Gary, since the topic comes up here again, could you please tell > me, if you got my patches and if you think that it's worth, to > include some or all of them ?! >=20 > BTW, I didn't get amanda working out of the box as well. Could the > port be changed, that the amount of work, to get it up and running > decreases to a small amount of work ? >=20 > It would be fine, Gary, if you could check and perhaps merge my > changes, since you are certainly someone, who got it running and > who could deceide faster than I if the patches are ok, or if I have > broken something. Although I think not. >=20 > Don't ask me, which error messages I got. I started to patch the > amanda port, because it wasn=C4t working out of the box. >=20 > Just for the case, that someone want's to see, what I 'hacked' in > this port, here again the diffs. >=20 > =09Andreas /// >=20 > *** man/amadmin.8.orig=09Wed Sep 25 11:06:05 1996 > - --- man/amadmin.8=09Wed Sep 25 11:07:14 1996 > *************** > *** 23,29 **** > .I hostname, > if no disks are specified. The > .I disks > ! parameters are prefixes, for example "sd0" will match disks "sd0a" and = "sd0g". > =20 > .HP 5 > .B force > - --- 23,30 ---- > .I hostname, > if no disks are specified. The > .I disks > ! parameters are prefixes, for example "sd0" will match disks "sd0a" and= =20 > ! "sd0s1g". You can also use mountpoints instead of disks, it's easier to remember. > =20 > .HP 5 > .B force > *** man/amanda.8.orig=09Wed Sep 25 11:11:28 1996 > - --- man/amanda.8=09Wed Sep 25 11:20:32 1996 > *************** > *** 135,153 **** > =20 > All the files are stored in a > .I config > ! directory under /etc/amanda. Often a single site will have more than > ! one configuration; these configurations are named by the directories > that their config files are in. For example, a site might have a > .I normal > configuration for every-day backups, and a > .I archive > configuration for 6-month full archival backups. The config files for > ! these two would be stored under /etc/amanda/normal and > ! /etc/amanda/archive, respectively. > =20 > All log and database files generated by Amanda go in corresponding > ! directories under /usr/adm/amanda. In our example, the logs would go > ! in /usr/adm/amanda/normal and /usr/adm/amanda/archive. > =20 > .SH CONFIG FILE PARAMETERS > =20 > - --- 135,153 ---- > =20 > All the files are stored in a > .I config > ! directory under /usr/local/etc/amanda. Often a single site will have mo= re > ! than one configuration; these configurations are named by the directori= es > that their config files are in. For example, a site might have a > .I normal > configuration for every-day backups, and a > .I archive > configuration for 6-month full archival backups. The config files for > ! these two would be stored under /usr/local/etc/amanda/normal and > ! /usr/local/etc/amanda/archive, respectively. > =20 > All log and database files generated by Amanda go in corresponding > ! directories under /var/log/amanda. In our example, the logs would go > ! in /var/log/amanda/normal and /var/log/amanda/archive. > =20 > .SH CONFIG FILE PARAMETERS > =20 > *************** > *** 210,216 **** > .TP > .B diskdir > Default: > ! .I /dumps/amanda. > The path name of the holding disk. Backups are deposited under this > directory when no tape is available. > =20 > - --- 210,216 ---- > .TP > .B diskdir > Default: > ! .I /var/spool/amdumps. > The path name of the holding disk. Backups are deposited under this > directory when no tape is available. > =20 > *************** > *** 223,229 **** > .TP > .B tapedev > Default: > ! .I /dev/rmt8. > The path name of the tape device file. > =20 > .TP > - --- 223,229 ---- > .TP > .B tapedev > Default: > ! .I /dev/rst0. > The path name of the tape device file. > =20 > .TP > *************** > *** 312,324 **** > .TP > .B infofile > Default: > ! .I /usr/adm/amanda/curinfo. > The file name for the historical information database file. > =20 > .TP > .B logfile > Default: > ! .I /usr/adm/amanda/log > The file name for the nightly log file. > =20 > .TP > - --- 312,324 ---- > .TP > .B infofile > Default: > ! .I /var/log/amanda/curinfo. > The file name for the historical information database file. > =20 > .TP > .B logfile > Default: > ! .I /var/log/amanda/log > The file name for the nightly log file. > =20 > .TP > *** man/amcheck.8.orig=09Wed Sep 25 11:21:05 1996 > - --- man/amcheck.8=09Wed Sep 25 11:22:18 1996 > *************** > *** 41,47 **** > If the -m option is given, nothing is printed, but mail is sent to the > "mailto" address (as specified by the > .I amanda.conf > ! file in /etc/amanda/\fIconfig\fR) if any errors are detected. =20 > .PP > See the > .IR amanda(8) > - --- 41,47 ---- > If the -m option is given, nothing is printed, but mail is sent to the > "mailto" address (as specified by the > .I amanda.conf > ! file in /usr/local/etc/amanda/\fIconfig\fR) if any errors are detected.= =20 > .PP > See the > .IR amanda(8) > *************** > *** 71,77 **** > .TP > % amcheck -m csd > If the line "mailto csd-amanda" is in > ! /etc/amanda/csd/amanda.conf, mail will be sent to csd-amanda > if the tape check returns an error. > =20 > .SH AUTHOR > - --- 71,77 ---- > .TP > % amcheck -m csd > If the line "mailto csd-amanda" is in > ! /usr/local/etc/amanda/csd/amanda.conf, mail will be sent to csd-amanda > if the tape check returns an error. > =20 > .SH AUTHOR > *** man/amcleanup.8.orig=09Wed Sep 25 11:23:08 1996 > - --- man/amcleanup.8=09Wed Sep 25 11:24:13 1996 > *************** > *** 31,37 **** > =20 > ..PP > .nf > ! if [ -s /usr/adm/amanda/csd/amanda.log ] > then > =09/usr/local/sbin/amcleanup csd > fi > - --- 31,37 ---- > =20 > .PP > .nf > ! if [ -s /var/log/amanda/csd/amanda.log ] > then > =09/usr/local/sbin/amcleanup csd > fi > *** man/amdump.8.orig=09Wed Sep 25 11:24:26 1996 > - --- man/amdump.8=09Wed Sep 25 11:25:02 1996 > *************** > *** 10,16 **** > =20 > .B Amdump > switches to the appropriate Amanda configuration directory, usually > ! /etc/amanda/\fIconfig\fR, then attempts to back up every disk as > specified by the=20 > .I amanda.conf > file. > - --- 10,16 ---- > =20 > .B Amdump > switches to the appropriate Amanda configuration directory, usually > ! /usr/local/etc/amanda/\fIconfig\fR, then attempts to back up every disk= as > specified by the=20 > .I amanda.conf > file. > *************** > *** 21,27 **** > .IR amanda(8) > man page for more details about Amanda. > =20 > ! If the file /etc/amanda/\fIconfig\fR/hold exists on startup, > .B amdump > will wait until the file is removed before proceeding with the night's = backups. > This allows the operators to delay the scheduled backups when the > - --- 21,27 ---- > .IR amanda(8) > man page for more details about Amanda. > =20 > ! If the file /usr/local/etc/amanda/\fIconfig\fR/hold exists on startup, > .B amdump > will wait until the file is removed before proceeding with the night's = backups. > This allows the operators to delay the scheduled backups when the > *** man/amflush.8.orig=09Wed Sep 25 11:25:40 1996 > - --- man/amflush.8=09Wed Sep 25 11:25:59 1996 > *************** > *** 22,28 **** > .B Amflush > will look in the holding disk specified by the > .I amanda.conf > ! file in /etc/amanda/\fIconfig\fR > for any non-empty Amanda work directories. It then prompts the > operator to select the correct directory. The work directories on the > holding disk are named by the date at the time > - --- 22,28 ---- > .B Amflush > will look in the holding disk specified by the > .I amanda.conf > ! file in /usr/local/etc/amanda/\fIconfig\fR > for any non-empty Amanda work directories. It then prompts the > operator to select the correct directory. The work directories on the > holding disk are named by the date at the time > *** man/amlabel.8.orig=09Wed Sep 25 11:26:11 1996 > - --- man/amlabel.8=09Wed Sep 25 11:26:58 1996 > *************** > *** 11,17 **** > .B Amlabel > writes an Amanda label on the tape in the tape drive specified by the > .I amanda.conf > ! file in /etc/amanda/\fIconfig\fR. The > .I label > can be any string that does not contain whitespace, and that matches th= e > .I amanda.conf=20 > - --- 11,17 ---- > .B Amlabel > writes an Amanda label on the tape in the tape drive specified by the > .I amanda.conf > ! file in /usr/local/etc/amanda/\fIconfig\fR. The > .I label > can be any string that does not contain whitespace, and that matches th= e > .I amanda.conf=20 > *************** > *** 25,33 **** > .SH EXAMPLE > .TP > % amlabel csd VOL1 > ! If the line "tapedev /dev/tape/1n" is in > ! /etc/amanda/csd/amanda.conf, an Amanda label with the name "VOL1" is > ! written on the /dev/tape/1n device. > =20 > .SH AUTHOR > James da Silva <jds@cs.umd.edu> > - --- 25,33 ---- > .SH EXAMPLE > .TP > % amlabel csd VOL1 > ! If the line "tapedev /dev/nrst0" is in > ! /usr/local/etc/amanda/csd/amanda.conf, an Amanda label with the name "V= OL1" is > ! written on the /dev/nrst0 device. > =20 > .SH AUTHOR > James da Silva <jds@cs.umd.edu> > *** man/amrestore.8.orig=09Wed Sep 25 11:27:27 1996 > - --- man/amrestore.8=09Wed Sep 25 11:33:27 1996 > *************** > *** 38,48 **** > may be regular expressions that can match many dumps. For example, if = a > .I diskname > of > ! .B rz[23]a > is given, it would match backups of disks > ! .B rz2a> and > ! .B rz3a. > .PP > Matching backup files from the tape are normally extracted to files in = the current directory named > .I hostname.diskname.datestamp.dumplevel. > - --- 38,48 ---- > may be regular expressions that can match many dumps. For example, if = a > .I diskname > of > ! .B rsd[01]a > is given, it would match backups of disks > ! .B rsd0a > and > ! .B rsd1a. > .PP > Matching backup files from the tape are normally extracted to files in = the current directory named > .I hostname.diskname.datestamp.dumplevel. > *************** > *** 98,119 **** > =20 > .SH EXAMPLES > .TP > ! % amrestore -p /dev/nrmt9 seine rz3g | restore ivbf 2 - > ! This does an interactive restore of disk /dev/rz3g from host seine, to > restore particular files. Note the use of the "b 2" option to > restore, which means read in units of 2 512-byte blocks (=3D=3D 1 Kbyte= ) > at a time. This keeps restore from complaining about short reads. > =20 > .TP > ! % amrestore /dev/nrmt9 seine > This extracts all backup files for host seine. This is the usual way t= o > extract all the data for a host after a disk crash. If the datestamp > for the backups is 19910125 and seine has level 0 backups of filesystem= s > ! rz1a and rz1g on the tape; the following files will be > created in the current directory: > ! =09seine.rz1a.19910125.0 > .br > ! =09seine.rz1g.19910125.0 > =20 > .SH AUTHOR > James da Silva <jds@cs.umd.edu> > - --- 98,119 ---- > =20 > .SH EXAMPLES > .TP > ! % amrestore -p /dev/nrst0 seine rsd0s3g | restore ivbf 2 - > ! This does an interactive restore of disk /dev/rsd0s3g from host seine, = to > restore particular files. Note the use of the "b 2" option to > restore, which means read in units of 2 512-byte blocks (=3D=3D 1 Kbyte= ) > at a time. This keeps restore from complaining about short reads. > =20 > .TP > ! % amrestore /dev/nrst0 seine > This extracts all backup files for host seine. This is the usual way t= o > extract all the data for a host after a disk crash. If the datestamp > for the backups is 19910125 and seine has level 0 backups of filesystem= s > ! rsd0a and rsds3g on the tape; the following files will be > created in the current directory: > ! =09seine.rsd0a.19910125.0 > .br > ! =09seine.rsds3g.19910125.0 > =20 > .SH AUTHOR > James da Silva <jds@cs.umd.edu> > *** common-src/conffile.c.orig=09Wed Sep 25 13:48:43 1996 > - --- common-src/conffile.c=09Wed Sep 25 13:51:24 1996 > *************** > *** 205,220 **** > /* defaults for exported variables */ > =20 > init_string(&conf_org.s, "YOUR ORG"); > ! init_string(&conf_mailto.s, "operators"); > ! init_string(&conf_dumpuser.s, "bin"); > ! init_string(&conf_tapedev.s, "/dev/rmt8"); > init_string(&conf_tpchanger.s, ""); > init_string(&conf_labelstr.s, ".*"); > init_string(&conf_tapelist.s, "tapelist"); > ! init_string(&conf_infofile.s, "/usr/adm/amanda/curinfo"); > ! init_string(&conf_logfile.s, "/usr/adm/amanda/log"); > init_string(&conf_diskfile.s, "disklist"); > ! init_string(&conf_diskdir.s, "/dumps/amanda"); > init_string(&tapetype_id.s, "EXABYTE"); > =20 > conf_dumpcycle.i=09=3D 10; > - --- 205,220 ---- > /* defaults for exported variables */ > =20 > init_string(&conf_org.s, "YOUR ORG"); > ! init_string(&conf_mailto.s, "dumper"); > ! init_string(&conf_dumpuser.s, "root"); > ! init_string(&conf_tapedev.s, "/dev/rst0"); > init_string(&conf_tpchanger.s, ""); > init_string(&conf_labelstr.s, ".*"); > init_string(&conf_tapelist.s, "tapelist"); > ! init_string(&conf_infofile.s, "/var/log/amanda/curinfo"); > ! init_string(&conf_logfile.s, "/var/log/amanda/log"); > init_string(&conf_diskfile.s, "disklist"); > ! init_string(&conf_diskdir.s, "/var/spool/amdumps"); > init_string(&tapetype_id.s, "EXABYTE"); > =20 > conf_dumpcycle.i=09=3D 10; The logs of amanda take rather much space, and also the holding=20 disk must be big enough, don't place it into /var/spool/amdumps > *** man/amanda.8.orig=09Wed Sep 25 14:42:23 1996 > - --- man/amanda.8=09Wed Sep 25 14:44:25 1996 > *************** > *** 168,175 **** > .TP > .B mailto > Default: > ! .I operators. > ! The list of recipients for the nightly mail report. > =20 > .TP > .B mincycle > - --- 168,175 ---- > .TP > .B mailto > Default: > ! .I dumper. > ! The list of dump operators that get the nightly mail report (see /etc/a= liases). > =20 > .TP > .B mincycle >=20 > - -- > andreas@klemm.gtn.com /\/\___ Wiechers & Partner > Datentechnik GmbH > Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@= wup.de > pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered = by <<< > ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeB= SD <<< >=20 Regards, --Yuri.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.961130135848.11593A-100000>