Comments
Sort by recent activity
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 $...
Makes sense to me! I'll raise this with the team.
When you say patching, is that when patching SQL Clone itself and its agents? / comments
Makes sense to me! I'll raise this with the team.
When you say patching, is that when patching SQL Clone itself and its agents?
Thanks for helping us understand!
We'll factor your feedback into our next-step discussions for this feature. / comments
Thanks for helping us understand!
We'll factor your feedback into our next-step discussions for this feature.
Hi Amirhadi,
The Clone agent creates a temporary user on the copied image database, gives it high privileges just on that database (db_owner), and then impersonates it to run your scripts. We implemented it that way for the first pass to keep the scripts from running under Clone agent's (normally high) server-level privileges.
As such, the temporary user is prevented from doing work outside that specific database (i.e. performing server-level activities and reading from or writing to other databases), which will include the use of xp_CMDShell.
I'd love to hear about what you were trying to get done with PowerShell, and how you were blocked with the current implementation. The current process is very much a work in progress - we're trying to get it to a place where it's easy to do whatever you need to do, as safely as possible. User feedback helps us figure out what we need to build next. [image] / comments
Hi Amirhadi,
The Clone agent creates a temporary user on the copied image database, gives it high privileges just on that database (db_owner), and then impersonates it to run your scripts. We imple...
Nowhere too accessible, now I look. I'll put a task up to improve our logging there, but in the meantime you can plow through SQL Clone's config database to find the information. First you need to find the operation that created your image. SELECT TOP 1000 *
FROM SQLClone_Config.dbo.Operations
WHERE Discriminator = N'ImageOperationEf'
ORDER BY Timestamp DESC;
Use that to find the Id of your image creation operation based on its timestamp (when the operation was created), then SELECT *
FROM SQLClone_Config.dbo.OperationMessages
WHERE OperationId = <YourId>;
That should provide you with the start and end times of the operation. / comments
Nowhere too accessible, now I look. I'll put a task up to improve our logging there, but in the meantime you can plow through SQL Clone's config database to find the information. First you need to ...
I'd be very interested in learning if this is reproducible too, either between different people, or just different times. Do you notice this taking reliably longer now, or is it intermittent? How large is the backup file now, roughly? (Just wondering if it has crossed some internal threshold somewhere.) / comments
I'd be very interested in learning if this is reproducible too, either between different people, or just different times. Do you notice this taking reliably longer now, or is it intermittent? How l...
Hi - just as a diagnostic, could you pop open Local Security Policy (secpol.msc), navigate to Local Policies->User Rights Assignment, and have a look under 'Perform volume maintenance tasks'? The agent user should be a member of at least one of the groups under that heading. You can check that via 'Edit local users and groups' (lusrmgr). / comments
Hi - just as a diagnostic, could you pop open Local Security Policy (secpol.msc), navigate to Local Policies->User Rights Assignment, and have a look under 'Perform volume maintenance tasks'? The a...