Sponsored Content
Operating Systems Linux Red Hat Advice on allocating SAN storage to a virtual database server on VMware Post 303027918 by gull04 on Friday 28th of December 2018 08:32:26 AM
Old 12-28-2018
Hi,

In general the same approach is probably the way to go - however if you are going to be doing significant amounts of migration work it is worth getting the planning right.

Much of the configuration is dependent on the way that the storage is configured and whether you are using Oracle ASM or not, ASM is worth having if you have significant I/O on the database but with a high performance backend the additional managemnt overhead may not be worth while.

If the storage is tiered and you think it will deal efficiently with the I/O, I'd go for the presentation of a single LUN - this makes future migrations, DR and failover really simple. The drawback would be if you have to run fsck or some other tool, it has to do the whole LUN not just a couple of small partitions or LUN's. Where you have SAN replication the single LUN approach makes life easy, you won't miss something if it's all in one place.

If performance is key, then you may want to take advantage of the tiering in a different way. There is much to consider when doing migration work like this, it is well worth while runing a proof of concept (if you can) just to check things out.

Regards

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... (1 Reply)
Discussion started by: frustrated1
1 Replies

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 ... (4 Replies)
Discussion started by: manni2
4 Replies

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... (1 Reply)
Discussion started by: aixlover
1 Replies

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. (2 Replies)
Discussion started by: ryanco
2 Replies

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 ... (0 Replies)
Discussion started by: ElVista
0 Replies
scconf_quorum_dev_netapp_nas(1M)			  System Administration Commands			  scconf_quorum_dev_netapp_nas(1M)

NAME
scconf_quorum_dev_netapp_nas - add and remove shared Network Appliance network-attached storage (NAS) quorum devices and change various NAS cluster quorum configuration properties or states. SYNOPSIS
scconf {-a|-c|-r} -q name=devicename otheroptions DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. A Network Appliance NAS device can be configured as a quorum device for Sun Cluster. The NAS configuration information consists of: o a device name, which must be unique across quorum devices o a filer name, which defaults to the device name if not specified o a LUN ID, which defaults to 0 if not specified To provide support for NAS devices as quorum devices, the administrator must install the quorum device support module provided by Network Appliance. If this module is not available, scconfprevents the addition of the quorum device. See Sun Cluster With Network-Attached Storage Devices Manual for Solaris OS for instructions about obtaining the support module. Additionally, the iSCSI license must be valid for the Network Appliance device. OPTIONS
The following options can be used for NAS quorum devices. See scconf(1M) for the list of supported generic options. See scconf_quo- rum_dev_netapp_nas(1M) for options that are specific to shared disk quorum devices. The add and remove forms of the command are used to add and remove NAS quorum devices to or from the configuration. The change form of the command is used for changing various properties of cluster quorum configuration. Before you add a quorum device, you must set up and configure the device and the logical unit number (LUN) on the device to be configured as a quorum device. For detailed procedures, see your Network Appliance documentation. For Sun Cluster requirements of device setup, see Sun Cluster With Network-Attached Storage Devices Manual for Solaris OS. After the quorum device is added, you cannot change the type. Add a NAS quorum device: -q -a name=devicename,type=netapp_nas[,filer=filer-name][,lun_id=0] Change a NAS quorum device's configuration: -q -c name=devicename,{maintstate | reset} Remove a NAS quorum device: -q -r name=devicename The -q option supports the following Network Appliance NAS-specific suboptions: filer=filer-name Specifies the name of the device on the network that you can use to access the NAS device when you are using rsh or telnet. lun_id=0 Specifies the LUN ID on the NAS device that will be a NAS quorum device. The LUN ID defaults to 0. When scconf is interrupted or fails while performing quorum-related operations, quorum configuration information can become inconsistent in the cluster configuration database. If an inconsistency occurs, either run the same scconf command again or run it with the reset option to reset the quorum information. EXAMPLES
Example 1 Adding Network Appliance NAS Quorum Devices The following scconf command adds the Network Appliance NAS quorum device qd1. -a -q name=qd1,type=netapp_nas,filer=nas1.sun.com,lun_id=0 Example 2 Removing Network Appliance NAS Quorum Devices The following scconf command removes the Network Appliance NAS quorum device qd1. -r -q name=qd1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scconf-quorum-dev-scsi(1M) Sun Cluster 3.2 10 Apr 2006 scconf_quorum_dev_netapp_nas(1M)
All times are GMT -4. The time now is 07:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy