when i typed command /usr/sbin/amcheck intra on client side i got following error.(expecting a new tape)
NOTE: info dir /var/log/amanda/intra/curinfo: does not exist
NOTE: it will be created on the next run.
NOTE: index dir /var/log/amanda/intra/index: does not exist
NOTE: it will be created on the next run.
I'm trying to install the client but getting failed dependencies:
libcrypto.so.0.9.7 is needed by amanda-backup_client-3.2.0-1.suse10.0.i586
libcurl.so.3 is needed by amanda-backup_client-3.2.0-1.suse10.0.i586
libssl.so.0.9.7 is needed by amanda-backup_client-3.2.0-1.suse10.0.i586
where to find those files and how to install them? I'm running OpenSuSE 11.1
I have looked many places for good tutorial on configuration of amanda client with Karmic, but none of them are good enough. I basically got following message no matter what I change in Client side.
1. I am using 64-bit Ubuntu Karmic client with 2.5.2p1 amanda-client with xinetd.
2. The user is backup, group is backup.
3. The config file is located at /etc/amandahosts, and /var/backups/.amandahosts and /var/lib/amanda/.amand ahosts using soft link to the /etc/amandahosts file.
4. /etc/amandahosts file have following line.192.168.0.14 backup amdump.The 192.168.0.14 is server IP address.
I read that AMANDA is only for Intel processors, but I have a PowerPC processor and I want to install AMANDA.Someone said that I have to find the distro of my RH and there should be AMANDA packages available.
My distro is: Red Hat Enterprise Linux AS release 4 (Nahant Update 7)Where can i find AMANDA for my distro??
I am trying to install AMANDA onto a RH Linux4 client, but when I type in: rpm -i amanda-backup_client-2.6.1p2-1.rhel4.i386.rpm
I get the error:
libcurl.so.3 is needed by amanda-backup_client-2.6.1p2-1.rhel4.i386
Suggested resolutions:
/var/spool/up2datecurl-7.12.1-11.el4.ppc.rpm
If I want to restore an full backup of AMANDA, will it restore the OS along with the files or does it just restore all the files in /
View 2 Replies View RelatedI've run into a problem when trying to restore a file using AMANDA. My setup is as follows: I have a server that runs on Red Hat Enterprise Linux Server release 5.4 and I have a client that runs on Red Hat Enterprise Linux AS release 4. I successfully backed up files on the client using AMANDA.
Now I am trying to restore a file from the backup and restore it to the client running Red Hat Enterprise Linux AS release 4. In order to do this, I have to go through the server which runs Red Hat Enterprise Linux Server release 5.4.
Here is the problem I encounter. When I try the restore, it freezes at the extraction process. I've left it running for the night and still it is stuck at the same place. The restore never completes.
So I'm wondering if anyone knows what seems to be the issue? Could it be that the AMANDA driver I installed does not allow restore with different versions of Red Hat? Or is there an update in Red Hat 4 that would fix this issue?
I installed amanda on a client that uses Red Hat Enterprise Linux 4. When I do an amcheck from the server, I get this:
Amanda Backup Client Hosts Check
--------------------------------
WARNING: 192.168.3.23: selfcheck request failed: recv error: Connection reset by peer
Client check: 1 host checked in 0.022 seconds. 1 problem found.
I am using bsdtcp. I get an ACK error if I switch the client to bsd authentication. I read that I should enter servers adress to hosts file in /etc/ directory?
When I do an amcheck, I get this Amanda Backup Client Hosts Check WARNING: noname.com: selfcheck request failed: recv error: Connection reset by peer Client check: 1 host checked in 0.022 seconds. 1 problem found.
I am using bsdtcp. I get an ack error if I switch the client to bsd authentication. What should I do, how do I fix it? I read that I should enter servers address to hosts file in /etc/ directory? Here is the log in /var/log/messages:
[Code]....
I am trying to backup a client called greetings.com, but when I do an amcheck on the server, I get:
WARNING: greetings.com: selfcheck request failed: Connection refused
I'm fairly competent with Linux at this stage and as we have just installed a new Red Hat 5.5 Server to host our DB at work it has basically fallen to me to sort everything out. The only thing I'm not 100% on is a backup strategy at the moment. Basically, the server / DB is not that big and as such we will be doing a full backup every night of the whole file system.
As it is there are several LVM partitions across several disks (these are all virtual both on the SAN and as a virtual machine). My question is what would be the best way to create a full backup overnight of the whole server including all the partitions (or a backup of each partition I'm guessing is more feasible). This doesn't seem to be too difficult to do, but my main problem is restoring the backup.
Is it a simple matter of basically .tar'ing the whole / filesystem? and if so, to restore can I just use a live CD to restore the partition that is needed? How does LVM affect the restoration process? I have looked at Amanda as a backup solution, though we wont be backing up directly to tape (backup to a share location then copy to the tape drive).
Where can I download the latest Red Hat drivers for AMANDA?
View 2 Replies View RelatedI've run into a problem when trying to restore a file using AMANDA.My setup is as follows:
I have a server that runs on Red Hat Enterprise Linux Server release 5.4 and I have a client that runs on Red Hat Enterprise Linux AS release 4. I successfully backed up files on the client using AMANDA.Now I am trying to restore a file from the backup and restore it to the client running Red Hat Enterprise Linux AS release 4. In order to do this, I have to go through the server which runs Red Hat Enterprise Linux Server release 5.4.
Here is the problem I encounter. When I try the restore, it freezes at the extraction process. I've left it running for the night and still it is stuck at the same place. The restore never completes.So I'm wondering if anyone knows what seems to be the issue? Could it be that the AMANDA driver I installed does not allow restore with different versions of Red Hat? Or is there an update in Red Hat 4 that would fix this issue?
I'm configuring Amanda Enterprise on an OpenSuSE 11.3 system, and everything but the scheduled backups are running. I decided to try and fix it tonight, but I'm pretty fed up by now.
So here's the background:
The application creates an account on the box named "amandabackup" and adds it to the 'video' and 'disk' groups.
It generates cron jobs in /etc/zmanda/zmc_aee/crontab, which is configured as the location of the crontab file for the amandabackup user.
The crontab is owned by amandabackup:disk with a mask of 644.
So I played around with it a little bit; I ran the backup task manually as amandabackup, which worked fine.
I then tried adding the following to the crontab:
And touched amandacron.log, then made sure it was owned by amandabackup with a mask of 644 (i also tried /etc/amanda/amandacron.log, which is a directory the account stores backup session configs in, so I know it can write to it properly). The file is never updated. I tried adding amandabackup to different groups (it's currently been added to the "Users" group), with no success. I tried a symlink to the crontab file in /etc/cron.d to see if that would make a difference, but it didn't.
At this point, I went online and tried some more stuff I found:
I checked /var/log/mail/amandabackup - everything *but* cron jobs were reporting to it.
I verified cron was running with both "ps -ef | grep cron" and "rccron status"
I ensured /var/spool/cron/tabs/amandabackup existed, showed the proper entries, and was set to 644. (this one's the important bit)I checked /var/log/messages, and every minute on the dot I see: <timestamp> /usr/sbin/cron[PID]: Permission Denied
I ensured there was no /etc/cron.allow, and that /etc/cron.deny did not contain amandabackup.
I tried making an /etc/cron.allow, adding amandabackup, and restarting the cron daemon, but this did nothing.
I don't think I've forgotten anything, but my attempts have been getting progressively more feverish, so I'm not positive. Is there some annoying YAST cron panel I'm not seeing? Is there some way of getting more verbose logging out of the cron daemon than just "permission denied"? Is there some draconian rule about crontabs only working based on some otherwise-arbitrary account setting?
I'm trying to install Amanda 3.2 on Ubuntu 10.10 (Maverick) using Ubuntu 10.04 deb package. The installation was successful using the dpkg command. The problem crops up when configuring such amanda. When creating a user amandabackup using passwd amandabackup and then enter in it through su - amandabackup a permission denied problem comes up. When enter amserverconfig Dailyset 1 etc etc the server response with :
amservingconfig: critical (fatal): Cannot create debug file "/var/log/amanda/server/amserverconfig.2010120307947.debug": Permission denied and continues
The permissions are set to rw 1 amandabackup backup. I can't understand why it's telling me permission denied each time.
I have a client that is using a windows based backup system called Retrospect and will be installing Linux to replace his windows server. Right now the way it works is on the XP pro workstation Norton 360 makes a backup to the server and then Retrospect make it backups every night. I want to add a linux based backup system that will give them a historical backup system that had XP pro client software that can backup open files and such I can do away with the Norton backup stuff and streamline this setup. I need it to have the capability to go back in time to restore something of an older date this historical. I was looking into:
[URL]
I have never used either one and was wondering what the linux community wold recommend between the two or if there is something better that has client software and free and does it have a GUI for my clients? I am leaning toward AMANDA after reading Jeremy's article:
[URL]
and there seams to be a webadmin gui as well.
[URL]
I can backup anything that is smaller then a single LTO4 tape, however I have one DLE where the amount of information I want to backup is 950GB (which happens to be on the backup server) but the tape is only 800GB. How can I get this to span multiple tapes for a single DLE?
I have set the tape_splitsize to 5GB for right now, but it is taking forever to backup the volume. Because the volume is larger then the holding disk, Amanda resorts to the fallback_splitsize which I have set to 1GB. My understanding is that this basically stores 1GB of data in memory and then writes it to tape?
Since I have a holding disk of 200GB, is there a way I can write 80GB of data to tape instead of 1GB chunks at a time?
What is the ideal way to backup large amounts of data by spanning multiple tapes and writing to the tape as quickly as possible?
After my 8.04 debacle here:I basically gave up on trying to write an install guide for Hardy and Amanda. Others had done it better and with how muddled I was by the end of getting a working server, I wasn't sure I could repeat it.Now in Lucid, I've managed to get another working amanda server going, I'm fairly sure I can repeat it and but I question:Installation with 'apt-get install amanda-server' uses the user backup in the group backup.Installation of the ZWC client uses the user amandabackup. while thankfully ZWC has included reg keys:
HKEY_LOCAL_MACHINESOFTWAREmandaWC1.0Install BackupUserHKEY_LOCAL_MACHINESOFTWAREmandaWC1.0Install RecoveryUserto change the user on the client, this is messy, requires regedit (which normally is locked out by group policy), editing the service in service.msc and creation of a new user account named backup in addition to the installer's default on each client.The actual question is:1) Is there a reason for the use of backup:backup? (rather than amandabackup:disk or amandabackup:backup)
2) Is there any sort of flag that could be set, script to change the user within the repo atinstall time.Or generally an easier way of doing this than compiling each time I do an install.
Amanda Backup System - Error
I have attached the error with amanda system. It is in Amanda is in OpenSuse, I checked for dtimeout in conf file but it is not there.
driver: find_diskspace: time 1641.864: find diskspace: selected /sandata/amanda/hdisk free 159240608 reserved 4633344 dumpers 3
driver: find_diskspace: time 1641.864: want 3185984 K
driver: find_diskspace: time 1641.864: find diskspace: size 3185984 hf 159240608 df 159240576 da 3185984 ha 3186016
driver: find_diskspace: time 1641.864: find diskspace: selected /sansdata/amanda/hdisk free 159240608 reserved 3186016 dumpers 3
driver: state time 1800.609 free kps: 1079613 space: 159240608 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 7 roomq: 0 wakeup: 0 driver-idle: client-constrained
driver: interface-state time 1800.609 if default: free 79613 if LOCAL: free 1000000
driver: hdisk-state time 1800.609 hdisk 0: free 159240608 dumpers 3
driver: result time 1800.729 from dumper2: FAILED 02-00003 "[data timeout] .....
I have some issue with my amanda backup server, which is connecting with Scalar Quantum i500 via FC. I got the error as below 3 days ago.
These dumps were to tape 000289.
*** A TAPE ERROR OCCURRED: [No more writable valid tape found].
Normally I will load the proper tapes and run the amflush to push stuff from the holding disk to tapes manually. However this time amflush in this case did not help, Amanda immediately responded with an out of tape error again.
Meanwhile I got some errors from dmesg as well
st3: Error 18 (sugg. bt 0x0, driver bt 0x0, host bt 0x0).
scsi1 (0,3,0) : reservation conflict
when i ran amcheck DailySet1 as backup user and got these messages:
[Code]....
I did a port scan on my server from outside my network and saw that port 10080 AMANDA is open.Amanda isn't installed on any of my computers or my server and the port is not forwarded by my modem or router. So why is this port open and how can I close it?
View 6 Replies View Relatedwhen I reviewed the error_log I found that it is logging thousands of errors which are similar. I've included a sample of the errors. The following error seems to happen constantly, from many different ip's...
Code:
[Thu Apr 22 01:02:06 2010] [error] [client (the ip address removed)]
File does not exist: /home/virtual/site4/fst/var/www/html/colombia-news,
I am in urgent requirement of free simulation source code for Intra-domain. Mobility Management in OMNETT++ or NS2. Where I can post queries for OMNETT++.
View 1 Replies View RelatedI'm running the ubuntu based Green OS and cant get my video card properly configured. i've already gone through the forums to figure out what i need to do to get my ATI card working but my system wont let me access the xorg.conf file. i can see it using the the GOS file editor but it wont let me save the modifications. when i attempt to edit from a terminal window with su privelages it tells me that /etc/x11/xorg.conf does not exist. i've even tried booting into recovery mode and using the root instead of the sudo command. nothing i've tried will let me open the file.
View 3 Replies View Relatedmonitor is a Optiquest Q19wb. I normally have is set on 1280x1024, but fedora will only go to 800x600. It has detected the monitor correctly. Not sure if being connected to KVM will cause issues. The xorg.conf does not exist. Have installed system-config-display but have not run yet.
View 1 Replies View RelatedWhen I use wvdial, most of the times on first attempt I get output like that
Quote:
[root@localhost apinder]# wvdial
--> WvDial: Internet dialer version 1.60
--> Warning: inherited section [Modem0] does not exist in wvdial.conf
--> Cannot get information for serial port.
[code]....
I find it very frustrating that documentation suggests using PEERDNS=no in /etc/sysconfig/network-scripts/ ifcfg-eth0 in order to override resolv.conf information only to find out that both NM and network init scripts ignore DNS1, DNS2 and DOMAIN settings.So my question is how do I correctly configure resolv.conf settings that will persistently override dhcp information on a F12 system that has NM removed and uses the network service scripts?
View 3 Replies View RelatedAlright, I have downloaded the upgrade for 10.04 and installed upgraded from my previous 8.04. Everything was working all fine until I had to reboot my pc. When I did i got some errors
Mount: Mounting none on /dev
It goes on to tell me that my UUID does not exist. Then it says
ALERT! Alert! /dev/disk/by-uuid/xxxxxxxx-xxxx-xxxx-xx$ does not exist. Dropping to a shell! It then drops to a very simple shell which has no flexibility and is very frustrating.
EDIT: This is the full error message
Mount: Mounting none on /dev
boot args cat /proc/cmdline
check rootdelay =(did the system wait long enough?)
check root =(did the system wait for the right device?)
missing modules ( cat /proc/modules)ALERT! /dev/mapper/debian-root does not exist dropping to a shell.
I have resolvconf installed to prevent multiple programs from fighting to update /etc/resolv.conf at the same time an corrupting it.From what I understand resolvconf a package found in the repos is suppose to act as the gatekeeper to /etc/resolv.conf and all programs must go thru it to update resolv.conf. Hence /etc/resolv.conf is written in a orderly manner.
from time to time though something goes awry and resolvconf writes old, wrong stale into /etc/resolv.conf, for a connection that may be down or no longer exists along with the correct info for the current connection.Usually i would fix this by uninstalling and reinstalling the resolvconf package.I was tired of this so i went digging around in
/etc/resolvconf and found the subdirectory
/etc/resolvconf/run/interface
This is where it looks like resolvconf caches interface info that goes into
/etc/resolv.conf
I think what happens is resolvconf is suppose to clean this up in an orderly way but sometimes old interface files may be left here.So for instance in mine were the files eth0 and wlan0.with dns info for each stored in the relative file. I no longer have an eth0 only a wlan0 so resolvconf was still pulling info from both
/etc/resolvconf/run/interface/wlan0 and /etc/resolvconf/run/interface/eth0
with the result of an incorrect dns info in /etc/resolv.conf To make a long story short I just deleted /etc/resolvconf/run/interface/eth0 and was good to go. So if you are using resolvconf and run into this problem you may use this work around.