Comments
Sort by recent activity
Hi! While not directly supported in-tool, it shouldn't be too difficult to move image files from one place to another, then update the SQL Clone config database to refer to the new location. If you'd like to pursue this, probably the simplest option is to get in touch with support@red-gate.com and we can figure this out properly. It's a different story for any existing clones of those images, though. Clone disk files are parented to a specific file path (i.e. pointing straight at the image file), and have that information written directly into them. This is the nature of the VHD file format. It won't be easy to point those at the new image location (you'd need to hack the clone files with a hex editor) - far easier to drop the clones and recreate them afresh once the images have been moved. Hope that helps! Owen / comments
Hi!While not directly supported in-tool, it shouldn't be too difficult to move image files from one place to another, then update the SQL Clone config database to refer to the new location. If you'...
Hi gemu, You can enter your license key via the 'SQL Clone Server Setup' tool installed alongside the SQL Clone server and available from the Start menu (use the 'Manage license...' button in the tool), or, on the web UI, on the Settings/Licensing page. Owen / comments
Hi gemu,You can enter your license key via the 'SQL Clone Server Setup' tool installed alongside the SQL Clone server and available from the Start menu (use the 'Manage license...' button in the to...
Hi Randy, As you'll know, clones are differencing disks, and will grow when something writes to their data files. The usual culprit is SQL Server, which makes its own decisions about what to write to attached data files, and when. That can make diagnosing these kinds of issues tricky. I've got a few diagnostic questions:
Do clones grow on their own if you don't write to them? (E.g. they're just created, with no modification template, and are left to sit there.)
Do clones grow on their own if they're made from images without any modifications?
If you've been seeing growth in clones based on an image from a live database, what about clones based on an image from a backup file? (Or vice versa if you've been making images from backup files?)
Do you have any clones that don't grow by themselves? Is there any pattern there?
Thanks! Owen / comments
Hi Randy,As you'll know, clones are differencing disks, and will grow when something writes to their data files. The usual culprit is SQL Server, which makes its own decisions about what to write t...
Hi David, How about something like this? # download a single use agent installer
<br><div>Invoke-WebRequest `
-Uri http://your.sqlclone.server:14145/api/installer `
-OutFile 'C:\My\Downloads\SingleUseSQLCloneAgentInstaller.exe' `
-UseDefaultCredentials</div><div>
<br># run silent installation
</div><div>C:\My\Downloads\SingleUseSQLCloneAgentInstaller.exe -s `
SERVICEUSERNAME=DOMAIN\Username `
SERVICEPASSWORD=MyPassword</div>
Many thanks! / comments
Hi David,How about something like this?# download a single use agent installer
<br><div>Invoke-WebRequest `
-Uri http://your.sqlclone.server:14145/api/installer `
-OutFile 'C:\My\Downloads\SingleUs...
Thanks for your help with us on this ticket! We've added a new troubleshooting page to help people in future. Owen / comments
Thanks for your help with us on this ticket! We've added a new troubleshooting page to help people in future.Owen
Hi Gert, We've made a change to how we use VSS in our latest release (2.6.3). It might be worth retrying with that version - let us know if that doesn't help! Owen / comments
Hi Gert,We've made a change to how we use VSS in our latest release (2.6.3). It might be worth retrying with that version - let us know if that doesn't help!Owen
Hi Ramūnas, Glad to hear it! I should make it clearer that these kinds of breaking changes are definitely out of the ordinary, and it's a policy of Clone's to retain backwards compatibility of our API within a major version. (In my previous post I made it sound as though such changes were an accepted fact of life.) In this case unfortunately something slipped through the cracks. We've since implemented a new suite of automated regression tests on our API to make this sort of thing less likely in the future. Owen / comments
Hi Ramūnas,Glad to hear it!I should make it clearer that these kinds of breaking changes are definitely out of the ordinary, and it's a policy of Clone's to retain backwards compatibility of our AP...
Hi Ramunas, Occasionally there are unavoidable changes to the Clone server API. As a result, anything expecting to target the old API falls over, including any old PowerShell cmdlets. You can re-download the cmdlets from the Clone UI's Settings page to upgrade them to the latest version. Sorry for the inconvenience - let me know if that doesn't solve the issue. (In future releases, we'll try to ensure the cmdlets give you a more sensible error message when you connect to a version of Clone that won't support them.) Many thanks, Owen / comments
Hi Ramunas,Occasionally there are unavoidable changes to the Clone server API. As a result, anything expecting to target the old API falls over, including any old PowerShell cmdlets. You can re-dow...
When masking an image, Clone will ignore the masking set's configuration for:
which database to mask (as Clone decides on the database's name when it attaches it for masking, so pre-defining the name won't work),
which instance and machine the database is on (as your masking set file may not know ahead of time which temporary instance will be used).
So if the masking set file expects to mask a database at MyMachine \ MyServer2014 \ MyDatabasebut in reality, for this run, Clone has attached the imaged database to SomeOtherMachine \ TemporaryInstance2016 \ SqlCloneTemp_yuR72then it's the latter that will be used, and the former details ignored. Hopefully that sheds some light on Clone's behaviour. / comments
When masking an image, Clone will ignore the masking set's configuration for:
which database to mask (as Clone decides on the database's name when it attaches it for masking, so pre-defining the na...
Hi Robert, We fixed an issue that sounds similar to what you're experiencing in Clone 4.4.33. Could you try updating the Clone server to that version (or newer), downloading and installing its PowerShell cmdlets from Settings, and retrying? Regarding your question, Clone server uses two ports - 14145 for communication with clients (that is, PowerShell cmdlets, and the web UI - it can also be configured to use a different port, and HTTPS) and 14146 for communication with agents. It won't vary by which cmdlet is called. Clients will always talk to the client port, and agents will always talk to the agent port, and they won't need to do otherwise.
/ comments
Hi Robert,We fixed an issue that sounds similar to what you're experiencing in Clone 4.4.33. Could you try updating the Clone server to that version (or newer), downloading and installing its Power...