/:) m0zgen

Linux Backup Solutions

I've been looking for the best Linux backup system, and also reading lots of HN comments.

Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.

Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.

Amanda (comments by sammcj)

It has a lot of management overhead and that's a problem if you don't have time for a full time backup administrator.

I was tired of Chrome eating all my laptop resources so I decided to put some limit to it with cgroup.

As I was using Ubuntu 12.04 with support for cgroup, I installed the package cgroup-bin and add the following group to the file /etc/cgconfig.conf:

group browsers {
    cpu {
#       Set the relative share of CPU resources equal to 25%
        cpu.shares = "256";
 }

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

	# === Optimized my.cnf configuration for MySQL/MariaDB (on Ubuntu, CentOS, Almalinux etc. servers) ===
	#
	# by Fotis Evangelou, developer of Engintron (engintron.com)
	#
	# ~ Updated September 2024 ~
	#
	#
	# The settings provided below are a starting point for a 8-16 GB RAM server with 4-8 CPU cores.
	# If you have different resources available you should adjust accordingly to save CPU, RAM & disk I/O usage.
	#

+# Add field
+echo '{"hello": "world"}' | jq --arg foo bar '. + {foo: $foo}'
+# {
+#   "hello": "world",
+#   "foo": "bar"
+# }
+# Override field value
+echo '{"hello": "world"}' | jq --arg foo bar '. + {hello: $foo}'
+{

	# This is just a cheat sheet:

	# On production
	sudo -u postgres pg_dump database \| gzip -9 > database.sql.gz

	# On local
	scp -C production:~/database.sql.gz
	dropdb database && createdb database
	gunzip < database.sql.gz \| psql database

	yum -y install texlive texlive-latex texlive-xetex
	yum -y install texlive-collection-latex
	yum -y install texlive-collection-latexrecommended
	yum -y install texlive-xetex-def
	yum -y install texlive-collection-xetex
	Only if needed:
	yum -y install texlive-collection-latexextra

	# Set variables in .bashrc file

	# don't forget to change your path correctly!

	export GOPATH=$HOME/golang
	export GOROOT=/usr/local/opt/go/libexec
	export PATH=$PATH:$GOPATH/bin
	export PATH=$PATH:$GOROOT/bin

	package main

	import (
	"fmt"
	"io/ioutil"
	"os"
	"path/filepath"
	"strings"
	)

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048