A VPlex administrator claims a 100GB Storage Volume that is thin provisioned on the storage
array and has 25GB physically allocated and creates a 1:1 encapsulated virtual volume. After a
local data mobility job for that Virtual Volume, the storage array administrator notices that the
allocated capacity has increased to 100GB.
Why did this happen?
![PrepAway - Latest Free Exam Questions & Answers](https://www.briefmenow.org/img/pa5.jpg)
A.
The destination Storage Volume was not claimed with the thin-rebuild parameter in VPLEX.
B.
VPLEX does not support thin devices.
C.
Neither the source nor the destination Storage Volume were claimed with the thin-rebuild
parameter in VPLEX.
D.
The source Storage Volume was not claimed with the thin-rebuild parameter in VPLEX.
Explanation:
A.
The destination Storage Volume was not claimed with the thin-rebuild parameter in VPLEX.
Not shure of this one.
0
0
Its A only. When you are claiming the storage volume, you need to use the options as –thin-rebuild. You can also change it from the properties of the Storage Volume after its claimed.
0
0
SREE
I am in same situation.I have did data mobility and committed removed source volume only target volume is online and active ,If i change rebuild now will i loss data which is written
today.Its bit urgent
0
0