Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

How to make Linux partition and configure the network on Redhat Linux7.3 ?

-
Server Information :
    master                 :192.168.2.2
    slave_1                :192.168.2.3
    slave_2                :192.168.2.4
    default gateway   :192.168.2.1
    OS                        :Red Hat Enterprise Linux Server release 7.3 Beta (Maipo)
    Adding extra slave:192.168.2.5 (without down time)

 MASTER PARTITION:
  • /mnt/DATA
  • /mnt/archive
  • /mnt/backup
Slave_1 and slave_2 PARTITION:
  • /DATA
  • /ARCHIVE
  • /BACKUP
1.Configure the network on  Master,Slave_1,Slave_2 server:

 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=master
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 

--Restart the network services
#systemctl restart network
        (OR)
#service network restart
FOR SLAVE_1 SERVER:
--Netcard Entry
cd /etc/sysconfig/network-scripts/
vi ifcfg-ens33

BOOTPROTO=static
IPADDR=192.168.2.3
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.3 slave1 

--Restart the network services
#systemctl restart network
        (Or)
#service network restart
FOR SLAVE_2 SERVER:
--Netcard Entry
cd /etc/sysconfig/network-scripts/
vi ifcfg-ens33

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

vi /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=slave2
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.4 slave2

--Restart the network services
#systemctl restart network
        (Or)
#service network restart
Now ping the server slave_1 from master and slave_1 to slave_2 if all successfull then we can go make partition ,if not successfully reaching the other server we can check it the fairwall status and stop it all server

 For Example:
From master:
ping 192.168.2.3
From slave_1:
ping 192.168.2.4

 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
[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.
[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
[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

[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.
[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.
.:. 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 /DATA

         2.This command will format the partition with ext4 FS
               mkfs.ext4 /dev/sdc1

         3.Mount the partition:
               sudo mount /dev/sdb1 /DATA
               sudo mount /dev/sdc1 /ARCHIVE
               sudo mount /dev/sdd1 /BACKUP
                           (OR)
               mount -t auto /dev/sdc1 /DATA

          4.Take ownership of the mount point:
               sudo chown -R postgres: /DATA
               sudo chown -R postgres: /ARCHIVE
       sudo chown -R postgres: /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"
 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 /DATA                   ext4    defaults        0 2
UUID=c5abf63e-a9ad-410c-a685-4407d9a12b93 /ARCHIVE                ext4    defaults        0 2
UUID=961e84b2-dbe2-4f2c-ade7-72c2b2b5289d /BACKUP                 ext4    defaults        0 2
B.For an NTFS formatted partition, add these two lines to end of fstab file:
# Mount DATA partition under /DATA
UUID=747D4C9C1EFAD1F2     /DATA     ntfs-3g     defaults,windows_names,locale=en_US.utf8     0     0
                      Save the changes to fstab and close the text editor or vim editor



Comments

Post a Comment

Popular posts from this blog

How to Configure User Equivalence (Key-Based Authentication) on Linux

-
Installation The SSH service should already be installed, but if it is not, install it from a Yum repository using the following command. # yum install openssh-server Turn on the SSH service and make sure it starts automatically on reboot. # service sshd start # chkconfig sshd on The SSH service is configured using the "/etc/ssh/sshd_config" file. Configuration changes have to be followed by a restart of the service. # service sshd restart # # or # service sshd reload Firewall The server must have the TCP port 22 open. This can be achieved by adding the following entry to the type of firewall script described  here . # Open port for NTP server. iptables -A INPUT -p tcp --dport 22 -j ACCEPT SELinux If you are using SELinux, you will need to consider the following points. The SELinux booleans associated with the SSH service are displayed using the  getsebool  command. # getsebool -a | grep ssh allow_ssh_keysign --> off fenced_can_ssh --> off ssh...
Read more

PostgreSQL - Access Oracle Database in PostgreSQL

-
          Today, organizations stores information(data) in different database systems. Each database system has a set of applications that run against it. This data is just bits and bytes on a file system - and only a database can turn the bits and bytes of data into business information. Integration and consolidation of such information(data) into one database system is often difficult. Because many of the applications that run against one database may not have an equivalent application that runs against another. To consolidate the information into one database system, we need a heterogeneous database connection.  In this post, I'll demo on how you may connect PostgreSQL to one of heterogeneous database Oracle using different methods. Below are few methods to make connection to Oracle database in PostgreSQL. Using ODBC Driver Using Foreign DataWrappers Using Oracle Call Interface(OCI) Driver Softwares used in demo(included download links): CentOS 7 64bit,...
Read more

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

Postgres Database Patch

-
If you are used to patch Oracle databases you probably know how to use opatch to apply PSUs. How does PostgreSQL handle this? Do we need to patch the existing binaries to apply security fixes? The answer is: No.Lets say you want to patch PostgreSQL from version 10.5/11.3 to version 10.10/11.5. This is called minor version postgres upgrade or postgres patching Why need to patch postgresql server  ? Multiple SQL injection vulnerabilities have been discovered in PostgreSQL that could allow for arbitrary code execution. The vulnerabilities are the result of the application’s failure to sufficiently sanitize user-supplied input before using it in an SQL query. These vulnerabilities allow attackers with the CREATE permission (or Trigger permission in some tables) to exploit input sanitation vulnerabilities in the pg_upgrade and pg_dump functions. The CREATE permission is automatically given to new users on the public schema, and the public schema is the default schema used on the...
Read more

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

-
In this post, I am sharing few important function for finding the size of database, table and index in PostgreSQL. Finding object size in postgresql database is very important and common. Is it very useful to know the exact size occupied by the object at the tablespace. The object size in the following scripts is in GB. The scripts have been formatted to work very easily with PUTTY SQL Editor. 1. Checking table size excluding table dependency: SELECT pg_size_pretty(pg_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 238 MB (1 row) 2. Checking table size including table dependency: SELECT pg_size_pretty(pg_total_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 268 MB (1 row) 3. Finding individual postgresql database size SELECT pg_size_pretty(pg_database_size('db_name')); 4. Finding individual table size for postgresql database -including dependency index: SELECT pg_size_pretty(pg_total_rel...
Read more