By now, which is not recommended when OceanProtect is working with Commvault? (Single- choice)

Question

Options

• ABackup using NFS and CIFS
• BBack end terabyte (BET) license for all use cases
• CBackup sets replication by OceanProtect
• DAuxiliary copy should be used for data migration

• A
  7% (3)
• B
  12% (5)
• C
  79% (33)
• D
  2% (1)

Explanation

When OceanProtect and Commvault are integrated, replication of backup sets should be managed by Commvault (via Auxiliary Copy), not by OceanProtect's native replication engine. Using OceanProtect to replicate Commvault backup sets bypasses Commvault's catalog management, leaving the secondary site's data untracked and unrecoverable through Commvault - defeating the purpose of the backup solution.

Why the distractors are wrong:

• A (NFS/CIFS): These protocols are fully supported and commonly used to present OceanProtect storage to Commvault as a backup target.
• B (BET license): The Back-End Terabyte licensing model is the recommended licensing approach for OceanProtect across use cases with Commvault.
• D (Auxiliary Copy for migration): Auxiliary Copy is the correct Commvault-native method for replication and data migration, ensuring catalog consistency is maintained.

Memory tip: Think "Commvault owns the catalog, Commvault owns the replication." Any movement of Commvault backup sets must go through Commvault's own mechanisms - if OceanProtect moves the data independently, Commvault has no record of where it went.

No community discussion yet for this question.