Leaderboard

CA Appdata Backup / Restore (v2) Due to some fundamental problems with XFS / BTRFS, the original version of Appdata Backup / Restore became unworkable and caused lockups for many users. Development has ceased on the original version, and is now switched over to this replacement. Fundamentally they are both the same and accomplish the same goals (namely, backing up your Appdata share and USB / libvirt), but this version is significantly faster at the job. This version uses tar instead of rsync (and offers optional compression of the archive - roughly 50% if not including any downloads in the archive - which you really shouldn't be anyways). Because of using tar, there is no longer any incremental backups. Rather, every backup goes into its own separate dated subfolder. Old backups can optionally be deleted after a successful backup. Even without incremental backups, the speed increase afforded by tar means that there should be no real difference in the end. (ie: A full backup using my appdata on the old plugin takes ~1.5 hours. This plugin can do the same thing uncompressed in about 10 minutes, and compressed in 20 minutes. The optional verification of the archive takes a similar amount of time. An incremental backup on the old plugin using my appdata averaged around 35 minutes). The options for separate destination for USB / VM libvirt backups is changed so that if there is no destination set for those backup's then they will not be backed up. Additionally, unlike the original plugin, no cache drive is necessary, and the appdata source can be stored on any device in your system (ie: unassigned devices). The destination as usual can go to any mount point within your system. Unfortunately because of no more incremental backups, this version may no longer be suitable for ultimately backing up offsite to a cloud service (ie: via rclone) You can find this within the Apps tab (Search for Appdata Backup). The original v1 plugin should be uninstalled if migrating to this version.

I changed the wording and help description. The processes are actually killed at an event before the unmounting of the disks.

Yes.

When testing, I have run 2 VM's with the same cores assigned and also run a Docker container with the same cores assigned as a VM had assigned. So, it doesn't seem like the CPU's are locked to the VM. You can test dynamically assign CPU's so that no cores are fixed to a VM. Basically, edit the XML and turn the section like this; <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> into something like this. <vcpu placement='static'>2</vcpu> This makes for a VM with 2 cores assigned but it spreads the load out over all the hardware CPU cores available instead of the fixed cores you assign.

Make the appdata share private. That way only specified users have access. You can also make it hidden to prevent anyone else from even seeing it, but you can still get to it by specifying its path. As for managing plex plugins, the approach I always take is to just copy them to somewhere else on my server, then ssh and use mc (Midnight Commander) to move them where they belong. And another possibility for editing files directly on your server is to use Squid's own plugin, CA Config Editor.

Add an entry to smb-extra.conf on the flash drive (/config) to share that specific folder directly. I'll post tonight the exact entries to use, but its not too hard with Goggle at your side.

@Paul_Ber Not sure to which price you refer to, but the rebranded LSI 9240-8i cards from IBM, DELL and Fujitsu are very competitive when it comes to costs. The only thing is, you have to crossflash em to IT mode. Check our wiki for other known working adapters. Maybe the trade section of the forum has something you're looking for? @Tuxtech The LSI SAS 9201-16i is often mentioned around here. Although pricing and availability is heavily dependent on your location. As the names suggests, you can hook up 16 drives on that one. I'm not up-to-date but expanders were not cheap also when I checked last time. Another option would be a second 8i card. Also, check the above link for alternative solutions.

Home-Assistant Docker with LetsEncrypt Docker setup on a sub domain Considering I spend/wasted a good deal of time running around in circles trying to get this working and looking at various locations for info, I thought it would be nice to share my setup just incase someone else is going through the same thing. Here is how I have my sub domain encrypted and setup as a reverse proxy through nginx in LetsEncrypt. My letsencrypt docker setup My Router's Firewall The configuration.yaml HTML section for Home-Assistant http: api_password: MyPassWord base_url: 192.168.1.2:8123 A secondary file named "ha" in the /nginx/site-confs directory containing the following code. map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { # Update this line to be your domain server_name SUB.MYDOMAIN.com; # These shouldn't need to be changed listen 80 default_server; #listen [::]:80 default_server ipv6only=on; return 301 https://$host$request_uri; } server { # Update this line to be your domain server_name SUB.MYDOMAIN.com; # Ensure these lines point to your SSL certificate and key ssl_certificate /config/etc/letsencrypt/live/MYDOMAIN.COM/fullchain.pem; ssl_certificate_key /config/etc/letsencrypt/live/MYDOMAIN.COM/privkey.pem; # Use these lines instead if you created a self-signed certificate # ssl_certificate /etc/nginx/ssl/cert.pem; # ssl_certificate_key /etc/nginx/ssl/key.pem; # Ensure this line points to your dhparams file ssl_dhparam /config/nginx/dhparams.pem; # These shouldn't need to be changed listen 443 ssl ; add_header Strict-Transport-Security "max-age=31536000; includeSubdomains"; ssl on; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; proxy_buffering off; location / { # Update this line to be your HA servers local ip and port proxy_pass http://192.168.1.2:8123; proxy_set_header Host $host; proxy_redirect http:// https://; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; } } Startup your HA and LetsEncrypt Docker and you should now be able to securely access Home-Assistant from outside your network. Thank you again to Tyler, Aptalca and CHBMB for your help.