Comments
Sort by recent activity
Hi Paul, I'm afraid neither Data Masker nor SQL Clone are currently included in the SQL Toolbelt. Sorry for any confusion! / comments
Hi Paul, I'm afraid neither Data Masker nor SQL Clone are currently included in the SQL Toolbelt. Sorry for any confusion!
No problem - bear in mind I've spotted a bug in the case where $environmentName is null (intended to specify 'no environment'), in that if there are machines of the given name with an environment set, it'll delete clones from them as well. I'll fix that today and update the post.
Edit: updated! / comments
No problem - bear in mind I've spotted a bug in the case where $environmentName is null (intended to specify 'no environment'), in that if there are machines of the given name with an environment s...
Hi Benethor, how about something like this? Connect-SqlClone -ServerUrl 'http://sql-clone.example.com:14145'
$environmentName = $null # replace with environment name string if desired
$machineName = 'myMachineName'
$instancesOnMachine = Get-SqlCloneSqlServerInstance -MachineName $machineName | where {$_.Environment -eq $environmentName}
foreach ($instance in $instancesOnMachine) {
$clonesToDelete = Get-SqlClone -Location $instance
foreach ($clone in $clonesToDelete) {
Remove-SqlClone $clone | Wait-SqlCloneOperation
}
}
This will find all SQL Server instances on a named machine, then find all clones based on those instances, and delete them. / comments
Hi Benethor, how about something like this?Connect-SqlClone -ServerUrl 'http://sql-clone.example.com:14145'
$environmentName = $null # replace with environment name string if desired
$machineName ...
Hi dbChanger,
If the old machine isn't in use anymore, and any images and clones made using it have been deleted, you can remove it from Clone Server's machines list with the Remove-SqlCloneMachine cmdlet introduced in version 2.3.2.
Let me know if you have any issues! / comments
Hi dbChanger,
If the old machine isn't in use anymore, and any images and clones made using it have been deleted, you can remove it from Clone Server's machines list with the Remove-SqlCloneMachine...
Version 2.3.2 is available via our check-for-updates system, so Clone Server should be automatically noticing it when its re-check interval swings around. Alternatively you can download it directly from here. / comments
Version 2.3.2 is available via our check-for-updates system, so Clone Server should be automatically noticing it when its re-check interval swings around. Alternatively you can download it directly...
Hi Roger, Remove-SqlCloneMachine was introduced in version 2.3.2, and will require you to update your Powershell cmdlets to use.
The intended usage is for you yourself to delete any clones and images associated with some machine, shut down the agent service on that machine, and then invoke the cmdlet. Clone Server will then forget about that machine.
We're working on introducing an updated version of that cmdlet with some more robust removal functionality. / comments
Hi Roger, Remove-SqlCloneMachine was introduced in version 2.3.2, and will require you to update your Powershell cmdlets to use.
The intended usage is for you yourself to delete any clones and imag...
Hi lpedersen, When a Clone agent connects to its Clone server (for example, after the Clone server has restarted following an update), it will query the server to determine if it needs to update itself. If it does, it will download an updated version of itself from the Clone server (not from the Internet), and update itself using that. If an agent isn't able to update itself, that'll be highlighted on the dashboard within the summary widget, and on the Machines page in Settings. In that case, manually downloading an agent installer from the Clone server and installing it onto that machine (i.e. the same process used to install it in the first place) should solve the issue.
Hope that helps - I'll take a look at the documentation and make sure there's something there about this process.
/ comments
Hi lpedersen,When a Clone agent connects to its Clone server (for example, after the Clone server has restarted following an update), it will query the server to determine if it needs to update its...
Ultimately this was resolved by updating the agent's settings file at %ProgramData%\Red Gate\SQL Clone Agent\settings.json. The ManagementService/Url key was updated to point at the agent's HTTPS port, 14146, on the management service machine. / comments
Ultimately this was resolved by updating the agent's settings file at %ProgramData%\Red Gate\SQL Clone Agent\settings.json. The ManagementService/Url key was updated to point at the agent's HTTPS p...
Hi Benethor,
That's definitely unexpected behaviour - could I ask you to get in touch with support@red-gate.com about this, including your SQL Clone agent logs from your agent machine, at %localappdata%/Red Gate/Logs/SQL Clone ? We'll be able to hash things out more simply and then post a solution on this thread. / comments
Hi Benethor,
That's definitely unexpected behaviour - could I ask you to get in touch with support@red-gate.com about this, including your SQL Clone agent logs from your agent machine, at %localapp...
It sounds like there is an Operation row in SqlClone_Config.dbo.Operations where the AgentId field refers to an Agent ID that doesn't exist in SqlClone_Config.dbo.Agents.
The foreign key we've introduced essentially says 'if an operation is associated with an agent, that agent must actually have existed at some point'. So, when Clone tries to perform the migration and apply that new constraint, it fails.
The best bet is to run some SQL updates on the data so that there's no such inconsistency and the migration can go ahead - if you get in touch with support@red-gate.com about this, we can help devise a path forward. / comments
It sounds like there is an Operation row in SqlClone_Config.dbo.Operations where the AgentId field refers to an Agent ID that doesn't exist in SqlClone_Config.dbo.Agents.
The foreign key we've intr...