Skip to main content
NetApp Knowledge Base

SnapCenter Deleted/Renamed SQL Database Resolution Guide

Views:
696
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Server (SC)
  • SnapCenter Plug-In for SQL (SCSQL)

Description   

  • SnapCenter keeps backup data in a MySQL database even after the database has been deleted
    • This is to prevent any accidental deletion and provide restore options
  • Common symptoms include
    • Display issues
      • Database remains in SnapCenter as Deleted/Renamed
    • Retention issues
      • 2020-06-29T21:00:29.6151224-07:00 DEBUG SnapManagerWeb_217073 PID=[25012] TID=[79] BackupComponent group contains deleted databases
    • Cloning issues
      • 2021-02-02T11:52:11.0356597+00:00 ERROR SnapManagerWeb_<Job_Id> PID=[7132] TID=[61] Failed to create clone request. System.Exception: Clone failed. Error details are Cannot clone database. Either the cloned database name <Target_Server_Name_Target_Database_Clone_Name> conflicts with another database on same instance or the same resource is registered by an other user during discovery.

Topic

Symptom

Retention

Snapshots remain past retention setting
Snapshots are deleted prior to retention setting

Display

SnapCenter displays Deleted/Renamed database with no backups to delete
Database is not recognized after renaming in SQL Server
Cloning Cannot create a clone due to duplicate database name

 

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.