Snap Management Utility(SMU) Fails to Fully Deprovision a Clone When the Snap Backup Name Contains a Colon ":" Causes Snap Backup Deletion to Fail with the Error "Backup <NAME> has dependent clones [<NAME>]"
(Doc ID 2552886.1)
Last updated on FEBRUARY 07, 2022
Applies to:
Oracle ZFS Storage ZS5-2 - Version All Versions to All Versions [Release All Releases]Oracle ZFS Storage ZS7-2 High End - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage Appliance Racked System ZS7-2 High-End - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS7-2 High End TAA Compliant - Version All Versions to All Versions [Release All Releases]
Sun Storage 7110 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
In Snap Management Utility(SMU), a snap backup has one clone associated with it.
Deprovision the clone, the tasks log says it successfully deprovisioned.
Delete the backup and it fails with the error:
The SMU Browser User Interface, still shows the number of clones associated with the backup as 1:
Changes
Deprovision a clone created from a snap backup that has a name that contains a colon ":".
For instance, mybackup:02:07:2022
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |