Re: magazine article, Solaris file system snapshots
Hi, > > Hey - we use snapshots on our Ultra 1 servers with about 142 MHz, > > running Solaris 8, works like a charm! :-) > > Do you use the snapshots for amanda backups? > > If so, how similar is your procedure to what J. Briggs describes? I don't have access to the SysAdmin magazine, so I could not read the article. But from what you write about it: > Mr. Briggs describes three approaches to creating the snapshots when > needed and eliminating them when finished. The approaches include: > > - bulk creation of all snapshots before amdump and deletion after > - using automount maps to create and mount snapshots as needed > - surrounding ufsdump with a wrapper that creates and mounts a > snapshot > during the dump phase, but not the estimate phase I chose to create the snapshots by cron, mount them, share them and have amanda back them up. Then I leave them mounted and shared the whole next day. This way users have access to the last backup and can restore files by themselves. This has saved us quite a lot of work. I also use the automounter to have the snapshots mounted anywhere automagically: local filesystem: /home, /home1 Snapshot: /snapshot/home, /snapshot/home1 automount point:/homes/, /homes1/ snapshot mount point: /snapshots/homes/, /snapshots/homes1/ By naming the snapshots this way, I can easily prefix a users home directory with "/snapshots" and have instantly access to his home the day before. So creation of a personal snapshot samba share is really easyly done: [homes] comment = Home Directories read only = no browseable = no inherit permissions = no [my_snapshot] comment = Home Directory from yesterday path= /snapshots/%H read only = yes Regards, Christopher -- == Dipl.-Ing. Christopher Odenbach HNI Rechnerbetrieb [EMAIL PROTECTED] Tel.: +49 5251 60 6215 ==
Re: magazine article, Solaris file system snapshots
On Thu, Apr 03, 2003 at 05:17:39PM -0500, Ron Bauman wrote: > I needed to lock our ClearCase databases while dumping, > so I wrap gtar with a shell script. I use this script to configure amanda: > > #!/bin/sh > # [[ snipped ]] > > > It's a bit quirky in that the script has to be there before running configure, > otherwise the check for gtar fails. On the first client install of amanda I did, /bin/tar was not gnu and /usr/local/bin/gtar was a bad version of gnutar. The client did not want me messing with either of those. Instead I installed a good version in /usr/local/libexec, where many other "am***" commands were going and called it "amgtar" and specified that as gnutar in my configure script. Since then I always do that and realized that amgtar can be a real gtar or a wrapper with no change to my configure. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: chg-zd-mtx issue ?
On Thu April 3 2003 15:34, Brian Cuttler wrote: >Amanda 2.4.4 >Solaris 9 >LTO tape in Storedge 9 jukebox (ie HP c7145 jukebox) >mtx 1.2.17rel > >> mtx -f /dev/scsi/changer/c5t4d0 inquiry > >Product Type: Medium Changer >Vendor ID: 'HP ' >Product ID: 'C7145 ' >Revision: '233S' >Attached Changer: No > >This is very intermittent... > > amdump always runs successfully >amcheck and amlabel, usually good, sometimes a little less > so amtape _always_ fails in the same manner. > >Actually I was seeing a higher rate of success with amanda 2.4.3 >on Solaris 8 but with the 2.4.4 chg-zd-mtx script. I'm sorry, I >don't recall the version of mtx I was using on Solaris 8. > >Please tell me what additional diagnostic information I can > provide, I just didn't want to include the kitchen sink. > >> amlabel ninfo NTNWKLY10 slot 3 > >labeling tape in slot 3 (/dev/rmt/0cn): >rewinding, reading label, not an amanda tape >rewinding, writing label NTNWKLY10, checking labelBus error (core > dumped) >From that hint, you have hardware problems, possibly related to the termination on the scsi bus. Bear in mind that a scsi bus is a transmission line, and as such it must be properly terminated AT BOTH ENDS of the bus. One cannot use any old connector on a multiconnector cable as the last device on the cable. The end connector must be used. Anything else and the signal echo's from the improper termination scheme will eat your lunch. Its been known to be picky, even about the virgins you occasionally have to sacrifice to make it work. >> amcheck ninfo > >Amanda Tape Server Host Check >- >WARNING: holding disk /amanda/work: only 34403066 KB free > (36700160 KB requested) amcheck-server: slot 3: date X > label NTNWKLY10 (first labelstr match) amcheck-server: slot 4: > not an amanda tape >amcheck-server: slot 5: date 20030327 label NEWTONR05 (no match) >amcheck-server: slot 6: date 20030328 label NEWTONR06 (no match) >amcheck-server: slot 7: date 20030331 label NEWTONR07 (no match) >amcheck-server: slot 8: date 20030401 label NEWTONR08 (no match) >amcheck-server: fatal slot 9: badly formed result from changer: > "9" ERROR: could not read result from > "/usr/local/libexec/chg-zd-mtx" (got signal 10) (expecting tape > NTNWKLY05 or a new tape) >NOTE: skipping tape-writable test >Server check took 459.881 seconds > >Amanda Backup Client Hosts Check > >Client check: 7 hosts checked in 2.112 seconds, 0 problems found > >(brought to you by Amanda 2.4.4) > >> cat chg-zd-mtx.conf > >firstslot=1 >lastslot=9 >#cleanslot=3 >AUTOCLEAN=0 >autocleancount=99 >havereader=1 >offlinestatus=0 >OFFLINE_BEFORE_UNLOAD=0 > > thanks, > > Brian > >--- > Brian R Cuttler [EMAIL PROTECTED] > Computer Systems Support(v) 518 486-1697 > Wadsworth Center(f) 518 473-6384 > NYS Department of HealthHelp Desk 518 473-0773 -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
amrecover Problem
Hi there, ive got a Problem with amrecover on an Debian GNU/Linux maschine. amrecover reports: No index records for disk for specified date If date correct, notify system administrator In debug files in /tmp i cant find any other Informations.Debugfile is there but the informations are the same shown on client. There is a backup on level 0 on specified date. In amanda.conf index yes is set on dumptype. -> index is on the secified indexdir, so i can zcat it and see all files an directorys. Iam using tar (GNU tar 1.13.25), so it cant be the known bug on older gtar versions, and amanda version 2.4.2p2. Are there any solutions. Greetings Daniel
Re: Strange problems backing up Windows users with Samba
On Thu April 3 2003 13:18, Tom Murphy wrote: >Hi all, > > I am running AMANDA v2.4.4 on Solaris and all was >working fine until recently. Now I get bizarre error >messages through my AMANDA logs like these: > >/-- saturn.res //spock/E$ lev 1 STRANGE >sendbackup: start [saturn.research.ets.org://spock/E$ >level 1] >sendbackup: info >BACKUP=/local/research/samba/bin/smbclient >sendbackup: info RECOVER_CMD=/local/research/bin/gzip >-dc >+|/local/research/samba/bin/smbclient -f... - >sendbackup: info COMPRESS_SUFFIX=.gz >sendbackup: info end >? Call timed out: server did not respond after 2 >milliseconds opening remote file >+\ebsco-1064\cueanalysisnew.zip (\ebsco-1064\) >? Call timed out: server did not respond after 2 >milliseconds opening remote file >+\ebsco-1064\cues.lst (\ebsco-1064\) >? Call timed out: server did not respond after 2 >milliseconds opening remote file >+\ebsco-1064\difficulties-td80.txt (\ebsco-1064\) >? Call timed out: server did not respond after 2 >milliseconds opening remote file >+\ebsco-1064\difficulties-td80.xls (\ebsco-1064\) > > >etc.. > >Tons upon tons of "Call timed out: server did not >respond after 2 milliseconds" error messages. > >Is there a fix for this somewhere? I am wondering if >possibly it's a samba problem, but I am not sure. > >The machine it's trying to back up is a windows >machine and is working fine as far as I know. > >Any help would be greatly apprciated! > Just off the top of my head, if its timing out with a 20 second timeout, thats looking like an access permissions problem of some kind. But thats just a guess, I'm not a winderz user, its against my religion. :-) -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
RE: magazine article, Solaris file system snapshots
Yeah, I was thinking that would be great, too. I had to hack up the installation
along the lines Jon was suggesting (thanks, Jon). I needed to lock our ClearCase
databases while dumping, so I wrap gtar with a shell script. I use this script to
configure amanda:
#!/bin/sh
#
# this is the configure shell script for Amanda on ccserv.
# list the command line options given to configure here "for the record."
# 3/11/03 Ron Bauman
./configure --prefix=/usr --with-user=amanda --with-group=disk \
--libexecdir=/usr/lib/amanda --with-config=DailySet1 \
--with-configdir=/etc/amanda --with-tape-device=/dev/tape \
--without-debugging \
--with-gnutar=/usr/lib/amanda/gtar-wrapper
# config file is in /etc/amanda/daily
And this script is /usr/lib/amanda/gtar-wrapper:
#!/bin/sh
#
# wrapper for the gtar utility. used to find out what Amanda is backing up.
# if ClearCase vobs, we lock before and unlock after to insure a coherent
# backup.
#
# loop over .vbs files found in /vobstore. perform operation (lock or unlock)
# found in argument 1.
dovobs() {
for file in `ls -1d /vobstore/*.vbs`
do
base=`basename $file .vbs`
sudo -u ccadmin /usr/atria/bin/cleartool $1 vob:/vobs/$base >>$DBGFILE
done
}
if [ -d "/tmp/amanda" ]; then
DBGFILE=/tmp/amanda/gtar-wrapper.debug
else
DBGFILE=/dev/null
fi
echo "calling args-> $*" >>$DBGFILE
# if requesting a tar (instead of an estimate) and tarring vobstore...
if [ "$3" == "-" -a "$5" == "/vobstore" ]; then
dovobs lock
gtar $*
result=$?
dovobs unlock
else
gtar $*
result=$?
fi
exit $result
-
It's a bit quirky in that the script has to be there before running configure,
otherwise the check for gtar fails. But it's working OK for us. But a generalized
pre- and post-dump option in the dumptypes would be very nice.
Ron Bauman
-Original Message-
From: Kirk Strauser [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 4:23 PM
To: Paul Bijnens
Cc: Jon LaBadie; Amanda Users
Subject: Re: magazine article, Solaris file system snapshots
At 2003-04-03T16:24:07Z, Paul Bijnens <[EMAIL PROTECTED]> writes:
> I was investigating how to incorporate the feature more solid it into the
> program.
What I'd ideally like are settings for programs to be executed pre- and
post-dump for each filesystem. Bonus points if the command is customizable
using variables like '%f' to mean the name of the filesystem.
--
Kirk Strauser
In Googlis non est, ergo non est.
Re: Backup of ACLs
On Thu April 3 2003 10:02, Jon LaBadie wrote: >On Thu, Apr 03, 2003 at 01:15:32PM +0200, Dalton Hubert wrote: >> Hi, >> >> we are thinking about using ACLs (extended attributes and access >> control lists) on our file server, of which we make a full >> backup by using Amanda every night. >> >> So my question concerning the backup is: >> Can Amanda also backup ACLs? > >The problem with your question is that amanda doesn't backup > anything. It manages backups done by other programs. The common > programs are gnutar and the OS's file system dump program. The > question then becomes can the backup program you choose save and > restore ACL's. Best way to answer that is to read the local > documentation and run a test backup and recovery. Amanda is not > needed to check this out. > >> Do i have to change something in my configuration? >> >> I have heard something about star, is this really necessary or >> can i use tar? >> >> If i must use star instead of tar, where i must configure this? >> (which entry in which file?) > >During configuration and build of amanda you specify what program > is your "gnutar". If you point it at star, amanda will try to use > it. But beware that amanda will think it is gnutar and use > gnutar options. They may, or may not, be the same for star. > >BTW what's star? STar is Jeorg Schilling's *posix* compliant tar replacement. 'Schillings Tar' in other words. I believe it has additional features over and above gnutar, but thats just from reading the "press releases" :-) But like others, I've not tried to use it with amanda, so I have NDI if its gnutar compatible or not. Thats the same Schilling (or is it Schilly? Alzheimers strikes again) that is much more famous as the author of the CD-RW toolbox and its ancilliary utilities such as cdrecord and others in that family. His code should be as solid as it comes, but absolute compatibility questions have neither been asked very often here, nor answered here. Such questions in my observations, seem to be ignored. Lack of knowledge, or something actually wrong with it, I have no clue. However, I believe there is a flag you can set on its command line that makes it 100% gnutar compatible. Do a search on freshmeat for more details. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: Strange problems backing up Windows users with Samba
Hi, Tom Murphy, on Donnerstag, 3. April 2003 at 20:18 you wrote to amanda-users: TM> Hi all, TM>I am running AMANDA v2.4.4 on Solaris and all was TM> working fine until recently. Now I get bizarre error TM> messages through my AMANDA logs like these: ... TM> ? Call timed out: server did not respond after 2 TM> milliseconds opening remote file Exactly the same problem here. Still using Amanda 2.4.2p2 on my customers server (Suse 8.0). Thought about upgrading to 2.4.4 but that doesn´t seem to make sense regarding your mail. I updated to Samba 2.2.8 today, only changed the error message to the one you mentioned. Before that it was something like ? SUCCESS - 0 opening remote file ... (using Samba 2.2.3) I googled for both messages and only found vague hints to doing a chkdsk on the windows share. I mailed my customer to do so tomorrow, we´ll see. The amanda-users will direct you to samba-users if they haven´t done yet ... It´s a samba-problem AFAIK. Please let me know if you find out something useful. -- best regards, Stefan oops monitor mailto:[EMAIL PROTECTED]
Re: magazine article, Solaris file system snapshots
At 2003-04-03T16:24:07Z, Paul Bijnens <[EMAIL PROTECTED]> writes: > I was investigating how to incorporate the feature more solid it into the > program. What I'd ideally like are settings for programs to be executed pre- and post-dump for each filesystem. Bonus points if the command is customizable using variables like '%f' to mean the name of the filesystem. -- Kirk Strauser In Googlis non est, ergo non est. pgp0.pgp Description: PGP signature
chg-zd-mtx issue ?
Amanda 2.4.4 Solaris 9 LTO tape in Storedge 9 jukebox (ie HP c7145 jukebox) mtx 1.2.17rel > mtx -f /dev/scsi/changer/c5t4d0 inquiry Product Type: Medium Changer Vendor ID: 'HP ' Product ID: 'C7145 ' Revision: '233S' Attached Changer: No This is very intermittent... amdump always runs successfully amcheck and amlabel, usually good, sometimes a little less so amtape _always_ fails in the same manner. Actually I was seeing a higher rate of success with amanda 2.4.3 on Solaris 8 but with the 2.4.4 chg-zd-mtx script. I'm sorry, I don't recall the version of mtx I was using on Solaris 8. Please tell me what additional diagnostic information I can provide, I just didn't want to include the kitchen sink. > amlabel ninfo NTNWKLY10 slot 3 labeling tape in slot 3 (/dev/rmt/0cn): rewinding, reading label, not an amanda tape rewinding, writing label NTNWKLY10, checking labelBus error (core dumped) > amcheck ninfo Amanda Tape Server Host Check - WARNING: holding disk /amanda/work: only 34403066 KB free (36700160 KB requested) amcheck-server: slot 3: date Xlabel NTNWKLY10 (first labelstr match) amcheck-server: slot 4: not an amanda tape amcheck-server: slot 5: date 20030327 label NEWTONR05 (no match) amcheck-server: slot 6: date 20030328 label NEWTONR06 (no match) amcheck-server: slot 7: date 20030331 label NEWTONR07 (no match) amcheck-server: slot 8: date 20030401 label NEWTONR08 (no match) amcheck-server: fatal slot 9: badly formed result from changer: "9" ERROR: could not read result from "/usr/local/libexec/chg-zd-mtx" (got signal 10) (expecting tape NTNWKLY05 or a new tape) NOTE: skipping tape-writable test Server check took 459.881 seconds Amanda Backup Client Hosts Check Client check: 7 hosts checked in 2.112 seconds, 0 problems found (brought to you by Amanda 2.4.4) > cat chg-zd-mtx.conf firstslot=1 lastslot=9 #cleanslot=3 AUTOCLEAN=0 autocleancount=99 havereader=1 offlinestatus=0 OFFLINE_BEFORE_UNLOAD=0 thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
result of ksyms
Hello again, I was trying to run amdump using tapelist backup. It just hangs there. I have done a ksymoops and here it is. Would someone like to help me decode it?? Thanks in advance. RH 8.0; kernel 2.4.18-19.8.0; amanda-2.4.4-20030318 CPU: AMD Athlon XP 1800+ running i386 arch. ksymoops 2.4.5 on i686 2.4.18-19.8.0. Options used -v /boot/vmlinux-2.4.18-19.8.0 (specified) -k ./20030403110534.ksyms (specified) -l /proc/modules (default) -o /lib/modules/2.4.18-19.8.0 (specified) -m /boot/System.map-2.4.18-19.8.0 (specified) Error (expand_objects): cannot stat(/lib/ext3.o) for ext3 Error (expand_objects): cannot stat(/lib/jbd.o) for jbd Error (expand_objects): cannot stat(/lib/aic7xxx.o) for aic7xxx Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique module object. Trace may not be reliable. Apr 3 11:38:42 snook kernel: Unable to handle kernel paging request at virtual address 002ddb04 Apr 3 11:38:42 snook kernel: c0138129 Apr 3 11:38:42 snook kernel: *pde = Apr 3 11:38:42 snook kernel: Oops: 0002 Apr 3 11:38:42 snook kernel: CPU:0 Apr 3 11:38:42 snook kernel: EIP:0010:[]Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 Apr 3 11:38:42 snook kernel: EFLAGS: 00210286 Apr 3 11:38:42 snook kernel: eax: df6a8b50 ebx: d73d3d74 ecx: d73d3d20 edx: 002ddb04 Apr 3 11:38:42 snook kernel: esi: df6a8b30 edi: c6cf04e0 ebp: df6a8b30 esp: d6acfe8c Apr 3 11:38:42 snook kernel: ds: 0018 es: 0018 ss: 0018 Apr 3 11:38:42 snook kernel: Process dumper (pid: 3959, stackpage=d6acf000) Apr 3 11:38:42 snook kernel: Stack: d73d3d20 e085f087 1000 c0138fef d73d3d20 d73d3d20 d73d3d20 Apr 3 11:38:42 snook kernel:1000 1000 e085eec1 c6cf04e0 df6a8b30 d73d3d20 c105b2e4 Apr 3 11:38:42 snook kernel:08054ce0 c1c0f000 df6a8b30 e085f2e8 c6cf04e0 df6a8b30 d73d3d20 Apr 3 11:38:42 snook kernel: Call Trace: [] journal_dirty_sync_data [ext3] 0x33 (0xd6acfe94)) Apr 3 11:38:42 snook kernel: [] __block_prepare_write [kernel] 0x197 (0xd6acfe9c)) Apr 3 11:38:42 snook kernel: [] walk_page_buffers [ext3] 0x65 (0xd6acfeb8)) Apr 3 11:38:42 snook kernel: [] ext3_commit_write [ext3] 0x13c (0xd6acfed8)) Apr 3 11:38:42 snook kernel: [] journal_dirty_sync_data [ext3] 0x0 (0xd6acfef4)) Apr 3 11:38:42 snook kernel: [] ext3_get_block [ext3] 0x0 (0xd6acff00)) Apr 3 11:38:42 snook kernel: [] generic_file_write [kernel] 0x43f (0xd6acff14)) Apr 3 11:38:43 snook kernel: [] ext3_file_write [ext3] 0x1f (0xd6acff7c)) Apr 3 11:38:43 snook kernel: [] sys_write [kernel] 0x84 (0xd6acff9c)) Apr 3 11:38:43 snook kernel: [] system_call [kernel] 0x33 (0xd6acffc0)) Apr 3 11:38:43 snook kernel: Code: 89 02 89 71 50 8b 46 20 8d 56 20 89 58 04 89 41 54 89 53 04 >>EIP; c0138129<= >>eax; df6a8b50 <_end+1f3195b0/2047dac0> >>ebx; d73d3d74 <_end+170447d4/2047dac0> >>ecx; d73d3d20 <_end+17044780/2047dac0> >>edx; 002ddb04 Before first symbol >>esi; df6a8b30 <_end+1f319590/2047dac0> >>edi; c6cf04e0 <_end+6960f40/2047dac0> >>ebp; df6a8b30 <_end+1f319590/2047dac0> >>esp; d6acfe8c <_end+167408ec/2047dac0> Trace; e085f087 <[ext3].text.start+4027/a7a8> Trace; c0138fef <__block_prepare_write+197/2e4> Trace; e085eec1 <[ext3].text.start+3e61/a7a8> Trace; e085f2e8 <[ext3].text.start+4288/a7a8> Trace; e085f054 <[ext3].text.start+3ff4/a7a8> Trace; e085eaf0 <[ext3].text.start+3a90/a7a8> Trace; c012b193 Trace; e085cbbb <[ext3].text.start+1b5b/a7a8> Trace; c0136c68 Trace; c0108957 Code; c0138129 <_EIP>: Code; c0138129<= 0: 89 02 mov%eax,(%edx) <= Code; c013812b 2: 89 71 50 mov%esi,0x50(%ecx) Code; c013812e 5: 8b 46 20 mov0x20(%esi),%eax Code; c0138131 8: 8d 56 20 lea0x20(%esi),%edx Code; c0138134 b: 89 58 04 mov%ebx,0x4(%eax) Code; c0138137 e: 89 41 54 mov%eax,0x54(%ecx) Code; c013813a 11: 89 53 04 mov%edx,0x4(%ebx) Apr 3 11:38:43 snook kernel: kernel BUG at transaction.c:248! Apr 3 11:38:43 snook kernel: invalid operand: Apr 3 11:38:43 snook kernel: CPU:0 Apr 3 11:38:43 snook kernel: EIP:0010:[]Not tainted Apr 3 11:38:43 snook kernel: EFLAGS: 00210286 Apr 3 11:38:43 snook kernel: eax: 0076 ebx: c6cf04e0 ecx: 0001 edx: c657e000 Apr 3 11:38:43 snook kernel: esi: d6ace000 edi: c24fd560 ebp: c1afa5c0 esp: d6acfcac Apr 3 11:38:43 snook kernel: ds: 0018 es: 0018 ss: 0018 Apr 3 11:38:43 snook kernel: Process dumper (pid: 3959, stackpage=d6acf000) Apr 3 11:38:43 snook kernel: Stack: e0855060 e085490f e08548e4 00f8 e08550e0 d065b810 d065b810 e0869b20 Apr 3 11:38:43 snook kernel:e085e003 c24fd560 000
Strange problems backing up Windows users with Samba
Hi all, I am running AMANDA v2.4.4 on Solaris and all was working fine until recently. Now I get bizarre error messages through my AMANDA logs like these: /-- saturn.res //spock/E$ lev 1 STRANGE sendbackup: start [saturn.research.ets.org://spock/E$ level 1] sendbackup: info BACKUP=/local/research/samba/bin/smbclient sendbackup: info RECOVER_CMD=/local/research/bin/gzip -dc +|/local/research/samba/bin/smbclient -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? Call timed out: server did not respond after 2 milliseconds opening remote file +\ebsco-1064\cueanalysisnew.zip (\ebsco-1064\) ? Call timed out: server did not respond after 2 milliseconds opening remote file +\ebsco-1064\cues.lst (\ebsco-1064\) ? Call timed out: server did not respond after 2 milliseconds opening remote file +\ebsco-1064\difficulties-td80.txt (\ebsco-1064\) ? Call timed out: server did not respond after 2 milliseconds opening remote file +\ebsco-1064\difficulties-td80.xls (\ebsco-1064\) etc.. Tons upon tons of "Call timed out: server did not respond after 2 milliseconds" error messages. Is there a fix for this somewhere? I am wondering if possibly it's a samba problem, but I am not sure. The machine it's trying to back up is a windows machine and is working fine as far as I know. Any help would be greatly apprciated! Thanks, Tom __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com
Re: Sharing index between configs ("full" and "incrementals")?
On 2003.04.03 16:54, Jon LaBadie wrote: On Thu, Apr 03, 2003 at 09:51:25AM +0200, Toralf Lund wrote: > As I've indicated earlier, I want to write full backups to tape, but keep > some or all of the incremental on the harddisk, so I've set up two > different configs; one with "skip-incr" that will write to tape, and one > without full dumps that will dump to harddisk, via chg-multi and a > chg-multi.conf where all slots point to file:. The > disklist is shared between the configs. The question is simply, can they > share the index as well? Will everything work all right if I simply > specify the same indexdir for both configs? I believe they can, however, you can't do an incremental for a config without first doing a level 0. Well, I'm also trying to tell Amanda that a full backup is done off-line by using "force" commands, with arguments based on data from the first (full) backup. And on recovery, the incrementals are ?useless? without the level 0. Really? I thought I could: 1. Do recovery with the full config, then the incremental, to reproduce the data fully. 2. Fetch individual files from the incremental config, provided that they were updated recently enough to be included on the incremenal-dump. Note that my primary concern here is in many ways the recovery of individual files. Not that I'm not worried about loosing everything on a disk crash, but I'm not sure I will use amrecover or the indexes on that event. (And after all, files being deleted by mistake *is* a lot more likely than a major crash.) The common index may solve the first problem, but I don't think it will help the second. Which is really the one I wanted solved, of course - Toralf
Re: magazine article, Solaris file system snapshots
Jon LaBadie wrote: In the current "SysAdmin" magazine (April, 2003, Vol. 12, No. 4, Pgs 43-47), there is an article by Julian Briggs on using a Solaris feature Not being a Linux user Paul, are the LVM, RAID, and filesystem snapshots a standard feature of your system? How have you incorporated them into amanda backups? RAID, and LVM are standard features of a recent Linux. With LVM you can make snapshots, similar to "fssnap" on Solaris 8. I just implemented a first working version, using a gnutar wrapper script, of using snapshot-backups with amanda. I was investigating how to incorporate the feature more solid it into the program. When I make more progress and have a stable version, I will surely send something to the list. -- 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: Sharing index between configs ("full" and "incrementals")?
On Thu, Apr 03, 2003 at 09:51:25AM +0200, Toralf Lund wrote: > As I've indicated earlier, I want to write full backups to tape, but keep > some or all of the incremental on the harddisk, so I've set up two > different configs; one with "skip-incr" that will write to tape, and one > without full dumps that will dump to harddisk, via chg-multi and a > chg-multi.conf where all slots point to file:. The > disklist is shared between the configs. The question is simply, can they > share the index as well? Will everything work all right if I simply > specify the same indexdir for both configs? You can't share the index directory for both config. Amanda will remove the index file that don't belong to the config. Amanda (amrecover) can't recover files from multiple config. But you can use a third config for recovery: Copy the index files to the new config (or symlink) Set your 'labelstr' to accept both label. Merge the tapelist files. Copy the LOGDIR/log..x to the new config (or symlink) (You can change the last number) Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Amanda TCP Reset Problem with CygWin
> /-- watertown. /home/watertown lev 0 STRANGE
> sendbackup: start [watertown.ott.precidia.com:/home/watertown level 0]
> sendbackup: info BACKUP=/usr/bin/tar
> sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/bin/tar -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> | Total bytes written: 20480 (20kB, ?B/s)
> ?
> ? gzip: stdout: Cannot send after transport endpoint shutdown
> ??error [compress returned 1]? dumper: strange [missing size line from sendbackup]
> ? dumper: strange [missing end line from sendbackup]
> \
>
> The same error message is on the client (naturally). So, it looks like gzip
> is still trying to send to the socket when sendbackup is closing the socket.
>
> My guess is that the path was closed after it had been dup'd and so an
> extra close wouldn't break things but a shutdown would. I'm going to try
> to figure out if that is the case.
So... I went in to sendbackup-gnutar.c and #if'd out some lines:
/* close the write ends of the pipes */
aclose(dumpin);
aclose(dumpout);
#if 0 // moved to sendbackup.c
aclose(dataf);
aclose(mesgf);
if (options->createindex)
aclose(indexf);
#endif
Then I went in to sendbackup.c and added the same there:
program->start_backup(g_options->hostname, disk, amdevice, level, dumpdate,
dataf, mesgpipe[1], indexf);
parse_backup_messages(mesgpipe[0]);
#if 1 // moved from sendbackup-*.c
dbprintf(("%s: closing paths (%d,%d,%d)\n",debug_prefix(NULL),indexf,mesgf,dataf));
shutdown(dataf,2);
aclose(dataf);
shutdown(mesgf,2);
aclose(mesgf);
if (!interactive && options->createindex) {
shutdown(indexf,2);
aclose(indexf);
}
#endif
This way, there is no longer a local "aclose(dataf)" and "aclose(mesgf)"
command while there are external processes still writing to that socket.
Things have improved, but still don't look correct. Here's the message
from the server:
/-- watertown. /home/watertown lev 1 FAILED [data timeout]
sendbackup: start [watertown.ott.precidia.com:/home/watertown level 1]
sendbackup: info BACKUP=/usr/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| Total bytes written: 10240 (10kB, ?B/s)
\
Unfortunately, I didn't have tcpdump running to learn more about exactly
what happened. Tonight, I guess. What perplexes me, though, is that
the socket shutdown code never seemed to be run becuase there was nothing
in the sendbackup log with the "closing paths (%d,%d,%d)" message I added:
sendbackup: debug 1 pid 1332 ruid 0 euid 0: start at Wed Apr 2 20:23:45 2003
/usr/local/lib/amanda/sendbackup: version 2.4.3
parsed request as: program `GNUTAR'
disk `/home/watertown'
device `/home/watertown'
level 1
since 2003:4:2:1:20:34
options
`|;bsd-auth;compress-fast;index;exclude-file=^(#|Backup.of)|.(bak|tmp|fla|fst|hex|lib|lst|m
51|wav|mp3|mpg|mpeg|avi|mov|obj|omf|prn|swp)$|~$;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.015: stream_server: waiting for connection: 0.0.0.0.597
sendbackup: time 0.016: stream_server: waiting for connection: 0.0.0.0.598
sendbackup: time 0.017: stream_server: waiting for connection: 0.0.0.0.599
sendbackup: time 0.018: waiting for connect on 597, then 598, then 599
sendbackup: got data path #0
sendbackup: time 0.035: stream_accept: connection from 10.0.1.2.3442
sendbackup: time 0.039: stream_accept: connection from 10.0.1.2.3443
sendbackup: got mesg path #7
sendbackup: time 0.043: stream_accept: connection from 10.0.1.2.3444
sendbackup: time 0.043: got all connections
sendbackup: time 0.044: spawning /usr/bin/gzip in pipeline
sendbackup: argument list: /usr/bin/gzip --fast
sendbackup-gnutar: time 0.094: pid 3564: /usr/bin/gzip --fast
sendbackup-gnutar: time 0.100: doing level 1 dump as listed-incremental from
/var/lib/amanda/gnutar-lists/watertown.ott.
precidia.com_home_watertown_0 to
/var/lib/amanda/gnutar-lists/watertown.ott.precidia.com_home_watertown_1.new
sendbackup-gnutar: time 0.114: doing level 1 dump from date: 2003-04-01 1:25:14 GMT
sendbackup: time 0.199: spawning /usr/local/lib/amanda/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory /home/watertown
--listed-incremental /var/lib/amanda/gnuta
r-lists/watertown.ott.precidia.com_home_watertown_1.new --sparse --ignore-failed-read
--totals --exclude-from /tmp/amand
a/sendbackup._home_watertown.20030402202345.exclude .
sendbackup: time 0.290: started index creator: "/usr/bin/tar -tf - 2>/dev/null | sed
-e 's/^\.//'"
sendbackup-gnutar: time 0.296: /usr/local/lib/amanda/runtar: pid 3604
sendbackup: time 0.693: 53:size(|): Total bytes written: 10240 (10kB, ?B/s)
sendbackup: time 0.826: index created successfully
Why was that message not there? Did the program exit? Th
Re: Backup of ACLs
On Thu, Apr 03, 2003 at 01:15:32PM +0200, Dalton Hubert wrote: > Hi, > > we are thinking about using ACLs (extended attributes and access control > lists) on our file server, of which we make a full backup by using Amanda > every night. > > So my question concerning the backup is: > Can Amanda also backup ACLs? The problem with your question is that amanda doesn't backup anything. It manages backups done by other programs. The common programs are gnutar and the OS's file system dump program. The question then becomes can the backup program you choose save and restore ACL's. Best way to answer that is to read the local documentation and run a test backup and recovery. Amanda is not needed to check this out. > Do i have to change something in my configuration? > > I have heard something about star, is this really necessary or can i use > tar? > > If i must use star instead of tar, where i must configure this? > (which entry in which file?) During configuration and build of amanda you specify what program is your "gnutar". If you point it at star, amanda will try to use it. But beware that amanda will think it is gnutar and use gnutar options. They may, or may not, be the same for star. BTW what's star? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Sharing index between configs ("full" and "incrementals")?
On Thu, Apr 03, 2003 at 09:51:25AM +0200, Toralf Lund wrote: > As I've indicated earlier, I want to write full backups to tape, but keep > some or all of the incremental on the harddisk, so I've set up two > different configs; one with "skip-incr" that will write to tape, and one > without full dumps that will dump to harddisk, via chg-multi and a > chg-multi.conf where all slots point to file:. The > disklist is shared between the configs. The question is simply, can they > share the index as well? Will everything work all right if I simply > specify the same indexdir for both configs? I believe they can, however, you can't do an incremental for a config without first doing a level 0. And on recovery, the incrementals are ?useless? without the level 0. The common index may solve the first problem, but I don't think it will help the second. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Backup of ACLs
Amanda manages backups using whatever native tool it's configured to use. You don't state what platform you're using I can't speculate as to an ACL-aware tool for it.
Re: magazine article, Solaris file system snapshots
On Thu, Apr 03, 2003 at 09:08:01AM +0200, Christopher Odenbach wrote: > > > > You mean smaller than my 400MHz pc running the latest Solaris > > > version? :) > > > > Ouch. Say, smaller than an E450. :) > > Hey - we use snapshots on our Ultra 1 servers with about 142 MHz, > running Solaris 8, works like a charm! :-) Do you use the snapshots for amanda backups? If so, how similar is your procedure to what J. Briggs describes? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: magazine article, Solaris file system snapshots
On Thu, Apr 03, 2003 at 09:06:05AM +0200, Paul Bijnens wrote: > Jon LaBadie wrote: > >On Wed, Apr 02, 2003 at 09:36:25AM -0600, Kirk Strauser wrote: > > > >>At 2003-04-02T07:28:33Z, Jon LaBadie <[EMAIL PROTECTED]> writes: > >> > >>>In the current "SysAdmin" magazine (April, 2003, Vol. 12, No. 4, Pgs > >>>43-47), there is an article by Julian Briggs on using a Solaris feature > >>>of > >>>"file system snapshots" with amanda backups. > >> > >>Very nice; thanks for the pointer. > >> > >>I'd also point out that FreeBSD 5.0 and beyond also supports filesystem > >>snapshots, so this will also be of interest on smaller machines in the > >>near > >>future. > > > >You mean smaller than my 400MHz pc running the latest Solaris version? :)) > > On my 333 MHz fileserver with Linux 2.4.18 it even works :-) > 2 disks 80 GByte with software RAID 1 and lvm snapshots, > all on a pc that nobody wants on his desk! Not being a Linux user Paul, are the LVM, RAID, and filesystem snapshots a standard feature of your system? How have you incorporated them into amanda backups? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
unsubscribe herbert@visi.com
unsubscribe [EMAIL PROTECTED]
Re: Backup of ACLs
On Thu, 3 Apr 2003 at 1:15pm, Dalton Hubert wrote > we are thinking about using ACLs (extended attributes and access control lists) > on our file server, of which we make a full backup by using Amanda every night. > > So my question concerning the backup is: > Can Amanda also backup ACLs? Amanda doesn't do backups. Amanda *schedules* backups. Amanda uses another program (a dump, or GNUtar) to actually do the backups. > Do i have to change something in my configuration? Well, since we don't know what your config is now... > I have heard something about star, is this really necessary or can i use tar? tar won't get ACLs. An FS specific dump program probably will. > If i must use star instead of tar, where i must configure this? > (which entry in which file?) I don't know if star is drop-in replaceable for tar. ISTR that it only does one level of incrementals, which amanda won't like if it needs to bump some backups. > Any experiences with ACL in combination with Amanda? I just started using ACLs on one of my Linux servers using XFS. The partition is too large for a tape, so I can't use xfsdump (which will get the ACLs). What I do is have cron run '/usr/bin/getfacl -R $DIR' on the $DIR in which I'm using ACLs. I dump the output of that somewhere else on disk that gets backed up. If I have to restore that $DIR, I can just run 'setfacl -R' on the directory after I restore it from tape. It may not be elegant, but it's what I came up with. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Backup of ACLs
On Thu, 2003-04-03 at 13:15, Dalton Hubert wrote: > Hi, > > we are thinking about using ACLs (extended attributes and access control lists) > on our file server, of which we make a full backup by using Amanda every night. > > So my question concerning the backup is: > Can Amanda also backup ACLs? That depends on what filesystem you want to use. If you first install SGI's XFS, and then rebuild amanda, amanda will use xfsdump (which is capable of backing up acl's/extended attributes) automagically. This works for me. hope this'll help you out.. roger > > Do i have to change something in my configuration? > > I have heard something about star, is this really necessary or can i use tar? > > If i must use star instead of tar, where i must configure this? > (which entry in which file?) > > Any experiences with ACL in combination with Amanda? > > Thank you for information, > best regards, > Dalton >
Re: backup with exclude
-Messaggio originale- Da: Valeria Cavallini [mailto:[EMAIL PROTECTED] Inviato: giovedi 3 aprile 2003 10.59 A: [EMAIL PROTECTED] Oggetto: backup with exclude Hi, I've read some tread on the hacker newsgroup and I've found that someone talks about the option exclude to exclude more then one pattern. I'd like to exclude from backup some type of file, such mp3 avi divx, but I didn't find the end of the tread, did anybody solved this problem? The explanation is in the "amanda" manpage; look for "exclude" under DUMPTYPE SECTION. Note that the exclusions support is a lot more flexible in version 2.4.3 onwards than it used to be in the past. - Toralf
skip-full/skip-incr vs strategy
I'm a bit confused about the "strategy" setting and the "skip-full"/"skip-incr". Although the functionality of these is not exactly the same, there definitely seems to be an overlap. Can someone explain the idea behind these settings, and why there isn't just one way of choosing what to include on the backup? -- Toralf Lund <[EMAIL PROTECTED]> +47 66 85 51 22 ProCaptura AS +47 66 85 51 00 (switchboard) http://www.procaptura.com/~toralf +47 66 85 51 01 (fax)
Backup of ACLs
Hi, we are thinking about using ACLs (extended attributes and access control lists) on our file server, of which we make a full backup by using Amanda every night. So my question concerning the backup is: Can Amanda also backup ACLs? Do i have to change something in my configuration? I have heard something about star, is this really necessary or can i use tar? If i must use star instead of tar, where i must configure this? (which entry in which file?) Any experiences with ACL in combination with Amanda? Thank you for information, best regards, Dalton
backup with exclude
-Messaggio originale- Da: Valeria Cavallini [mailto:[EMAIL PROTECTED] Inviato: giovedi 3 aprile 2003 10.59 A: [EMAIL PROTECTED] Oggetto: backup with exclude Hi, I've read some tread on the hacker newsgroup and I've found that someone talks about the option exclude to exclude more then one pattern. I'd like to exclude from backup some type of file, such mp3 avi divx, but I didn't find the end of the tread, did anybody solved this problem? many thanks Valeria
Re: Slow dumper
On Tue May 28 2002 05:09, Bartho Saaiman wrote:
I have a problem where my dumper is slow and the taper seems to be
faster:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min)11:21
Dump Time (hrs:min)9:42 9:42 0:00
Output Size (meg) 14818.314818.30.0
Original Size (meg) 20804.720804.70.0
Avg Compressed Size (%)71.2 71.2--
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 434.8 434.8--
Tape Time (hrs:min)1:37 1:37 0:00
Tape Size (meg) 14818.414818.40.0
Tape Used (%) 74.1 74.10.0
Filesystems Taped 1 1 0
Avg Tp Write Rate (k/s) 2606.1 2606.1--
Is there a way of changing this to speedup backups.
You have 1 DLE, size 20 Gbyte, dumping to holdingdisk at a speed
of 434.8 Kbytes/sec. Then it is written to tape at a speed of 2606
Kbytes/sec.
Amanda cannot take advantage of parallelizing different DLE's
if there is only one.
You do have the advantage that your tape is written at the best speed,
without having to stop/start the drive (bad for the tape and drive and
sometimes wasting tape capacity too).
Also, if you add more DLE's (other computers) they will be done
in parallel, and will not add much (if any) to your total run time.
So you have a nice growth path :-)
I see you also compress the backup. You can play a little with the
compression settings in your dumptype:
- where to compress: 'server' or 'client (use the fastest CPU!)
- algorithm: 'fast' or 'best' (fast can much faster than 'best')
Set something like: "compress server fast".
(But this will not speed up your process from 434 k/s to 2600 k/s.)
Maybe you to investigate a little if there is another reason (besides
a slow file server) why the dumping is so slow.
--
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 *
***
[no subject]
subscribe amanda-users
Sharing index between configs ("full" and "incrementals")?
As I've indicated earlier, I want to write full backups to tape, but keep some or all of the incremental on the harddisk, so I've set up two different configs; one with "skip-incr" that will write to tape, and one without full dumps that will dump to harddisk, via chg-multi and a chg-multi.conf where all slots point to file:. The disklist is shared between the configs. The question is simply, can they share the index as well? Will everything work all right if I simply specify the same indexdir for both configs? -- Toralf Lund <[EMAIL PROTECTED]> +47 66 85 51 22 ProCaptura AS +47 66 85 51 00 (switchboard) http://www.procaptura.com/~toralf +47 66 85 51 01 (fax)
Escalate Your Cup Size Quickly n31il
Enlarge Your Breasts Quickly And Easily! To Learn More, Click Here To Visit Our Website! 100% Naturally With No Surgery! It will dramatically increase the size of any womans bust sizeNo negative side effects whatsoever This product will help you achieve firmer, larger and more beautiful breasts! Learn More, Click Here To Visit Our Website! To Take Yourself Off our list click
