Amanda backup issue, taking too long now
 

I had an issue where the holding area was getting full, I moved it to another array mounted to /share/stuff/temp problem with this was stuff was completely backed up in the disklist.
So after trying an exclude file that didn't work, I changed the disklist to individual folders under /share/stuff and excluded temp and some other folders that didn't need backing up, now the estimate and backup take ten times longer than they used to?
I ran amcheck conf and get that the holding area is 90gb and 90gb will be used, does this mean it needs a larger holding area? or is it set to tar everything then dump to tape, can I change this so it tars, dumps, delete tar etc?

I can post any configs you want or the log if need be.

No one knows?
running amcheck gives me the following

amcheck conf
Amanda Tape Server Host Check
-----------------------------
Holding disk /home/common/temp: 93867116 KB disk space available, using 93867116 KB

amcheck error
 

I am running a Amanda on Centos el5.


while running amcheck -c backupname I am getting followwing error

please help me out.


ERROR: samurai.esoftech.com: [This client is not configured for samba: //windsor.esoftech.com/ravi]
ERROR: samurai.esoftech.com: [SMBCLIENT program not available]
Client check: 1 host checked in 1.106 seconds. 2 problems found.

(brought to you by Amanda 2.6.0p1)

hmm. Took me a moment to realize that your post is actually a new thread. So, now we have 2 questions kind of tangled.

sachin_shetty -- your error message seems to be telling you what the problem is. Apparently, you have your Amanda configuration set up to do a samba mount and then backup from that? Check out http://wiki.zmanda.com/index.php/Bac...t#Installation. If that doesn't answer your question, please provide some more information about what your configuration is and how you have it installed.

changlinn -- I hope you got things worked out. That post is pretty old. I'm sorry I missed it when it was first posted.

I believe the 90G/90G question is based on your configuration. If your configuration indicates that 100% of the space should be available to be used, it will say that. If your configuration says to reserve, say, 10% for incremental only, then it will tell you 90G available, 81G [to be] used. It doesn't necessarily mean that it will fill up all that space.

If you have your DLE's broken up so that there are several of them representing different directories in /share/stuff, then each of those will be estimated separately. As far as holding disk space, this should end up using less, because when a DLE is completed it can then be put on tape. Depending on how you have your configuration set up, you could have several things running at once, and while one is taping, others could be accumulating on the holding disk.

I'm not sure why the estimates are taking so much longer. I would expect them to take somewhat longer, just because there are multiple of them. The backups themselves are not going to be very efficient, because you have the holding disk on the same partition (I'm assuming) as your DLE's (unless, of course, /share/stuff/temp is itself a partition). I prefer to have my holding disk on a completely separate drive.

Yeah I vaguley recall the resolution being something like that, I think I changed it to tar to the temp directory individual folders then dump to tape.
Way to dig up an old thread though.

amcheck Error
 

Hi;

Somebody please suggest me How to open a new thread. i am new to this forum I searched everything but couldnt find. So finally i have posted it hear

More inforamtion about my amnada server configuration


I have configured a amandaserver 2.61 in my (linux server cent OS el5)(lucknowbackup)and I am have configured two client one of them is windsor(which is running on windows OS (server 2003). and the another client is on linux os (fedora 8).

I have done all the necessary configuration in /etc/amanda/lucknowbackup/amanda.conf

everything was configured properly. Even I have
./confiured --with smbclinet

but still its giving me the same error
tried with installing trough source and even with rpm package but still
the same error



amcheck -cl lucknowbackup
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps/amanda: 45719552 KB disk space available, using 45617152 KB
NOTE: skipping tape checks
NOTE: conf info dir /etc/amanda/lucknowbackup/curinfo does not exist
NOTE: it will be created on the next run.
NOTE: index dir /etc/amanda/lucknowbackup/index does not exist
NOTE: it will be created on the next run.
Server check took 0.001 seconds

Amanda Backup Client Hosts Check
--------------------------------
ERROR: samurai.esoftech.com: [This client is not configured for samba: //windsor.esoftech.com/ravi]
ERROR: samurai.esoftech.com: [SMBCLIENT program not available]
Client check: 1 host checked in 1.104 seconds. 2 problems found.

(brought to you by Amanda 2.6.0p1)

up the top of a forum it has a button that says "Post New Thread" click it and give the thread a tittle and then your first post describing your issues.

From the issue you are having it looks like the server running amanda doesn't have smbclient installed, I am not 100% how to install this on redhat, it has been a long time since I admined any redhat servers but I would say a simply yum install smbclient will do the trick.

You indicate that you did "./confiured --with smbclinet". Hard to tell if that is a typo here or in your original configure. It should be "--with-smbclient" (note the dash in between, tying it together as a single option). Then you have to scan through the output of the configure and make sure there are no errors. It generates a LOT of output, so you might have missed whether it complained that it could not find the smbclient program.

You should make sure samba is installed before doing the configure for Amanda. Then if the smbclient is not in your path, you should use "./configure --with-smbclient=/full/path/to/smbclient". If it is in your path, it will find it, without setting the "=/full/path..."

Hi everybody!!


Hip Hip hurray.we have solved the problem

the problem was in the disklist configuration
we have changed the tar-compress to zwc-compress. so this things worked properly now there is no error

amcheck -c lko

Amanda Backup Client Hosts Check
--------------------------------
Client check: 2 hosts checked in 0.304 seconds. 0 problems found.

(brought to you by Amanda 2.6.0p1)

Thanx a lot

Look at this
 

Hi,

I found about this PCI based hardware products from Indra Networks which can make backup of Amanda faster and also encrypt the data. See if you find this useful. I have not used this personally, but looks like good help.

I've seen and heard enough independent reports to confirm that the posting by encryptionfunda is a case of http://en.wikipedia.org/wiki/Astroturfing