RE Monthly archival tapes
The usual way to go is to create a second amanda configuration for monthly archival only. From the doc: To do periodic archival full dumps, create a new Amanda configuration with its own set of tapes but the same disklist as the normal configuration (e.g. symlink them together). Copy amanda.conf, setting all dumpcycle values to 0 and record to no, e.g. in the global dumptype. If a changer is used, set runtapes very high so tape capacity is not a planning restriction. Disable the normal Amanda run, or set the hold file as described in Operating Amanda, so Amanda does not try to process the same client from two configurations at the same time. Joe Donner (sent by Nabble.com) [EMAIL PROTECTED] Envoyé par : [EMAIL PROTECTED] 08/08/2006 17:51 Veuillez répondre à Joe Donner [EMAIL PROTECTED] A amanda-users@amanda.org cc Objet Monthly archival tapes The amanda configuration I'm planning to put live this week includes these entries in amanda.conf: dumpcycle 0 (to force a full backup on every run, because all our data fit comfortably onto a single tape every night, and amdump only runs for 4.5 hours) runspercycle 5 days (to do an amdump each day Monday to Friday) tapecycle 21 tapes (to have 4 weeks' worth of historical backups + one extra tape for good measure) How do I now handle taking out one tape a month for long-term archiving? If my tapes are labelled daily-1, daily-2, etc., then how do I take out one tape a month but make sure that this doesn't confuse amanda, and that I will be able to restore from that tape in the future? Do I add a new tape each time in my numbering sequence? Can I reuse tape labels but somehow cause amanda to not overwrite the information needed to do restores from the archived tapes? Your insights will be much appreciated. -- View this message in context: http://www.nabble.com/Monthly-archival-tapes-tf2073538.html#a5709386 Sent from the Amanda - Users forum at Nabble.com.
Re: amanda-2.5.0p2 hanging on smbclient with configure
quote who=Gavin Henry quote who=Gavin Henry quote who=Gavin Henry quote who=Paul Bijnens On 2006-08-08 16:17, Gavin Henry wrote: Currently trying to compile 2.5.0p2 with: ./configure --with-user=amanda --with-group=disk --with-ssh-security --with-config=Suretec --with-changer-device=/dev/sg2 --with-tape-device=/dev/nst0 But configure just sits there at: checking for smbclient... /usr/bin/smbclient Upgrading to Samba 3.0.23b fixed it. Not sure, but can now move on. Thanks. Same when adding --with-smbclient=/usr/bin/smbclient If you do not need smbclient support, then you can configure with --without-smbclient and work around this problem. I have tried that, and with --with-smbclient=no. I've been going through configure.in to see what the probs are. If you do need it... then try to investigate what is blocking. It seems like configure is hanging in one of the next steps. Configure tries to find out what version of smbclient you have by running the command: smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null Looks like it's this. It just hangs. Must be smbclient, as it is taking forever, even when I jsut run: smblcient with no options. Forget it, will debug smbclient. Nothing wrong with Amanda. Thanks all. strace smbclient -d 5 show it sitting at: futex(0x2bdf2dc0, FUTEX_WAIT, 2, NULL Hmm. I just setup 2 clients on Fedora Core 5 with 2.5.0p2, and they both are fine. The server is on a SUSE 9.3 x86_64 box, that has (Is a Samba PDC too): free -m total used free sharedbuffers cached Mem: 3961296 3665 0 48 154 -/+ buffers/cache: 93 3868 Swap: 2070 0 2070 uname -a Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64 x86_64 x86_64 GNU/Linux df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage lsscsi [0:0:0:0]diskATA HTS541080G9SA00 MB4O /dev/sda [4:0:1:0]tapeCERTANCE ULTRIUM 21775 /dev/st0 [4:0:1:1]mediumx QUANTUM UHDL 000E - [6:0:0:0]diskArecaARC-1160-VOL#00 R001 /dev/sdb What happens if you run that manually? Hangs The output of that step does not appear on screen however, so it could be that configure is actually hanging on the step after that. I think it's smbclient that is the problem. The next step is finding out where the gzip program lives. Is does that by looking in several directories. If one of those directories happens to be mounted on a non-responsive NFS-server, you hang here too. The list of directories is: /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc /usr/local/sbin:/usr/local/bin:/usr/ccs/bin and the value of $PATH from the user that runs configure. Anything strange when trying test -e /bin/gzip? (Try that for all the above dirs) Nope, looks fine. -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
RE: Next Tapes are Offsite
-Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 4:32 PM To: McGraw, Robert P. Subject: Re: Next Tapes are Offsite On Tue, Aug 08, 2006 at 03:58:21PM -0400, McGraw, Robert P. wrote: If Amanda's behavior hasn't changed (I'm still using 2.4.5), it will use the first non-active tape it finds in the changer. It appears to just load the next tape until it finds a non-active one, not look for an unused one or find the oldest. From this discussion, your and my observations also, it appears the order of tapes listed in the tapelist file is immaterial. Anyone disagree? [McGraw, Robert P.] Not from what I see. I always reverse sort my tape list so that the oldest and lowest number is at the bottom. zorn-[537] cat tapelist 0 D00010 reuse 0 D9 reuse 0 D8 reuse 0 D7 reuse 0 D6 reuse 0 D5 reuse 0 D4 reuse 0 D3 reuse 0 D2 reuse 0 D1 reuse zorn-[538] amadmin daily tape The next Amanda run should go onto a new tape. a new tape. The next 2 new tapes already labelled are: D1, D2. zorn-[541] cat tapelist 0 D1 reuse 0 D2 reuse 0 D3 reuse 0 D4 reuse 0 D5 reuse 0 D6 reuse 0 D7 reuse 0 D8 reuse 0 D9 reuse 0 D00010 reuse zorn-[539] amadmin daily tape The next Amanda run should go onto a new tape. a new tape. The next 2 new tapes already labelled are: D00010, D9. Robert, Yeah, I found out that if two already used tapes have the same date (yours do also, date 0) that it selects the tape based on the tapelist file order. It doesn't seem that amadmin config tape accesses the drive. For my testing I used amtape config taper which actually accesses the tape drive and changer looking of the tape it wants. I wonder if it would handle new tapes differently. I you get the chance, could you try to put a tape, say tape D05 in the drive slot and then run amtape daily taper. Does it say, I'll take any new tape, or does it go searching for the new tape in the last tapelist entry? Just another piece of info that could be interesting. [McGraw, Robert P.] To answer your question I put D6 in the drive with mtx zorn-[49] mtx1 status Storage Changer /dev/scsi/changer/c6t0d0:1 Drives, 38 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 6 Loaded):VolumeTag = D6L2 Storage Element 1:Full :VolumeTag=D1L2 Storage Element 2:Full :VolumeTag=D2L2 Storage Element 3:Full :VolumeTag=D3L2 Storage Element 4:Full :VolumeTag=D4L2 Storage Element 5:Full :VolumeTag=D5L2 Storage Element 6:Empty Storage Element 7:Full :VolumeTag=D7L2 Storage Element 8:Full :VolumeTag=D8L2 zorn-[57] cat tapelist 20060808 D2 reuse 20060808 D1 reuse 0 D00010 reuse 0 D9 reuse 0 D8 reuse 0 D7 reuse 0 D6 reuse 0 D5 reuse 0 D4 reuse 0 D3 reuse zorn-[58] amadmin daily tape The next Amanda run should go onto a new tape. The next new tape already labelled is: D3. Now I resort tape list zorn-[69] cat tapelist 0 D3 reuse 0 D4 reuse 0 D5 reuse 0 D6 reuse 0 D7 reuse 0 D8 reuse 0 D9 reuse 0 D00010 reuse 20060808 D1 reuse 20060808 D2 reuse zorn-[70] !57 amadmin daily tape The next Amanda run should go onto a new tape. The next new tape already labelled is: D00010. So it seems to pick up the last entry in tape that is available even thought I have a tape in the drive that can be used. Robert -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) smime.p7s Description: S/MIME cryptographic signature
Re: Next Tapes are Offsite
On 2006-08-09 14:59, McGraw, Robert P. wrote: Not from what I see. I always reverse sort my tape list so that the oldest and lowest number is at the bottom. zorn-[537] cat tapelist 0 D00010 reuse 0 D9 reuse 0 D8 reuse 0 D7 reuse 0 D6 reuse 0 D5 reuse 0 D4 reuse 0 D3 reuse 0 D2 reuse 0 D1 reuse zorn-[538] amadmin daily tape The next Amanda run should go onto a new tape. a new tape. The next 2 new tapes already labelled are: D1, D2. All the tapes are never used. Any tape is fine. There is a difference between the output of amadmin tape and actually checking what is inserted in the tape drive/changer. I found out that if two already used tapes have the same date (yours do also, date 0) that it selects the tape based on the tapelist file order. It doesn't seem that amadmin config tape accesses the drive. For my testing I used amtape config taper which actually accesses the tape drive and changer looking of the tape it wants. I wonder if it would handle new tapes differently. I you get the chance, could you try to put a tape, say tape D05 in the drive slot and then run amtape daily taper. Does it say, I'll take any new tape, or does it go searching for the new tape in the last tapelist entry? Just another piece of info that could be interesting. [McGraw, Robert P.] To answer your question I put D6 in the drive with mtx zorn-[49] mtx1 status Storage Changer /dev/scsi/changer/c6t0d0:1 Drives, 38 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 6 Loaded):VolumeTag = D6L2 Storage Element 1:Full :VolumeTag=D1L2 Storage Element 2:Full :VolumeTag=D2L2 Storage Element 3:Full :VolumeTag=D3L2 Storage Element 4:Full :VolumeTag=D4L2 Storage Element 5:Full :VolumeTag=D5L2 Storage Element 6:Empty Storage Element 7:Full :VolumeTag=D7L2 Storage Element 8:Full :VolumeTag=D8L2 zorn-[57] cat tapelist 20060808 D2 reuse 20060808 D1 reuse 0 D00010 reuse 0 D9 reuse 0 D8 reuse 0 D7 reuse 0 D6 reuse 0 D5 reuse 0 D4 reuse 0 D3 reuse zorn-[58] amadmin daily tape The next Amanda run should go onto a new tape. The next new tape already labelled is: D3. Now I resort tape list zorn-[69] cat tapelist 0 D3 reuse 0 D4 reuse 0 D5 reuse 0 D6 reuse 0 D7 reuse 0 D8 reuse 0 D9 reuse 0 D00010 reuse 20060808 D1 reuse 20060808 D2 reuse zorn-[70] !57 amadmin daily tape The next Amanda run should go onto a new tape. The next new tape already labelled is: D00010. So it seems to pick up the last entry in tape that is available even thought I have a tape in the drive that can be used. Actually no. When you ask Amanda what tape is next, it does not scan the changer, and gives you what the last entry in tapelist. But when actually doing a amcheck, then Amanda will use an available tape in the first slot encountered (starting from the current). -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
amcheck and BIG holding disks
Dear all, We've put Amandas Holding disk on a NAS, which has 6.6T free on it: df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage amcheck doesn't like it though: Amanda Tape Server Host Check - WARNING: holding disk /storage/amanda: only -2048 GB free, using nothing in our amanda.conf we've put in the holdingdisk section: use -1000Gb Anything else we can do? -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/
Re: AMRESTORE
Never mind I found the -C option and that worked fine. Thanks for any replies. James Wilson wrote: I am trying to do a test restore from amanda and I get this error Could not read config file /etc/amanda/DailySet1/amanda.conf! I don't have a DailySet1 directory. Where do I change the path for this?
Re: amcheck and BIG holding disks
On Wed, Aug 09, 2006 at 02:41:29PM +0100, Gavin Henry wrote: Dear all, We've put Amandas Holding disk on a NAS, which has 6.6T free on it: df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage amcheck doesn't like it though: Amanda Tape Server Host Check - WARNING: holding disk /storage/amanda: only -2048 GB free, using nothing in our amanda.conf we've put in the holdingdisk section: use -1000Gb Anything else we can do? Damn wrap around/overflow on big numbers. Do you expect to be able to feed your unbelievably fast LTO-3 drive fast enough from network storage? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Monthly archival tapes
On Tue, Aug 08, 2006 at 09:22:20PM +0100, Alan Pearson wrote: Guys, On this subject, I'd like to do something similar. Unfortunately my backups don't fit on one tape ! How can I take a _complete_ backup off site in this situation, and how can I identify which tapes I need to take ? I'd recommend a separate config of no-record, full dumps only. But assuming you can't, the answer is complicated. Nominally you need any dumpcycle's set of tapes. It doesn't matter which day you start, any sequence of a dumpcycle's number of tapes should contain a level 0 of each DLE from someday within that cycle. How many tapes are in a dumpcycle? Well, the max should be runtapes X runspercycle. But if runtapes is 1 and the same number of tape is not used each day, how many were used in the dumpcycle you are collecting? Furthermore, there can be multiple dumpcycles and runspercycles in a single config. These parameters can now be set differently in different dumptypes. So which do you use in collecting your tapes? Another potential problem to look out for is DLEs that should have had their level 0 on the last tape you select but due to some error (eg. system down or tape problems leaving some things on holding disk for taping next run), you might not have a level 0 of each DLE on the tapes you select. I don't know of any tool that would let you do something like: given a date (or a tape), determine the minimal collection of tapes, going forward or backward, that contain at least one level 0 (successful dump and taping) of each DLE. Could be a useful tool. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amcheck and BIG holding disks
quote who=Jon LaBadie On Wed, Aug 09, 2006 at 02:41:29PM +0100, Gavin Henry wrote: Dear all, We've put Amandas Holding disk on a NAS, which has 6.6T free on it: df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage amcheck doesn't like it though: Amanda Tape Server Host Check - WARNING: holding disk /storage/amanda: only -2048 GB free, using nothing in our amanda.conf we've put in the holdingdisk section: use -1000Gb Anything else we can do? Damn wrap around/overflow on big numbers. Say again? Do you expect to be able to feed your unbelievably fast LTO-3 drive fast enough from network storage? Yeah, it's on the same server (www.dnuk.com NAS Server): Dual AMD64 2GHz 4GB Ram 80GB OS Disk 6.9T /storage SUSE 9.3 64Bit Quantum SuperLoader 3 LT0-2 Autoloader LSI Logic/Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) Just running amtapetype now via screen, so might just pick one from: http://wiki.zmanda.com/index.php/Tapetype_definitions#LTO-2_.28Ultrium_2.29 Gavin. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amcheck and BIG holding disks
quote who=Gavin Henry quote who=Jon LaBadie On Wed, Aug 09, 2006 at 02:41:29PM +0100, Gavin Henry wrote: Dear all, We've put Amandas Holding disk on a NAS, which has 6.6T free on it: df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage amcheck doesn't like it though: Amanda Tape Server Host Check - WARNING: holding disk /storage/amanda: only -2048 GB free, using nothing in our amanda.conf we've put in the holdingdisk section: use -1000Gb Anything else we can do? Damn wrap around/overflow on big numbers. Say again? Do you expect to be able to feed your unbelievably fast LTO-3 drive fast enough from network storage? Yeah, it's on the same server (www.dnuk.com NAS Server): Dual AMD64 2GHz 4GB Ram 80GB OS Disk 6.9T /storage SUSE 9.3 64Bit Quantum SuperLoader 3 LT0-2 Autoloader Any advice on a changer script for this loader? Was going to use chg-scsi? http://wiki.zmanda.com/index.php/Changers#chg-scsi_.28new_interface.2C_try_to_drive_a_robot_with_direct_scsi_commands.29 Thanks. LSI Logic/Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) Just running amtapetype now via screen, so might just pick one from: http://wiki.zmanda.com/index.php/Tapetype_definitions#LTO-2_.28Ultrium_2.29 Gavin. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel: writing label: Device or resource busy
On Wed, Aug 09, 2006 at 05:22:37PM +0200, Franz-Heinrich Massmann wrote: Hi, The same problem as Sven reported on 02-Aug has been seen with Novell Suse 10.1/Qualstar TLS46120/Amanda 2.5.0. Six out of 20 tapes have been labelled some time ago, but no way to label another one. Does somebody know any workaround? Do I have to delete all tapelist files and label everything from the beginning? Could you, and/or Sven, file a bug report on sourceforge? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Support for DVD-RAM?
mario wrote: Hello Chris, Hello Sebastian, On Mon, 2006-08-07 at 01:00 +0100, Chris Dennis wrote: Hello folks I use DVD-RAMs successfully with Amanda too, accessing them directly as though they were tapes. The key is the tapedev file:/dvdram line in the configuration file, and NOT using any sort of tape changer. Unlike Sebastian, I format the DVD-RAM disks as ext2 before using them. How do you two solve the splitting problem? What happens in your case if your backup does not fit onto one DVD? Yours, Mario I've avoided the problem (so far) by making sure that none of my DLE's are that big. cheers Chris
Amcheck doesn't work as well as it used to
Hello folks I'm using Amanda with DVD-RAM disks on my home network, and it's working fine. One slight irritation is that when I use 'amcheck -ta' (via a cron job) to tell me which disk to use next, I get the following emailed to me: == Subject: 76awd AMCHECK REPORT: NO PROBLEMS FOUND ERROR: /dvdram/data/: No such file or directory ERROR: /dvdram/data/: No such file or directory Amanda Tape Server Host Check - rewinding tape: Input/output error (expecting tape 76awd013 or a new tape) Server check took 0.032 seconds (brought to you by Amanda 2.5.0p2) === It says 'NO PROBLEMS FOUND' despite not finding the correct disk in the drive. It used to work properly, with amcheck setting a return code and only sending the email if the correct disk was not found. Now it always gets a zero return code, so I have to make it always send the email. I'm not sure which version of Amanda introduced this change. Has anyone else seen this problem? regards Chris
Re: amcheck and BIG holding disks
On Wednesday 09 August 2006 12:05, Gavin Henry wrote: quote who=Gavin Henry quote who=Jon LaBadie On Wed, Aug 09, 2006 at 02:41:29PM +0100, Gavin Henry wrote: Dear all, We've put Amandas Holding disk on a NAS, which has 6.6T free on it: df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 73G 6.0G 67G 9% / tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/sdb 6.9T 263G 6.6T 4% /storage amcheck doesn't like it though: Amanda Tape Server Host Check - WARNING: holding disk /storage/amanda: only -2048 GB free, using nothing in our amanda.conf we've put in the holdingdisk section: use -1000Gb Anything else we can do? Damn wrap around/overflow on big numbers. Say again? Do you expect to be able to feed your unbelievably fast LTO-3 drive fast enough from network storage? Yeah, it's on the same server (www.dnuk.com NAS Server): Dual AMD64 2GHz 4GB Ram 80GB OS Disk 6.9T /storage SUSE 9.3 64Bit Quantum SuperLoader 3 LT0-2 Autoloader Any advice on a changer script for this loader? Was going to use chg-scsi? That was I believe, written to handle the likes of the Seagate 4586n changers, which could hand 4 DDS2 cartridges in an internal magazine, or 12 if it had a long stretch of clear space above and below so it could run a magazine up and down in front of the front panel. The changer apparently had about a 1 year lifespan in the use I gave it, and the chg-scsi utility never did learn howto rewind a tape by any means but ejecting it and loading the next tape in the magazine. This meant I had to run amcheck twice to cycle it back around to the right tape, accelerating the wear on the mechanism IMO. For this reason alone I would explore other means of controlling the mechanism besides chg-scsi. I finally got tired of buying already run out drives on ebay and went to vtapes on a big hard drive and have had zero trouble with that since, about 2 years now. That doesn't mean I haven't had trouble with amanda though, I play the part of the canary in the coal mine playing with bleeding edge stuffs here. There appears to be some sort of a problem with amanda snapshot versions newer than 2.5.0-20060424 and kernels newer than 2.6.16.11. And it never exhibets the problem on the first run after a reboot, so one gets a false sense of complacency that the next run will probably destroy. Random invocations of gtar, on either the client or the server, may turn into zombies. All this of course is taking place while Jean-Louis is on sabbatical, which I believe continues for the rest of this week. In the meantime I've found the missing audio problem with the 2.6.18-rcN kernels, and will run 2.6.18-rc4 for the next several days. Maybe by the time Jean-Louis gets back, amanda will have attempted to get the schedule back in balance, at the moment its totally fubared from all the failures. http://wiki.zmanda.com/index.php/Changers#chg-scsi_.28new_interface.2C_tr y_to_drive_a_robot_with_direct_scsi_commands.29 Thanks. LSI Logic/Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07) Just running amtapetype now via screen, so might just pick one from: http://wiki.zmanda.com/index.php/Tapetype_definitions#LTO-2_.28Ultrium_ 2.29 Gavin. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Monthly archival tapes
On 9 Aug 2006, at 15:15, Jon LaBadie wrote: On Tue, Aug 08, 2006 at 09:22:20PM +0100, Alan Pearson wrote: Guys, On this subject, I'd like to do something similar. Unfortunately my backups don't fit on one tape ! How can I take a _complete_ backup off site in this situation, and how can I identify which tapes I need to take ? I'd recommend a separate config of no-record, full dumps only. But assuming you can't, the answer is complicated. Nominally you need any dumpcycle's set of tapes. It doesn't matter which day you start, any sequence of a dumpcycle's number of tapes should contain a level 0 of each DLE from someday within that cycle. How many tapes are in a dumpcycle? Well, the max should be runtapes X runspercycle. But if runtapes is 1 and the same number of tape is not used each day, how many were used in the dumpcycle you are collecting? Furthermore, there can be multiple dumpcycles and runspercycles in a single config. These parameters can now be set differently in different dumptypes. So which do you use in collecting your tapes? Another potential problem to look out for is DLEs that should have had their level 0 on the last tape you select but due to some error (eg. system down or tape problems leaving some things on holding disk for taping next run), you might not have a level 0 of each DLE on the tapes you select. I don't know of any tool that would let you do something like: given a date (or a tape), determine the minimal collection of tapes, going forward or backward, that contain at least one level 0 (successful dump and taping) of each DLE. Thanks for the answers guys, I'm tempted to have different config for this, given the ease at which I can. The only question is then what happens if it all doesn't fit on one tape ? Just amflush to as many tapes as required ? Cheers AlanP
Re: Monthly archival tapes
On Wed, Aug 09, 2006 at 10:27:36PM +0100, Alan Pearson wrote: On 9 Aug 2006, at 15:15, Jon LaBadie wrote: On Tue, Aug 08, 2006 at 09:22:20PM +0100, Alan Pearson wrote: Guys, On this subject, I'd like to do something similar. Unfortunately my backups don't fit on one tape ! How can I take a _complete_ backup off site in this situation, and how can I identify which tapes I need to take ? I'd recommend a separate config of no-record, full dumps only. ... Thanks for the answers guys, I'm tempted to have different config for this, given the ease at which I can. The only question is then what happens if it all doesn't fit on one tape ? Just amflush to as many tapes as required ? Essentially yes. Considerations: Make sure record is set to no. You don't want a record of this full dump upsetting the scheduling of your daily config. Make sure index is yes. Make sure runtapes is sufficient. Make it big, amanda will only use what it needs anyway and you will only be running this manually or infrequently. If runtapes is too small amanda will, during planning, think it has too little tape space and not schedule some dumps. If you have sufficient holding disk space, let it all collect on the holding disk (leave out the tape) and do the taping with amflush. By having all the dumps available at the start, the taper algorithm largestfit can be more effective. Set a suitable taperalgo. Set your holding disk reserve to 0, you won't be doing any incrementals. If on a 2.5 or greater server version, consider tape spanning. HW compression rather than SW? Faster dumps, larger holding disk usage. Consider dump vs tar if you don't need tar'isms like exclude. Probably faster, probably saves ACL's and devices (dubious value). No need for precise estimates, so use one of the much more efficient estimating procedures. Others ?? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
