• Restore der DB:
    cat southpo_pm_technologiefonds.sql | mysql southpo_pm_technologiefonds

    Restore des binlogs:
    mysqlbinlog –start-datetime=”2018-06-13 20:19:48″ –stop-datetime=”2018-06-18
    16:51:00″ –database southpo_pm_dbname mysql-bin.001226
    mysql-bin.001227 mysql-bin.001228 mysql-bin.001229 mysql-bin.001230
    mysql-bin.001231 mysql-bin.001232 mysql-bin.001233 | mysql
    southpo_pm_dbname

sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdc

sudo mount -o discard,defaults /dev/sdc /mnt/back

https://cloud.google.com/compute/docs/disks/add-persistent-disk

 

SSH as admin (you should never have a problem here if you do set password for admin in the Control Panel > Users in DSM)
Type
sudo -i

This will prompt you for a password use your admin password

Now you’ll be SSH in as Root

Type this, it will set the password of your choosing to the root account.

synouser –setpw root [PASSWORD]

some-boring-process is running in your current bash session:

  1. halt it with ctrl-z to give you the bash prompt
  2. put it in the background with bg
  3. note the job number, or use the jobs command
  4. detach the process from this bash session with disown -h %1 (substitute the actual job number there).

or use screen or tmux

 parted -s /dev/sda mklabel gpt
parted -s /dev/sda unit mib mkpart primary 1 100%

parted -s /dev/sda set 1 lvm on

or interactive

root@srsouthp06:/var/log# lsblk
NAME                  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                     8:0    0   2.7T  0 disk
├─sda1                  8:1    0  18.6G  0 part /
├─sda2                  8:2    0   3.7G  0 part [SWAP]
└─sda3                  8:3    0   2.7T  0 part
  └─lvm-backup (dm-0) 254:0    0   8.2T  0 lvm  /home
sdb                     8:16   0   2.7T  0 disk
└─sdb1                  8:17   0   2.7T  0 part
  └─lvm-backup (dm-0) 254:0    0   8.2T  0 lvm  /home
sdc                     8:32   0   2.7T  0 disk
└─sdc1                  8:33   0   2.7T  0 part
  └─lvm-backup (dm-0) 254:0    0   8.2T  0 lvm  /home
sdd                     8:48   0   5.5T  0 disk
[20354456.836296] end_request: I/O error, dev sdc, sector 2884604760
[20354456.836339] Buffer I/O error on device dm-0, logical block 1093140587
root@srsouthp06:/var/log# pvcreate /dev/sdd
  Writing physical volume data to disk “/dev/sdd”
  Physical volume “/dev/sdd” successfully created
root@srsouthp06:/var/log# vgs
  VG   #PV #LV #SN Attr   VSize VFree
  lvm    3   1   0 wz–n- 8.17t    0
root@srsouthp06:/var/log# vgextend lvm /dev/sdd
  Volume group “lvm” successfully extended
root@srsouthp06:/var/log# pvmove /dev/sdc1 /dev/sdd
  /dev/sdc1: Moved: 0.0%
takes long time
vgreduce lvm /dev/sdc1
to extend if the disk was larger
lvextend -L+2.44T /dev/lvm/backup /dev/sdc
pvdisplay -v
resize2fs /dev/mapper/lvm-backup

UPDATE `accounts_cstm` ca, recovery re SET ca.accounttypetwo_c = ‘Project Owner’ WHERE re.ID = ca.id_c;

SELECT * FROM `accounts_cstm` WHERE `accounttypetwo_c` LIKE ‘Proj%’

http://pgtune.leopard.in.ua/

PGTune calculate configuration for PostgreSQL based on the maximum performance for a given hardware configuration. It isn’t a silver bullet for the optimization settings of PostgreSQL. Many settings depend not only on the hardware configuration, but also on the size of the database, the number of clients and the complexity of queries, so that optimally configure the database can only be given all these parameters.