MENU
An administrator originally configured the storage for an Oracle database running on Nutanix NDB using ASMLib. The administrator would like to scale the size of the database.
What should the administrator do to most efficiently increase the size of the database?
41 comments · newest first
SH
Shelton
10 months ago
Wait, can you really resize vDisks like that? Sounds too easy!
LE
Leanna
11 months ago
D could work, but is it really necessary?
KA
Kasandra
11 months ago
C sounds like a hassle, who wants to migrate?
SO
Sophia
11 months ago
I think B might be better for flexibility.
PA
Pansy
11 months ago
A is definitely the way to go for efficiency!
VA
Valene
11 months ago
Mounting an iSCSI LUN sounds familiar, but I can't recall if that's the most efficient method for this scenario.
CY
Cyril
12 months ago
I practiced a similar question where migrating to a new database was suggested, but that seems like a lot of work for just scaling up.
EL
Elke
12 months ago
I think adding new vDisks could be a straightforward way to scale, but I wonder if it would be as efficient as resizing.
ZA
Zana
1 year ago
I remember something about leveraging NDB's scaling features, but I'm not sure if resizing existing vDisks is the best option.
BE
Beula
1 year ago
I'm a bit confused by the question. Does the administrator have the option to use iSCSI LUNs, or is that not a supported configuration? I'll need to research Nutanix NDB a bit more to make sure I understand the best approach.
CE
Celestina
1 year ago
Creating a new, larger database and migrating the data seems like the most reliable way to increase the size, but it could be a lot of work. I'll need to weigh the pros and cons of each option.
HA
Hannah
1 year ago
Extending the size by adding new vDisks sounds like a good approach to me. That way, I can scale the storage without having to migrate the entire database.
JU
Junita
1 year ago
Hmm, I'm not too familiar with Nutanix NDB and how it handles database storage. I'll need to think this through carefully to make sure I understand the implications of each option.
JE
Jessenia
1 year ago
This seems pretty straightforward. I think the best option is to leverage the scaling ability built into NDB to resize the existing vDisks.
GE
Gerald
1 year ago
Ah, the Orange Book! I remember learning about that in one of my pharmacy classes. Definitely going with C on this one.
MI
Mireya
1 year ago
I remember discussing how workflow changes could impact existing filters and gadgets, but I'm not sure which option covers that.
TI
Tiara
1 year ago
When in doubt, RFP is almost always the standard document for soliciting vendor proposals. I'd choose C.
BE
Beckie
1 year ago
I'm pretty sure the Electronic Discovery Reference Model (EDRM) is the right answer here. It's a well-known framework for managing the e-discovery process, which includes legal holds.
DE
Desirae
1 year ago
Wait, you can scale the database in Nutanix? That's like the eighth wonder of the world! Sign me up for Option A.
CH
Charisse
1 year ago
User 3: That sounds like the most efficient way to increase the size of the database.
LE
Leonora
1 year ago
User 2: Yeah, it's like the eighth wonder of the world. I would go with Option A to resize existing vDisks.
FR
Freeman
1 year ago
User 1: I heard you can scale the database in Nutanix. It's amazing!
DE
Deandrea
1 year ago
I'm tempted by Option D, but mounting an iSCSI LUN just sounds like a lot of extra steps. Why not keep it simple with NDB?
AL
Alaine
1 year ago
User 1
AR
Aracelis
1 year ago
User 2
FE
Felicia
1 year ago
User 1
LI
Linn
1 year ago
Oh man, Option C is way too much work. Who wants to create a new database and migrate all that data? No thanks!
EZ
Ezekiel
1 year ago
D) Mount an iSCSI LUN and extend the database onto the new LUN.
QU
Queenie
1 year ago
B) Extend the size by adding new vDisks.
KI
Kimi
1 year ago
A) Leverage the scaling ability built into NDB to resize existing vDisks.
KR
Kristel
1 year ago
I'd go with Option A. The scaling abilities of NDB should make it easy to resize the existing vDisks and expand the database.
SH
Sheridan
1 year ago
User 2: Yeah, leveraging the scaling ability of NDB to resize existing vDisks sounds like the way to go.
CH
Cherelle
1 year ago
User 1: I agree, Option A seems like the most efficient way to increase the size of the database.
SH
Shaun
2 years ago
I'm not sure, I think creating a new, larger database and migrating might be a better option for scalability.
XU
Xuan
2 years ago
Option B makes the most sense to me. Scaling existing vDisks is the most efficient way to increase the database size without having to migrate data or add new hardware.
SH
Shelia
1 year ago
Mounting an iSCSI LUN and extending the database onto the new LUN would be more complicated.
YU
Yuette
1 year ago
Creating a new, larger database and migrating seems like a lot of unnecessary work.
RO
Rozella
1 year ago
It's definitely the most efficient way to increase the database size.
LA
Lavonna
1 year ago
I agree, extending the size by adding new vDisks seems like the best option.
CO
Colene
2 years ago
I agree with Caitlin, it seems like the most efficient way to increase the size of the database.
CA
Caitlin
2 years ago
I think we should leverage the scaling ability built into NDB to resize existing vDisks.