Bibszone.

  Simple Storage Service S3 (Object level storage any type of data, you can access it anywhere)         2.Elastic file system EFS: (common storage you can share across different regions and VPCs ex: patch files, updated files, Linux files)      3.Elastic block storage EBS (it is accessible through EC2 only like HDD work in a computer)      4.Glacier (): now it is part of S3 storage and cost-effective,     not frequently used data. Snowball :     (Huge amount of data We can transfer one DC to another DC) Part-2 ———————— Block Level v/s Object Lebel Storage: Block storage: —> Block starts is suitable for transactional databases, random read/write loads, and structured database storage —>Block storage divides the data to be stored in evenly sized blocks(data chunks) for instance,       a file can be split into evenly sized blocks before it is stored —>data blocks stored in block storage ...

  Terraform is this amazing tool to provision and manage changes on your cloud infrastructure while following the great practice of keeping your infrastructure-as-code. One common need on infrastructure management is to build multiple environments, such as testing and production, with mostly the same setup but keeping a few variables different, like networking and sizing. The first tool help us with that is terraform workspaces. Previously called environments, it allows you to create different and independent states on the same configuration. And as it’s compatible with remote backend this workspaces are shared with your team. As an example, let’s work with the following simple infrastructure: =============== provider “aws” {   region= “us-east-1” } resource “aws_instance” “my_service” {   ami=”ami-7b4d7900″   instance_type=”t2.micro” } ================ Now we have defined a single aws ec2 instance andterraform apply will have your testing server up. B...

Step 1: Scan the new Luns. Check how many Scsi hosts are available # ls –l /sys/class/scsi_host/ # echo “- – -” > /sys/class/scsi_host/host1/scan # echo “- – -” > /sys/class/scsi_host/host2/scan # echo “- – -” > /sys/class/scsi_host/host3/scan # echo “- – -” > /sys/class/scsi_host/host4/scan For fibre channel you have to scan like below. # echo “1” >/sys/class/fc_host/host0/issue_lip # echo “1” >/sys/class/fc_host/host1/issue_lip Step 2: Verify the new Lun with the LDEV number provided by Storage side. # multipath –ll | grep –I # /opt/osit/linux/bin/xpinfo -il | grep -i Step 3: Provide the new lun details to Requestor/Database Team Step 4: Add the Alias name for the new lun which they have provided.. Example: Before change: # vi /var/lib/multipath/bindings mpatha 3600508b1001034323720202020200000 mpathd 350002ac92e6c1340 mpathe 350002ac92ec31340 mpathf 350002ac92ec81340 After Change: # vi /var/lib/mul...

While many of the controls discussed in this document were available in earlier versions of the Solaris OS, some of the functionality discussed may not be present in those older versions. OS Platform The recommendations and actions described in this document are based upon a complete Solaris OS installation using the SUNWCXall ìEntire Distribution Plus OEMî software installation cluster. Therefore, some actions may not apply to systems that have been installed with other installation clusters or fewer software packages. System State It is recommended that all actions be applied when the system is in a ìquietî state ñ one in which application and third party software and services are not active. Hardening services used by applications while they are active could have unpredictable results. Test Actions It is strongly recommended that all actions be first executed on a test or non-critical system before being performed on a production server. While the actions described i...

  Solving boot problems in Solaris. Booting problems poses serious challenge to the system administrators as system is down and no one can use it . This article tries to cover some of the general booting problems and their possible solutions to enable understand the problem cause and bring the system up very quickly. 1.Booting in single user mode and mounting root hard disk. Most important step in diagnosing the booting problems is booting the system in single user mode and examining the hard disk for possible errors & work out the corrective measure. Single user mode can be achieved by any of the following methods :- ok> boot -s ;from root disk ok> boot net -s ;from network ok>boot cdrom -s ;from cdrom Rebooting with command: cdrom -s Configuring the /devices directory Configuring the /dev directory | INIT: SINGLE USER MODE # fsck /dev/rdsk/c0t3d0s0 # mount /dev/dsk/c0t3d0s0 /mnt Perform the required operati...