nerdexam
Veeam

VMCA2022 · Question #74

During a proof of concept deployment at Veeam University Hospital, it is noted that only some of the backup files in a specific Scale-out Backup Repository are immutable. What can cause this behavior?

The correct answer is B. Not all XFS extents in the Scale-out Backup Repository performance tier have the required flag. To make backup files immutable in a Scale-out Backup Repository, you need to use XFS extents with the reflink attribute enabled. This attribute allows Veeam Backup & Replication to create immutable backup files using the fast clone technology. If some of the XFS extents do not…

Backup Repository Design

Question

During a proof of concept deployment at Veeam University Hospital, it is noted that only some of the backup files in a specific Scale-out Backup Repository are immutable. What can cause this behavior?

Options

  • AThe ReFS extents do not have immutable enabled.
  • BNot all XFS extents in the Scale-out Backup Repository performance tier have the required flag
  • CAll extents in the Scale-out Backup Repository performance tier are ReFS.
  • DNot all EXT in the Scale-out Backup Repository performance archive tier have the required flag

How the community answered

(35 responses)
  • A
    3% (1)
  • B
    77% (27)
  • C
    11% (4)
  • D
    9% (3)

Explanation

To make backup files immutable in a Scale-out Backup Repository, you need to use XFS extents with the reflink attribute enabled. This attribute allows Veeam Backup & Replication to create immutable backup files using the fast clone technology. If some of the XFS extents do not have this attribute enabled, they will not support immutability and the backup files stored on them will not be protected from deletion or modification.

Topics

#SOBR#XFS immutability#hardened repository#partial immutability

Community Discussion

No community discussion yet for this question.

Full VMCA2022 Practice