Backup of controlfile to trace cannot be made on the ASM diskgroup since ASM will allow a text file in a data DG. For ASM environments, SCO points the "backup controlfile to trace" command to the /tmp directory and then copies the complete content in the NSM database (SnapCenter's repository) for future use.
- manual snap restore yesterday snapshot for data and log volumes
- dev Redhat Oracle 12C stanalone import above ASM disk group
- fail bring up the database due to control file did not have snapshot/backup restore to yesterday status
Refer SnapCenter will take snapshot for data and log volumes when backup, could move control file LUNs to log volume (volume include log and control file LUNs) with SnapCenter daily backup, when simulate above disaster recovery, manual restore data and log/control_file volume snapshot for above disaster recovery?