similar to: amanda-client does not recognise 'dump'

hello puppet list My puppet server is now working quite wonderfully. Thanks go out to all who have assisted in getting it to this point. At this point in time my config is now correctly installing packages according to arch,os and release. Centos is working quite well as of now, but I am attempting to get the ubuntu side of things to work as well. I am frankly more familiar with RHEL under

CentOS Linux release 7.2.1511 (Core) Hi, Last night our CentOS 7 server rebooted. Seemingly it's a very clean reboot. I can't find a shred of evidence as to why it happened though. Things I've checked: * sa reports * /var/log/{messages,secure,dmesg,cron} * /var/log/audit/audit.log * lastlog The host is used for KVM virtualisation and connects via multipathing to our OmniOS SAN via

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, Is there a step by step guide to configure amanda server and client on CentOS and backup on hard drive? Regards Kaushal

How about trying commercial RHEV? Eero 22.6.2016 8.02 ap. "Tom Robinson" <tom.robinson at motec.com.au> kirjoitti: > Hi, > > I have two KVM hosts (CentOS 7) and would like them to operate as High > Availability servers, > automatically migrating guests when one of the hosts goes down. > > My question is: Is this even possible? All the documentation for HA

Hi, I've been looking for an answer to this question and can't find anything concrete that says full support for write barriers has been backported to the stock kernel. I've read that: "There is incomplete write barrier support in kernel versions 2.6.32 and earlier (2.6.31 has some support, while 2.6.33 works for all types of device target) - RHEL 6 uses 2.6.32." Now, I

Hi, Not sure if I should post in samba-technical or just samba list. Please advise. Back in February I was trying to do a samba-tool classicupgrade but kept getting SIGSEGV: https://lists.samba.org/archive/samba/2017-February/206409.html I didn't progress much after that. This week I've compiled samba-4.6.5 and installed that. Following the HOW-TO for classic upgrade

Hi, I'm having trouble with the classic upgrade. We have three samba servers: Server1: CentOS 5/Samba 3.6 (with smbldap-tools) Server2: CentOS 6/Samba Version 4.2.14-SerNet-RedHat-23.el6 Server3: CentOS 7/Samba Version 4.2.14-SerNet-RedHat-23.el7 Server 1: CentOS 5/Samba 3.6 (with smbldap-tools) Serves our OpenLDAP backend for centralised authentication (LDAP replicated to two other servers

Hi, I have two KVM hosts (CentOS 7) and would like them to operate as High Availability servers, automatically migrating guests when one of the hosts goes down. My question is: Is this even possible? All the documentation for HA that I've found appears to not do this. Am I missing something? My configuration so fare includes: * SAN Storage Volumes for raw device mappings for guest vms

Hi All, I'm migrating a CentOS 6 bind instance (chrooted) to a CentOS 7 box and am curious of people's opinions on chrooting vs selinux as a way of securing bind. The bind-chroot on CentOS 7 also comes with a script (/usr/libexec/setup-named-chroot.sh) that sets up the much maligned systemd and, through bind mounts, creates and extra level of chroot hierarchy giving:

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

# cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) # uname -r 3.10.0-123.20.1.el7.x86_64 Hi, We use iSCSI over a 10G Ethernet Adapter and SRP over an Infiniband adapter to provide multipathing to our storage: # lspci | grep 10-Gigabit 81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 81:00.1 Ethernet controller: Intel Corporation

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

Hi all, I have two centos 5.4 servers that I use to run several windows kvm guests (10). All works ok (more or less) but I have a problem with backups. These windows guests are configured to use lvm partitions as a virtual disks. My problem is when I need to do guests backups. which is the best form to backup and restore these windows guests? Some examples? I see snapshot's lvm

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

Hi, I've done a classic upgrade to from samba 3.6.23 to samba 4.6.5 bringing across all the user accounts. The samba 3.6.23 we set up with smbldap as an NT Domain with OpenLDAP. After a lot of effort the classic upgrade worked well but now I'm a bit stuck with idmapping. The new AD DC is running 4.6.5 on CentOS7 and I can connect using ADUC. I set up a separate AD DM on a another CentOS7

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

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

At the bottom is what I got returned from AMANDA 2.3.0.5 after patching Samba 1.9.16p11 to give estimates. Any idea what I might not have done yet? My disklist reads: shokk \\thor\depot nocomp-user-gnutar To connect successfully to that server with smbclient, I have to do this, giving the same password that I now have in /etc/amandapass: smbclient \\\\THOR\\DEPOT -U BACKUP Also, the

Hello guys, hope i am not making an offtopic Currently we are looking for storage/backup solution in our company. Basically we need to backup data incrementaly from windows server and centos server + subversion repositories. So far i believe amanda would be best for this situation and also has good reference. Is there anything else - i would be glad to have space for research and choose