New drive, old problem.
Hi all; I had to give up and install another of those ctl-96's this morning. The old one seemed to be cooking the tapes (they were near 140F when I ejected them) and I had to replace the one in slot 3 as it kept giving me an error 40 on the changers display. NDI what an error 40 realy is at this point. And I'm back to a couple of old problems. 1st, and most important is this: I dd'd good labels to a replacement tape in slot 3 (changer number, next to last in a 4 slot magazine), edited the label and did slot 4 while I was at it. Labels checked with dd of course, and forced dumped to the media by writing another 4+ megs after writing the label. So, after doing a startx, leaving the tape in slot 4 loaded, I opened a shell, made myself amanda and ran amcheck. This is what I got back: Amanda Tape Server Host Check - Holding disk /dumps: 17528692 KB disk space available, using 17016692 KB amcheck-server: slot 0: date 20040111 label DailySet1-13 (active tape) amcheck-server: slot 1: date 20040406 label DailySet1-11 (active tape) amcheck-server: slot 2: date 20040111 label DailySet1-12 (exact label match) NOTE: skipping tape-writable test Tape DailySet1-12 label ok Server check took 264.645 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.654 seconds, 0 problems found (brought to you by Amanda 2.4.5b1-20040405) Note that it did not know that slot 4 (3 to amanda) was loaded, but did then load the next slot (1) correctly. Is there not some command that can query the changer to find out which slot is actually loaded so that amanda can realign herself that could be incorporated into amcheck? Because amcheck only checks the slots it thinks it know about, there have been many occasions when it didn't find the tape it wanted on the first pass because it never rechecked the slot the tape was in when it starts out out of sync with the real world due to the magazine being reloaded. mtx gives me this report now, which is correct, but if I were to manually load a different slot, amcheck will get confused, while mtx still gets it right. [EMAIL PROTECTED] root]# mtx -f /dev/sg0 status Storage Changer /dev/sg0:1 Drives, 4 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 3 Loaded) Storage Element 1:Full Storage Element 2:Full Storage Element 3:Empty Storage Element 4:Full All amcheck needs to know is the actual slot thats loaded if there is one, or to load the last known slot to get started, in which case it would properly cycle thru and find the tape it wants if its in the magazine. It could also avoid that by issueing a command to actually load the last slot amcheck knows about, thereby ejecting the one thats (as far as its concerned) in the wrong slot. The other problem is that this drive, once its been told to load a tape, will not stop at ejecting the current one, but will load the next one if its not at the end of the magazine. I checked the dip switches, but they all seem to be set identicaly to the old drive. This one however looks like a much newer production run. The special chips are all about half the size of the older drives chips. Bah, I'm gettin picky in my old age :) -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Amanda backup strategy thoughts, full and incremental backups to tape once a week.
Hello All, I would like to ask a general Amanda backup 'strategy' question here, given by backup 'goals' below. I have a configured and working Amanda set-up but I want to try and fit a backup policy that I believe is best suited to our site around Amanda. I have an 8-tape (DLT 35/70gb each) auto changer library linked to Amanda via mtx, this works well. I want to do a full backup of various file systems on a remote host once a week and then, ideally, incremental backups once a day to that same tape. At the end of a week's backup, the tape should switch. One week's backup is far less than a single tape's capacity. I would like to be able to hold 8 weeks worth of backups on tape, that is one tape a week and then reuse the oldest tape. I'm not sure this is possible with Amanda.. as I believe I can't append the daily incremental backups onto the same tape as the full backups. Is it the case that if I want to run Amanda every day that I would also have to use a tape every day, thus meaning the tapes in the library are all used after a week. I'm fixed in the number of tapes I can use and can't add/replace them, so they would get reused after a week and wouldn't provide much of a 'backup horizon'. If this isn't possible does anyone have some suggestions? I was thinking I could do the incremental backups to a hard disk area on the tape server each night and then run Amanda once a week to archive the full backups plus the HDD incremental ones. Many thanks in advance for everyone's thoughts. William.
TCP Port Usage
Hi all. I have compiled Amanda using the following options: ./configure --with-user=amanda \ --mandir=/usr/share/man \ --prefix=/usr \ --infodir=/usr/share/info \ --sysconfdir=/etc \ --libdir=/usr/lib \ --libexecdir=/usr/lib/amanda \ --localstatedir=/var/lib \ --with-index-server=admin01 \ --with-gnutar-listdir=/var/lib/amanda/gnutar-lists \ --with-smbclient=/usr/bin/smbclient \ --with-amandahosts \ --with-gnutar=/bin/tar \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-debugging=/tmp/amanda \ --with-tape-server=admin01 \ --with-configdir=/etc/amanda \ --with-tcpportrange=52000,6 \ --with-udpportrange=850,851 As you can see, Ive ensured the tcp port-range used is between 52000 and 6. There are no problems when using amcheck. However, when trying to use amdump, I cannot connect to the client and my firewall reports the following packet drops: Shorewall:all2all:REJECT:IN= OUT=bond1 SRC="" DST=192.168.100.20 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=14897 DF PROTO=TCP SPT=55003 DPT=46882 WINDOW=5840 RES=0x00 SYN URGP=0 i.e. packet from Amanda server source port 55003 (within the range I built Amanda with) is trying to be sent to the client on client port 46882 why is Amanda trying to use this port when I have configured it not to? Thanks for any replies in advance. Dean Pullen
Re: Amanda backup strategy thoughts, full and incremental backups to tape once a week.
On Tue, Apr 06, 2004 at 12:12:05PM +0100, William Hargrove wrote: Hello All, I would like to ask a general Amanda backup 'strategy' question here, given by backup 'goals' below. I have a configured and working Amanda set-up but I want to try and fit a backup policy that I believe is best suited to our site around Amanda. I have an 8-tape (DLT 35/70gb each) auto changer library linked to Amanda via mtx, this works well. I want to do a full backup of various file systems on a remote host once a week and then, ideally, incremental backups once a day to that same tape. At the end of a week's backup, the tape should switch. One week's backup is far less than a single tape's capacity. I would like to be able to hold 8 weeks worth of backups on tape, that is one tape a week and then reuse the oldest tape. I'm not sure this is possible with Amanda.. as I believe I can't append the daily incremental backups onto the same tape as the full backups. Is it the case that if I want to run Amanda every day that I would also have to use a tape every day, thus meaning the tapes in the library are all used after a week. I'm fixed in the number of tapes I can use and can't add/replace them, so they would get reused after a week and wouldn't provide much of a 'backup horizon'. If this isn't possible does anyone have some suggestions? I was thinking I could do the incremental backups to a hard disk area on the tape server each night and then run Amanda once a week to archive the full backups plus the HDD incremental ones. Where is that Top Ten Questions document when you need it? Amanda will not reuse a tape for a new run of amdump, fulls or incrementals, until it cycles through tapecycle number of tapes. So you are correct, amanda will NOT append a second amdump to a tape. Amanda only overwrites tapes! However, an amflush can overwrite a tape with multiple dumps from the holding disk. Thus collect as many amdumps as you want with the tape offline. Then amflush when you want to tape them. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda backup strategy thoughts, full and incremental backups to tape once a week.
Here's a strategy that I implemented about a month ago that is working pretty well so far: 1. run amdump every night to large RAID w/o tape, mix of full and incr 2. run script to separate images to amanda-incr and amanda-full 3. when amanda-full exceeds size of tape, run amflush 4. when RAID approaches capacity, flush some incrs to tape Since it's a RAID, there is less chance it will go to crap than a regular disk partition, but it is still possible. And if it does, I still have the full dumps on tape to fall back on. To give you some gauge of capacities, I'm backing up about 300 GB of disks, have ~600 GB RAID5 (on a Snap 4500) and am using 100/200 GB LTO (Ultrium-1) tapes. So far, it's mostly web servers, but I haven't moved everything to the new backup cycle yet. I have flushed 2 tapes worth of full dumps, and accumulated about 167 GB of incrementals that are still on the RAID. The goal and idea is that 90% of the time, I will only need to load one tape to do a restore, and the rest will come out of holding files. Even better, there is a good chance that the tape that I need will be the last one that I flushed, so I won't have to change the tape. /snap/amanda-hd is the directory that amanda.conf looks for, which is actually a symbolic link to /snap/amanda-full. Therefore, I just move the incremental dumps from amanda-full to amanda-incr, both actually on the same filesystem (a simple directory rename in the filesystem inode table). If I need to flush incrementals, I just change the link amanda-hd - amanda-incr and run the flush (this could be done more elegantly with a patch, but this is so easy, so why bother?) In the cron job, I make sure amanda-hd - amanda-full before amdump runs. I'm using NFSv3 to XFS filesystem through a dedicated 100baseTX FD connection, so I'm using a chunksize of ~600 GB, and that makes the rename script very simple since I don't have to worry about any backup getting split into chunks. AFAIK NFSv3 and XFS both support 64-bit addressing, so I shouldn't run into any filesize limits. --jonathan
Re: Amanda backup strategy thoughts, full and incremental backups to tape once a week.
In a message dated: Tue, 06 Apr 2004 12:12:05 BST William Hargrove said: I was thinking I could do the incremental backups to a hard disk area on the tape server each night and then run Amanda once a week to archive the full backups plus the HDD incremental ones. I did this once, way back when all I had was a single DLT drive and no autoloader. I would just leave the drive empty all week, and on Friday mornings I would pop that week's tape in then amflush everything to tape. When that was done, I would place the weekend tape in the drive and the full dumps on Saturday night would go direct to tape, or, if I forgot, end up on the holding disk for amflushing Monday morning. This worked quite well IMO for the small environment I had at the time. HTH, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
DDS3 Auto loader on Solaris
hello, I'm a newbie to amanda and mtx. I'm running solaris 2.6(sprac). Want to know how to configure the DDS3 autoloader to do backingup. I don't use any commercial software. I need to use the 6 slots of the cartridge for different filesystem backups. Also does amanda support resuming or continuing the backup to the next tape. Thanks for your time R - Disclaimer and Confidentiality This material has been checked for computer viruses and although none has been found, we cannot guarantee that it is completely free from such problems and do not accept any liability for loss or damage which may be caused. Please therefore check any attachments for viruses before using them on your own equipment. If you do find a computer virus please inform us immediately so that we may take appropriate action. This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The views expressed in this message are those of the individual sender, and may not necessarily be that of JKCS. ---
