Вы находитесь на странице: 1из 1

Scale Out SAN – Configure New Service for Oracle Visual PRD v1.

iSCSI Target iSCSI Initiator

(Prism) (Host)

Create New Install NT (1)

Storage Service

Name: Orapp
Workload: Oracle/Other

Select Machine(s) from

Saved List
Select Machine(s)
- Machine 1
- Nutanix VM (3)
- Machine 2
- Non Nutanix VM
- Machine 3
- Bare Metal
Install NT

Auto Discover if Manual Whitelist

NT installed on
Host - IQN (4,5)
- DNS Name
- IP Address

Select Capacity
Nutanix decides to (9, 12)
create Volume Group(s) Configure Disk Groups
- Size: 10 TB
Expose vDisks & based on vDisks/LUNs
(13) and associate vDisk(s). - ‘Volume Type(s)’:
type(s) as LUNs and their type(s)
vDisks inherit type from - Data: 7 TB
VG - Logs: 3 TB (embed in IQN)

Enable Flash Configure Database

Advanced Setting if Mode (14)
user wants to specify


- Reverse CHAP

1. Installing NT on Host side is optional to begin with. The flow addresses the case when NT is not installed on host.
2. Each database on a cluster is a different storage service/application. This allows user to take a snapshot per database (requirement).
Data and log files are snapshotted at the same time. Ability to ‘clone’ an application so admins need not add machines again and again
3. Non Nutanix VM and Bare Metal can behave similar in terms of configuration
4. Open Question: Can we get rid of IQN configuration during whitelisting?
5. Open Question: Do IQNs duplicate when cloning, whitelist the new one?
6. Future: Consider ability to convert/migrate Oracle workload from non Nutanix VM to Nutanix VM
7. Users are more likely to install NGT from host vs logging in as root user to istall NGT from Prism esp. when the system is up and running
and it is a production environment
8. Consideration: Oracle is up and running and requires additional storge that is coming from Nutanix
9. Consideration: Storage is thin provisioned but admins are used to specifying a size. Fixed size vs dynamic size – we provide a default
size that a user can change. As Microsoft SQL best practice, we don’t recommend dynamic disks size.
10.Consideration: For resizing database workloads, LUNs are not generally resized but new LUNs are added. In ASM when a LUN is added
to a disk group, it automatically stripes across all the LUNs to balance across
11. Oracle Recommendation to have atleast 2 disk groups – for data and logs. Also suggests another one - Bootup and OCR (Oracle Cluster
Registry) disk. Any number of data files (vDisks) in disk groups.
12. User provides a size and metadata tag (type) eg: data, log, OS, Temp etc. User can select one or more types to specify what should be
stored on that Volume Group. Nutanix decides to create volume groups as needed and attaches vDisk(s) as needed. Pass on the type
associated to a VG/vDisk to host. vDisk inherits the type from its VG.
13. Open Question: Can we have 1 vDisk per VG and get desired performance? If so, is VG an overhead – can the storage service have
different vDisks of different types or or vDisk of same type as requested by the admin?
14. When high performance mode is enabled, enable flash mode on heuristically selected vDisks. Type is used for performance optimization.