Broken Pipe errors
I recently added a new machine to my backups, and seem to be having a problem with a couple of file systems with index tee cannot write [Broken pipe] errors. Client is Solaris 7 Server is Solaris 7 amanda version 2.4.2p2 gnutar 1.13.19 firewall between the two servers, but no security restrictions (as in all other backups work fine). Server is NAT'ed at firewall I've run some tests just backing one of those filesystems up, and no matter how I fiddle with the dumptype (thinking compression in particular might be part of the problem) I cannot get this error to go away. In test mode I'm trying to dump only to holding disk which has 11.5 GB free. The file system in question is only ~1.5 GBs. Larger filesystems on the same host can be backed up with the same dumptype parameters with no problems. When I was watching the backup being performed with amstatus it showed data being transferred, and the correct file was being created and updated on the server. I think when it stopped updating, the size sent reported by amstatus was a few KB (32?) over the estimated backup size (didnt write the data down like a fool) - I realize this may or may not mean a thing, but just throwing it out there. Here are some (hopefully!) appropriate log files (they dont tell me too much): = log.20020225.0 from server = START planner date 20020225 START driver date 20020225 ERROR taper no-tape [no tape online] FINISH planner date 20020225 STATS driver startup time 2.472 FAIL dumper rnbuyer /export/home 0 [mesg read: Connection timed out] sendbackup: start [rnbuyer:/export/home level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end FINISH driver date 20020225 time 7744.120 = amdump.1 from server = amdump: start at Mon Feb 25 10:38:00 EST 2002 planner: pid 5123 executable /usr/local/libexec/planner version 2.4.2p2 planner: build: VERSION=Amanda-2.4.2p2 planner:BUILT_DATE=Mon Jul 30 12:22:45 EDT 2001 planner:BUILT_MACH=SunOS utl-atl-05 5.7 Generic_106541-15 sun4u sparc SUNW,Ultra-4 planner:CC=gcc planner: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin planner:libexecdir=/usr/local/libexec mandir=/usr/local/man planner:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda planner:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/dsk/ planner:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump planner:RESTORE=/usr/sbin/ufsrestore planner:SAMBA_CLIENT=/usr/local/samba/bin/smbclient planner:GNUTAR=/usr/local/bin/tar planner:COMPRESS_PATH=/usr/local/bin/gzip planner:UNCOMPRESS_PATH=/usr/local/bin/gzip planner:MAILER=/usr/bin/mailx planner:listed_incr_dir=/usr/local/var/amanda/gnutar-lists planner: defs: DEFAULT_SERVER=utl-atl-06 DEFAULT_CONFIG=DailySet1 planner:DEFAULT_TAPE_SERVER=utl-atl-06 planner:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE planner:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS planner:CLIENT_LOGIN=siteops FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast planner:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc planner: dgram_bind: socket bound to 0.0.0.0.603 READING CONF FILES... startup took 0.010 secs SETTING UP FOR ESTIMATES... setting up estimates for rnbuyer:/export/home rnbuyer:/export/home overdue 11744 days for level 0 setup_estimate: rnbuyer:/export/home: command 4, options: last_level -1 next_level0 -11744 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates took 0.000 secs GETTING ESTIMATES... driver: pid 5122 executable /usr/local/libexec/driver version 2.4.2p2 driver: send-cmd time 0.005 to taper: START-TAPER 20020225 taper: pid 5124 executable taper version 2.4.2p2 driver: started dumper0 pid 5126 dumper: dgram_bind: socket bound to 0.0.0.0.606 dumper: pid 5126 executable dumper version 2.4.2p2, using port 606 dumper: dgram_bind: socket bound to 0.0.0.0.607 dumper: pid 5127 executable dumper version 2.4.2p2, using port 607 driver: started dumper1 pid 5127 driver: started dumper2 pid 5128 driver: started dumper3 pid 5129 driver: started dumper4 pid 5130 driver: started dumper5 pid 5131 dumper: dgram_bind: socket bound to 0.0.0.0.608 dumper: pid 5128 executable dumper version 2.4.2p2, using port 608 dumper: dgram_bind: socket bound to 0.0.0.0.610 dumper: pid 5130 executable dumper version 2.4.2p2, using port 610 dumper: dgram_bind: socket bound to 0.0.0.0.612 dumper: pid 5132 executable dumper version 2.4.2p2, using port 612 dumper: dgram_bind: socket bound to 0.0.0.0.611 dumper: pid 5131 executable dumper version 2.4.2p2, using port 611 driver: started dumper6 pid 5132 dumper: dgram_bind: socket bound to 0.0.0.0.609 dumper: pid 5129 executable dumper version
RE: Disaster Recovery on Windows
my personal strategy is as follows: - I have Imagecast images for our 4 generic server types (NT/2000 web and db). this allows me to quickly deploy the OS and necessary applications. There are several products like Imagecast out on the market for imaging windows partitions. - change the network configurations on the box by hand - restore critical application and database files backed-up using amanda I've tested this 3 times, and actually did one real DR late one evening. And the lesson I can tell you from years of experience is to test your DR plans early and often - it will pay off when you actually have to perform one with every manager in the company calling you every minute for a status update... Matt +- Matthew Galer Senior Systems Engineer [EMAIL PROTECTED] 770-453-9001 x127 -Original Message- From: Jan Boshoff [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 3:58 PM To: Amanda Users Subject: Disaster Recovery on Windows Hi all I just had a thought and would like to probe the great minds of this list. Would anyone do a disaster recovery type of restore of a Winbox that was backed up using smbclient?I'm currently backing up the complete winbox, but it occured to me that I don't know how I would restore if something happened to the Winbox that we needed to restore the complete drive. I mean, you need to have Win installed for smbclient to talk to it accross the network. Any thoughts would be helpful! Thanks again! Jan -- Jan Boshoff PhD Student, Chemical Engineering Univ. of Delaware, DE USA www.che.udel.edu/research_groups/nanomodeling
amrecover issue
Greetings. I just got amanda up and backing things up fine. The next step is obviously to test restores, and I've come up with some questions/concerns in this area. first, I have NO tape drive yet - I'm trying to pry some dollars out of managements' hands for this, but no luck so far - so all backups are being done to holding disks only (RAID 0+1). anyway, I wanted to restore a file from yesterdays backup as a test. from log.20010805.0: SUCCESS dumper utl-atl-06 /export/home 20010805 0 [sec 59.666 kb 393280 kps 6591.3 orig-kb 393260] so a full backup was done successfully. I went ahead and verified the file in question was in the index file: [siteops@utl-atl-06 _export_home]$ zgrep sysedge.cf * 20010731_0.gz:07330357423/./siteops/sysedge.cf 20010805_0.gz:07331665340/./siteops/sysedge.cf ok, looks good to me! I su over to root and go into amrecover inside the /export/home directory [root@utl-atl-06 home]# amrecover Daily AMRECOVER Version 2.4.2p2. Contacting server on utl-atl-06 ... 220 utl-atl-06 AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2001-08-06) 200 Working date set to 2001-08-06. 200 Config set to Daily. 200 Dump host set to utl-atl-06. $CWD '/export/home' is on disk '/export/home' mounted at '/export/home'. 200 Disk set to /export/home. /export/home amrecover history 200- Dump history for config Daily host utl-atl-06 disk /export/home 201- 2001-08-05 0 /backup/hd2/20010805/utl-atl-06._export_home.0 0 201- 2001-08-04 1 /backup/hd2/20010804/utl-atl-06._export_home.1 0 201- 2001-08-03 1 /backup/hd1/20010803/utl-atl-06._export_home.1 0 201- 2001-08-02 1 /backup/hd3/20010802/utl-atl-06._export_home.1 0 201- 2001-08-01 1 /backup/hd2/20010801/utl-atl-06._export_home.1 0 201- 2001-07-31 0 /backup/hd2/20010731/utl-atl-06._export_home.0 0 200 Dump history for config Daily host utl-atl-06 disk /export/home amrecover setdate ---05 200 Working date set to 2001-08-05. amrecover ls 2001-08-05 app/ amrecover hmm.. not good - here is a directory listing for /export/home: [root@utl-atl-06 home]# ls -la total 26 drwxr-xr-x 6 root root 512 Dec 13 2000 . drwxrwxr-x 3 root sys 512 Dec 11 2000 .. drwxr-xr-x 5 root other512 Dec 15 2000 app drwxr-xr-x 8 aribaariba512 Dec 27 2000 ariba drwx-- 2 root root8192 Dec 11 2000 lost+found drwxr-xr-x 6 siteops siteops 512 Aug 6 12:19 siteops so we are missing a couple of directories in the interactive part of amrecover. Being semi-concerned at the integrity of the backups, I decided to try a manual restore, and so extracted the gzip-tar image from the holding disk with dd. Then unzipped it, and verified that the file was there: [root@utl-atl-06 20010805]# dd if=utl-atl-06._export_home.0 bs=32k skip=1 of=/tmp/out 12290+0 records in 12290+0 records out [siteops@utl-atl-06 /tmp]$ tar tvf out | grep sysedge.cf -rw--- siteops/siteops 2678 2001-04-20 16:41 07331665340/./siteops/sysedge.cf extracting the file and diff'ing the original confirms that it is ok. any suggestions? is this a by-product of only using holding disks, or something else? (note that I got similar results for all the filesystems I backed-up - some directories would appear in amrecover, some would not. Thanks in advance! Matt +- Matthew Galer [EMAIL PROTECTED] 770-453-9001 x149
