Re: [Amanda-users] backup analysis
On Mon, Mar 14, 2011 at 06:17:41PM -0700, upengan78 wrote: Couple of questions: ... Does amoverview work on weeklyfull but not on monthlyfull? no amoverview doesn't work on any of above. Always E. The amoverview output you show indicated errors for 3 weeks of daily runs. What did the associated daily reports show? Were there errors? No errors in daily reports. Daily report was OK for all DLEs. Sometimes it was STRANGE when part was retried successfully. No, that should not cause problems. There were some problems with amoverview when the C source was recoded to perl. But those problems were accompanied by many error messages about uninitialized variables. I assume you are using a recent release of amanda? Jon -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Status 'OK FAIL Missing part' in amadmin find - Bug is still in 3.2.2
Hi Jean-Louis Martineau wrote Mon, 03 Jan 2011 07:15:43 -0800: your patch fixed it for 3.2.0. But wasn't it applied to the sources of 3.2.1? This version is still having the bug The patch was committed after the 3.2.1 release. Are you sure, that the patch was really committed? *3.2.2* is still having this issue: $ amadmin KDD find | grep OK FAIL Missing part| head -3 2011-02-19 21:00:02 ... /home 4 KDD117 103 1/3 OK FAIL Missing part 2011-02-23 21:00:02 ... /home 6 KDD140 101 1/3 OK FAIL Missing part 2011-02-24 21:00:02 ... /home 7 KDD14787 1/2 OK FAIL Missing part 2011-03-01 21:00:01 ... /home 2 KDD172 105 1/3 OK FAIL Missing part 2011-03-08 21:00:01 ... /home 4 KDD03194 1/2 OK FAIL Missing part Also I saw that the amount of this messages changes on what I query: $ amadmin KDD find | grep OK FAIL Missing part | wc -l 6 $ amadmin KDD find genome | grep OK FAIL Missing part | wc -l 346 $ amadmin KDD version build: VERSION=Amanda-3.2.2 Regards, Marc -- Marc Muehlfeld (IT-Leiter) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780 http://www.medizinische-genetik.de
monthly archive config
I'd really appreciate it if someone can just go over what I'm doing below, so I don't miss out anything silly. I'm using Amanda version 2.6.0p1, and finally cannot effectively make full backups each night anymore, so I'm looking into using Amanda the 'classic' way and to set up another config for monthly full backups. If I recall correctly, then something like this should work for the monthly backup runs. I simply made a copy of my daily config and am just modifying the existing files, e.g. amanda.conf: dumpcycle 0 to make full backups on each run runspercycle 1 not really sure about this because dumpcycle is 0?? tapecycle 12 tapes one tape for each month of the year, but will actually use 15 in the set up tapes for the odd amflush, if necessary index yes to generate the catalogue for use by amrecover record noapparently: This is normally enabled for daily backups and turned off for periodic archival runs. (Amanda wiki) infofile /etc/amanda/monthly/curinfo logdir /etc/amanda/monthly indexdir /etc/amanda/monthly/index Other than that, because I made a copy of the daily config, I've cleaned out the copied config folder's index and log files, and tapelist file. Does that look sensible? Thanks. Johan
[Amanda-users] backup analysis
I assume you are using a recent release of amanda? I am sure this is not latest because I went with OpenCSW repository available for solaris platform instead of compiling amanda package myself from source. 3.1.1 is the version of amanda on this system, as shown below. /opt/csw/bin/pkgutil -a | grep amanda gpg: Signature made Mon Mar 14 20:32:35 2011 CDT using DSA key ID E12E9D2F gpg: Good signature from CSW Distribution Manager d...@opencsw.org amanda CSWamanda3.1.1,REV=2010.07.20 8.2 MB Thanks for continuing the discussion and help! +-- |This was sent by upendra.gan...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Status 'OK FAIL Missing part' in amadmin find - Bug is still in 3.2.2
Marc,
It is not the same bug I fixed.
Can you try this path?
Jean-Louis
Marc Muehlfeld wrote:
Hi
Jean-Louis Martineau wrote Mon, 03 Jan 2011 07:15:43 -0800:
your patch fixed it for 3.2.0. But wasn't it applied to the sources of
3.2.1? This version is still having the bug
The patch was committed after the 3.2.1 release.
Are you sure, that the patch was really committed? *3.2.2* is still
having this issue:
$ amadmin KDD find | grep OK FAIL Missing part| head -3
2011-02-19 21:00:02 ... /home 4 KDD117 103 1/3 OK FAIL Missing part
2011-02-23 21:00:02 ... /home 6 KDD140 101 1/3 OK FAIL Missing part
2011-02-24 21:00:02 ... /home 7 KDD14787 1/2 OK FAIL Missing part
2011-03-01 21:00:01 ... /home 2 KDD172 105 1/3 OK FAIL Missing part
2011-03-08 21:00:01 ... /home 4 KDD03194 1/2 OK FAIL Missing part
Also I saw that the amount of this messages changes on what I query:
$ amadmin KDD find | grep OK FAIL Missing part | wc -l
6
$ amadmin KDD find genome | grep OK FAIL Missing part | wc -l
346
$ amadmin KDD version
build: VERSION=Amanda-3.2.2
Regards,
Marc
diff --git a/server-src/find.c b/server-src/find.c
index b387a9d..cfe33d6 100644
--- a/server-src/find.c
+++ b/server-src/find.c
@@ -1012,6 +1012,17 @@ search_logfile(
host, disk, date, level);
find_result_t *new_output_find = g_new0(find_result_t, 1);
part_find = g_hash_table_lookup(part_by_dle, key);
+ maxparts = partnum;
+ if (maxparts totalparts)
+ maxparts = totalparts;
+ for (a_part_find = part_find;
+ a_part_find;
+ a_part_find = a_part_find-next) {
+ if (maxparts a_part_find-partnum)
+ maxparts = a_part_find-partnum;
+ if (maxparts a_part_find-totalparts)
+ maxparts = a_part_find-totalparts;
+ }
new_output_find-timestamp = stralloc(date);
new_output_find-write_timestamp = stralloc(datestamp);
new_output_find-hostname=stralloc(host);
[Amanda-users] backup analysis
Could it be because of trying to fill tapes(vtapes in my case) to 100%? following is configured in monthlyfull and weeklyfull amanda configuration, flush-threshold-dumped100 flush-threshold-scheduled 100 taperflush100 autoflush yes +-- |This was sent by upendra.gan...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: [Amanda-users] backup analysis
On Tue, Mar 15, 2011 at 07:23:38AM -0700, upengan78 wrote: Could it be because of trying to fill tapes(vtapes in my case) to 100%? following is configured in monthlyfull and weeklyfull amanda configuration, flush-threshold-dumped100 flush-threshold-scheduled 100 taperflush100 autoflush yes I wouldn't expect those settings to affect amoverview. However, I've not played with them, leaving the first three at the default 0. I do set autoflush to yes. jl -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Status 'OK FAIL Missing part' in amadmin find - Bug is still in 3.2.2
Am 15.03.2011 15:06, schrieb Jean-Louis Martineau: Can you try this path? If the find contains a hostname, it seems fixed now (before it were 346): $ amadmin KDD find genome | grep OK FAIL Missing part | wc -l 0 But without hostname still 6 are found $ amadmin KDD find | grep OK FAIL Missing part | wc -l 6 $ amadmin KDD find | grep OK FAIL Missing part 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 1 35/40 OK FAIL Missing part 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 2 36/40 OK FAIL Missing part 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 3 37/40 OK FAIL Missing part 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 4 38/40 OK FAIL Missing part 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 5 39/40 OK FAIL Missing part 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 6 40/40 OK FAIL Missing part -- Marc Muehlfeld (IT-Leiter) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780 http://www.medizinische-genetik.de
Re: Status 'OK FAIL Missing part' in amadmin find - Bug is still in 3.2.2
Am 15.03.2011 16:11, schrieb Jean-Louis Martineau: Do that dle is on the genome host? No. It's a windows host with name lysine that is backuped via the linux host nucleus. 2011-02-11 21:00:01 ... //lysine/backup$ 1 KDD075 1 35/40 OK FAIL Missing part Do the part 1 to 34 are still available? The volume might already been overwritten by new dump. You are right. The first 34 parts are already overwritten. Then your patch fixes the whole issue. Thanks. Regards, Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Labormedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780 http://www.medizinische-genetik.de
NOTES: big estimate
My daily reports regularly contain lines like the following (commas added): NOTES: big estimate: lastchance Cdrive 1 est: 6,944,416Mout 975,940M big estimate: mumsxp Cdrive 1 est: 3,303,904Mout 288,480M big estimate: vostxp Cdrive 1 est: 1,902,400Mout 390,089M big estimate: vost Home 0 est: 17,729,952Mout 12,318,804M The first 3 are Windows partitions and are using ZWC on the clients. They always show up big. Others show up sporadically, but I can assure you my laptop vost does not have a 17 terrabyte drive :) Obviously these are KB, not MB as the units suffix suggests. But even adjusting for that, the estimates are way off. For example, 6.9GB reported in the above compared with 1.4GB dumped in the Summary below. DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s --- - lastchance Cdrive 1147095365 14:00 1162 0:45 21688 mumsxp Cdrive 1 66828242 57:34 84 0:12 24040 vostxp Cdrive 1 880381439:28686 0:17 22946 vost Home0 21726 1203055 105:22 1948 9:14 22236 Is anyone else seeing this? Jon -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: NOTES: big estimate
Jon, We also see 'big estimate' output for some partitions. I assumed some sort of bounding but never looked into it any further. Reminds me of the O (big-oh) and omega we'd compute for algorithms back in computer science class [upper and lower bounds limits for algorithms]. Something that I suspect is missing from more current programming classes. Brian On Tue, Mar 15, 2011 at 12:44:19PM -0400, Jon LaBadie wrote: My daily reports regularly contain lines like the following (commas added): NOTES: big estimate: lastchance Cdrive 1 est: 6,944,416Mout 975,940M big estimate: mumsxp Cdrive 1 est: 3,303,904Mout 288,480M big estimate: vostxp Cdrive 1 est: 1,902,400Mout 390,089M big estimate: vost Home 0 est: 17,729,952Mout 12,318,804M The first 3 are Windows partitions and are using ZWC on the clients. They always show up big. Others show up sporadically, but I can assure you my laptop vost does not have a 17 terrabyte drive :) Obviously these are KB, not MB as the units suffix suggests. But even adjusting for that, the estimates are way off. For example, 6.9GB reported in the above compared with 1.4GB dumped in the Summary below. DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s --- - lastchance Cdrive 1147095365 14:00 1162 0:45 21688 mumsxp Cdrive 1 66828242 57:34 84 0:12 24040 vostxp Cdrive 1 880381439:28686 0:17 22946 vost Home0 21726 1203055 105:22 1948 9:14 22236 Is anyone else seeing this? Jon -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive(703) 787-0884 Reston, VA 20194(703) 787-0922 (fax) --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
