NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Data Protection

Clone_database created database with wrong name.

Mayur_Shelke
3,534 Views

Hi All,

 

We regularly create database snapshots using SMSQL. We have recently found one strange issue with database creation. We use below command to create db clone.

 

clone-database –svr 'servername' –inst 'servername' -d 'PROD_DB' -tgInst 'SERVERNAME' -tgDb 'PROD_DB_01' -tgmpdir 'DirectoryDetails' -ForceTerminateConnection -RetainBackups 1 -trunclog $false –mgmt standard

 

 

So instead of creating database PROD_DB_01 the snap manager restored database with name PROD_DB__Clone on it's own.

 

The command mentioned above is scheduled through sql agent job to avoid any manual intervention. 

 

Can somebody help with the same to resolve the issue of wrong database creation with completely different name even when we pass the name of database through command only.

1 ACCEPTED SOLUTION

Mayur_Shelke
3,394 Views

This was resolved. Somehow the delete-clone step was missed and the new clones were created with different as the clone name specified was already existing.

View solution in original post

1 REPLY 1

Mayur_Shelke
3,395 Views

This was resolved. Somehow the delete-clone step was missed and the new clones were created with different as the clone name specified was already existing.

Public