similar to: Amanda Testing RPMs

Hi Robert - I'm running it successfully on C7 using xinetd.? Do you have documentation for running it directly from systemd?? Working xinetd configuration: cat /etc/xinetd.d/amanda # default: off # description:? The client for the Amanda backup system.\ #?????????????? This must be on for systems being backed up\ #?????????????? by Amanda. service amanda { ??? disable???????? = no ???

I am trying to get amanda backup going on a CentOS 7 system and things are not working: sharky4.deepsoft.com% sudo systemctl start amanda-udp [sudo] password for heller: Job for amanda-udp.service failed because a configured resource limit was exceeded. See "systemctl status amanda-udp.service" and "journalctl -xe" for details. sharky4.deepsoft.com% sudo systemctl status -l

CentOS Linux release 7.1.1503 (Core) amanda-3.3.3-13.el7.x86_64 amanda-client-3.3.3-13.el7.x86_64 amanda-libs-3.3.3-13.el7.x86_64 dump-0.4-0.22.b44.el7.x86_64 Hi, I have been using amanda backup for quite a long time now. I'm busy migrating some older hosts to CentOS 7 but have found that the available amanda packages (see above) have not been compiled on a host that has the 'dump'

CentOS Errata and Bugfix Advisory 2015:0748 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0748.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6028eb7fd61883f440b98464a64e4ea9046b940fb71ca21910403d76d1ec1f9a amanda-2.6.1p2-9.el6_6.i686.rpm

CentOS Errata and Bugfix Advisory 2013:0427 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0427.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3bbffdc2b0f669627853199868cf58cc3397e0f108fb856b54421271399359d9 amanda-2.6.1p2-8.el6.i686.rpm 4e1e14f387dfbb9d2658aec76eb9585edca1de73e0600e245da0eb4a395dd884

CentOS Errata and Bugfix Advisory 2011:1539 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1539.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 26faeaceb119c3b27d50abf8c55c7da5 amanda-2.5.0p2-9.el5.i386.rpm 5ced8d685aba893883dcb15bf1955cb3 amanda-2.5.0p2-9.el5.x86_64.rpm 3f3e3b4da4e779db6c577f4ce303c311

CentOS Errata and Bugfix Advisory 2011:1539 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1539.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 26faeaceb119c3b27d50abf8c55c7da5 amanda-2.5.0p2-9.el5.i386.rpm 0220489340c703613394ec0ff19f000a amanda-client-2.5.0p2-9.el5.i386.rpm

Hello, we are using amanda for backup with 2 tape libraries. Last days we made CentOS 7 update to CentOS Linux release 7.6.1810 (Core) Includes from base repository: amanda-client-3.3.3-21.el7.x86_64 amanda-server-3.3.3-21.el7.x86_64 amanda-3.3.3-21.el7.x86_64 amanda-libs-3.3.3-21.el7.x86_64 deleted: version 3.3.3-17 Before the update (= version 3.3.3-17) we run to configs in parallel without

Would anyone have any ideas with smbclient sits at FUTEX_WAIT in below message? Typing: strace smbclient -d 5 shows it sitting at: futex(0x2aaaabdf2dc0, FUTEX_WAIT, 2, NU. SUSE 9.3 x86_64, Samba RPMS from main Samba site rpm -q samba-client samba-client-3.0.23a-0.1.34 -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E

I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the

Hi folks, I've got a bit of a different scenario than I imagine most, and have spent the last 60 or 90 minutes searching Amanda list archives and googling, but did not come up with anything much. Then I went browsing around the Amanda website and found "vaulting" and was wondering whether this would suit my needs. I'm basically searching around for a backup solution and

Hi all, Has anyone used amanda in combination with samba to back up an NT4 server system? I'm able to connect to the server with both smbclient and smbtar on the command line, but I can't get amanda to connect. Supposedly amanda uses smbclient and smbtar to perform the backups. I'm continually getting the following error from amcheck: ERROR: amanda: [PC SHARE //servername/share

hello list, I am attempting to ssh via a user account setup for amanda backups from the backup server to the test backup client. AFAIK everything is setup correctly yet when I ssh as the user to the client I have to type the password. the public key is in the authorized_keys file of the client and permissions all seem correct. Here is a verbose output of the ssh session [amandabackup at

There's an option to get selinux to report on all the 'don't audit' bits, which can be toggled on and off as needed. This may help in debugging. On 01/19/2017 06:25 PM, Jon LaBadie wrote: > Anyone familiar with the selinux policy for the > amanda backup software package? I'm getting lots > of data not being backed up. For example, under > /home there are 2

Anyone familiar with the selinux policy for the amanda backup software package? I'm getting lots of data not being backed up. For example, under /home there are 2 directory trees owned by root. Those get backed up, user home dirs do not. No AVC denials nor messages in /var/log/messages or journalctl log. But if I turn off selinux enforcing, or set amanda_t type to permissive, complete

My whole problem as far as samba was concerned was not compiling with DES support *and* that I did compile with FAST_SHARE_MODES. One clue was this in the samba.log. file. I then did a dejanews search for smb_shm_open and came up with that portion of the solution. ERROR smb_shm_open : mmap failed with code 11 The DES portion came from just reading the WinNT.txt file that came with Samba. I

Ronny Blomme <Ronny.Blomme@elis.rug.ac.be> writes: > The default configuration for smbclient in samba-1.9.18p8 is to send > verbose output to stdout. The output sent to tape is a mix of this > verbose output and the tar-file => corrupt tar file on tape The attached patch for SAMBA fixes this problem, preventing log messages from being printed to stdout if the tar-file is

Has anyone noticed that there appears to be a few problems with regards to Samba and in particular the usage of smbclient, which can do one of the following : 1) Complete & udder death of the NT networking subsystem (which requires a reboot to cure) 2) smbclient appears to lose its connection with the host being contacted and eventually needs to be killed. I'm not too sure how

Hi experts, I didn't have samba installed when I installed amanda, is there any way to add it without re-configure/make amanda ? Thanks Allen Liu IP Application Design and Engineering Bell Canada (613) 781-7368, allen@bellglobal.com 1240 -160 Elgin St, Ottawa,ON, K2P 2C4

Helo, we have had well runnung amanda tape backup with 3.3.3.-17 in CentOS 7. Two weeks ago we updated the server und got the new release. Now LEOM will no longer be correct recognized. Other experince? How to downgrade? amanda is part of base repository and no former release will be found by yum search. -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565