Re: [CentOS] Offsite hosted backup solutions
-Original Message- From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Nicolas Kovacs Sent: Sunday, December 17, 2017 12:52 PM To: centos@centos.org Subject: Re: [CentOS] Offsite hosted backup solutions > Can't say about Windows clients, but for all my Linux machines, I'm Hands down Veeam Endpoint Backup for Windows clients to a secure samba share. https://www.veeam.com/windows-endpoint-server-backup-free.html 1. Veeam Endpoint Backup is FREE (Seriously) 2. I backup to a Samba share that is locked to the user computer name and unique password a. CentOS 6.9, Samba 3.x, RAID1 backup array 6 TB. (About 78% full) b. WDC WD6002FFWX-68TZ4N0 Red Pro drives c. 40 Windows clients on a 1g connection to BackupPC server (in name only) d. Backups scheduled over a 12 hour period in the evening, e. TWO off-site backups via USB 3.0 interface and external drives using rsync (takes roughly 6-9 hours depending on load) f. ProLiant ML310e Gen8 v2, Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz, 8g ram, SSD / drive 3. YES, I've had to use it for BMR and it does work! a. A BMR over the network is slow but works. Particular machine was a 10/100 client. Been using it for not quite 3 years now after finally giving up on BackupPC. I wrote a simple script to tell me when machines haven't backup in over 5 days so I can go pay attention to them. It's pretty much set and forget. Regards, Richard ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Offsite hosted backup solutions
On 12/18/17 3:14 PM, Richard Zimmerman wrote: > -Original Message- > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Nicolas Kovacs > Sent: Sunday, December 17, 2017 12:52 PM > To: centos@centos.org > Subject: Re: [CentOS] Offsite hosted backup solutions > >> Can't say about Windows clients, but for all my Linux machines, I'm > > Hands down Veeam Endpoint Backup for Windows clients to a secure samba share. > https://www.veeam.com/windows-endpoint-server-backup-free.html Sounds like a good solution for PC backups. Instead of using USB drives, you can set up an offsite server with a cheap server with big drives. OVH low cost brands offer this: https://www.kimsufi.com/us/en/servers.xml https://www.soyoustart.com/us/server-storage/ The cheapest ones only have 1 disk (not softraid) but since it´s a second copy, depending on your budget you can assume the risk that the offsite backup could fail (considering you are already assumming some risk involved on using USB drives). Miguel --- This email has been checked for viruses by AVG. http://www.avg.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos7: backup with rsync problem: "rsync: rsync_xal_set: lremovexattr(""/tmp/test/etc/fstab"", "security.selinux") failed: Permission denied (13)"
If I run this command in order to backup /etc from remote server to
local dir I get a lot of this message:
[root@s-virt tmp]# rsync -a --delete --numeric-ids --relative
--delete-excluded --compress --acls --xattrs rsync://server-dati/root/etc/
/tmp/test/ -v
receiving incremental file list
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/fstab"","security.selinux") failed: Permission
denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/resolv.conf"","security.selinux") failed:
Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/rsyncd.conf"","security.selinux") failed:
Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/rsyncd.secrets"","security.selinux") failed:
Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/lvm/archive/dati_1-728488062.vg"","security.selinux")
failed: Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/lvm/backup/dati"","security.selinux") failed:
Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/samba/.smb.conf.swp"","security.selinux") failed:
Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/samba/smb.conf"","security.selinux") failed:
Permission denied (13)
rsync: rsync_xal_set:
lremovexattr(""/tmp/test/etc/systemd/system/multi-user.target.wants/rsyncd.service"","security.selinux")
failed: Permission denied (13)
sent 671 bytes received 49804 bytes 100950.00 bytes/sec
total size is 30375007 speedup is 601.78
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1518) [generator=3.0.9]
I have also try to "setenforce 0" but the result is the same
It's possible to do a full backup of remote /etc with SElinux attrs to
a local dir?
Many thanks
--
Dario Lesca
(inviato dal mio Linux Fedora 27 Workstation)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] broadcom and centos 7
Hi all, A year or two ago, I installed CentOS 7.0 (or 7.1) on an old MacBook Pro, and compiled the Broadcom drivers as documented here: https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom After not using it for a while, I recently resurrected it, and updated to 7.4. Unfortunately that page has not been updated in a while, so only documents compiling for 7.3. When I try the patch, it fails on one of the hunks (I don't have the exact error, I can grab it later if important). Has anyone had success with this on CentOS 7.4, either with this compile, or the one documented by ELRepo (which I haven't tried yet)? https://elrepo.org/tiki/wl-kmod --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] kernel: blk_cloned_rq_check_limits: over max segments limit., Device Mapper Multipath, iBFT, iSCSI COMSTAR
Hi, WARNING: Long post ahead I have an issue when starting multipathd. The kernel complains about "blk_cloned_rq_check_limits: over max segments limit". The server in question is configured for KVM hosting. It boots via iBFT to an iSCSI volume. Target is COMSTAR and underlying that is a ZFS volume (100GB). The server also has two infiniband cards providing four (4) more paths over SRP (SCSI RDMA Protocol). With multipathd in the initramfs and enabled at boot, I get five paths (but also now the blk_cloned_req_check_limits error) on boot. I/O on the boot volume also causes the multipaths to fail one after the other until only one path remains, issuing the kernel message "blk_cloned_rq_check_limits: over max segments limit" for each failed path. The paths then recover one after the other but have also 'frozen' the system (final path did not recover!) at which point all I can do is reset the power. (I/O can be KVM Guest read/write, running "dracut -f", copying an ISO to /var/lib/libvirt/images or 'dd'ing a 1GB file to /tmp). I have read: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/pdf/dm_multipath/Red_Hat_Enterprise_Linux-7-DM_Multipath-en-US.pdf I have read: https://access.redhat.com/solutions/2437991 I don't use GPFS: http://www-01.ibm.com/support/docview.wss?uid=ssg1S1009622 I actually have two servers with the exact same hardware configuration. Originally they were both CentOS 7 with the default install LVM partitioning structure. For the above host, I have re-installed and removed LVM as it complicated the issue further. It does appear to be somewhat more stable but results on I/O testing are now inconsistent. Things that have changed are: Not using LVM on the host. Freed up some storage reservations (removed snapshots) on the SAN. ENVIRONMENT: CentOS 7.4 System is iBFT boot (boots from iSCSI on 10G card to COMSTAR zfs volume) System also has Infiniband which provide another four (4) paths multipath is initialised in initramfs Kernel is 3.10.0-693.11.1.el7.x86_64 With respect to https://access.redhat.com/solutions/2437991 there is a recommendation to adjust the 'max_sectors_kb' for devices when seeing the kernel error I am encountering. To that end I have queried the /sys/block area for that information the below. For debugging, at boot, I have disabled multipathd service I wrote the below script to query /sys/block for block device information: # cat bin/max_sectors_kb #!/bin/bash printf "%-18s: %-37s %-15s %-18s\n" $sysblk "Sys Block Node" "Device" "max_sectors_kb" "max_hw_sectors_kb" for b in `ls /sys/block/` do sysblk=/sys/block/$b ls $sysblk/dm/name > /dev/null 2>&1 if [ $? -ne 0 ]; then vendor=`cat $sysblk/device/vendor` model=`cat $sysblk/device/model` name="$vendor $model" else name=`cat $sysblk/dm/name` fi max_sectors_kb=`cat $sysblk/queue/max_sectors_kb` max_hw_sectors_kb=`cat $sysblk/queue/max_hw_sectors_kb` printf "%-18s: %-37s %-15s %-18s\n" $sysblk "$name" $max_sectors_kb $max_hw_sectors_kb done The boot volume is identified by the multipath wwid 3600144f05a2769c70001. It's underlying device nodes are: sda, sdd, sde, sdk and sdj. Running the script after boot for the boot device I get this: # max_sectors_kb | grep -e 3600144f05a2769c70001 -e sda -e sdd -e sde -e sdk -e sdj -e max Sys Block Node : Device max_sectors_kb max_hw_sectors_kb /sys/block/dm-1 : 3600144f05a2769c70001 512 32767 /sys/block/dm-5 : 3600144f05a2769c70001p1 512 32767 /sys/block/dm-6 : 3600144f05a2769c70001p2 512 32767 /sys/block/dm-7 : 3600144f05a2769c70001p3 512 32767 /sys/block/sda : SUN COMSTAR 512 32767 /sys/block/sdd : SUN COMSTAR 512 512 /sys/block/sde : SUN COMSTAR 512 512 /sys/block/sdj : SUN COMSTAR 512 512 /sys/block/sdk : SUN COMSTAR 512 512 On starting multipathd service manually I get: Dec 18 12:46:41 lemans systemd: Starting Availability of block devices... Dec 18 12:46:41 lemans systemd: Starting Device-Mapper Multipath Device Controller... Dec 18 12:46:41 lemans systemd: Started Availability of block devices. Dec 18 12:46:41 lemans systemd: Started Device-Mapper Multipath Device Controller. Dec 18 12:46:41 lemans multipathd: 3600144f05a2769c70001: load table [0 209715200 multipath 1 queue_if_no_path 0 1 1 service-time 0 5 1 8:64 1 8:144 1 8:48 1 8:160 1 8:0 1] Dec 18 12:46:41 lemans multipathd: 3600144f000
Re: [CentOS] broadcom and centos 7
On 2017-12-19, Keith Keller wrote: > > https://elrepo.org/tiki/wl-kmod I decided to give this a go, and so far so good. I did need to rebuild the rpm after updating the kernel version from the previous one to the current one, but from the page above it sounds like that's reasonably expected. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
