MENU
When attempting to protect new XtremlO LUNs, the administrator is unable to add an XtremIO source LUN to the Consistency Group. What is a possible reason for this issue?
Suggested Answer: A
Get Premium D-RP-OE-A-24 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
AL
Alishia
10 months ago
I disagree with B, RecoverPoint should support more than just VNX.
HA
Hayley
10 months ago
D could be a factor too, block size matters!
SA
Sanjuana
10 months ago
Wait, are you saying B is true? That sounds off.
TO
Torie
10 months ago
A is definitely a reason, no license means no protection.
JO
Johna
10 months ago
I think C is the right answer, XtremIO and VMs are a thing.
DE
Denise
11 months ago
I vaguely remember something about block sizes affecting LUN protection, so option D might be a possibility too.
MI
Mireya
11 months ago
I feel like I read that XtremIO has specific requirements for protection, but I can't recall if it was about VMs or something else. Maybe option C?
NG
Nguyet
11 months ago
I’m not entirely sure, but I think I saw a question about RecoverPoint only supporting certain arrays. Could that be option B?
CE
Celia
11 months ago
I remember something about licensing issues with XtremIO and RecoverPoint, so maybe option A could be the reason.
CR
Cristen
12 months ago
Ah, I think I've got it! The key is the block size. Option D is the answer - the XtremIO LUN was created with a 512-byte block size, which RecoverPoint doesn't support. Good to know for the exam!
NA
Nan
12 months ago
I'm a bit confused on this one. I'm not as familiar with XtremIO and RecoverPoint integration, so I'll need to review the material again before deciding.
VI
Vilma
12 months ago
I've seen this issue before, and I think the answer is most likely A. The XtremIO array needs to be licensed in RecoverPoint for it to work properly.
MY
Myra
1 year ago
Okay, let's see. I'm pretty sure it's not option B or C, since those seem too specific. I'm leaning towards A or D, but I'm not totally sure.
SU
Sunny
1 year ago
Hmm, this seems like a tricky one. I'll need to think through the possible reasons carefully.
CA
Catrice
1 year ago
Waiting for the day when storage vendors stop creating these obscure compatibility issues. It's like they want us to fail the certification exam!
AL
Alberto
1 year ago
A 512-byte block size? That's some old-school stuff right there. I doubt that's the issue, but hey, you never know with these storage systems.
KA
Kathrine
1 year ago
Hold up, XtremIO arrays are only protected with RecoverPoint for VMs? That's a weird restriction. I wonder if there's a workaround for physical LUNs.
GR
Gregoria
1 year ago
Ah, I see. RecoverPoint/EX is limited to VNX arrays, so that's a no-go for this XtremIO setup. Good to know the limitations.
LE
Lettie
1 year ago
Maybe we can consider using a different solution that is compatible with XtremIO arrays.
LE
Lettie
1 year ago
Looks like we'll need to explore other options for protecting XtremIO LUNs.
LE
Lettie
1 year ago
Yes, that's correct. RecoverPoint/EX only supports VNX arrays.
CI
Ciara
1 year ago
Hmm, the XtremIO array not being licensed in RecoverPoint seems like the most likely culprit here. Gotta make sure all the pieces are properly licensed and configured.
MY
Myong
1 year ago
D) XtremIO LUN was created with a 512-byte block size
CH
Cheryl
1 year ago
Yeah, that could definitely be the issue. Licensing is key.
LO
Lottie
1 year ago
A) XtremlO array was not licensed in RecoverPoint
MA
Maile
2 years ago
I'm not sure about the licensing issue. Could it also be because the XtremIO LUN was created with a 512-byte block size?
JE
Jeffrey
2 years ago
I agree with Valentine. Without the proper licensing, it makes sense that the administrator is unable to add the XtremIO source LUN to the Consistency Group.
VA
Valentine
2 years ago
I think the possible reason could be that XtremlO array was not licensed in RecoverPoint.