Database Vault is licensed on a per-computer basis. One license authorizes installation and use on exactly one machine at a time. The license cannot be moved or swapped between computers without first completely removing the software from the original system. To perform a transfer, contact the sales department with your license key and new computer details. For MySQL, a single licensed installation can back up as many remote servers as required. SQL Server backups, however, are limited to the instance running on the same machine because of dependencies on the Microsoft SMO library. Additional SQL Server systems each require a separate license.

These rules exist because Database Vault performs tight integration with the host operating system and database engines. The model prevents unlicensed concurrent use while allowing practical flexibility where technically feasible. Administrators responsible for mixed database environments must map their server inventory against these distinctions to purchase the correct number of licenses. Ignoring the SQL Server restriction, in particular, can lead to failed backup jobs or compliance violations. Planning around the terms avoids downtime and ensures reliable database protection across your infrastructure.

#License Installation and Mobility

The core restriction is that each license is permanently associated with one computer until a formal transfer occurs. This binding happens at activation and uses hardware identifiers to enforce compliance. You cannot simply copy the license file or run the executable on a second machine while leaving the first installation intact. Any attempt to do so risks activation errors or license revocation. When migrating to new hardware, such as during server upgrades or consolidations, the only supported path is complete uninstallation from the source computer. This includes removing program files, configuration data, and any registry entries created during installation. Once those steps are verified, the sales department can re-issue activation for the destination system. The process typically takes one to two business days and requires proof of ownership.

#Steps to Transfer a License

  • Uninstall Database Vault from the original computer and confirm all components have been removed to prevent duplicate activation.
  • Collect your license key, purchase receipt, hostname and OS details of the new computer, and any other identifiers requested by sales.
  • Open a request with the sales department explaining the hardware change and supplying the gathered information.
  • After receiving transfer approval, install the software on the new machine and complete the activation process using the updated license.

#MySQL Remote Backup Capabilities

A single Database Vault license permits backup operations against any number of MySQL servers reachable over the network. The MySQL servers do not need to be installed on the same physical or virtual machine that hosts Database Vault. This design leverages standard MySQL client libraries and network protocols that support remote TCP/IP connections, authentication, and consistent backup methods such as logical or binary logging. In practice, this allows a dedicated backup server to protect dozens or even hundreds of remote MySQL instances without additional per-server licensing fees. The approach is especially valuable in hosting environments or distributed application stacks where databases reside on separate infrastructure for performance or security reasons. Network connectivity, proper user privileges with backup permissions, and firewall rules allowing the traffic are the only prerequisites. Because there is no technical tie to a local MySQL installation, one licensed copy scales efficiently across an entire MySQL estate.

#SQL Server Backup Constraints

SQL Server backup functionality is deliberately limited to the database engine installed on the same computer as Database Vault. The restriction originates from the software's reliance on Microsoft's SMO library, a .NET component set that manages SQL Server instances, databases, and backup operations. SMO performs best when it has local access to the SQL Server services, shared memory endpoints, and Windows-level permissions that are difficult to replicate securely over the network. As a direct consequence, you cannot use one Database Vault installation to back up SQL Server instances running on separate machines. Each distinct SQL Server host requires its own licensed copy of Database Vault. This per-machine model must be factored into budgeting and deployment planning whenever your environment contains multiple SQL Server systems, whether they are standalone, clustered, or virtualized. Attempting remote SQL Server backups will fail because the underlying SMO calls are not supported in that configuration.

#Common Pitfalls to Avoid

  • Treating SQL Server the same as MySQL and assuming one license can protect multiple remote SQL instances.
  • Installing on additional machines before uninstalling from the original, which can invalidate the license or block activation.
  • Underestimating the number of physical or virtual machines running SQL Server when determining license quantities.
  • Overlooking hardware changes that necessitate a formal transfer, leading to expired activations during maintenance windows.

Evaluate your database inventory and count the distinct machines running SQL Server before purchasing licenses. Use the flexible MySQL remote support to centralize backups where possible. When hardware refreshes or infrastructure changes arise, follow the transfer process exactly to maintain continuous protection. Contact the sales department for any clarification on your specific environment or to adjust licensing as your server count evolves.