Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

SnapCenter Deleted/Renamed Database Resolution Guide

Views:
91
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

 

Scan to view the article on your device