Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Configure the network & Disk Partition

-
Server Information :
master                 :192.168.2.2
OS                        :Red Hat Enterprise Linux Server release 7.3 Beta (Maipo)
MASTER PARTITION:
  • /mnt/DATA
  • /mnt/archive
  • /mnt/backup
1.Configure the network on  Master:
[postgres@master ~]$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.3 Beta (Maipo)
--Netcard Entry
cd /etc/sysconfig/network-scripts/
vi ifcfg-ens33

BOOTPROTO=static
IPADDR=192.168.2.2
NETMASK=255.255.255.0
DEVICE="ens33"
ONBOOT=yes

vi /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=slave1
GATEWAY=192.168.2.1

## Configure DNS Server
# vi /etc/resolv.conf

nameserver 8.8.8.8     # Replace with your nameserver ip
nameserver 192.168.2.1  # Replace with your nameserver ip

--Host Entry
vi /etc/hosts
192.168.2.2 master master.master

--Restart the network services
#systemctl restart network
        (OR)
#service network restart



Copy
2.Disk Parition for data/archive/backup:
a)100GB data,50GB archive,40GB backup
For out of range error use “extended” option
[root@localhost ~]# fdisk -l

Disk /dev/sda: 214.7 GB, 214748364800 bytes, 419430400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00022715

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      616447      307200   83  Linux
/dev/sda2          616448     4812799     2098176   82  Linux swap / Solaris
/dev/sda3         4812800   419430399   207308800   83  Linux

Disk /dev/sdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 53.7 GB, 53687091200 bytes, 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 42.9 GB, 42949672960 bytes, 83886080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes



Copy




[root@localhost ~]# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table
Building a new DOS disklabel with disk identifier 0x4f696ae8.

Command (m for help): n
Partition type:
   p   primary (0 primary, 0 extended, 4 free)
   e   extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-209715199, default 2048): 
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199): 
Using default value 209715199
Partition 1 of type Linux and of size 100 GiB is set

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.



Copy




[root@localhost ~]# fdisk -l

Disk /dev/sda: 214.7 GB, 214748364800 bytes, 419430400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00022715

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      616447      307200   83  Linux
/dev/sda2          616448     4812799     2098176   82  Linux swap / Solaris
/dev/sda3         4812800   419430399   207308800   83  Linux

Disk /dev/sdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x4f696ae8

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   209715199   104856576   83  Linux

Disk /dev/sdc: 53.7 GB, 53687091200 bytes, 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 42.9 GB, 42949672960 bytes, 83886080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes



Copy




[root@localhost ~]# fdisk -l /dev/sdb1

Disk /dev/sdb1: 107.4 GB, 107373133824 bytes, 209713152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

[root@localhost ~]# fdisk  /dev/sdbc
fdisk: cannot open /dev/sdbc: No such file or directory



Copy




[root@localhost ~]# fdisk  /dev/sdc
Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table
Building a new DOS disklabel with disk identifier 0x4efbaaa0.

Command (m for help): n
Partition type:
   p   primary (0 primary, 0 extended, 4 free)
   e   extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-104857599, default 2048): 
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-104857599, default 104857599): 
Using default value 104857599
Partition 1 of type Linux and of size 50 GiB is set

Command (m for help): w       
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.



Copy




[root@localhost ~]# fdisk  /dev/sdd
Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table
Building a new DOS disklabel with disk identifier 0xaf00340d.

Command (m for help): n
Partition type:
   p   primary (0 primary, 0 extended, 4 free)
   e   extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-83886079, default 2048): 
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-83886079, default 83886079): 
Using default value 83886079
Partition 1 of type Linux and of size 40 GiB is set

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.



Copy
.:. restart the server using init 6,init 0 for shutdown
B)add the mount point:
As root user:
1. create a mount point for the data partition:
sudo mkdir  /mnt/DATA
2.This command will format the partition with ext4 FS
mkfs.ext4 /dev/sdc1
3.Mount the partition:
sudo mount /dev/sdb1 /mnt/DATA
sudo mount /dev/sdc1 /mnt/ARCHIVE
sudo mount /dev/sdd1 /mnt/BACKUP
(OR)
mount -t auto /dev/sdc1 /mnt/DATA4.Take ownership of the mount point:
sudo chown -R postgres: /mnt/DATA
sudo chown -R postgres: /mnt/ARCHIVE
sudo chown -R postgres: /mnt/BACKUP
5.Find out the UUID# for your data partition:
[root@localhost ~]# sudo blkid
/dev/sda1: UUID="15fe408e-72ef-47fe-b3f0-e33f032c1d9f" TYPE="xfs" 
/dev/sda2: UUID="03a8e0e8-ae89-4a1f-bafc-c03826de7ea5" TYPE="swap" 
/dev/sda3: UUID="f45ae60c-162f-4da2-aa33-f76723e0c5fe" TYPE="xfs" 
/dev/sdb1: UUID="46c3be28-2646-495e-9d1b-5f9be9d1e154" TYPE="ext4" 
/dev/sdc1: UUID="c5abf63e-a9ad-410c-a685-4407d9a12b93" TYPE="ext4" 
/dev/sdd1: UUID="961e84b2-dbe2-4f2c-ade7-72c2b2b5289d" TYPE="ext4" 
/dev/sr0: UUID="2016-08-17-06-07-50-00" LABEL="RHEL-7.3 Server.x86_64" TYPE="iso9660" PTTYPE="dos"



Copy
6.Open your fstab file and make an entry to auto-mount the data partition on boot:
                gksu gedit /etc/fstab (OR) vi /etc/fstab
(Note: you may need to substitute a different text editor if gedit not installed to your version of Mint.)
In gedit, add either of the two examples below (substitute your UUID# for the ones listed here):
A.For an Ext4 formatted partition, add these two lines to end of fstab file:
# Mount DATA partition under /DATA
UUID=46c3be28-2646-495e-9d1b-5f9be9d1e154 /mnt//DATA                   ext4    defaults        0 2
UUID=c5abf63e-a9ad-410c-a685-4407d9a12b93 /mnt//ARCHIVE                ext4    defaults        0 2
UUID=961e84b2-dbe2-4f2c-ade7-72c2b2b5289d /mnt//BACKUP                 ext4    defaults        0 2



Copy
B.For an NTFS formatted partition, add these two lines to end of fstab file:
# Mount DATA partition under /DATA
UUID=747D4C9C1EFAD1F2     /mnt/DATA     ntfs-3g     defaults,windows_names,locale=en_US.utf8     0     0



Copy
Save the changes to fstab and close the text editor or vim editor

Comments

Post a Comment

Popular posts from this blog

VMWARE WORKSTATION 3,4,5,6,7,8,9,10,11,12,14,15...etc LICENSE KEYS COLLECTION

-
Image
Below tutorialdba.com collected and sorted out hundreds of universal License Keys for all major versions of VMware Workstation Pro (not for VMware Workstation Player) 4.x, 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x and v14.x on Windows and Linux platforms (support both 32-bit and 64-bit operating system) in this single post. Besides, we also provide some license keys for VMware other projects. Just enjoy and share them. // 4~14 Universal License Keys // Version License Keys VMware Workstation VMware Workstation 4.x.x ZHDH1-UR90N-W844G-4PTN6 G1NP0-T88AL-M016F-4P8N2 ZC14J-4U16A-0A04G-4MEZP J1WF8-58LDE-881DG-4M8Q3 VMware Workstation 5.x.x LUXRM-WP0DN-A256U-4M9Q3 DJXDR-NDT27-Y2NDU-4YTZK DA925-HP80U-Z8HDC-4WXXP 3KW2W-AYR2C-88M6F-4MDQ2 VMware Workstation 6.x.x A0E8R-YUDFV-6AK2F-4GAN2 CRX0D-VWL0V-7CJ6C-46C7A NA8RX-QPNDU-D2LA9-4WAZL 1H4WM-N21FZ-7GK2A-44U5U 6AJ6N-THY2P-42KEF-4WTFG FK8R9-LPCDT-88H4Y-4WRN3 KAR8R-T8MAL-K8J6A-4WDXQ YJEKW-JMFF4-YA1DC-4WTQ...
Read more

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

Oracle to Postgresql migration

-
Oracle migration: For migration first we need to install oracle database and ora2pg software and DBD oracle packages. =>first install oracle database in server and note down the paths,username,password needed For installing the oracle database follow the below steps: From the root user: create group "groupadd oinstall" create group "dba" create user "useradd oracle -G dba -g oinstall create directory "mkdir /home/oracle/software" Change ownership permissions to software directory chown oracle:oinstall /home/oracle/software copy the downloaded files to /home/oracle/software and untar the files After untaring we can find "database" directory in /home/oracle/software In database directory we find runinstaller file we need to run that file ./runinstaller and finish the oracle database installation. ======================================================================= After finishing the installation switch to oracle use...
Read more

PostgreSQL Enterprise Manager - PEM Monitoring Tools

-
Image
Database administration and management is required for any database on which there are continuous business transactions.  If databases across enterprises are not monitored and maintained, then such databases are vulnerable to disasters, which eventually brings downtime to missions-critical application and, of course, it will incur losses in the business. Data is now one of the key assets for running a business, globally. Hence, it is one of the major responsibilities of enterprises to invest in resources for database monitoring and management. There are many database management and monitoring tools available for proactive database monitoring. In this article, we will look at  PEM – “PostgreSQL Enterprise Manager” .Enterprise Manager, or PEM, is a graphical database management/monitoring tool that can help database administrators, system administrators, database developers, database managers, system architects, and performance analysts manage databases efficiently and proacti...
Read more

7 Steps to configure BDR replication in postgresql

-
Image
 The  BDR  (Bi-Directional Replication) project adds multi-master replication to PostgreSQL 9.4.  Postgres-BDR has a lower impact on the masters(s) than trigger-based replication solutions. There is no write-amplification, as it does not require triggers to write to queue tables in order to replicate writes.   Here We are using  postgres version 9.4.12 and bdr version 1.0.2. for configuring  multi master replication . Simply Following 7 steps you can configure the multi master replication in postgresql. To download the bdr in below link. .   https://github.com/2ndQuadrant/bdr/archive/bdr-pg/REL9_4_12-1.tar.gz $ tar -xzvf REL9_4_12-1.tar.gz $ wget https://github.com/2ndQuadrant/bdr/archive/bdr-plugin/1.0.2.tar.gz $ tar -xzvf 1.0.2.tar.gz 1. To install BDR. $ cd ~/bdr-bdr-pg-REL9_4_12-1 $ ./configure --prefix=/usr/lib/postgresql/9.4 --enable-debug --with-openssl $ make -j4 -s install-world $ cd ~/bdr-bdr-plugin-1.0.2 $ PATH=/usr/lib/p...
Read more