Comments
Sort by recent activity
Ah, of course. I assume the same thing persists when opening Clone in an incognito browser window? The UI retains a small state cache (which is cleared out in an incognito window or via a ctrl-F5 hard refresh), and I'm keen to rule out some odd transient error. In the meantime, it might be worth trying to do the same thing you're trying to do on the UI, but through PowerShell instead (e.g. with New-SqlCloneImage). This would rule out a functional issue on the agent, and should unblock you while the UI issue is tracked down. / comments
Ah, of course. I assume the same thing persists when opening Clone in an incognito browser window? The UI retains a small state cache (which is cleared out in an incognito window or via a ctrl-F5 h...
For general reference, we took this to support@red-gate.com and determined that, after deleting an old agent and installing a fresh one on a machine with the same machine name and SQL Server instance names (i.e. a VM refresh), the associated SQL Server instances weren't getting hooked up to the new agent. We'll be looking to improve Clone's behaviour here, but as a workaround, destroyed agents can be cleaned up with the Remove-SqlCloneMachine cmdlet, which should make all this behave more sensibly for now. If that's done after the agent is destroyed, but before the new one is installed, this issue shouldn't arise. / comments
For general reference, we took this to support@red-gate.com and determined that, after deleting an old agent and installing a fresh one on a machine with the same machine name and SQL Server instan...
Looks like the agent is online and happy from that - just the web UI doesn't agree. I'll have to identify some diagnostic steps to help us figure out why. In the meantime, to confirm that the agent is functioning normally, could you try creating a clone or image using that agent's SQL Server instance(s)? / comments
Looks like the agent is online and happy from that - just the web UI doesn't agree. I'll have to identify some diagnostic steps to help us figure out why. In the meantime, to confirm that the agent...
That's unusual. Could I ask you to use Clone's PowerShell cmdlets to help diagnose this? (The module can be downloaded from the UI's settings page.) The Get-SqlCloneMachine cmdlet should return information on your agents, including their state. Ordinarily the web UI would be a perfectly good source of information for this, but it seems as though in this case it's disagreeing with itself. / comments
That's unusual. Could I ask you to use Clone's PowerShell cmdlets to help diagnose this? (The module can be downloaded from the UI's settings page.) The Get-SqlCloneMachine cmdlet should return inf...
Great, I'm glad you were able to get things sorted. / comments
Great, I'm glad you were able to get things sorted.
Apologies for the delay on getting back to you on this! Ordinarily the database files would be restored from backup directly into the image destination, so for them to appear in the temporary directory is unusual. The best path forward here is probably to get in touch with our support team directly (support@red-gate.com) so that we can arrange to have a look at the agent log files and see what's been going on. / comments
Apologies for the delay on getting back to you on this!Ordinarily the database files would be restored from backup directly into the image destination, so for them to appear in the temporary direct...
Hi Aziz, Thanks for trying out Clone. The best bet based on my understanding of your situation is to: a) restart the Clone server service, b) restart the Clone agent services, c) let them hook up and settle in for a few minutes, d) try to delete your images using the Clone UI, e) uninstall Clone once your dashboard is clear. The Clone UI should be accessible once the Clone server service is running. Even if your trial has expired, Clone will still allow you to delete your images and clones from the UI (since otherwise you wouldn't be able to clean up after a trial!). Hopefully that helps - let me know if there are any more issues. Owen / comments
Hi Aziz,Thanks for trying out Clone.The best bet based on my understanding of your situation is to:a) restart the Clone server service,b) restart the Clone agent services,c) let them hook up and se...
Hi Sean,
Probably the best place to ask would be the SQL Server Central forums - this is the forum for our SQL Clone product. [image]
Owen / comments
Hi Sean,
Probably the best place to ask would be the SQL Server Central forums - this is the forum for our SQL Clone product.
Owen
Hi Garry, as of Clone 2.4.2, there is an -OverrideStorageLocation parameter on the New-SqlClone cmdlet that allows you to specify a different folder to store your clone files (for this specific clone) in.
Example usage: New-SqlClone -Name MyClone `
-Image (Get-SqlCloneImage -Name MyImage) `
-Location (Get-SqlCloneSqlServerInstance -InstanceName SQL2014) `
-OverrideStorageLocation D:\FolderOnTheMachineHostingThatSQL2014Instance
Hope that helps! / comments
Hi Garry, as of Clone 2.4.2, there is an -OverrideStorageLocation parameter on the New-SqlClone cmdlet that allows you to specify a different folder to store your clone files (for this specific clo...
Would something like this do the job? $allSqlServerInstances = Get-SqlCloneSqlServerInstance
$myClone = Get-SqlClone -Name MyClone
$myCloneInstance = $allSqlServerInstances | Where-Object Id -Eq $myClone.LocationId
/ comments
Would something like this do the job?$allSqlServerInstances = Get-SqlCloneSqlServerInstance
$myClone = Get-SqlClone -Name MyClone
$myCloneInstance = $allSqlServerInstances | Where-Object Id -Eq $...