nerdexam
Veeam

VMCE_V12 · Question #183

A customer is backing up to a local hardened repository configured with XFS for the purpose of keeping their most recent backups immutable. Their retention is set to keep 90 days with synthetic full…

The correct answer is A. XFS does not allow for fast cloning. The unexpected growth is due to your XFS‐based repo not leveraging Veeam's fast-clone (block- clone) technology the way ReFS does, every synthetic full is actually copying full files instead of just referencing existing blocks. In short, XFS does not allow for fast cloning in…

Configure Backup Storage

Question

A customer is backing up to a local hardened repository configured with XFS for the purpose of keeping their most recent backups immutable. Their retention is set to keep 90 days with synthetic full backups running once a week. After several months, the backup storage is twice the amount originally sized, and yet the growth rate is normal. What is the cause of the storage increase compared to the sizing?

Options

  • AXFS does not allow for fast cloning.
  • BThe fast cloning process is hung.
  • CImmutability settings for the repository are set too high.
  • DXFS does not allow for immutability.

How the community answered

(34 responses)
  • A
    82% (28)
  • B
    6% (2)
  • C
    9% (3)
  • D
    3% (1)

Explanation

The unexpected growth is due to your XFS‐based repo not leveraging Veeam's fast-clone (block- clone) technology the way ReFS does, every synthetic full is actually copying full files instead of just referencing existing blocks. In short, XFS does not allow for fast cloning in this scenario, so your weekly synthetic fulls are each doubling your used space.

Topics

#XFS fast cloning#hardened repository#immutability#storage sizing

Community Discussion

No community discussion yet for this question.

Full VMCE_V12 Practice