Re: Zmanda Windows Client ZIP files
Hello Markus, We have mostly win clients on Amanda for several years now. What you describe should work fine. I'll double check my procedure later this morning and post exactly how it goes. Chris -Sent from my droid On Nov 13, 2013 5:14 PM, Markus Iturriaga Woelfel mitur...@eecs.utk.edu wrote: Hi fellow Amanda Users - I've been trying to figure out how to read the ZIP files generated by the ZManda Windows Client on our Red Hat 6 Amanda server. The information I can find on the mailing list is somewhat conflicting. We've been using Amanda for years to back up Linux/Unix systems but I'd like to add a few Windows computers to our list of clients. Here is my problem: 1) I can use amfetchdump to get what appears to be a zip file: # file staff15.zip staff15.zip: Zip archive data, at least v2.0 to extract 2) The unzip command (which has ZIP64 support) does not recognize this as a proper file: # unzip -l staff15.zip Archive: staff15.zip warning [staff15.zip]: 12551715855 extra bytes at beginning or within zipfile (attempting to process anyway) error [staff15.zip]: start of central directory not found; zipfile corrupt. (please check that you have transferred or created the zipfile in the appropriate BINARY mode and that you have compiled UnZip properly) I have also tried 7za (7-zip for Linux) to no avail. 3) Copying the archive to Windows, the Explorer built-in zip mechanisms just hang indefinitely. 7Zip for Windows complains that it cannot open the file as an archive. I should say that there were no errors reported when this backup was taken. Some of the posts I've seen say try PKZip but PKZip is not free software and that defeats the purpose of us using Amanda. I downloaded the evaluation version of PKZip and it could indeed see the contents of the archive and extract files. So, my questions is - is there no free/open source software that can read and extract from the zip files generated by the Zmanda client for Windows? Can I switch the compression to server if all else fails? Thanks as always, Markus --- Markus A. Iturriaga Woelfel, IT Administrator Department of Electrical Engineering and Computer Science University of Tennessee Min H. Kao Building, Suite 424 / 1520 Middle Drive Knoxville, TN 37996-2250 mitur...@eecs.utk.edu / (865) 974-3837 http://twitter.com/UTKEECSIT
Re: ZWC on W2008-SP2 fails with Connection timed out
On Mon, Nov 5, 2012 at 7:19 PM, Neil Carter nltra...@gmail.com wrote: Well, after your eMail I checked and the firewall was enabled, with exceptions. I turned it completely off, no difference. So, I've uninstalled and re-installed, same exact situation. I've not been able to find much in the way of instructions for the ZWC client. Does it automatically register with the server? Here is the wiki page in case you've not seen it: http://wiki.zmanda.com/index.php/Zmanda_Windows_Client There is no registration as such. You give the server perms during the installation of ZWC. ZWC could stand a number of improvements. Unfortunately, ZWC is closed source. An open source version is possible, just not enough time, etc. Kind Regards, Chris
Re: ZWC on W2008-SP2 fails with Connection timed out
On Mon, Nov 5, 2012 at 12:27 PM, Neil Carter bigfoot...@gmail.com wrote: This box used to backup fine, along with all of the other servers in my disklist. Then, in comes 'Big Brother' and both changes the root password and adds the server to a domain. This was done with a couple of other windows boxes in my diskllist as well, they still backup fine. Did Big Brother turn on the FW on that machine when he did the other work? Just a thought. Kind Regards, Chris
Taper died
I woke up this morning to the following in my last evening's backup report: FAILURE DUMP SUMMARY: taper: FATAL TypeError in method 'log_add', argument 2 of type 'char *' A look a the log shows what appears to be an mtx error the taper or changer does not know about. This appears to cause the taper to call log_add with an integer or undef as the second arg which, in turn, causes the taper to go south as we say. I've attached the log for reference. I'm fairly sure this is a fringe case, but the taper should still handle it gracefully imho. Kind Regards, Chris taper.20120605230007.debug Description: Binary data
Re: Taper died
On Wed, Jun 6, 2012 at 11:59 AM, Jean-Louis Martineau martin...@zmanda.comwrote: Chris, Apply the attached patch, this bug is already fixed in 3.3.1 Thanks Jean-Louis! Jean-Louis On 06/06/2012 11:13 AM, Chris Nighswonger wrote: I woke up this morning to the following in my last evening's backup report: FAILURE DUMP SUMMARY: taper: FATAL TypeError in method 'log_add', argument 2 of type 'char *' A look a the log shows what appears to be an mtx error the taper or changer does not know about. This appears to cause the taper to call log_add with an integer or undef as the second arg which, in turn, causes the taper to go south as we say. I've attached the log for reference. I'm fairly sure this is a fringe case, but the taper should still handle it gracefully imho. Kind Regards, Chris
Re: New problem, no access to ubuntu clients
Hi Gene, 2012/4/6 gene heskett ghesk...@wdtv.com On Friday, April 06, 2012 01:13:17 AM Nathan Stratton Treadway did opine: On Thu, Apr 05, 2012 at 23:37:51 -0400, Nathan Stratton Treadway wrote: $ netstat -a | grep amanda on those machines... Does the output from that command on 192.168.71.3 look any different from that on your other clients? p.s. on my Lucid boxes, the Amanda client is invoked from inetd, so if netstat doesn't show the ports open then the issue is probably that inetd isn't running, or the amanda entry in /etc/inetd.conf has been changed. But I don't know off hand why both your machines would have problems with inet at the same time. (Obviously if you are using xinetd or whatever, check that instead.) Something must have pulled in xinetd, which removed inetd on the shop box, so I'm fixing that back to inetd since the .conf still exists. Apparently no conflict. Since I know inetd was working until the 3rd, I have reinstalled it on both machines. However amanda is running on this box ATM, so I can't check with amcheck until that has finished. If this doesn't do it, I'm back to square one. Have you tried $ amservice clienthostname yourauth noop /dev/null to see if you get an option string back? (per http://wiki.zmanda.com/index.php/Selfcheck_request_failed) I've had similar experiences with clients suddenly disappearing and this has helped me to troubleshoot. HTH. Kind Regards, Chris
Re: Windows - ZWC Encryption
On Tue, Apr 3, 2012 at 12:33 PM, April Rosenberg apr...@yelp.com wrote: Thank you, I am. I will look at upgrading. This seems to be the motive behind not releasing the code for the Win32 client under some OSS license. *From:* prashant.zma...@gmail.com [mailto:prashant.zma...@gmail.com] *On Behalf Of *Prashant Joshi *Sent:* Tuesday, April 03, 2012 1:00 AM *To:* April Rosenberg *Cc:* amanda-users@amanda.org *Subject:* Re: Windows - ZWC Encryption Hi April, I am assuming that you are using a Community version of ZWC. Encryption is not supported in the Community version of ZWC. It is only supported in the Enterprise version. This is the reason why ZWCService is crashing when a request for encrypted backup is sent by the Amanda server. In a nut-shell, ZWC is simply zipping a copy of an MS volume shadow copy of the requested DLE and piping it back to the Amanda server. It would be nice to see someone in the community with some VB expertise whip up an open source equivalent. It also looks like ZWC is using PKZip's library. PKZip supports encryption of zip'd files. This could probably all be replaced with an open source zip library like 7-zip which also supports encryption. Nothing against Zamanda here, however, it just goes against open source principles to cripple open source software in order to hold the corner on the market. Kind Regards, Chris
Re: Fit algorithm revisited
FWIW here is info from my 3.3.0 I have a large DLE which seems to end up lumped in as well. amandabackup@scriptor:/etc/amanda/campus$ amadmin campus balance due-date #fsorig kB out kB balance -- 3/23 Fri2 301391927 239048829 +129.4% 3/26 Mon 25 86797389 67410086-35.3% 3/27 Tue0 0 0 --- 3/28 Wed4 323587432 214586650 +105.9% 3/29 Thu0 0 0 --- -- TOTAL 31 711776748 521045565 104209113 (estimated 5 runs per dumpcycle) (2 filesystems overdue. The most being overdue 12 days.) amandabackup@scriptor:/etc/amanda/campus$ amadmin campus balance due-date #fsorig kB out kB balance -- 3/27 Tue0 0 0 --- 3/28 Wed1 155896462 127850688+19.1% 3/29 Thu0 0 0 --- 3/30 Fri2 317983843 254166593 +136.7% 3/31 Sat0 0 0 --- 4/01 Sun 16 58918273 49239791-54.1% 4/02 Mon 12 196858600 105678053 -1.6% -- TOTAL 31 729657178 536935125 107387025 (estimated 5 runs per dumpcycle) amandabackup@scriptor:/etc/amanda/campus$ On Tue, Mar 27, 2012 at 1:44 PM, Jean-Louis Martineau martin...@zmanda.comwrote: Bernhard, Use the attached patch for 3.3 Let me know if it improve the balancing, or if some dle get promoted too often. Jean-Louis On 03/27/2012 01:27 PM, Bernhard Erdmann wrote: Hi Jean-Louis, will your patch apply to Amanda version 3.3.1? For several months I have an ongoing similar problem with one Amanda configuration. One big DLE (120 GB), two DLEs at 75 and 50 GB and ca. 35 DLEs at 20-35 GB each. Amanda 3.3.1 does not move the biggest DLE to a day when it only full-dumps this DLE or shuffles the smaller DLEs around so that only the biggest DLE is full-dumped at a particular day. Instead, always the second medium-sized DLE (50 GB) is full-dumped at the same day as the biggest DLE. This configuration has been stable for more than half a year, i.e. 4-5 dumpcycles have passed. $ amadmin be balance due-date #fsorig kB out kB balance --** 3/27 Tue2 50952368 50952368 -9.5% 3/28 Wed2 49318040 49318040-12.4% 3/29 Thu1 73811810 73811810+31.1% 3/30 Fri2 40733720 40733720-27.6% 3/31 Sat2 55579040 55579040 -1.3% 4/01 Sun2 180292110 180292110 +220.3% 4/02 Mon1 44029300 44029300-21.8% 4/03 Tue2 67804280 67804280+20.4% 4/04 Wed2 48122090 48122090-14.5% 4/05 Thu2 55214820 55214820 -1.9% 4/06 Fri2 58847690 58847690 +4.5% 4/07 Sat2 47259350 47259350-16.1% 4/08 Sun1 39843350 39843350-29.2% 4/09 Mon1 41888900 41888900-25.6% 4/10 Tue2 58437479 58437479 +3.8% 4/11 Wed2 55687590 55687590 -1.1% 4/12 Thu0 0 0 --- 4/13 Fri2 56478270 56478270 +0.3% 4/14 Sat2 61045722 58645042 +4.2% 4/15 Sun1 44408210 44408210-21.1% 4/16 Mon2 56126655 51227393 -9.0% 4/17 Tue3 65676196 53594814 -4.8% 4/18 Wed2 64966230 64966230+15.4% 4/19 Thu4 81805259 55246746 -1.9% 4/20 Fri 10 67815815 54983817 -2.3% --** TOTAL 54 1466144294 1407372459 56294898 (estimated 25 runs per dumpcycle) Quoting Jean-Louis Martineau martin...@zmanda.com on Fri, 23 Mar 2012 08:18:51 -0400: Hi Gene, Can you try the attached patch? (it is lightly tested and uncommitted). Jean-Louis On 03/21/2012 12:48 PM, gene heskett wrote: Greetings from the canary; One of the things that constantly get under my skin is the apparent lack of amanda's ability to juggle backup order in order to balance the sizes of the backups from night to night. I have fussed about this before without arriving at a solution, but it seems to me amanda has gone dumb with all the re-writes in the last 3 or 5 years. I am seemingly locked into a cadence of 4 nights worth of doing about 15Gb a night, followed by the night when it does the largest 5 or so DLE's all on the same run, which makes that run be 45+Gb. The biggest one is /usr/movies, at a bit over 16Gb. If I could get that one separated from the other larger ones, it would help. Sure, I could comment that DLE out for a day or 2. Or I could force a level 0 on Friday. The point is that 5 years ago, amanda would do this all by itself and it is no longer even making the effort for at least the last 2 or 3 years. Here is the output of amadmin Daily balance: due-date #fsorig MB out MB balance
Windows Vista/7
Hi all, Does anybody have a disklist used for backing up Windows Vista/7 user data they would be willing to share in a sanitized form? From my little bit of reading, it appears that the storage of user data changed quite a bit from XP to Vista to 7. What I am looking for specifically is a disklist which will ensure the ability to completely restore a user's environment and data. Incidentally, this might make for a nice section of the wiki. Kind Regards, Chris
Robot Woes
Having exhausted all other resources, I'm turning to the list... I have just installed a Superloader 3 with a DLT-V4 drive on my Amanda backup system. This drive replaces a non-robotic DLT-V4 which failed recently. I loaded up my original 12 tapes along with three fresh tapes and a cleaning tape (16 slots). (It turns out I loaded the two cartridges backwards, but that is irrelevant to my problem.) The next tape in sequence when the original drive failed was 12 (CAMPUS-12). The cleaning tape is in slot 8 and is not listed in my changer definition. I ran a quick amcheck and amanda locate tape 12 (slot 4). I then ran an amflush to purge the holding disk (quite full by this time). Everything went fine. At this point I ran another amcheck to be sure things were setup for the next run and the chunks began to fly. Amanda began searching for tape 1 (CAMPUS-01) which is in slot 9. It found the tape, but complained about an error. i pulled the cartridge and checked the physical state of the tape; everything looked fine. So I reloaded the cartridge and executed amtape show to get a look from amanda's prospective. Below is what amtape show says. Slots 5-7 are new, unlabeled tapes, so the errors are expected... I assume. However, the mtx error is troubling. This same error shows up if I do 'mtx -f /dev/sg4 load 9' and then do 'amcheck -t config' or any variation thereof. 'mtx -f /dev/sg4 load 9' followed by 'mtx -f /dev/sg4 status' shows the tape loads up fine. I was also able to 'amrmtape' and 'amlabel' this same tape and amanda reported success writing the label. However, it still persists in this error with 'amcheck.' Is this simply a bad tape? Any help would be greatly appreciated! Kind Regards, Chris $ amtape campus show amtape: scanning all 15 slots in changer: slot 1: date 20120108230004 label CAMPUS-09 slot 2: date 20120119172116 label CAMPUS-10 slot 3: date 20120119191431 label CAMPUS-11 slot 4: date 20120119210149 label CAMPUS-12 slot 5: Error reading Amanda header: Error reading 32768 bytes from /dev/st0: Input/output error slot 6: Error reading Amanda header: Error reading 32768 bytes from /dev/st0: Input/output error slot 7: Error reading Amanda header: Error reading 32768 bytes from /dev/st0: Input/output error ERROR: error from mtx: Loading media from Storage Element 9 into drive 0...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Hardware Error mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 53 mtx: Request Sense: Additional Sense Qualifier = 00 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no MOVE MEDIUM from Element Address 264 to 32 Failed $
Tapetype request
Does anyone have a tapetype for a Quantum Super Loader 3 with a DLT-V4 drive they would be willing to share before I go off hacking up my own? The wiki has one for the Super Loader 3 with a DLT-S4 drive, but I'm not sure if that will work. Kind Regards, Chris Christopher Nighswonger Faculty Member Network Systems Director Foundations Bible College Seminary www.foundations.edu www.fbcradio.org - NOTICE: The information contained in this electronic mail message is intended only for the use of the intended recipient, and may also be protected by the Electronic Communications Privacy Act, 18 USC Sections 2510-2521. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender, and delete the original message. Thank you.
Re: Zmanda Windows Client with dumpuser other than amandabackup
Hi Alden, On Thu, Jul 21, 2011 at 5:25 PM, Alden Timme alden.ti...@gmail.com wrote: Is there really no other way for the backup to work? I.e. something like being able to set client_username as you can with rsh or ssh authentication? The truth of the matter is that ZWC is a proprietary product which is close sourced. Thus as long as the code owner elects not to invest the time to add the ability to set the username at install time or in a config file, we are stuck with the registry hack mentioned in the wiki. This is another case-in-point for open source code. Kind Regards, Chris
Re: Fare Thee Well
On Thu, Oct 14, 2010 at 1:03 PM, Jon LaBadie j...@jgcomp.com wrote: Dustin, I've been a member of the Amanda community sufficiently long to have seen the departure of a handful of star contributors. I count you among them, your impact on the project has been enormous. As you leave for Mozilla, I wish you well and am confident you will flourish in any future endevour. We will be diminished by your absence. My best wishes go out to you my friend, Jon Well said! Best wishes, Chris
Re: Amanda changes bite me again.
amcheck dead in water: [ama...@coyote amanda-3.2.0alpha.svn.3460]$ amcheck Daily Amanda Tape Server Host Check - Holding disk /usr/dumps: 620929024 kB disk space available, using 620417024 kB amcheck-device: syntax error at /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 473, near Amanda::Debug: syntax error at /usr/lib/perl5/site_perl/5.10.1/Amanda/Changer/disk.pm line 497, near ) symlink Line 473 should have a double colon rather than a single... ie. Amanda::Debug::debug rather than Amanda::Debug::debug Kind Regards, Chris
Re: Nitpicks?
This may be a little late, but it would be nice to have a switch on most status, etc. utils to format the output for texting to a mobile device rather than email. According to Verizon's website, the 160 char limit on text messages is as follows: The 160 character limit includes the sender's email address (if applicable), the composed message and, if provided, the subject and callback number. It seems that sending an email to a device that only supports text messages results in char-length-of-email/160 text messages. This can add up if one has to pay per message or has a set limit of free messages. Output formatted for texting might be sent only when there was an error detected or might only include limited summary info depending on the script being run. Kind Regards, Chris On Thu, Sep 9, 2010 at 11:55 AM, Dustin J. Mitchell dus...@zmanda.com wrote: I bet most of you have some small nitpick with Amanda that you've never felt warranted an email. Well, now's your chance! I'd like to put some polish on Amanda, and it's hard for me to see the areas that need burnishing, since I work on Amanda all day, every day. - typo in a manpage? - command-line usage oddity? - confusing use of terminology? - something else? Start up a new thread on the mailing list, or email me privately if you'd prefer, to let me know what's bugging you. Bonus points for also supplying a patch, but that's not at all required! Note that I do reserve the right to say, actually, that's complicated (and explain why). Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: Problems After Upgrading to 3.1.2
On Sun, Aug 29, 2010 at 11:32 AM, Steven Backus bac...@whimsy.med.utah.edu wrote: Perhaps you've built Amanda without indicating the printing utility? This was not necessary in the past. The 3hole.ps just worked. Check the amreport logfile for more detail, and have a look at the source to see how it decides whether to generate labels or not. The logic hasn't changed, but a rebuild may have altered some of the inputs to that algorithm. I'll try to figure out more details, here again is the amreport debug log. It looks like the code is fubared, not that my settings are incorrect. -- Tue Aug 24 23:59:10 2010: amreport: pid 31955 ruid 0 euid 0 version 3.1.2: start at Tue Aug 24 23:59:10 2010 Tue Aug 24 23:59:10 2010: amreport: pid 31955 ruid 0 euid 0 version 3.1.2: rename at Tue Aug 24 23:59:10 2010 Tue Aug 24 23:59:10 2010: amreport: using logfile: /usr/adm/amanda/gen/log Tue Aug 24 23:59:10 2010: amreport: operating in script mode Tue Aug 24 23:59:10 2010: amreport: warning: Use of uninitialized value in substitution (s///) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Report.pm line 856. Tue Aug 24 23:59:10 2010: amreport: planned output: human mail root Tue Aug 24 23:59:10 2010: amreport: planned output: postscript /local/etc/amanda/gen/3hole.ps printer SteveLaser Tue Aug 24 23:59:10 2010: amreport: invoking mail app: /usr/bin/Mail -s gen FAIL: AMANDA MAIL REPORT FOR August 23, 2010 root Tue Aug 24 23:59:10 2010: amreport: warning: Use of uninitialized value in numeric gt () at /usr/lib/perl5/site_perl/5.8.8/Amanda/Report/human.pm line 608. Tue Aug 24 23:59:10 2010: amreport: warning: Argument -- isn't numeric in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Report/human.pm line 1312. Regardless of the real cause of this problem, it seems to be very bad practice to have a sub return a non-numeric value to a test looking for a numeric value. And at the very least, fixing it would clean up the logs from distracting errors. Kind Regards, Chris
Re: More on 3hole.ps Problem
Hi Steven, On Wed, Aug 25, 2010 at 3:42 PM, Steven Backus bac...@whimsy.med.utah.edu wrote: Dustin and Jean-Louis are both on vacation, Dustin asked me to look into this further. Here's the pertinent log: Tue Aug 24 23:59:10 2010: amreport: pid 31955 ruid 0 euid 0 version 3.1.2: start at Tue Aug 24 23:59:10 2010 Tue Aug 24 23:59:10 2010: amreport: pid 31955 ruid 0 euid 0 version 3.1.2: rename at Tue Aug 24 23:59:10 2010 Tue Aug 24 23:59:10 2010: amreport: using logfile: /usr/adm/amanda/gen/log Tue Aug 24 23:59:10 2010: amreport: operating in script mode Tue Aug 24 23:59:10 2010: amreport: warning: Use of uninitialized value in substitution (s///) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Report.pm line 856. Tue Aug 24 23:59:10 2010: amreport: planned output: human mail root Tue Aug 24 23:59:10 2010: amreport: planned output: postscript /local/etc/amanda/gen/3hole.ps printer SteveLaser Tue Aug 24 23:59:10 2010: amreport: invoking mail app: /usr/bin/Mail -s gen FAIL: AMANDA MAIL REPORT FOR August 23, 2010 root Tue Aug 24 23:59:10 2010: amreport: warning: Use of uninitialized value in numeric gt () at /usr/lib/perl5/site_perl/5.8.8/Amanda/Report/human.pm line 608. Tue Aug 24 23:59:10 2010: amreport: warning: Argument -- isn't numeric in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Report/human.pm line 1312. Well, for some reason, $orig_size ends up set to zero which causes Amanda::Report::Human::divzero_col to return a string (-- )rather than a numeric. Never having read this code before and so shooting from the hip, I'd say the code does not handle the case where orig_kb == 0. Since divzero_col could return a non-numeric value, at the very least, the conditionals at lines 1289 and 1312 in Human.pm should be modified to take in to count the possibility of a non-numeric value in their test. However, there looks to have been substantial changes to other parts of the code, so the true problem may lie farther back up the food chain. Kind Regards, Chris
Re: Review Request: amvault --only-fulls option
On Mon, Aug 23, 2010 at 6:29 PM, Dustin J. Mitchell dus...@zmanda.com wrote: I've already rewritten amvault to use the same underlying machinery as amfetchdump and taper -- at the same time. That means that amvault can now re-assemble dumps from the source volume and re-split them on the destination volume. Making this more general requires some hard thought about configurations and whatnot, but in the interim, it was pretty easy to add support for a frequently-requested feature: only vaulting full dumps. I've implemented it here (and I checked the link this time): http://github.com/djmitche/amanda/commit/z11694 and the patch is attached, as well. Like last time, it'd be great if someone could take a look and, if the patch looks good, let me know. Please feel free to add any comments on the github commit, too. Here's how it reads to me: Now we pass in a dump level when creating our dump spec object. For the present, the only dump level supported is 0 or full. Without testing (sorry, I'm not setup to test atm), it looks fine to me. Kind Regards, Chris
Re: Review Request: don't require that CONT_FILENAME have no spaces
On Fri, Aug 20, 2010 at 10:03 PM, Dustin J. Mitchell dus...@zmanda.com wrote: On Fri, Aug 20, 2010 at 8:48 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: http://github.com/djmitche/amanda/commit/z8198 Is it me or is this a broken link? No, it's me. I totally botched that link, sorry. http://github.com/djmitche/amanda/commit/z11741 Removing the call to validate_no_space looks like the correct solution to me. Kind Regards, Chris
Re: Review Request: don't require that CONT_FILENAME have no spaces
On Fri, Aug 20, 2010 at 5:49 PM, Dustin J. Mitchell dus...@zmanda.comwrote: With Jean-Louis out of town, my patches are piling up. We have a strict review policy that at least one other dev needs to review a patch before it goes in. Hopefully someone here can free the logjam. This particular patch: http://github.com/djmitche/amanda/commit/z8198 Is it me or is this a broken link? Kind Regards, Chris
Re: Restart of /etc/xinetd.d/amanda
On Mon, Aug 2, 2010 at 3:21 PM, Steven Backus bac...@whimsy.med.utah.eduwrote: Dustin J. Mitchell dus...@zmanda.com wrote: That particular timeout is hard-coded in amandad.c -- REP_TIMEOUT. It's six hours, though - if your estimates are taking that long, you may want to consider 'estimate server' instead.. Can you point me to documetation about how to set up an estimate server? Not an estimate server, but the 'estimate server' directive. See the section on Dump Type here: http://wiki.zmanda.com/man/amanda.conf.5.html Kind Regards, Chris
Re: ZWC exclude path wildcard support question
Hi Prashant,
On Tue, Jul 20, 2010 at 5:32 AM, Prashant Joshi prash...@zmanda.com wrote:
Hi Chris,
What version of ZWC Community edition are you using?
3.1.beta
I added the following disklist and it worked fine for me:
--
192.168.15.176 C:/Documents and Settings/ C:/Documents and Settings/ {
exclude C:\\Documents and Settings\\*\\Application
Data\\Microsoft
--
That appears to be a non-standard exclude syntax. By that I mean that
all available information indicates either no escaping of the spaces
in the path or using a standard '\' char to escape. While it
apparently worked on your test setup, it bears noting that having
multiple variations and non-standard syntax only confuses things.
Perhaps an enhancement would be to make ZWC honor the exact syntax of
the *nix Amanda clients.
The Microsoft directory directory from all the user's Application Data
folder got excluded.
I will try your exact syntax on my sandbox and see what the results are.
In case, the above exclude path does not work, please send us the logs. To
collect the logs, run Start Menu Programs Zmanda Zmanda Client for
Windows ZWC Support.
I'll do this as well.
Please note that I will be out of town for the rest of the week and
will reply to this on Monday next.
Thanks Prashant.
Kind Regards,
Chris
Re: ZWC exclude path wildcard support question
On Wed, Jul 14, 2010 at 2:20 PM, Chris Nighswonger
cnighswon...@foundations.edu wrote:
On Wed, Jul 14, 2010 at 12:46 PM, Dustin J. Mitchell dus...@zmanda.com
wrote:
On Wed, Jul 14, 2010 at 11:08 AM, Chris Nighswonger
cnighswon...@foundations.edu wrote:
Since no one has spoken up, I'm calling it a bug. The wildcard is
clearly supported in a filename in exclude lists with ZWC. It follows,
therefore, that it should be supported in pathing as well. So is there
a bug tracking system for ZWC? If not, what is the procedure for
filing a bug against it?
I had a look at the source code, and it looks like this is *intended*
to work, although the code is pretty gnarly so it's hard to tell for
sure. I tried extracting it to a test function and translating the
various Windowsisms (DWORD, _tcs functions, etc.) but it didn't work
out.
C:\\Documents\ and\ Settings\\*\\foo\\bar would be unquoted to
C:\Documents and Settings\*\foo\bar
I wonder if that \* is being taken as an escape for the *? Does
...Settings\\C*\\fo... match against your user directory?
Here's the DLE I tested:
client.foo.bar.com C:/Documents and Settings {
zwc-compress
exclude C:\\Documents\ and\ Settings\\a*\\Application\ Data
}
Here's a few lists (sanitized of usernames) of the resulting index. As
you can see we still get both Application Data and all subdirs below
that level. But what I may be looking for should be something along
this line: exclude C:\\Documents\ and\
Settings\\%USERNAME%\\Application\ Data and allow VSS to do the env
var interpolation on the fly.
Being able to eyeball the source for ZWC would sure be nice in this
situation. Besides having the advantage of giving insight into how
things are supposed to work, it might also yield additional features
contributed by the community.
On that note, perhaps some of the community members should get
together and collaborate on development of a true open source Win32
Amanda client. My time is at a premium at the moment, but the time I'm
spending trying to get ZWC figured out/working may be better spent
developing.
How say ye?
Kind Regards,
Chris
Re: ZWC exclude path wildcard support question
On Mon, Jul 12, 2010 at 9:17 PM, Dustin J. Mitchell dus...@zmanda.com wrote: On Mon, Jul 12, 2010 at 12:04 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: I'm wondering if the problem described below is a bug or expected behavior? Well, if it's not in the docs, then it's not expected :) Has anyone else on the list worked with exclude lists with ZWC? Since no one has spoken up, I'm calling it a bug. The wildcard is clearly supported in a filename in exclude lists with ZWC. It follows, therefore, that it should be supported in pathing as well. So is there a bug tracking system for ZWC? If not, what is the procedure for filing a bug against it? BTW: I'd love find this is just another matter of syntax ignorance... Kind Regards, Chris
Re: ZWC exclude path wildcard support question
On Wed, Jul 14, 2010 at 12:46 PM, Dustin J. Mitchell dus...@zmanda.com wrote:
On Wed, Jul 14, 2010 at 11:08 AM, Chris Nighswonger
cnighswon...@foundations.edu wrote:
Since no one has spoken up, I'm calling it a bug. The wildcard is
clearly supported in a filename in exclude lists with ZWC. It follows,
therefore, that it should be supported in pathing as well. So is there
a bug tracking system for ZWC? If not, what is the procedure for
filing a bug against it?
I had a look at the source code, and it looks like this is *intended*
to work, although the code is pretty gnarly so it's hard to tell for
sure. I tried extracting it to a test function and translating the
various Windowsisms (DWORD, _tcs functions, etc.) but it didn't work
out.
C:\\Documents\ and\ Settings\\*\\foo\\bar would be unquoted to
C:\Documents and Settings\*\foo\bar
I wonder if that \* is being taken as an escape for the *? Does
...Settings\\C*\\fo... match against your user directory?
Here's the DLE I tested:
client.foo.bar.com C:/Documents and Settings {
zwc-compress
exclude C:\\Documents\ and\ Settings\\a*\\Application\ Data
}
Here's a few lists (sanitized of usernames) of the resulting index. As
you can see we still get both Application Data and all subdirs below
that level. But what I may be looking for should be something along
this line: exclude C:\\Documents\ and\
Settings\\%USERNAME%\\Application\ Data and allow VSS to do the env
var interpolation on the fly.
amrecover setdisk C:/Documents and Settings
200 Disk set to C:/Documents and Settings.
amrecover ls
2010-07-14-12-48-05 s/
2010-07-14-12-48-05 p/
2010-07-14-12-48-05 p/
2010-07-14-12-48-05 m/
2010-07-14-12-48-05 m/
2010-07-14-12-48-05 l/
2010-07-14-12-48-05 l/
2010-07-14-12-48-05 l/
2010-07-14-12-48-05 k/
2010-07-14-12-48-05 j/
2010-07-14-12-48-05 j/
2010-07-14-12-48-05 f/
2010-07-14-12-48-05 e/
2010-07-14-12-48-05 e/
2010-07-14-12-48-05 e/
2010-07-14-12-48-05 d/
2010-07-14-12-48-05 d/
2010-07-14-12-48-05 b/
2010-07-14-12-48-05 a/
2010-07-14-12-48-05 a/
2010-07-14-12-48-05 a/
2010-07-14-12-48-05 a/
2010-07-14-12-48-05 a/
2010-07-14-12-48-05 N/
2010-07-14-12-48-05 L/
2010-07-14-12-48-05 Default User/
2010-07-14-12-48-05 All Users/
2010-07-14-12-48-05 Administrator/
amrecover cd a/
/a
amrecover ls
2010-07-14-12-48-05 ntuser.pol
2010-07-14-12-48-05 ntuser.ini
2010-07-14-12-48-05 ntuser.dat.LOG
2010-07-14-12-48-05 ntuser.dat
2010-07-14-12-48-05 Templates/
2010-07-14-12-48-05 Start Menu/
2010-07-14-12-48-05 SendTo/
2010-07-14-12-48-05 Recent/
2010-07-14-12-48-05 PrivacIE/
2010-07-14-12-48-05 PrintHood/
2010-07-14-12-48-05 NetHood/
2010-07-14-12-48-05 My Documents/
2010-07-14-12-48-05 Local Settings/
2010-07-14-12-48-05 IETldCache/
2010-07-14-12-48-05 IECompatCache/
2010-07-14-12-48-05 Favorites/
2010-07-14-12-48-05 Desktop/
2010-07-14-12-48-05 Cookies/
2010-07-14-12-48-05 Application Data/
2010-07-14-12-48-05 .
amrecover cd Application Data/
/a/Application Data
amrecover ls
2010-07-14-12-48-05 desktop.ini
2010-07-14-12-48-05 Sun/
2010-07-14-12-48-05 OpenOffice.org2/
2010-07-14-12-48-05 OpenOffice.org/
2010-07-14-12-48-05 Mozilla/
2010-07-14-12-48-05 Microsoft/
2010-07-14-12-48-05 Macromedia/
2010-07-14-12-48-05 Identities/
2010-07-14-12-48-05 Adobe/
2010-07-14-12-48-05 .
amrecover cd Adobe/
/anbrock/Application Data/Adobe
amrecover ls
2010-07-14-12-48-05 Flash Player/
2010-07-14-12-48-05 Acrobat/
2010-07-14-12-48-05 .
amrecover
Re: ZWC exclude path wildcard support question
I'm wondering if the problem described below is a bug or expected behavior? On Thu, Jul 8, 2010 at 3:36 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: Does ZWC support wildcards in exclude path notations? If so, could someone provide an example of the proper syntax? C:\\Documents\ and\ Settings\\*\\foo\\bar does not work in my sandbox. (ie. This is intended to exclude foo\bar under every user's documents and settings directory.) Kind Regards, Chris
ZWC exclude path wildcard support question
Does ZWC support wildcards in exclude path notations? If so, could someone provide an example of the proper syntax? C:\\Documents\ and\ Settings\\*\\foo\\bar does not work in my sandbox. (ie. This is intended to exclude foo\bar under every user's documents and settings directory.) Kind Regards, Chris
Re: ZWC and exclude list not behaving as expected
On Thu, Jul 1, 2010 at 10:59 AM, Dustin J. Mitchell dus...@zmanda.com wrote:
1. Correct exclude pattern (Added using ZMC):
*
192.168.15.217 C:/Documents and Settings/Administrator/My
Documents/My Music C:/Documents and Settings/Administrator/My
Documents/My Music {
zmc_windows_base
exclude *.mp3 *.avi *.pdf
*
All files with extension .mp3, .avi .pdf got excluded.
I was able to confirm this using ZWC 3.1.beta (3.1.1 is not available
on the download site yet.)
So, to help out other poor souls who may be having a very bad day,
I've added this to the wiki:
http://wiki.zmanda.com/index.php/Zmanda_Windows_Client#Adding_dumptype_definitions_on_the_Amanda_server_for_Windows_clients
Also note that using single, forward slashes in the path seems to work
fine in 3.1.beta. Apparently it did not in the past.
Thanks to Dustin and the others who helped solve this syntax problem.
Kind Regards,
Chris
ZWC and exclude list not behaving as expected
Hi all, I'm here again with another ZWC-exclude list issue. This paste (http://pastebin.mozilla.org/743992) shows a DLE for a ZWC client and a listing of the resulting dump. This configuration is setup with the sole purpose of testing the ZWC and exclude lists. As you can see, the exclude list has a number of multi-media file extensions in regexp form. The target directory is almost entirely mp3 files. In spite of this exclude list, the ZWC still insists on dumping all of the mp3 files. I have verified via tcpdump that the exclude list is passed to the ZWC. However, setting the log level of ZWC to 5 shows a call to zwcIncludeExcludeList(), but logs nothing to indicate that the client actually received the exclude list. 2304:2112:30/6/2010:13:45:602::Entering zwcIncludeExcludeList() 2304:2112:30/6/2010:13:45:602::Leaving zwcIncludeExcludeList() So... am I missing something that I don't know about or is this a bug? Incidentally, if the source for ZWC were available, I'd be glad to take a look and see if I could fix this. Kind Regards, Chris
Re: ZWC and exclude list not behaving as expected
http://pastebin.mozilla.org/744016 Updated to include a bit more information. On Wed, Jun 30, 2010 at 1:58 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: Hi all, I'm here again with another ZWC-exclude list issue. This paste (http://pastebin.mozilla.org/743992) shows a DLE for a ZWC client and a listing of the resulting dump. This configuration is setup with the sole purpose of testing the ZWC and exclude lists. As you can see, the exclude list has a number of multi-media file extensions in regexp form. The target directory is almost entirely mp3 files. In spite of this exclude list, the ZWC still insists on dumping all of the mp3 files. I have verified via tcpdump that the exclude list is passed to the ZWC. However, setting the log level of ZWC to 5 shows a call to zwcIncludeExcludeList(), but logs nothing to indicate that the client actually received the exclude list. 2304:2112:30/6/2010:13:45:602::Entering zwcIncludeExcludeList() 2304:2112:30/6/2010:13:45:602::Leaving zwcIncludeExcludeList() So... am I missing something that I don't know about or is this a bug? Incidentally, if the source for ZWC were available, I'd be glad to take a look and see if I could fix this. Kind Regards, Chris
Re: ZWC and exclude list not behaving as expected
On Wed, Jun 30, 2010 at 7:21 PM, Dustin J. Mitchell dus...@zmanda.com wrote: On Wed, Jun 30, 2010 at 12:58 PM, Chris Nighswonger cnighswon...@foundations.edu wrote: So... am I missing something that I don't know about or is this a bug? Replying on Paddy's behalf: There's a 3.1.1 that's currently in internal testing that might improve the situation. It should be ready in a few days. Send another email if you don't hear anything about it soon? Ok. I did find some further info in the wiki which indicated that the ZWC requires the full path for each entry in the exclude list. I did verify that this does work. However, it makes for quite a chore from the administrative aspect trying to keep up with a full path to every directory where one wants to exclude a certain file type or types. Other backup solutions which use the MS VSS services allow both exclusion and inclusion based on file extension matching patterns alone. It seems that ZWC could be made to behave this way as well. Kind Regards, Chris
Re: ZWC and exclude list question (another one)
On Thu, Jun 24, 2010 at 12:34 PM, Dustin J. Mitchell dus...@zmanda.com wrote: On Wed, Jun 23, 2010 at 8:22 AM, Chris Nighswonger cnighswon...@foundations.edu wrote: So is the only way to do this to have a dumptype setup using 'exclude' and 'exclude append' to catch each of potentially 300 some multimedia file extensions? This would mean 300 some 'exclude'/'exclude append' directives. It seems there must be a better way. Surely you could get 90% of the space-saving effects with only 10 extensions.. True. However, there could still quite a bit of administrative overhead to exclude files based on extensions if the list were to become very long. It would be nice to be able to reference an exclude file on the amanda server in such a case as this. Or just have ZWC support exclude files client-side. Kind Regards, Chris
ZWC and exclude list question (another one)
I'm wanting to exclude from my user's Windows clients all multimedia files. I plan to use regexps to match file extensions (ie. ./*.mp3 and so forth). It is my understanding that ZWC does not respect exclude lists stored on the client. So is the only way to do this to have a dumptype setup using 'exclude' and 'exclude append' to catch each of potentially 300 some multimedia file extensions? This would mean 300 some 'exclude'/'exclude append' directives. It seems there must be a better way. Kind Regards, Chris
ZWC and exclude/include lists
Does ZWC honor exclude/include lists?
I have a DLE like:
foo.bar.com C:\\Documents\ and\ Settings {
exclude list C:\\.exclude
zwc-compress
estimate server
}
c:\.exclude includes several entries like:
.\user1
.\user2
Looking at a tcpdump of the resulting transactions, I see the exclude
list passed to the client, but the client still dumps the entirety of
c:\documents and settings.
Am I missing some syntax error here?
Or perhaps this is the purpose of templates in the ZWC?
Kind Regards,
Chris
Re: ZWC and exclude/include lists
On Wed, Jun 9, 2010 at 2:00 PM, Paddy Sreenivasan pa...@zmanda.com wrote:
On Wed, Jun 9, 2010 at 8:00 AM, Chris Nighswonger
cnighswon...@foundations.edu wrote:
Does ZWC honor exclude/include lists?
I have a DLE like:
foo.bar.com C:\\Documents\ and\ Settings {
exclude list C:\\.exclude
zwc-compress
estimate server
}
include is not supported. exclude is supported. See
http://forums.zmanda.com/showthread.php?t=2701 for
more information.
A couple more questions to help clarify things for me:
1. So exclude list/file is not supported, only the vanilla exclude?
2. Should I be using ZWC templates for this instead?
Kind Regards,
Chris
ZWC template not applying as expected
I have a template setup in ZWC which contains the single entry: C:\Documents and Settings. The corresponding DLE is: foo.bar.com c: zwc-compress The problem is that Amanda then backs up the entire C drive rather than just the Documents and Settings folder. What is it I'm missing? Kind Regards, Chris
Re: ZWC template not applying as expected
Well, Google turned up this: http://forums.zmanda.com/showthread.php?t=2588 But trying to apply it to my DLE results in an Invalid disk list entry. For taking backup of a single file use templates. Sort of ironic considering I *am* trying to use a template. ;-) On Tue, Jun 8, 2010 at 1:17 PM, Brian Cuttler br...@wadsworth.org wrote: Chris, Glad I was able to help. I'll let you know if I learn more but do believe/agree with you that it seems to be a documentation issue. best, brian On Tue, Jun 08, 2010 at 01:08:42PM -0400, Chris Nighswonger wrote: Hi Brian, On Tue, Jun 8, 2010 at 11:06 AM, Brian Cuttler br...@wadsworth.org wrote: Chris, I'd puzzeled over that too. I believe that the templates are for amanda servers, you are only running the client and the tempate is never used for anything. A look at a tcpdump does show that the diskdevice in the DLE is passed to the zwc and the next piece of traffic is the estimated size of the backup of that device. So template.txt appears to be ignored. It seems that if it is not meant to be used it should be removed from the community version or at least documented as such. My (unix based) dislist files contain dle's that look like foo ? c:/database-backups ?zwc-compress foo ? c:/users-data1 ? ? ? zwc-compress foo ? c:/users-data2 ? ? ? zwc-compress Rather than a template that contains the 3 entries. This is what I have resorted to for the time being as well. Thanks for the response. Kind Regards, Chris --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support (v) 518 486-1697 Wadsworth Center (f) 518 473-6384 NYS Department of Health Help 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.
Re: ZWC template not applying as expected
On Tue, Jun 8, 2010 at 2:58 PM, Paddy Sreenivasan pa...@zmanda.com wrote: On Tue, Jun 8, 2010 at 7:53 AM, Chris Nighswonger cnighswon...@foundations.edu wrote: I have a template setup in ZWC which contains the single entry: C:\Documents and Settings. The corresponding DLE is: foo.bar.com c: zwc-compress The disklist entry should be foo.bar.com template name zwc-compress The template should be defined on the Windows client as C:\Documents and Settings. It is not necessary to use template unless you want to back all the folders using the same snapshot. What I'm really looking for is a way for certain users to manage their own backups. Is this the wrong way to go about it? Chris
DLE exclude file problem
When defining DLE like this:
hostname diskname [ diskdevice ] {
normal
holdingdisk never
} [ spindle [ interface ] ]
Is it possible to use the 'exclude' or 'include' directive inside of
the disktype definition? I have tried this multiple ways and cannot
seem to get it to work. My latest attempt was to use an exclude file.
foobar.foo.bar /home/user {
comp-tar
exclude list .amanda.exclude
}
Here is .amanda.exclude (the amandauser is a member of the backup
group which has read permissions to .amanda.exclude):
$ cat .amanda.exclude
./Failed\ Raid\ 5\ Images
./RAID\ Image\ Backup
./Downloads
amcheck seems to like this, however amdump dumps the entire /home/user
without the exclusions.
What am I doing wrong here?
Kind Regards,
Chris
