Published 27 October 2016
Both Server and Agent require a 64-bit operating system.
SQL Clone Server requirements
A single central server is required to use SQL Clone within an organization, it co-ordinates agents, and serves the SQL Clone web app.
- Windows Server 2008 R2 or Windows 7 (or later)
- Access to a SQL Server (2008 or later, or Azure SQL Database) for storing configuration data
- An empty database, or CREATE ANY DATABASE permission on the server so that SQL Clone can create its configuration database
- At least SELECT/UPDATE/INSERT/DELETE/ALTER permissions on the configuration database
- .NET Framework 4.6.1 or later
- If using Windows Server 2008 R2 or Windows 7, installation upgrades security defaults to match later Windows versions:
- TLS 1.2 enabled (part of installation)
- SendTrustedIssuerList disabled (part of installation)
- If using Windows 10 or Windows Server 2016, installation allows Edge to access sites hosted on the local machine:
- LoopbackExempt permission added to Edge (part of installation)
By default the SQL Clone server web UI is served over HTTP and uses port 14145. To use HTTPS or a different port number follow the instructions on Configuring HTTPS and custom ports
Firewall must permit incoming connection to Port 14145 (or the custom configured port - see above) and port 14146
SQL Clone Agent requirements
An agent should be installed on the same machine as any SQL Server you wish SQL Clone to use as a source of images, destination for clones, or temporary scratch space for restoring backups.
- Minimum (limited to <1.8TB images): Windows Server 2008 R2 or Windows 7
- Recommended (limited to <64TB images): At least Windows Server 2012 or Windows 8.1
- SQL Server 2008 or later (Express edition is sufficient - though Clones will not circumvent SQL Server Express' 10GB database size limit)
- .NET Framework 4.7.2 or later (part of installation)
- Outbound connection to remote (SQL Clone Server) port 14146 must be allowed
This requires a Windows user account which has:
- Local admin privileges in order to use the Virtual Disk Service
- Read/write access to network locations where images will be stored
On local SQL Server instances where clones will be created or dropped, or images created from, the agent will also need a login with:
- Membership in the sysadmin fixed server role
This can be either a Windows login tied to the agent's Windows account, or a SQL Server login.
If you want to use a SQL Server login, you will need to provide the username and password (once) when creating an image or clone with the instance.
For a computer not connected to the internet, you will need to manually install these pre-requisites before running the SQL Clone Agent installer
If any of these requirements are problematic for you (or your organization), we'd love to hear about it by email.