Comments
Sort by recent activity
I assume by "Unregistered the SQL Clone agent" you mean running the Remove-SqlCloneMachine cmdlet? I have run the steps you gave, starting with a non-domain clean install of Windows 7, and did not have a problem installing an agent on the clone. That said, if I ran the original machine from a snapshot before I removed the clone that didn't work; SQL Clone got confused as to which machine was which.
If you're going to clone a VM that previously had a SQL Clone agent running on it, I would recommend removing the agent certificate and the agent settings.json file as well as uninstalling the agent before cloning:
Open the Windows Certificates snap-in (Run mmc.exe, go to File -> Add/Remove Snap-in, choose Certificates on the left, click Add, choose Computer account, click Next, click Finish, click OK)
Go to Certificates (Local Computer) -> Personal -> Certificates, and delete the SQL Clone Agent certificate
Remove the "settings.json" file under "%allusersprofile%\Red Gate\SQL Clone Agent" folder
If the snapshot you clone from has no agent installed, no agent certificate, and no settings.json, you should be able to clone as many times as you like and install agents on the clones.
/ comments
I assume by "Unregistered the SQL Clone agent" you mean running the Remove-SqlCloneMachine cmdlet?I have run the steps you gave, starting with a non-domain clean install of Windows 7, and did not h...
Is the VM on a domain? / comments
Is the VM on a domain?
Thanks. I've confirmed this is a bug in SQL Clone. I'll post back here when we've made any progress. / comments
Thanks. I've confirmed this is a bug in SQL Clone. I'll post back here when we've made any progress.
Hi, we have a fix for this, and will be releasing it next week. / comments
Hi, we have a fix for this, and will be releasing it next week.
Hmm, that's odd. There's no reason ALTER PROCEDURE shouldn't work. Could you share the modification script you're using? (you can send it to support@red-gate.com if you don't want it public.) GO and comments are supported - scripts should work just the same as they do in SSMS. Does the script you upload to SQL Clone work if you run it in SSMS against a restore of the same backup you're using to create the image?
/ comments
Hmm, that's odd. There's no reason ALTER PROCEDURE shouldn't work. Could you share the modification script you're using? (you can send it to support@red-gate.com if you don't want it public.)GO and...
Does the image creation succeed eventually, just staying at 9% for a long time, or does it hang forever at 9%? / comments
Does the image creation succeed eventually, just staying at 9% for a long time, or does it hang forever at 9%?
No, this is not possible, as SQL Server does not allow database version downgrades. / comments
No, this is not possible, as SQL Server does not allow database version downgrades.
OK - so SQL Clone still things the ProPolis_FinancieelSSI... image still exists. An image isn't just a file - it's also metadata stored in SQL Clone, so just deleting the file won't delete the image, you always need to delete image from SQL Clone. I'm not sure why running Remove-SqlCloneImage didn't work though. Most SQL Clone cmdlets just start an operation, and return immediately, including Remove-SqlCloneImage. They return an operation id that you can then pass to Wait-SqlCloneOperation. Could you try running Remove-SqlCloneImage again, piping the output to Wait-SqlCloneOperation? Like in example 2 on https://documentation.red-gate.com/clone2/automation/powershell-cmdlet-reference/remove-sqlcloneimage?
/ comments
OK - so SQL Clone still things the ProPolis_FinancieelSSI... image still exists. An image isn't just a file - it's also metadata stored in SQL Clone, so just deleting the file won't delete the imag...
Ah, turns out SQL Clone can't delete an image if its backing folder has been deleted outside of SQL Clone. This is a bug in SQL Clone which I have now fixed. We will hopefully release today, if not Monday. / comments
Ah, turns out SQL Clone can't delete an image if its backing folder has been deleted outside of SQL Clone. This is a bug in SQL Clone which I have now fixed. We will hopefully release today, if not...
That's fine, you can use PowerShell, but the quickest way for me to get an overview of the situation so I can help would be a screenshot of the web UI. / comments
That's fine, you can use PowerShell, but the quickest way for me to get an overview of the situation so I can help would be a screenshot of the web UI.