Re: DAT hardware or software compression
HW compression is more efficient and less CPU intense, but if you're drives fail you must have extra drives in order to read the tapes as HW compression is usually performed by proprietary hardware. SW compression is hard on you CPU(s), but much more portable. Gzip can be read anywhere on most any platform. If you have more than one CPU, you should consider SW compression. On Wednesday 20 November 2002 08:13 am, [EMAIL PROTECTED] wrote: Hello, I have got here a DDS-3 tape drive which has per default hardware compression enabled and was wondering what is the best deal with AMANDA. Would you guys suggest hardware compression or should I disable hardware compression and have software compression done for example with gzip ? Regards Marc
amrecover fails *again*
No one answered my first post. So here's a brief reminder. -- I use NTBACKUP to copy the entire 'Documents and Settings' directory on the Windows PC to a file. This file may be as large as 2 Gigabytes (almost, but not quite). Amanda copies the files OK and amverify can read all the files successfully. However, amrecover fails when trying to restore the large files, the error message is below: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow amrecover: error reading tape: Bad file descriptor extract_list - child returned non-zero status:1 Continue? [Y/n]: amrecover - I can restore the files with native Unix utilities (mt, dd and tar) below is a step by step method of how I do this, but I would like for amrecover to be able to restore these files... Any suggestions? 1. mt -f /dev/nst0 rewind 2. cd to /scratch2/ftp_root 3. mt -f /dev/nst0 fsf 1 4. dd if=/dev/nst0 bs=32k count=1 5. repeat 3 4 until finding the header that I would like to restore. 6. once finding the correct header I do this: dd if=/dev/nst0 bs=32k | /bin/tar -xvf -
Re: wierd amandad timeout error
This is correct. It depends on what c lib that tar was compiled with. See Tom's Root Boot website for an explanation of this. He distributes 2 versions of dd, one has Large File System support while the other does not. He goes into detail of the differences. http://www.toms.net/rb/ On Wednesday 20 November 2002 11:04 am, Christoph Scheeder wrote: Hi, Galen Johnson schrieb: Jon LaBadie wrote: [] It might also be pointed out that 'tar' has this 2 Gb limitation, unless they fixed it in 1.13.25. I've run headlong into it before. =G= i think this is not correct. i've handeled archives 2gb with tar 1.12. If you are on a filesystem with a 2 gb limit, your libc has a 2g Limit or the system your tar was compiled on had a 2gb limit, yes then tar too has the 2GB problem when reading/writing from/to hd. This was true for most intel-linux systems until auround the middle of this year. (don't remember exact time when it went away) Christoph
Re: amrecover fails *again*
Thanks for the smart response. I'll just stick with my manual method of restoring as I don't have time to change a src file (that I don't currently have) and recompile. Besides, my method works... it's amanda's method that doesn't work, but no one seems to care about that. Read The Fucking Manual punk. My balls are bigger than yours punk so don't bother me. Do what the error message says dog-breath before I squash you with my 64-bit souped-up, compiled the compiler ... yadah yadah yadah Now, I wonder why Open Source and Free Software aren't more main stream? On Wednesday 20 November 2002 03:27 pm, Jon LaBadie wrote: Did you try what the message suggests? That is generally a good first attempt.
amrecover fails
Hello, I have some very large backup files that amanda pulls from Windows 2000 PCs. I use ntbackup to copy the entire 'Documents and Settings' directory on the Windows PC to a file. This file may be as large as 2 Gigabytes. Amanda copies the files OK and amverify can read all the files successfully. However, amrecover fails when trying to restore the large files, the error message is below: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow amrecover: error reading tape: Bad file descriptor extract_list - child returned non-zero status:1 Continue? [Y/n]: amrecover Is there a way to correct this? I use RH 7.3 and amanda 2.4.2p2 that came with the distro. Amrecover has no problem restoring the smaller files (400 - 600 MB), it's just the largest files that fail. My tape drives are Quantum DLT 4000. Any help would be much appreciated. Thanks, Brad
Smbclient Question
Hello All, I have successfully been using amanda now for a week on all my Linux servers, and it works beautifully. Now I would like to try it on a few NT4 and W2K machines. I have created a NT4 domain user that can mount all the windows shares that I would like to backup. I have tested that this user can indeed mount the shares by manually running smbclient //server/share -U user_name from the amanda server and it works. I have also created a amandapass in /etc on the amanda server with entries for the Windows machines. My question is this: what do I do now? How can I make amanda automate the mounts and perform the backups? If this info is on the Net somewhere, please forgive my question and simply point me to it. Thank you, Brad
Re: Smbclient Question
I want to thnak everyone for the samba tips. Everything works fine now. I did have some problems with the white spaces under the Windows naming convention; you know, like //MACHINE/Documents and Settings/user name/My Documents Anyway, I made a share named amanda diretly under the W2K root, and it worked fine when I ran amcheck. How do you guys address the white space problem? I assume most users want My Documents saved. Do you make a short cut without any white spaces? Thanks, Brad
tapecycle question
Hello Everyone, I'm new to amanda. I have succesfully compiled and installed the latest version from amanda.org onto a RH7.2 machine. I have a Quantum DLT4000 tape drive with 5 tapes. I would like to run amanda every weekend to do a full weekly backup (no incrementals) of about 12 networked machines, but I don't quiet understand how to set the dumpcycle, runcycle and tapecycyle to do this. Could someone give me a brief example of how to setup these cycles? Thanks for your time, Brad
