Restore fails because aggregate is not found during creation of volume clone
- Views:
- 673
- Visibility:
- Public
- Votes:
- 0
- Category:
- snapcenter
- Specialty:
- snapx
- Last Updated:
- 3/14/2025, 2:35:00 PM
Applies to
- ONTAP 9
- SnapCenter Plug-in for VMware vSphere (SCV)
- CommVault
- Veeam
Issue
- An API-driven restore, as used by SnapCenter, CommVault, or Veeam, fails with
Failed to create the volume clone.
- Examples of API driven restore jobs and errors:
vmcontrol_<JOB_ID>.log
indicates the error as follows:ERROR <SCV_HOST> --- [1825027294-3939] c.n.a.s.c.SnapManagerStorageServiceImpl : [JobId:<JOB_ID>] Mount Backup failed: Failed to create the volume clone.
Cannot create volume. Reason: aggregate <AGGREGATE> is not in aggr-list of Vserver <SVM>.ERROR <SCV_HOST> --- [ Thread-19] c.n.a.s.c.SnapManagerStorageServiceImpl : [JobId:<JOB_ID>] Mount Backup failed: Failed to create the volume clone.
Aggregate <AGGREGATE> not found. Reason: entry doesn't exist.
- CommVault
Error Code: [32:392] Description: Failed to create volume clone. : [Error:Unable to clone volume from snap:<Snapshot name> of volume:<volume name> on file server: Error[Failed to clone volume... <Aggregate> not found. Reason: entry doesn't exist.
- When the API-driven restore job fails, the ONTAP audit log (
/etc/log/mlog/audit.log
) will log the failure of thevolume-clone-
create
operation:
volume-clone-create :: Error: Aggregate <AGGREGATE> not found. Reason: entry doesn't exist.