Skip to main content
NetApp Knowledge Base

SCSQL database restores on ONTAP 9.15.1 fail to delete the Database volume clone on clean up

  1. Last updated
  2. Save as PDF
Views:
13
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Server 6.0

Issue

When restoring a database to an alternative instance, host or database name, the database clone volume, containing the LUN is not destroyed as it should be.
 
The log volume appears to be cleaned up properly, although offlining both DB and LOG (LUN) volumes, is see in the SMCore_<JOB-ID>.log log as also giving an error:

vol offline: Volume \"<SVM_NAME>:<LOG_LUN_VOLUME_NAME>mmddYYhhMMssnnn\" is already offline.
vol offline: Volume \"<SVM_NAME>:<DB_LUN_VOLUME_NAME>mmddYYhhMMssnnn\" is already offline.

(where mmddYYhhMMss  is Month, Day, Year, Hour, Minute, Second of the cloning process)

The actual error on the removal (volume destroy) of the database (LUN) volume clone, only appears in the SMCoreService.log on the SnapCenter Server,
where it asks for the status of the cloning job several times, until it's no longer 'Running":
Set Volume <SVM_NAME>:<DB_LUN_VOLUME_NAME>mmddYYhhMMssnnn to offline state failed with error 'Invalid response returned by Set-NcVol: 1 offline'. Returning with no retry.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.