Advice on allocating SAN storage to a virtual database server on VMware Post: 303027932

Sponsored Content

Operating Systems Linux Red Hat Advice on allocating SAN storage to a virtual database server on VMware Post 303027932 by gull04 on Friday 28th of December 2018 10:19:35 AM

12-28-2018

Registered User

Hi dkmartin,

I'll reiterate, there is a dependency on the backend configuration.

If you have a requirement to slice and dice a 1Tb LUN, you'll end up (from your comments) /dev/sda1, /dev/sda2, /dev/sda3 etc....... These would then be used for the "rootvg", the "appvg" the "dbvg" or any other way that you decide to apportion the disk.

If you decide to go for individual LUN's then you would have effectively a "ROOT_LUN", an "APP_LUN" and a number of "ORACLE_LUNS" for things like redo, archive, table space and all the other bits of an Oracle Instance - basically whatever your standard build is.

Without knowing what the backend storage is and how it is configured, how the storage is managed and how it is tiered are the arrays intelligent along with a miriad of other requirements it isn't possible to be any clearer with the information.

At the back end this could be all on one physical disk (You don't want that) or it could be spread over many physical disks.

For simplicity of management a single LUN is good, if the I/O on the VM will allow you to do that without impacting performance.

As to this being "configuration advice" it is not, there is no way that any advice could be given based on what you have told me - the sum total of the knowledge inparted by yourself is that "It's currently AIX and it's moving to Linux on VMware - the LUN mentioned is 1Tb and you use Oracle".

Oh! and it won't be using ASM.

Regards

Gull04

Last edited by gull04; 12-28-2018 at 11:25 AM.. Reason: Minor addition.

gull04

View Public Profile for gull04

Visit gull04's homepage!

Find all posts by gull04

5 More Discussions You Might Find Interesting

1. Solaris

Using San storage - advice needed

Thinking of using our San for network backups.. Have a Netra 240 being installed and planning to get some space on our San. Do you know what software is used to access the San from my server or what I would need to do? I know how to connect to local storage, disk arrays etc but not sure what...

2. Solaris

SAN Storage to solaris 10 server

Hi, I have configured our SAN Storage to be connected to our new SUN T5220. On the SAn it looks all fine on the server I do not see any connection: cfgadm -al Ap_Id Type Receptacle Occupant Condition c1 scsi-bus connected ...

3. SuSE

Hot-add memory to SuSE / VMware virtual server

Hi, Here is the issue. Some more memory has been added from vCenter to the virtual machine. From the virtual machine running SuSE 11 SP3. # modprobe acpiphp # modprobe acpi-memhotplug # grep -v online /sys/devices/system/memory/*/state # It looks like there is no offline memory, but free...

4. UNIX for Dummies Questions & Answers

Allocating Unallocated Drive Space from a SAN to a filesystem

Good Morning everyone, I want to know how to allocate unallocated drive space from a SAN to a file system that desperately needs the drive space. Does anyone have any documentation or tips on how to accomplish this? I am running on AIX version 6.1.

5. Homework & Coursework Questions

How to mount a 79TB SAN storage to another server?

Hi Team, How do i mount or connect the SAN storage to a specific folder. I have tried to mount it but each time i can only mount 900GB of the storage to the folder: ipmi1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup-root_vol ...

LEARN ABOUT OPENSOLARIS

blk2scsa

blk2scsa(7D)							      Devices							      blk2scsa(7D)

NAME

       blk2scsa - SCSA block device emulation

DESCRIPTION

       The blk2scsa module provides support services for generic block devices so that they appear to the system as devices on a virtual SCSI bus,
       thus allowing them to be serviced by the sd(7D) SCSI disk driver. The blk2scsa device supports the SCSI-2 command  set  for  Direct  Access
       Devices.  The  blk2scsa device supports multiple LUNs per physical device and creates a separate child device for each LUN. All child nodes
       attach to sd(7D).

DEVICE SPECIAL FILES

       Disk block special file names are located in /dev/dsk. Raw file names are located in /dev/rdsk.	See sd(7D).

IOCTLS

       See dkio(7I)

ERRORS

       See sd(7D).

FILES

       Device special files for the storage device are created in the same way as those for a SCSI disk. See sd(7D) for more information.

       /dev/dsk/cntndnsn

	   Block files for disks.

       /dev/rdsk/ctndnsn

	   Raw files for disks.

       /kernel/misc/blk2scsa

	   32-bit ELF kernel module (x86).

       /kernel/misc/amd64/blk2scsa

	   64-bit ELF kernel module (x86).

       /kernel/misc/sparcv9/blk2scsa

	   64-bit ELF kernel module (SPARC).

ATTRIBUTES

       See attributes(5) for a description of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Architecture		     |SPARC, x86		   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWckr			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       eject(1), rmformat(1), rmmount(1), cfgadm_scsi(1M), fdisk(1M), mount(1M), umount(1M), scsi(4), vfstab(4), attributes(5), sd(7D),  dkio(7I),
       pcfs(7FS)

       802.11b Standard for Wireless Local Area Networks (WLANs) - IEEE

SunOS 5.11							    28 Feb 2008 						      blk2scsa(7D)