Close

PFsense 2.4.3 There were error(s) loading the rules: /tmp/rules.debug:18: cannot define table bogonsv6: Cannot allocate memory – The line in question read

Increase the Firewall Maximum Table Entries size to 400000 in System > Advanced, Firewall & NAT

Advertisements

Free DNS providers

Google 8.8.8.8: Private and unfiltered. Most popular option.
CloudFlare 1.1.1.1: Private and unfiltered. New player.
Quad9 9.9.9.9: Private and security aware. New player that blocks access to malicious domains.
OpenDNS 208.67.222.222: Old player that blocks malicious domains and offers the option to block adult content.
Norton DNS 199.85.126.20: Old player that blocks malicious domains and is integrated with their Antivirus.
CleanBrowsing 185.228.168.168: Private and security aware. New player that blocks access to adult content.
Yandex DNS 77.88.8.7: Old player that blocks malicious domains. Very popular in Russia.
Comodo DNS 8.26.56.26: Old player that blocks malicious domains.

If you’re still using old release (Ubuntu < 12.04) and still want to get updates using apt-get

deb http://old-releases.ubuntu.com/ubuntu/ oneiric main
deb-src http://old-releases.ubuntu.com/ubuntu/ oneiric main
deb http://old-releases.ubuntu.com/ubuntu/ oneiric-updates main
deb-src http://old-releases.ubuntu.com/ubuntu/ oneiric-updates main
deb http://old-releases.ubuntu.com/ubuntu/ oneiric universe
deb-src http://old-releases.ubuntu.com/ubuntu/ oneiric universe
deb http://old-releases.ubuntu.com/ubuntu/ oneiric-updates universe
deb-src http://old-releases.ubuntu.com/ubuntu/ oneiric-updates universe
deb http://old-releases.ubuntu.com/ubuntu oneiric-security main
deb-src http://old-releases.ubuntu.com/ubuntu oneiric-security main
deb http://old-releases.ubuntu.com/ubuntu oneiric-security universe
deb-src http://old-releases.ubuntu.com/ubuntu oneiric-security universe

Installing Veeam Agent for Microsoft Windows in Unattended Mode (Veeam Agent for Microsoft Windows 2.1)

Installation Syntax

To install Veeam Agent for Microsoft Windows in the unattended mode, use a command with the following syntax:

<path_to_exe> /silent /accepteula

where <path_to_exe> is a path to the Veeam Agent for Microsoft Windows installation file.

Veeam Agent for Microsoft Windows uses the following codes to report about the installation results:

1000 — Veeam Agent for Microsoft Windows has been successfully installed.
1001 — prerequisite components required for Veeam Agent for Microsoft Windows have been installed on the machine. Veeam Agent for Microsoft Windows has not been installed. The machine needs to be rebooted.
1002 — Veeam Agent for Microsoft Windows installation has failed.
1101 — Veeam Agent for Microsoft Windows has been installed. The machine needs to be rebooted.

Proxmox VE differential backups

Source: https://ayufan.eu/projects/proxmox-ve-differential-backups/

Proxmox VE is a complete virtualization management solution for servers. You can virtualize even the most demanding application workloads running on Linux and Windows Servers. Checkout their page: proxmox.com

Due to lack of better backup functionality I prepared patches to support differential backups in Proxmox VE. These patches are in use for over a year.

Currently supported versions are 3.4, 4.1, 4.2, 4.3, 4.4, 5.0.

What are differential backups?

According to Wikipedia:

A differential backup is a type of data backup that preserves data saving only the difference in the data since the last full backup. (…) Another advantage, at least as compared to the incremental backup method of data backup, is that at data restoration time, at most two backup media are ever needed to restore all the data. This simplifies data restores as well as increases the likelihood of shortening data restoration time.

What my patches do?

My patches extends vzdump, xdelta3 and Web-GUI support. And yes, these patches fully support OpenVZ and KVM.

System administrator can use one additional parameter in Backup Jobs (Datacenter -> Backup -> Add/Edit) the Full Backup Every:

  • By default this value is set to 0. Which simply means: use old behavior (always create full backups).
  • But if you specify value larger than 0, for example 7. It will instruct the vzdump to create full backup once a week and use differentials for the rest.

Please consider the following example:

    vzdump 101 --remove 0 --mode snapshot --compress lzo --storage local --node hvm --fullbackup 4

It will create full backup of VM101 every 4 days, compressed using lzo, stored on local storage.

How to install?

There are three files:

    c760d7481beae8dba3c62f1d95c6fbde  pve-2.2-diff-backup-addon
    42c1a0f34eca9ac23de83523db00f6c5  pve-2.3-diff-backup-addon
    1292670afa84914aac4ebda59d2a7122  pve-3.0-diff-backup-addon
    cd68c203bb1804105a3b4acd52382f6d  pve-3.1-diff-backup-addon
    67fb4d2b397759fb83066ae93cc07b78  pve-3.2-diff-backup-addon
    3e095bd0ed5744a545016018e235fa27  pve-3.3-diff-backup-addon
    350ed7844a5802ca114a6b60e0b013dc  pve-3.4-diff-backup-addon
    e33ef0b546fb16baacc4baed57af20d2  pve-3.4-14-diff-backup-addon
    1657dbc46d9f8b379896a9c0a7dffc3e  pve-4.0-diff-backup-addon
    e5701606733fb10dc117ff2b008da11b  pve-4.1-diff-backup-addon
    9fd8b3cb99283e55b00d694ce633b723  pve-4.1-22-diff-backup-addon
    300b07f7837200b9cc281aff06105991  pve-4.2-diff-backup-addon
    05c8520f87443a8902faa3b24d25735f  pve-4.2-17-diff-backup-addon
    c9fc4aeb2e42d1d78f54c8e7b007fc3d  pve-4.3-diff-backup-addon
    3991a5773e1d85503513889eaf04910c  pve-4.4-diff-backup-addon
    6646d0bc79a70beeca482dcf5354d021  pve-4.4-13-diff-backup-addon
    cc07c340b4dbfcf00e9d216a2f8f8466  pve-5.0-diff-backup-addon

The installation procedure is fairly simple:

  1. Logged as root download:For PVE 2.2 (deprecated):
    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-2.2-diff-backup-addon
    

    For PVE 2.3 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-2.3-diff-backup-addon
    

    For PVE 3.0 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.0-diff-backup-addon
    

    For PVE 3.1 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.1-diff-backup-addon
    

    For PVE 3.2 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.2-diff-backup-addon
    

    For PVE 3.3 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.3-diff-backup-addon
    

    For PVE 3.4 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.4-diff-backup-addon
    

    For PVE 4.0 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.0-diff-backup-addon
    

    For PVE 4.1 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.1-diff-backup-addon
    

    For PVE 4.1-22 (compatible with 4.1-22 and newer) (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.1-22-diff-backup-addon
    

    For PVE 4.2 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.2-diff-backup-addon
    

    For PVE 3.4-14 (compatible with 3.4-14 and newer) (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.4-14-diff-backup-addon
    

    For PVE 4.2-17 (compatible with 4.2-17 and newer) (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.2-17-diff-backup-addon
    

    For PVE 4.3 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.3-diff-backup-addon
    

    For PVE 4.4 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.4-diff-backup-addon
    

    For PVE 4.4-13 (compatible with 4.4-13 and newer) (stable):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.4-13-diff-backup-addon
    

    For PVE 5.0 (stable):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-5.0-diff-backup-addon
    
  2. Execute bash script. The script contains all needed patches:
    bash pve-4.4-diff-backup-addon apply
    
  3. When everything went right, you’ll see:
    Proxmox VE 5.0 - differential backup support
    Kamil Trzcinski, http://ayufan.eu/, ayufan@ayufan.eu
    
    PATCHED: /usr/share/pve-manager/
    PATCHED: /usr/share/perl5/PVE/
    
    Restarting PVE API Proxy Server: pveproxy.
    Restarting PVE Daemon: pvedaemon.
    
  4. Download and install xdelta3. If you want to use LZOP compressor, you have to download my xdelta3 compilation.
    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-xdelta3_3.0.6-1_amd64.deb
    dpkg -i pve-xdelta3_3.0.6-1_amd64.deb
    

    However, if you paranoid about installing untrusted applications you can compile the package yourself. All the sources can be found here: pve-xdelta3-master.tar.bz2

    Previous release of xdelta was 3.0.5. Please update to the newer one: 3.0.6.

And what about uninstall?

The procedure is simpler than installation. Type in the bash:

    bash pve-5.0-diff-backup-addon revert

After a while, you’ll see:

    Proxmox VE 5.0 - differential backup support
    Kamil Trzcinski, http://ayufan.eu/, ayufan@ayufan.eu

    RESTORED: /usr/share/pve-manager/
    RESTORED: /usr/share/perl5/PVE/

    Restarting PVE API Proxy Server: pveproxy.
    Restarting PVE Daemon: pvedaemon.

What about UPGRADE? (READ THIS)

This is important part. If you will ever want to upgrade your Proxmox installation (by apt-get dist-upgrade or apt-get upgrade) ALWAYS revert/uninstall patches. You will still be able to apply them afterwards.

How to apply new patch version?

  • Use previous patch to revert changes.
  • Download new patch version and apply as described before.

The results

The results are really astonishing! These are real word values:

    VM   full      diff 1day   diff 2days   diff 3days    diff 4days
    1.   39.10GB   41MB        47MB         51MB          55MB
    2.   96.84GB   1.07GB      1.38GB       1.43GB        1.68GB
    3.   83.95GB   1.68GB      2.66GB       3.69GB        4.25GB
    4.   9.19GB    76KB        76KB         166MB         198MB

You see the differences. The diff sizes strictly depends on the use of the VMs. Using differential backups I have backups from last month (full backup once a week, differential daily)

Why this is not upstream?

I tried to push the changes upstream. They were rejected by Dietmar:

We removed that feature 3 years ago. I have no plans to re-add that. We want to keep vzdump a simple tool.

But I thought that it would be really shame if I wouldn’t go public with this.

Is it stable?

Yes, it is. This extensions uses xdelta3 as differential backup tool, which proven to be well tested and stable. I use it for about 9 months on 4 different Proxmox based servers. No problems so far.

However, if you happen to be paranoidal about backups… You should consider running following script. The script simply tries to verify all differential backups. I recently updated the script to support new VMA archive. So now you can verify backups all supported backups.

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-verify-backups
    chmod +x pve-verify-backups
    ./pve-verify-backups <backup-dir>

FAQ

In case of any problems applying or reverting patches you can always simple revert back to stock. Simply reinstall modified packages:

    apt-get --reinstall install pve-manager qemu-server libpve-storage-perl

Then you can try to reapply patches once again.

In order to remove all leftovers you have to edit /etc/pve/vzdump.cron and remove fullbackup switch from vzdump command line.

Changelog

  • v1: initial public release with support for PVE2.2 and PVE2.3 (2013-03-05)
  • v2: improved kvm backup size and speed for PVE2.3 (2013-03-08)
  • v3: added support for PVE3.0 (2013-06-02)
  • v3′: updated pve-verify-backups to support VMA archives (2013-06-06)
  • v3”: updated patches to support PVE3.1 (2013-08-24)
  • v3”: updated xdelta3 to 3.0.6. More info about changes: http://xdelta.org/ (2013-08-24)
  • v3”: updated patches to support PVE3.2 (2014-03-15)
  • v3”: added FAQ (2014-04-30)
  • v3”: updated patches to support PVE3.3 (2014-09-23)
  • v3”: updated patches to support PVE3.4 (2015-02-26)
  • v3”: updated patches to support PVE4.0 (2015-11-07)
  • v3”: updated patches to support PVE4.1 (2016-01-22)
  • v3”: updated patches to support PVE4.1-22 (2016-04-13)
  • v3”: updated patches to support PVE4.2 (2016-05-02)
  • v3”: updated patches to support PVE3.4-14 (2016-08-02)
  • v3”: updated patches to support PVE4.2-17 (2016-08-02)
  • v3”: updated patches to support PVE4.3 (2016-10-24)
  • v3”: updated patches to support PVE4.4 (2017-01-23)
  • v3”: updated patches to support PVE4.4-13 (2017-04-10)
  • v3”: updated patches to support PVE5.0 (2017-07-20)

Detailed list of changes

  1. pve-xdelta3:
  2. vzdump:
    • added “fullbackup” option
  3. qmrestore and vzrestore:
    • added support for differential backups
  4. PVE.dc.BackupEdit:
    • added controls for maxfiles and fullbackup

How to completely disable Cortana on Windows 10c

Cortana is very integrated with Windows Search and fully disabling it will break Search. However, if you would like to keep Search functional, you can just disable the “Cortana-y” parts of Cortana.

To disable Cortana in windows 10

  1. Press Win + R keyboard accelerator to open Run dialog box.
  2. Type GPedit.msc and hit Enter or OK to open Local Group Policy Editor. Navigate to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Search.
  3. In the right pane, double click on policy named Allow Cortana.
  4. Select the Disabled radio button.
  5. Restart the PC and Cortana and Bing Search will be disabled. (May work after signing out and in again)

Policy Description

This policy setting specifies whether Cortana is allowed on the device.

If you enable or don’t configure this setting, Cortana will be allowed on the device. If you disable this setting, Cortana will be turned off.

With this set, users will still be able to use search to find things on the device and on the Internet.

Source: https://superuser.com/questions/949569/can-i-completely-disable-cortana-on-windows-10

Safest way to clean up boot partition – Ubuntu 14.04LTS-x64

Reference

Case I: if /boot is not 100% full and apt is working

1. Check the current kernel version

$ uname -r 

It will shows the list like below:

3.19.0-64-generic

2. Remove the OLD kernels

2.a. List the old kernel

$ sudo dpkg --list 'linux-image*'|awk '{ if ($1=="ii") print $2}'|grep -v `uname -r`

You will get the list of images something like below:

linux-image-3.19.0-25-generic
linux-image-3.19.0-56-generic
linux-image-3.19.0-58-generic
linux-image-3.19.0-59-generic
linux-image-3.19.0-61-generic
linux-image-3.19.0-65-generic
linux-image-extra-3.19.0-25-generic
linux-image-extra-3.19.0-56-generic
linux-image-extra-3.19.0-58-generic
linux-image-extra-3.19.0-59-generic
linux-image-extra-3.19.0-61-generic

2.b. Now its time to remove old kernel one by one as

$ sudo apt-get purge linux-image-3.19.0-25-generic
$ sudo apt-get purge linux-image-3.19.0-56-generic
$ sudo apt-get purge linux-image-3.19.0-58-generic
$ sudo apt-get purge linux-image-3.19.0-59-generic
$ sudo apt-get purge linux-image-3.19.0-61-generic
$ sudo apt-get purge linux-image-3.19.0-65-generic

When you’re done removing the older kernels, you can run this to remove ever packages you won’t need anymore:

$ sudo apt-get autoremove

And finally you can run this to update grub kernel list:

$ sudo update-grub

Case II: Can’t Use apt i.e. /boot is 100% full

NOTE: this is only if you can’t use apt to clean up due to a 100% full /boot

1. Get the list of kernel images

Get the list of kernel images and determine what you can do without. This command will show installed kernels except the currently running one

$ sudo dpkg --list 'linux-image*'|awk '{ if ($1=="ii") print $2}'|grep -v `uname -r`

You will get the list of images somethign like below:

linux-image-3.19.0-25-generic
linux-image-3.19.0-56-generic
linux-image-3.19.0-58-generic
linux-image-3.19.0-59-generic
linux-image-3.19.0-61-generic
linux-image-3.19.0-65-generic
linux-image-extra-3.19.0-25-generic
linux-image-extra-3.19.0-56-generic
linux-image-extra-3.19.0-58-generic
linux-image-extra-3.19.0-59-generic
linux-image-extra-3.19.0-61-generic

2. Prepare Delete

Craft a command to delete all files in /boot for kernels that don’t matter to you using brace expansion to keep you sane. Remember to exclude the current and two newest kernel images. From above Example, it’s

sudo rm -rf /boot/*-3.19.0-{25,56,58,59,61,65}-*

3. Clean up what’s making apt grumpy about a partial install.

sudo apt-get -f install

4. Autoremove

Finally, autoremove to clear out the old kernel image packages that have been orphaned by the manual boot clean.

sudo apt-get autoremove

5. Update Grub

sudo update-grub

6. Now you can update, install packages

sudo apt-get update

https://gist.github.com/ipbastola/2760cfc28be62a5ee10036851c654600Source: 
Back to top