A and C
Deduplication and compression with Object Space Reservation
There is a major consideration if you already use object space reservation (OSR) and now wish to use deduplication and compression. In essence, objects either need to have 0% OSR (thin) or 100% OSR (fully reserved – thick). You cannot have any values in-between. If you already have VMs deployed with an OSR value that is somewhere in between, you will not be able to enable deduplication and compression. It will error as shown here:
A&C is correct
The object space reservation value is the percentage of the logical size of the VMDK object that is reserved when provisioned:
• Default value: Thin Provision.
• Possible values: Thin, 25%, 50%, 75%, and Thick.
Object space reservation must be either thick or thin when deduplication and compression are enabled.
After deduplication and compression are enabled, thick and thin are the only compatible options.
Taken from vSAN 6.7 Deploy and Manage Lecture Manual - Object Space Reservation section
From training document:
4-27 Object Space Reservation
Object space reservation must be either thick or thin when deduplication and compression are enabled. After deduplication and compression are enabled, thick and thin are the only compatible options.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Lazylinux
3 years, 6 months agodiegof1
4 years, 5 months agosasaz
4 years, 7 months agoVMwareARCHI
4 years, 7 months agoalsmk2
4 years, 10 months agoAolivera
4 years, 10 months ago