RE: Best Amanda Setup for Restores
I guess I am doing something wrong here. I would like to find out what it is. In /tmp/amanda, amrecover creates a file named server.domain.name._.20080114.0.0002048. That file is 55G when I delete it. I have to delete it because at that point the disk is full. This is a backup of the / folder and it is compressed. The folder that is selected for extraction is 4.3G. I have used the lcd command to select the folder where it want the restore to be put. The client and the server are the same machine in this scenario. The amrecover.*.debug file is 2.5M. I will send it to you if that will help. The amrecover session all goes fine. I run it. Select the disk, date, folder that I want, etc. run the extract. Where can I get the complete output of the session? Thanks, -Gordon -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 3:32 PM To: [EMAIL PROTECTED] Cc: amanda-users@amanda.org Subject: Re: Best Amanda Setup for Restores amrecover only write to disk the files you asked for extraction. amrecover extract in the current directory when we executed amrecover (not on /tmp/Amanda), you can use the lcd command to change the cwd. Can you post the complete output of the amrecover session and the complete amrecover.*.debug file. Jean-Louis Gordon J. Mills III wrote: >> Is this simply a case of not realizing that 'amrestore' is generally used >> for complete dle restoration while 'amrecover' is used for individual >> file/directory recovery? >> > > I am beginning to question my sanity here . I am using the amrecover > interface to recover it but it seems that it will first extract the entire > tar'd up dle to /tmp/Amanda before extracting the small folder that I > requested. Am I wrong about that? > If this is the case (and it seems to be what I have experienced) then my > problem is that the entire tar'd up dle will not fit on the partition which > contains /tmp/Amanda/. So to get at this particular folder for this restore > I need to change that default to another drive which does have enough free > space. > > To further clarify, I am running Debian and using the packages in the debian > archive for Amanda. I am using vtapes also. > > Thanks for the help, > Gordon > > >
RE: Best Amanda Setup for Restores
>Let me assure, AFAIK Amanda does not do that. >How did you come to that conclusion? >What is the name of the file that is created in "/tmp/Amanda" (uppercase >A in the name???) The A is lowercase. My mail client put the uppercase. The file is server.domain.name._.20080114.0.0002048. It is 55G when I am forced to delete it because the disk is full. Scratching head now. -Gordon > If this is the case (and it seems to be what I have experienced) then my > problem is that the entire tar'd up dle will not fit on the partition which > contains /tmp/Amanda/. So to get at this particular folder for this restore > I need to change that default to another drive which does have enough free > space. > > To further clarify, I am running Debian and using the packages in the debian > archive for Amanda. I am using vtapes also. -- 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: Best Amanda Setup for Restores
>Is this simply a case of not realizing that 'amrestore' is generally used >for complete dle restoration while 'amrecover' is used for individual >file/directory recovery? I am beginning to question my sanity here . I am using the amrecover interface to recover it but it seems that it will first extract the entire tar'd up dle to /tmp/Amanda before extracting the small folder that I requested. Am I wrong about that? If this is the case (and it seems to be what I have experienced) then my problem is that the entire tar'd up dle will not fit on the partition which contains /tmp/Amanda/. So to get at this particular folder for this restore I need to change that default to another drive which does have enough free space. To further clarify, I am running Debian and using the packages in the debian archive for Amanda. I am using vtapes also. Thanks for the help, Gordon
RE: Best Amanda Setup for Restores
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin J. Mitchell Sent: Friday, February 22, 2008 12:24 PM >Are you using amrestore or amrecover? Amrecover will only actually >write the files you have requested to disk, although your observation >that it reads the entire dump from tape is correct. Dustin, thanks for the response. I am using amrecover but it will extract the entire dle first. Is there a way I can redirect it to use a different directory for this so that I can extract this 100G dle? After that I will try to break it up. >> My first question is: How can I have Amanda use a different path for this >> task. I have an NFS mounted external drive that has much more room on it. >If you're using amrecover, you should 'cd' into the directory into >which you want to recover your files before starting amrecover. This is not really what I'm asking. Apparently Amanda has a default to restore the dle into /tmp/Amanda before actually extracting what you requested. I did cd to the proper directory first, but this is irrelevant here. I need to be able to change the location that it restores the dle (before doing the actual restore) because the drive that /tmp is on is not large enough to handle it. >Currently, that's the only solution -- smaller DLEs. That is a bummer. >Not yet, but that is a major aim of the Application API and transfer >architecture, which are under active development. For a hint as to >how complex this is, see >http://wiki.zmanda.com/index.php/User:Dustin/Data_Handling_Model. >There's no specific ETA on this development at the moment. Thanks for the link. I looked at it but I think most of it is beyond my understanding of things here. Gordon
Best Amanda Setup for Restores
I have recently run into a problem with restoring. I want to restore a folder on a DLE that is about 100G. The folder I want to restore is small but apparently Amanda has to restore the entire DLE to get at the 1 folder. It is restoring the large file to /tmp/Amanda/. Unfortunately, I do not have enough room there to extract the entire DLE. My first question is: How can I have Amanda use a different path for this task. I have an NFS mounted external drive that has much more room on it. 2nd question: Is there a way to setup Amanda so that it does not have to retrieve the entire DLE file? Is it just removing compression from the DLE def? Or chopping up the DLE to smaller chunks (this will be hard since most of the data is in 1 place on that dle). I would like for Amanda to behave in a similar way that I have had other backup software behave. That is, if I just want a single file or folder, then it scans the tape (in this case vtapes) and retrieves only what I want. When I have successfully retrieved files with Amanda before it took a very long time. Is there a way to set it up so that it will do this? Thanks for the help. Regards, Gordon
Strange tape usage
Hello all. I have been off of the list for a while and recently rejoined. I have had some strange behavior lately with some tapes. Amanda has been using 2 tapes when the backup could have easily fit on one tape. Here is the message in the mail report: taper: tape TAPE07 kb 4651360 fm 6 writing file: Input/output error taper: retrying trc-router.trc.crownmx.com://trc-ex2/d$.1 on new tape due to: [writing file: Input/output error] taper: tape TAPE08 kb 7318816 fm 6 [OK] Does this mean my tapes are going bad and I need new tapes or what? Thanks, Gordon
Splitting Dumps
I have recently setup my config to be able to split dumps across tapes due to an increase in size. I get the following message in the backup report: taper: no split_diskbuffer specified: using fallback split size of 10240kb to buffer localbackupservername:/home.1 in-memory And in the verify report I get the following for each DLE and hundreds of them for the DLE's that are local and do not go to holding disk: Skipped /bin/tar check on partial dump . I have specified the runtapes and the tape_splitsize in the amanda.conf. It appears from the first message that I need to add the split_diskbuffer option to my amanda.conf. And perhaps some other options too. Can anyone guide me in this new setup? Something seems to be wrong since I have gone to splitting across tapes. I am using amanda 2.5.0p2 on Debian. Regards, Gordon
RE: Using no-reuse with vtapes
Jean-Louis, thanks for the patch! I applied it when you sent it but had to wait to see if the system would cycle through past the "no-reuse" tape. It did so successfully and all is working fine now! Thanks again! Regards, Gordon Mills -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: Monday, November 20, 2006 2:20 PM To: [EMAIL PROTECTED] Cc: amanda-users@amanda.org Subject: Re: Using no-reuse with vtapes I attached a bad version of the patch, Try this one instead. Jean-Louis Jean-Louis Martineau wrote: > > Changing tapecycle will not fix your problem because the chg-disk > changer script use it to set it's LASTSLOT. > > The use of chg-disk with 'no-reuse' is incompatible, but it could be > easily fix (attached patch): > - chg-disk must set its LASTSLOT from a changer configuration file. > > After that, you will have 2 possibilities: > set LASTSLOT to 22, create the slot directory and label it. > or > set LASTSLOT to 21 and tapecycle to 20. > > > Try the attached patch, the changer configuration filename is your > setting of changerfile with a ".conf" appended. > Add a "LASTSLOT=22" to the changer configuration file. > > Jean-Louis > > > Gordon J. Mills III wrote: >> I am having a problem using the no-reuse feature with vtapes. I have >> a tape that contains files from a machine that is going to be >> decommissioned. I want to save the last full backup of that machine. >> So I put no-reuse next to that tape in the tapelist file. The problem >> is that the next time the tape cycle comes around to that tape it >> acts like there is no available tape. It cycles through all the tapes >> and says "(expecting a new tape)" at the end. >> So the question is: how can I use the "no-reuse" feature? It seems >> that amanda has to have tapecycle number of tapes even if dumpcycle >> is set to a number lower than that. The relative section of my >> amanda.conf is below. >> This is on 2.5.0b1. >> >> dumpcycle 10 days # the number of days in the normal dump cycle >> runspercycle 10 >> tapecycle 21 tapes # the number of tapes in rotation >> >> bumpsize 10 MB # minimum savings (threshold) to bump level 1 >> -> 2 >> bumpdays 2 # minimum days at each level >> bumpmult 1.5# threshold = bumpsize * (level-1)**bumpmult >> >> runtapes 1 # explained in WHATS.NEW >> tpchanger "chg-disk" # the tape-changer glue script, see >> TAPE.CHANGERS changerfile "/etc/amanda/DailySet1/changer" >> tapedev "file:/amandatapes/DailySet1/" # Linux @ tuck, important: >> norewinding >> # tapedev "/dev/nrst8" # or use the (no-rewind!) tape device >> directly rawtapedev "file:/amandatapes/DailySet1/" >> >> tapetype HARD-DISK # what kind of tape it is (see tapetypes >> below) >> labelstr "^TAPE[0-9][0-9]*$"# label constraint regex: all tapes must >> match >> >> Regards, >> Gordon >> >> >> > > -- > -- > >
Exclude Lists - Amanda 2.5.0
Could somebody please point me to a good explanation of the exclude lists? I am trying to create an exclude list for some windows machines that I back up. Will excludes work on the windows machines (using smbclient backup in Amanda 2.5.0)? If they will work, I would like a good explanation of the syntax of the file, specifically wildcards. i.e. can I specify /*/somedirectory/file???.chk? How about file paths with spaces in them. Do I just put them with the spaces or do I have to use some special syntax for that? I tried searching the net and the wiki but I did not find the answers. I found some references to it, but it did not answer the questions above. Thanks for the help. Regards, Gordon
Exclude Lists - Amanda 2.5.0
I have a question about Exclude lists. I am finally sick of seeing all of the missed open files for my windows boxes, so I want to put the common ones in an exclude list. First, is there any difference in specifying a directory or a file? Second, how do I specify a path that has spaces in it (in the exclude list file)? And finally, does anyone out there have a generic exclude list for windows servers? If not, I may post mine after I get it working correctly if anyone is interested. Regards, Gordon
RE: Windows domains...
I am using a domain user with success. However, my amandapass entries look like your #2 entry below. Basically: //servername/d$ user%password NETBIOSDOMAINNAME I'm not sure what to tell you to try, but I wanted to let you know I have it working. :-) Is the domain user a Domain Admin? Regards, Gordon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Clement Sent: Wednesday, August 30, 2006 11:16 AM To: amanda-users@amanda.org Subject: Windows domains... We've recently been 'upgraded' to a Windows domain, part of this upgrade appears to have involved removing the local amanda account from each Windows server. Is there any way of getting amanda to auth using domain logon? I've tried the following varients in amandapass (with the resulting error from amcheck below, oh and yes that account does exist on the domain and has the password set) but no joy, any suggestions welcome! Thanks, jc //server.domain.local/c$ amanda%password domain.local -- Domain=[READINGROOM] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]: tree connect failed: NT_STATUS_ACCESS_DENIED: returned 1] //server.domain.local/c$ amanda%password domain -- Domain=[READINGROOM] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]: tree connect failed: NT_STATUS_ACCESS_DENIED: returned 1] //server.domain.local/c$ [EMAIL PROTECTED] -- session setup failed: NT_STATUS_LOGON_FAILURE: returned 1] //server.domain.local/c$ [EMAIL PROTECTED] -- session setup failed: NT_STATUS_LOGON_FAILURE: returned 1]
RE: Amanda backup server restore
Olivier Nicole wrote: > > > In particular "amadmin export". What I am currently doing is this: > > tar -cpPzf /home/myname/cjs-amback.tar.gz /var/lib/amanda/ > > /etc/amandahosts /etc/amandapass /etc/amanda/ /var/log/amanda/ > > It's hard for us to say what is in /var/lib/amanda/ or > /etc/amanda/ or /var/log/amanda/ > > You should save the index directory that is usually in the > amanda user home directory. That you save it one way (tar and > scp) or another (amadmin > export) or both, it is up to your policy. > > Olivier Thanks for the info Olivier. What files should I look for to identify the index directory? I am running the std debian package and I believe the directories listed are the right ones. Someone please correct me if I am wrong. Thanks, Gordon
Amanda backup server restore
I have seen some posts lately refering basically to recovering your amanda backup server in case of failure. i.e. if you have to rebuild your backup server and you want to restore all your amanda data, etc. In particular "amadmin export". What I am currently doing is this: tar -cpPzf /home/myname/cjs-amback.tar.gz /var/lib/amanda/ /etc/amandahosts /etc/amandapass /etc/amanda/ /var/log/amanda/ Then I scp that file to other backup servers. And the other servers do the same. My question is: Is it necessary to do the "amadmin export" also? Thanks, Gordon Mills
RE: RPM for RHEL3
You can download it from:http://www.zmanda.com/downloads.html
Thanks. I see they have added it. It wasn't there a few
weeks ago.
I have downloaded it and installed it. Now the problem
appears to be the xinetd setup. The RPM did not install the files for xinetd.
Can someone tell me what I need for the redhat xinetd? I tried to add an amanda
entry, but it is not working.
I added a file named "amanda" to /etc/xinetd.d/. It
contains:
service amanda{ socket_type
= dgram protocol = udp
wait = yes
user = amandabackup
group = disk
server = /usr/lib/amanda/amandad
disable = no}
Do I need to add files for amandidx and amidxtape? Does my entry above
look correct? Can anyone give me the right setup for this?
Thanks,
Gordon
RPM for RHEL3
Does anyone have an amanda rpm for RHEL3? I have a client with this server and I would like to put amanda on it to do the backups. Will one of the rpm's for rhe[ls]4 work? I would prefer to use a package instead of compiling. I tried to compile and apparently the server doesn't have all the necessary packages to compile. TIA, Gordon
RE: Amverifyrun not working in 2.5.0
It did work in 2.4.5. I have 2 other servers that are running 2.4.5
successfully (as this one was before yesterday). I used this one as a test
since it is not in production yet, but will be soon.
I compared the versions of the script and they are identical. It is the
amdump.1 file that appears to have changed and now doesn't contain the lines
that the script is grepping for.
Thanks,
Gordon
> -Original Message-
> From: Brad Willson [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 19, 2006 11:43 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Amverifyrun not working in 2.5.0
>
> Welcome to the club. 2.5.0 gives 'stable' a new meaning.
>
> Jon Badie made the following suggestion off-list:
>
> >If you are switching back and chg-zd-mtx works in 2.4.5,
> save a copy of
> >the script. Then compare it to the 2.5 version (diff cmd)
> and if there
> >are differences (I don't think there should be) try the
> older version
> >as a drop-in replacement.
> >
>
> Gordon J. Mills III wrote:
>
> >I just upgraded one of my amanda servers to 2.5.0. This is on a
> >debian-stable (sarge) machine using the apt packages. I was using
> >2.4.5p1 before. The backup appears to have worked fine, but
> when I run
> >amverifyrun to determine which tape(s) to verify, I get the
> Illegal slot: "-1" error.
> >
> >This problem appears to stem from these lines in the
> amverifyrun script:
> >FIRST_SLOT=`grep "taper: slot" $AMLOG | fgrep 'exact label match new
> >tape first labelstr match' | sed 1q | sed 's/://g' | awk
> '{print $3}'`
> >if [ X"$FIRST_SLOT" = X"" ]; then
> > FIRST_SLOT='-1'
> >fi
> >
> >If I grep for those strings in the amdump.1 file, I do not
> find them.
> >Is this a bug in 2.5.0 or is it just a problem with the
> debian packages
> >or perhaps somehow my setup is messed up?
> >
> >Regards,
> >Gordon
> >
> >
> >
> >
> >
>
> --
> Brad Willson, Sr. Computer Specialist
> UW GeneTests, UW Box: 358735
> EM: [EMAIL PROTECTED]
> W: 206.221.4674, C: 425.891.2732
> http://www.genetests.org
>
>
RE: Amverifyrun not working in 2.5.0
> Hi Gordon,
>
> This is a known bug that was fixed by Jean-Louis in 2.5.0p2.
> Where did you get debian packages from 2.5.0? Did you build
> on your own? If so, you can update the tree and try again.
>
> Thanks,
> Paddy
>
Thanks Paddy. I simply installed the version using Debian's apt package
manager. It gives the version as 1:2.5.0-2 and is from the debian/testing
branch. I guess I'd have to build my own to update to the latest or email
the maintainer of the packages.
Thanks,
Gordon
> On 5/19/06, Gordon J. Mills III <[EMAIL PROTECTED]> wrote:
> > I just upgraded one of my amanda servers to 2.5.0. This is on a
> > debian-stable (sarge) machine using the apt packages. I was using
> > 2.4.5p1 before. The backup appears to have worked fine, but
> when I run
> > amverifyrun to determine which tape(s) to verify, I get the
> Illegal slot: "-1" error.
> >
> > This problem appears to stem from these lines in the
> amverifyrun script:
> > FIRST_SLOT=`grep "taper: slot" $AMLOG | fgrep 'exact label
> match new
> > tape first labelstr match' | sed 1q | sed 's/://g' | awk
> '{print $3}'`
> > if [ X"$FIRST_SLOT" = X"" ]; then
> > FIRST_SLOT='-1'
> > fi
> >
> > If I grep for those strings in the amdump.1 file, I do not
> find them.
> > Is this a bug in 2.5.0 or is it just a problem with the debian
> > packages or perhaps somehow my setup is messed up?
> >
> > Regards,
> > Gordon
> >
> >
> >
> >
>
Amverifyrun not working in 2.5.0
I just upgraded one of my amanda servers to 2.5.0. This is on a
debian-stable (sarge) machine using the apt packages. I was using 2.4.5p1
before. The backup appears to have worked fine, but when I run amverifyrun
to determine which tape(s) to verify, I get the Illegal slot: "-1" error.
This problem appears to stem from these lines in the amverifyrun script:
FIRST_SLOT=`grep "taper: slot" $AMLOG | fgrep 'exact label match
new tape
first labelstr match' | sed 1q | sed 's/://g' | awk '{print $3}'`
if [ X"$FIRST_SLOT" = X"" ]; then
FIRST_SLOT='-1'
fi
If I grep for those strings in the amdump.1 file, I do not find them. Is
this a bug in 2.5.0 or is it just a problem with the debian packages or
perhaps somehow my setup is messed up?
Regards,
Gordon
RE: Would like to get list's impression on (amanda 4TB backup)
> > Paddy, will it only work when using cygwin client on > windows or will > > it also be possible using smbclient from the server? I have > setup the > > backup of several windows servers using the smbclient > method. I have > > not yet attempted a cygwin client, but if it will offer > more options > > it may be worth it. How much trouble is it to install > amanda on cygwin? > > > > The real problem (as I see it) is support, your support time that is. > With smbclient nothing needs be done/added to the windows system. > With cygwin, you have to add and maintain cygwin on 'each' > windows client. > Then on 'each' windows client also add and maintain amanda. > > If you need it, you need it though. > > For one or two windows systems not too bad, for fifty or a > hundred that don't use cygwin otherwise? > bleech! > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) Thanks Jon. That is a good point. I'm not sure what would be the best answer for Windows clients...I guess it depends on each environment. On TSM I had to install client software on each machine. Of course it wasn't very hard since it was a win32 client. Took about 5 min. If it could all be done from the amanda machine using smbclient, that would sure be easy. It would put a much greater load on the backup server, but it would not require anything on the win client. For that to work though, smbclient would need to support windows ACL's and include/exclude lists. The latter is definitely do-able. I have no idea about adding ACL support... That would be nice though :-). Regards, Gordon
RE: Would like to get list's impression on (amanda 4TB backup)
> > > Probably most important to me though would be the ability to handle > > Windows backups better. I know that it is not necessarily Amanda's > > fault, but the file permissions (ACLs) cannot currently be > backed up > > with Amanda. Also, it does not allow exclude lists for windows > > clients. This should be possible since now smbclient has > this feature. > > Amanda 2.5.1 will support Schily tar (GNU tar) that has > ability to backup to POSIX ACLs. > Windows ACLs will be added to Schily tar. So Cygwin clients > can backup windows ACLs. > Paddy Paddy, will it only work when using cygwin client on windows or will it also be possible using smbclient from the server? I have setup the backup of several windows servers using the smbclient method. I have not yet attempted a cygwin client, but if it will offer more options it may be worth it. How much trouble is it to install amanda on cygwin? Regards, Gordon
RE: Would like to get list's impression on (amanda 4TB backup)
> Gordon J. Mills III wrote: > > Josef, here are some of my comments about TSM that I sent > to a lister > > off list. I think in a later email I will try to list the > things that > > I liked about TSM that I would like to see in Amanda. Some > may not be possible. > > > > At my previous job we used TSM and it is a very nice backup > solution. > > We had a tape library that held about 250 tapes and up to 8 > drives (We > > had 5 drives in it). It seems to excel at backing up large > amounts of > > data. One unique thing it does is that it uses and "incremental > > forever" backup strategy. It backs up a machine fully only once (it > > can probably be setup other ways, but that's the way we > used it)<--(I > > could be wrong about that). There is a backup server > (similar to the > > way Amanda is setup) and it has a database that keeps track of > > everything that has been backed up (all files). It knows > what files are on what tapes (Also similar to Amanda). > > > > One possible downside of the TSM approach is this database. > If it is somehow lost or corrupted, all you have is a bunch > of tapes with random chunks of data that may not be > recoverable into its original structure. While it is a > robust database, things can happen (such as failing RAID or > SAN controllers wiping out all of your redundant disks), so > you need to make sure that you have backups of the database > that are outside of TSM (somewhat similar to what can happen > if you lose your Amanda indexes, except that with Amanda you > can use native tools to restore everything on your tapes. > > Frank > > > -- > Frank Smith [EMAIL PROTECTED] > Sr. Systems Administrator Voice: 512-374-4673 > Hoover's Online Fax: 512-374-4501 > Hello Frank. That is true, as you point out the DB becomes VERY important in this type of backup scheme. I believe the way we handled it was to use their BMR (Bare Metal Recovery) on the backup server (and other critical servers). I suspect it backs up everything necessary to rebuild the database in case of failure. Of course this all goes towards the more overhead necessary for such a scheme. Regards, Gordon
RE: Would like to get list's impression on (amanda 4TB backup)
> On Tue, May 16, 2006 at 09:53:13AM -0500, Gordon J. Mills III wrote: > > here are some of my comments about TSM > > Thanks Gordon. Tivoli sounds like an interesting enterprise system. > > "incremental forever" is a feature I've heard of in some > other backup systems. I wouldn't expect that to fit the mold > of amanda as recovery would then truly demand amanda software > and indexes to be present. > > One feature you describe I would like to see added to amanda. > It really is not a change to the operation, but a new utility. > That is copying all or portions of a set of backups to new > "tapes" or a new config. With many people doing amanda > backups to vtapes, it would be nice to be able to archive > desired parts to "offsite" ptapes. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) > It is true that the "incremental forever" brings up other issues. I think a discussion of some of the features/differences between Amanda and TSM may bring out some additional feature requests to improve Amanda. The Inc Forever method does demand a lot more overhead, not to mention the ability to append to tapes. I guess it doesn't "need" that, but it sure cuts down on the number of tapes required in the library. I think if you look at a "traditional" backup scheme vs TSM, Amanda falls somewhere in the middle. It is a very nice approach. I guess if I had 80 tapes with a 7 or 10 day dumpcycle I would have a lot of versions of files to choose from :-). I think that one of the things I liked the most about TSM was the saving of multiple versions of a file and being able to choose which one I wanted. In a way it had a lot to do with the way the recovery interface was done. This can sort of be done in Amanda now, but would be better if the amrecover interface listed the versions and dates available. The more I think about it, the more I think Amanda can come closer to achieving this simply by having a lot of tapes (which would be necessary anyway for the TSM approach). As you pointed out, the offsite feature would also be a nice addition. All of this stuff works best with a tape library that has more than 1 drive, so I suspect it only applies to a small percentage of Amanda users. The offsite feature would require a database to keep track of what is offsite and what is not. What new files need to be written to a tape to go offsite and what tape(s) need to come back, etc. Probably most important to me though would be the ability to handle Windows backups better. I know that it is not necessarily Amanda's fault, but the file permissions (ACLs) cannot currently be backed up with Amanda. Also, it does not allow exclude lists for windows clients. This should be possible since now smbclient has this feature. Regards, Gordon
RE: Would like to get list's impression on (amanda 4TB backup)
of TSM. I know there must be settings/etc for a much smaller implementation of TSM, I am just describing what we had and how it worked. If I have not been clear on something I will try to explain better. Also, please do not think I am badmouthing Amanda, I am not. I think it is a fine system. Also, I am not a representative of IBM or TSM, I am/was just a happy user at my old job. Since Josef asked that I post to the list in hopes of generating a discussion on some of the features of TSM and if it might be something to add to the amanda wishlist, I would love to discuss that. I hope that wasn't too much rambling. I just wrote down things as they came to mind :-). Regards, Gordon Mills > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Josef Wolf > Sent: Sunday, May 14, 2006 4:20 PM > To: amanda-users@amanda.org > Subject: Re: Would like to get list's impression on (amanda > 4TB backup) > > On Thu, May 11, 2006 at 12:34:00PM -0500, Gordon J. Mills III wrote: > > > Hello Ronald and Ross. Just a note on other backup > solutions...If you > > do decide to to commercial I would recommend you take a > look at IBM's > > Tivoli (aka TSM) backup system if you are looking at large > libraries > > and lots of data. It is a very impressive system with a completely > > different stategy than other backup solutions I've seen. > > I'm very interested about the startegy. Would you please > spend a couple of words about it to us? > > > That said, Amanda comes the closest so far to bridging the gap > > (commercial or GPL). Amanda is a great backup solution, but if I > > wanted to go commercial I'd definitely look at TSM. We had > it at my old job and it was fantastic. > > What makes it superior to amanda? > > > I > > won't go into a detailed description unless others would > like to read > > it. If you want to know more about the comparisons I will > answer privately. > > I definitely would like to know more. And I think such a > discussion would be perfectly on-topic on this list. There's > no reason to go privately because most people on this list > are interested (IMHO). > > > PS: I am not trying to start a flame war here nor am I an > affiliate of IBM. > > Just trying to give some info. > > Hey, that's not fair! > > Please avoid statements like "they are superior" without an > explanation _why_ they are superior. instead, please provide > us with information about what is missing to come close to > this superior system. > >
RE: Would like to get list's impression on (amanda 4TB backup)
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ronald > Vincent Vazquez > Sent: Thursday, May 11, 2006 11:48 AM > To: amanda-users@amanda.org > Subject: Re: Would like to get list's impression on (amanda > 4TB backup) > > Hi Ross: > > The 4TB will be the initial phase of our go live period. We > envision going to 15-20TB during the first two years. Oh > yes, this will be the backup system for our cluster and all > other servers. We are looking at tape hardware solutions > from multiple manufacturers (24-50 tape libraries) but have > time to lock the *right* one. > > Right now I am trying to collect as many "pro/con" as I am > able to before we have to say "Veritas...". > > RV > > / > Ronald Vincent Vazquez > (301) 540-9394 Home > (240) 401-9192 Cell > > On Thu, May 11, 2006 at 12:27:31PM -0400, Ronald Vincent > Vazquez wrote: > > Is anyone out there using Amanda to back up this much data with any > > tape library that would be willing to share their experiences? > > Are you talking about a single host that needs 4TB backed up, > or do you mean a bunch of hosts that add up to 4TB? > > I don't have a system large enough to test a 4TB disk backup. > Hope you have big tapes! :-) > > If you mean the second, my Amanda setup does almost 16TB, > split across four servers. I recently lost backups due to no > fault of Amanda. Had an issue with the HBA for our EMC SAN. > > Amanda is great! > > -- > Ross Vandegrift > [EMAIL PROTECTED] > > "The good Christian should beware of mathematicians, and all > those who make empty prophecies. The danger already exists > that the mathematicians have made a covenant with the devil > to darken the spirit and to confine man in the bonds of Hell." > --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37 > > > > Hello Ronald and Ross. Just a note on other backup solutions...If you do decide to to commercial I would recommend you take a look at IBM's Tivoli (aka TSM) backup system if you are looking at large libraries and lots of data. It is a very impressive system with a completely different stategy than other backup solutions I've seen. That said, Amanda comes the closest so far to bridging the gap (commercial or GPL). Amanda is a great backup solution, but if I wanted to go commercial I'd definitely look at TSM. We had it at my old job and it was fantastic. I won't go into a detailed description unless others would like to read it. If you want to know more about the comparisons I will answer privately. Regards, Gordon PS: I am not trying to start a flame war here nor am I an affiliate of IBM. Just trying to give some info.
RE: Disabling LTO-2 hardware compression
Sven, if you don't mind my asking...how did you setup stinit? I installed it but it seems a bit confusing as to what I need to do to have it disable compression on reboots, etc. Thanks, Gordon > -Original Message- > From: Sven Rudolph [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 03, 2006 10:02 AM > To: Graeme Humphries > Cc: [EMAIL PROTECTED]; 'amanda users list' > Subject: Re: Disabling LTO-2 hardware compression > > Graeme Humphries <[EMAIL PROTECTED]> writes: > > > Gordon J. Mills III wrote: > >> Just a note on this: > >> There needs to be a tape in the drive when you execute that > >> command...at least on my drives. > >> Anyone have any further info on this? > >> > > We've seen the same thing, the command fails if there's > tapes in the > > changer but not in the drive on our Exabyte LTO-3 unit. Also, we've > > noticed that if the tape unit is reset (power failure, > whatever) then > > it resets back to compression *on*. > > Use stinit from mt-st, it resets these parameters whenever an > open(2) on the device is done. > > Sven > >
RE: Newbie needs Help
On this same topic, is there a way to have amrecover list the available
versions of a file that are currently on tape?
i.e. list the 5 versions of the file with the dates so that you can choose
the one you want?
Regards,
Gordon
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Geert Uytterhoeven
> Sent: Thursday, May 04, 2006 10:41 AM
> To: Luis Rodrigues
> Cc: amanda-users@amanda.org
> Subject: Re: Newbie needs Help
>
> On Thu, 4 May 2006, Luis Rodrigues wrote:
> > The normal everyday amanda incremental backup saves all the
> touched files to the holding disk?
>
> Yes.
>
> > If the file is changed 5 times in a backup cicle it will
> get backed up
> > 5 times? if so how do I access it using amandarecover?
>
> By specifying the date of the version you want to recover.
>
> > On Thu, 4 May 2006 10:26:39 -0400
> > Jon LaBadie <[EMAIL PROTECTED]> wrote:
> > > On Thu, May 04, 2006 at 03:52:07PM +0200, Luis Rodrigues wrote:
> > > > I've just started a job at a new company. They have an backup
> > > > system with everyday copies the touched files to a disk
> on a backup server and on the weekend it makes a 0 level to tape.
> > > >
> > > > They say the system is not really relayable because
> some times they don't find the files an want a new one.
> > > >
> > > > So I will install amanda.
> > > >
> > > > The problem is that they want to keep the old backup
> touched files each day and zero level on the weekend.
> > > > In http://www.amanda.org/docs/topten.html#id2552255
> says this is not possible.
> > > >
> > > > So I will use amanda with a weekly cycle so that at
> saturday everyting is backuedup.
> > > >
> > > > But I still need to incremental backup the touched files since
> > > > last inscremental, is it possible to force amanda to
> (in its runs during week) first copy to backup server the
> touched files and them some others?
> > > >
> > >
> > > You can nearly mimic what they have been doing. Not
> necessarily my
> > > recommendation, but sometimes "ya gotta do what da boss
> sais ya gotta do".
> > >
> > > Think of their current backup disk as amanda's "holding disk".
> > > Set up your amanda config to 'autoflush" the holding disk
> whenever
> > > it actually does tape.
> > > Set up your config to not do level 0's except when forced
> with amadmin.
> > > I forget if this is "skip-full" or "incr-only".
> > > Set up amanda to use a symbolic link to the tape device,
> eg. /dev/amandatape.
> > > This will be missing normally, so incremental backups
> will collect
> > > on the holding disk, waiting to autoflush.
> > > Set up your daily cron job to "rm amandatape" then amdump.
> > > Set up your weekend cronjob to amadmin force level 0's,
> create the
> > > symbolic tape device link, then do amdump, the rm amandatape.
> > > The entire week will go to tape.
> > >
> > > > If so what will happen if a file is changed two times
> in one week?
> > >
> > > You will have a copy of each version.
> > > During the week you can still use amrecover to get at the
> > > incrementals collecting on the holding disk.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> [EMAIL PROTECTED]
>
> In personal conversations with technical people, I call
> myself a hacker. But when I'm talking to journalists I just
> say "programmer" or something like that.
> --
> Linus Torvalds
>
>
RE: Disabling LTO-2 hardware compression
Just a note on this: There needs to be a tape in the drive when you execute that command...at least on my drives. Anyone have any further info on this? My drives are AIT35 autoloaders. Regards, Gordon > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Loftis > Sent: Tuesday, May 02, 2006 2:21 PM > To: Guy Dallaire; amanda users list > Subject: Re: Disabling LTO-2 hardware compression > > mt -f datcompression 0 > > That should work but it will likely come back on after a > restart though. > > --On May 2, 2006 10:17:48 AM -0400 Guy Dallaire > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Recently added an Overland LoaderXpress LTO 2 tape library > to my setup. > > Inside the loader is an OEM HP Ultrium tape drive. My tape > server is a > > centos 4.2 box (RHEL 4 clone) > > > > I'm using software compression with amanda 2.4.5p1 already. > > > > Problem is, the tape drive in the library always seems to have > > hardware compression ON. There is no way on the library > operator panel > > to force the compression OFF. > > > > I've heard that LTO2 drives can easily cope with already compressed > > data (and do not try to re compress it). Is this true ? > Otherwise, I > > fear that trying to compress already compressed data might actually > > use more tape space and reduce throughput. > > > > I've searched the amanda wiki and di not find anything. > > > > Has anyone devised a way to force hw compression off on a > similar setup ? > > > > Thanks > > > > -- > "Genius might be described as a supreme capacity for getting > its possessors into trouble of all kinds." > -- Samuel Butler >
RE: Planning to use Amanda and have a few questions.
> > Hello all, > > I am working for a middle-size company and we are planning to deploy a backup solution for our systems. > Most of our servers are MS 2003 based servers (like DC, Exchange, SQL and some Web servers). > > I just wondered if there are some other amanda users who backup their MS based servers lik Exchange, SQL > and etc. with amanda? Are there any specific problems using amanda with Windows Servers? > Are they happy with their performance and the effectiveness of the Amanda software with > their windows servers? Are there any direct built-in software support for such servers (like SQL)? > > Simply i would love hear feedbacks of Amanda users who backup their Windows > servers using amanda and guide me during our decision for our backup plan. > > thank you in advance for your helps ! and hope to hear from you soon, > Emre. > system and software eng. I am doing the same here including Exchange and SQL. I am using the Amanda method that uses smbclient to backup the windows servers. Unfortunately there is no way to exclude file patterns, etc with that. For Exchange I do an exmerge dump each night on the server so that I can restore mails/mailboxes if necessary. I also do an exchange backup with the MS Backup software to a file on the exchange server. That file gets backed up also. Oh yeah, for all windows servers I do an MS Backup of the "System Settings" or whatever it is MS calls it to a file on the server. For SQL it does a similar thing. Backup data to a folder on server including trans logs, etc. That all gets backed up by amanda. So, you can either have the windows server dump the data to your amanda server and then back it up (as suggested by another user) or have the amanda server backup the windows servers using smbclient. In the end it seems the same Regards, Gordon
RE: Restore WO Amanda, what am I doing wrong?
> >By config directory I presume you mean like "/etc/amanda/Daily"? > > If that is where you put it when amanda was "./configured" > > >And where is the indices directory? > > And that is specified in the amanda.conf file, like this: > > snip from amanda.conf-- # Amanda > needs a few Mb of diskspace for the log and debug files, # as > well as a database. This stuff can grow large, so the conf # > directory isn't usually appropriate. Some sites use > /usr/local/var # and some /usr/adm. > # Create an amanda directory under there. You need a > separate infofile # and logdir for each configuration, so > create subdirectories for each # conf and put the files > there. Specify the locations below. > > # Note that, although the keyword below is infofile, it is > only so for # historic reasons, since now it is supposed to > be a directory (unless # you have selected some database > format other than the `text' default) infofile > "/usr/local/var/amanda/Daily/curinfo" # database DIRECTORY > logdir "/usr/local/var/amanda/Daily" # log directory > indexdir "/usr/local/var/amanda/Daily/index"# index directory > tapelist "/usr/local/etc/amanda/Daily/tapelist" # list of > used tapes # tapelist is stored, by default, in the directory > that contains amanda.conf > -- > > Which should explain it. You're welcome to a copy of the > script I use if you'd like, just yell. It checks to see what > it was called when invoked and modifies its behaviour > accordingly. You would need to edit it for some of the > paths, or to extract those paths from the amanda.conf, one of > those things the infamous shoemaker never did get around to > building for his kids :) Thanks for the help Gene. I have addded a couple of lines to my backup script that look like this: # backup the amanda files in case of backup server crash tar -czf /home/myhome/serverA.tar.gz /var/lib/amanda/ /etc/amandahosts /etc/amandapass /etc/amanda/ /var/log/amanda/ scp -2pi /location/of/keyfile /home/myhome/serverA.tar.gz [EMAIL PROTECTED]:/home/myhome/ Does that look like it will get all the necessary files? I wouldn't mind taking a look at your script too :-). Also, this is on a Debian system and all of the files are in the default location for the debian packages (2.4.5p1). Regards, Gordon
Extracting files error
When trying to extract files using amanda I get the following error. I have substituted for the actual hostname. Any hints/ideas on what the problem is? Amanda ver: 2.4.5p1 Tape drive is 35G autoloader Extracting files using tape drive changer on host cuu-router.cuu.crownmx.com. The following tapes are needed: TAPE03 amrecover> list TAPE TAPE03 LEVEL 2 DATE 2006-03-25 /data/IT/VirtualStats/VirtualStats.cfg amrecover> extract Extracting files using tape drive changer on host The following tapes are needed: TAPE03 Restoring files into directory /root Continue [?/Y/n]? Y Extracting files using tape drive changer on host Load tape TAPE03 now Continue [?/Y/n/s/t]? Y ./data/IT/VirtualStats/VirtualStats.cfg tar: ./var/log/lastlog: invalid sparse archive member tar: Skipping to next header tar: Error exit delayed from previous errors extract_list - child returned non-zero status: 2 Continue [?/Y/n/r]? Thanks, Gordon
RE: Restore WO Amanda, what am I doing wrong?
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Olivier Nicole > Sent: Wednesday, March 29, 2006 10:06 PM > To: [EMAIL PROTECTED] > Cc: amanda-users@amanda.org > Subject: Re: Restore WO Amanda, what am I doing wrong? > > > So, it's time to get the config files, and maybe indexes off of the > > tapes from the faile machine. > > And eventually, like it was suggested some time ago (from a > web page that I was directed to for some otherproblem); > > you should double back-up the indexes, so you can put up a new > Amanda machine with little efforts. > > I do that by rsync'ing the indexes to anothermachine and by > emailing to me the result of amadmin export after every run > of amanda and every amflush. > > Cheers, > > Olivier > What are the relevant things that need to be double backed up to ease the recovery of a failed amanda machine? Regards, Gordon
RE: Release of amanda-2.5.0b2
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Till
> Sent: Wednesday, February 22, 2006 10:24 AM
> To: amanda-users@amanda.org
> Subject: Re: Release of amanda-2.5.0b2
>
> Jon LaBadie wrote:
> > On Wed, Feb 22, 2006 at 07:47:02AM +0100, Josef Wolf wrote:
> >
> >>On Thu, Jan 19, 2006 at 07:31:08PM -0500, Jean-Louis
> Martineau wrote:
> >>
> >>
> >>>The Amanda core team is pleased to announce the release of Amanda
> >>>2.5.0b2. It is stable and we hope to release 2.5.0 soon.
> test it and
> >>>report it if you find a bug in this release.
> >>
> >>The mail reports that are mailed by amdump have bogus
> numbers in the
> >>MMM:SS columns. For example: this line comes from the logfile:
> >>
> >>
> >> SUCCESS dumper host.do.main /m/b 20060222 2 [sec 115.740 kb 142504
> >> kps 1231.2 orig-kb 521380] SUCCESS chunker host.do.main
> /m/b 20060222
> >> 2 [sec 115.822 kb 142504 kps 1230.6]
> >>
> >>And this is what the mail contains:
> >>
> >>STATISTICS:
> >>
> >> Run Time (hrs:min) 0:14
> >>
> >> DUMPER STATS
> TAPER STATS
> >> HOSTNAME DISK L ORIG-MB OUT-MB COMP% CRYPT% MMM:SS
> KB/s MMM:SS KB/s
> >> -
>
> >> host.do.main /m/b 2 509139 27.3 1:561231.2 N/A N/A
> >>
> >>
> >>The real dump duration was about 115 seconds, but amdump
> says 1231.2 minutes.
> >>Note that the "kps" filed in the logfile contains the value that is
> >>reported my the mail.
> >>
> >
> >
> > I think it is missing data in the new column, CRYPT% ---
> What is that?
>
> I have checked in code to remove "CRYPT%".
>
> >
> > If the data are moved over one column it makes more sense,
> 116sec ==
> > 1:56,
> > 1231 == 1231.
> >
>
> The following patch by John Franks will help too:
> --- server-src/conffile.c 28 Jan 2006 01:40:13 - 1.122
> +++ server-src/conffile.c 18 Feb 2006 01:55:07 - 1.123
> @@ -25,7 +25,7 @@
>*University of Maryland at College Park
>*/
> /*
> - * $Id: conffile.c,v 1.122 2006/01/28 01:40:13 paddy Exp $
> + * $Id: conffile.c,v 1.123 2006/02/18 01:55:07 jfranks Exp $
>*
>* read configuration file
>*/
> @@ -144,12 +144,12 @@
> { "Disk", 1, 11, 11, 0, "%-*.*s", "DISK" },
> { "Level", 1, 1, 1, 0, "%*.*d", "L" },
> { "OrigKB", 1, 7, 0, 0, "%*.*f", "ORIG-KB" },
> -{ "OutKB", 0, 7, 0, 0, "%*.*f", "OUT-KB" },
> -{ "Compress", 0, 6, 1, 0, "%*.*f", "COMP%" },
> -{ "DumpTime", 0, 7, 7, 0, "%*.*s", "MMM:SS" },
> -{ "DumpRate", 0, 6, 1, 0, "%*.*f", "KB/s" },
> +{ "OutKB", 1, 7, 0, 0, "%*.*f", "OUT-KB" },
> +{ "Compress", 1, 6, 1, 0, "%*.*f", "COMP%" },
> +{ "DumpTime", 1, 7, 7, 0, "%*.*s", "MMM:SS" },
> +{ "DumpRate", 1, 6, 1, 0, "%*.*f", "KB/s" },
> { "TapeTime", 1, 6, 6, 0, "%*.*s", "MMM:SS" },
> -{ "TapeRate", 0, 6, 1, 0, "%*.*f", "KB/s" },
> +{ "TapeRate", 1, 6, 1, 0, "%*.*f", "KB/s" },
> { NULL, 0, 0, 0, 0, NULL, NULL }
> };
>
>
>
>
>
>
> --
> Thank you!
> Kevin Till
>
> Amanda documentation: http://wiki.zmanda.com
> Amanda forums:http://forums.zmanda.com
>
I have added the following in my amanda.conf file. It seems to line up the
columns quite nicely without running them all together as in the initial
example:
displayunit "m"
columnspec
"HostName=1:10,Disk=1:14,Level=1:1,OrigKB=1:10,DumpTime=1:8,DumpRate=1:8,Tap
eTime=1:8,TapeRate=1:8"
This is in Amanda 2.4.5. Not sure if there is a setting for the Crypt%
column in 2.5.0.
Regards,
Gordon
RE: Microsoft & Oracle backups
For Exchange you can use exmerge to dump all mailboxes to pst and then back that up. Also, you can use the microsoft backup to backup Exchange as a database (to a file). Run that backup before amanda and then backup that file. SQL can also backup to files which can then be backed up. Active Directory can be handled like Exchange I would think. Use MS backup and then backup that file. Not the most elegant solution, but it will work. Regards, Gordon Mills From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett MarloweSent: Thursday, February 09, 2006 9:57 PMTo: amanda-users@amanda.orgSubject: Microsoft & Oracle backups Hi folks, I’m looking for a way to back up several different Microsoft applications (Exchange 2003, SQL Server, Active Directory) as well as interfacing Amanda with Oracle RMAN. File level backups via Samba won’t quite cut it; file locking issues, etc. I thought I read somewhere (SysAdmin magazine) that there is a windows agent but I can’t seem to find it anywhere. Is there a good reference for how these special cases can be handled? Thanks, Brett
RE: First try at backing up other clients
>> Does you firewall allow outbound connections to your Amanda Server? >> Also, there was a problem with the Amanda connection tracking module about >> a year ago that would prevent backups from working if it was loaded, even if >> there were enough rules otherwise to allow the packets. >> Not sure of the kernel versions that were affected, but it might be in the >> list archives. If you have that module loaded, try unloading it and see if >> it helps (although you would still need rules allowing the Amanda connections). >> Frank Thanks Frank (and everyone else who replied). Frank's suggestion did point me in the right direction. I had an older 2.6.8-mppe kernel. Since I no longer needed the mppe stuff I upgraded to the 2.6.12 kernel in debian's archive. Now it works! Again, thanks to all who helped. Somehow it was the kernel. Regards, Gordon
RE: dumper: FATAL must be run setuid root
Gordon J. Mills III wrote: > Stefan, the only problem I have had with the debian packages was with the > amverifyrun script. It probably depends on the version that you use. > There were some spaces at the end of the fgrep fields which caused it > to not find the tapes used. Once I deleted the extra space at the end > of each line it worked fine. >>>>>Should we take this as a bug into the bugtracker? I guess it could be entered into bugtracker. Of course it may just be a problem with the deb packages in which case the maintainer may just be able to fix them. Like I said, they may already be fixed. Cheers, Gordon
RE: First try at backing up other clients
Thanks Stefan, I do have iptables running on the client since it is my firewall machine. It is currently set to allow all connections from the internal network to the fw though. There is always a chance that I have mangled something there though :-). I will check out the article you cited below. Monitoring the fw logs I see connections from the backup server to the fw on 10080 being accepted. However on the fw machine in the amanda sendbackup logs I see: sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50084 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50085 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50086 sendbackup: time 0.006: waiting for connect on 50084, then 50085, then 50086 sendbackup: time 30.001: stream_accept: timeout after 30 seconds sendbackup: time 30.001: timeout on data port 50084 sendbackup: time 59.997: stream_accept: timeout after 30 seconds sendbackup: time 59.997: timeout on mesg port 50085 sendbackup: time 89.992: stream_accept: timeout after 30 seconds sendbackup: time 89.992: timeout on index port 50086 sendbackup: time 89.992: pid 16879 finish time Sat Feb 4 18:09:20 2006 Any suggestions? Thanks, Gordon -Original Message- From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] Sent: Saturday, February 04, 2006 2:28 PM To: [EMAIL PROTECTED] Subject: Re: First try at backing up other clients Gordon J. Mills III wrote: > I am having a problem backing up another host with my amanda server. > This is my first try at backing up another linux machine. These are > both debian machines. The tape server can backup itself just fine. I > installed amanda-common and amanda-client on the client machine. I > setup the amandahosts file. On the tape server I added the client to > the disklist, etc. If I run amcheck it gives no errors and says all > clients are fine. But when I run the backup (amdump) I get an error for the remote client. > > Here are the lines out of amdump.1: > dumper: stream_client: connect to 10.10.10.3.50037 failed: Connection > refused > driver: result time 69.587 from dumper0: TRY-AGAIN 00-1 could not > connect to data port: Connection refused > > After that it tries again with the same result. Can someone please > point me in the right direction. I know its probably something stupid > but I cannot figure it out. > > Using vtapes, 2.4.5p1 Any firewall active on server and/or client? These issues are very often related to AMANDA's usage of high ports. I don't know how the maintainer of the Debian-AMANDA-pkgs has configured the software, but there are configure-options to choose the port-range AMANDA uses. Maybe read http://wiki.zmanda.com/index.php/Configuration_with_iptables for a start and look for any active firewalling rules. Stefan.
First try at backing up other clients
I am having a problem backing up another host with my amanda server. This is my first try at backing up another linux machine. These are both debian machines. The tape server can backup itself just fine. I installed amanda-common and amanda-client on the client machine. I setup the amandahosts file. On the tape server I added the client to the disklist, etc. If I run amcheck it gives no errors and says all clients are fine. But when I run the backup (amdump) I get an error for the remote client. Here are the lines out of amdump.1: dumper: stream_client: connect to 10.10.10.3.50037 failed: Connection refused driver: result time 69.587 from dumper0: TRY-AGAIN 00-1 could not connect to data port: Connection refused After that it tries again with the same result. Can someone please point me in the right direction. I know its probably something stupid but I cannot figure it out. Using vtapes, 2.4.5p1 Regards, Gordon
RE: dumper: FATAL must be run setuid root
Gene Heskett schrieb: > On Monday 30 January 2006 03:08, Leonid Shulov wrote: >> After I have upgraded amanda in server side to 2.4.5p1-2 version it >> stoped backup. >> In log file of amdump I see: >> >> dumper: FATAL must be run setuid root to communicate correctly >> > What means did you use to install it, rpms, debs, tarballs built onsite? >Yes, Debian-packages, as mentioned before. > >To all users of AMANDA on Debian: >Are these packages problematic in general? > >Thanks, Stefan Stefan, the only problem I have had with the debian packages was with the amverifyrun script. It probably depends on the version that you use. There were some spaces at the end of the fgrep fields which caused it to not find the tapes used. Once I deleted the extra space at the end of each line it worked fine. Oh yeah, there was one other issue with debian but it is not really amanda's fault. You have to change the permissions on the tape device so that the backup user can access it or add the backup user to the group. Regards, Gordon
ACL's on Windows Machines
I'm sure this has come up before but I've only been on the list a short while. Has anyone ever looked into backing up the file permissions (ACL's) on windows client machines using Amanda? For windows clients that seems to be the only major thing missing. Of course an exclusion list would be nice too, but maybe not as important. Just curious as to what others have done or experienced in the way of backing up windows clients and acls. I have seen references to star on the net as perhaps being able to do it Regards, Gordon
RE: System Crash when using Amanda
Yes, I am using the aic7xxx driver. I am using the adaptec 39160 card. My tape drive is a dell 112T, basically a 1U unit with 2 DLT 40/80 drives in it. The other server had the same scsi card with Compaq AIT-35 8 tape autoloader. I will try installing the new kernel to see. The 2 servers that it happened to recently had the debian package kernel 2.6.12-1-smp. Thanks for the info. Regards, Gordon Do you happen to be using the aic7xxx driver ? If so, I had the same problem until the new kernel 2.6.15. --James D. Freels, Ph.D.Oak Ridge National Laboratory[EMAIL PROTECTED]http://www.comsol.com/stories/hfir/
System Crash when using Amanda
I hope this is not a rerun of a previous topic but I have not found anything on the net yet. I have amanda 2.4.5 running on 2 different servers. The problem started about 5 or 6 weeks after implementing amanda. Kernel is 2.6. Several times, shortly after amanda started a backup the server locked up. I could not log on at the console and it did not respond to any services. It seems to be related to when amanda accesses the tape drive to write to tape. Can anyone point me in the right direction as to the cause (and a possible solution) to this problem. I have had to suspend backups on both servers since it happened on both. In fact, the first one ended up crashing 3 times and somehow the server became unrecoverable. I installed a totally new server with new SCSI card for the tape drive and it locked up after 1 week. Hopefully someone will have some insight. Thanks, Gordon
