Online Documentation for SQL Backup for SQL Server
EMS SQL Backup FAQ
Please read this page attentively if you have questions about EMS SQL Backup.
- What versions of SQL Server does EMS SQL Backup support?
- Must EMS SQL Backup be installed on each server which I want to work with?
- I have 5 SQL Servers, 2 of which have two SQL Server instances running, how many licenses for EMS SQL Backup do I need to purchase?
- How to transfer a license from one SQL Server instance to another?
- How does EMS SQL Backup reduce backup size?
- Does the backup compression depend on SQL Server version or edition?
- How much is a backup file size reduced and what does it depend on?
- Can I restore a backup file of EMS SQL Backup on SQL Server with no EMS SQL Backup components installed?
- What are the reasons for reduction of time required for backup and recovery?
- Does EMS SQL Backup use undocumented features of SQL Server?
- Can EMS SQL Backup perform a standard backup, suitable for recovery on SQL Server, without using EMS SQL Backup?
- Does EMS SQL Backup support log shipping?
- I have servers in different time-zones. At what time-zone will tasks be launched?
- What is the advantage of using the Policy Engine of EMS SQL Backup compared to standard maintenance plans of SQL Server?
- Can different types of maintenance tasks go in the same policy?
- Can policy tasks have their own execution schedules?
- Can EMS SQL Backup perform a single maintenance task without creating policies?
- Can I execute multiple policies simultaneously on one server?
- I have setup SQL Server maintenance plans. Can I use them in EMS SQL Backup?
- How does EMS SQL Backup notify about a policy execution failure?
- Can I monitor/manage my set of servers using two (three) different (installed on different computers) consoles?
- Whether the servers, EMS SQL Backup works with, must be located within one local network?
- Do I need to open any additional ports or to enable protocols for working with EMS SQL Backup?
- Can I install EMS SQL Backup server components remotely?
- I failed to install server components remotely from EMS SQL Backup Console due to insufficient privileges or errors on installation. Can I run the installation wizard on the server machine to install server components?
- What kind of account should be used for running EMS SQL Backup service?
- Policy execution failed with the error: "The task cannot be completed. The owner (NT AUTHORITY\SYSTEM) of SqlBackup_XXXXXXXX_Task does not have access to server". Why does it happen?
- What are the differences between different versions of EMS SQL Backup?
- May I not pay the program maintenance?
- I get the "Access is denied" error on trying to install EMS SQL Backup server-side components via NetBIOS. How can I fix the problem?
A: EMS SQL Backup works with all SQL Server versions (except Compact Edition) from SQL Server 2000 up to SQL Server 2019.
A: Yes, EMS SQL Backup server components must be installed on each instance of SQL Server.
A: Totally you have 7 instances of SQL Server, it means that you need to purchase 7 licenses for EMS SQL Backup.
In order to transfer a license from one server to another perfrom the following steps.
- In the EMS SQL Backup Administration Console select the server which you wish to move the license from.
- In the context menu of the server select the "Deactivate license on ..." item.
- Follow the steps of the License Deactivation Wizard.
- Select the server on which you want to activate the deactivated license key.
- In the context menu of this server select the "Activate license on ..." item.
- Follow the steps of the License Activation Wizard.
A: This is achieved by compressing data received from the server during the backup process.
A: EMS SQL Backup uses its own data compression function, which does not depend on a version and edition of SQL Server.
A: It depends on data stored in the database and on a selected in EMS SQL Backup compression level. In case of text\numeric data when using compression a backup file size can be up to 80% less in comparison when compression is disabled. If a database mostly stores difficult to compress binary data, such as raster images in JPEG, the compression function cannot significantly reduce the backup file size.
A: No, you cannot. However, you can use the ConvertUtil.exe command line utility, which does not need to be installed and registered to convert backup files of EMS SQL Backup format to a standard SQL Server format. After being converted backup can be restored using standard SQL Server tools.
A: The compression level selection allows you to find a compromise between the backup speed and file size. At the same time the backup time execution can be reduced up to 80% compared with a native tool due to a lower load on the disk subsystem.
A: EMS SQL Backup uses only documented features of SQL Server, which guarantee its correct working on all available versions of SQL Server, as well as on future version releases.
A: Yes, EMS SQL Backup can do it. To do this you need to select SQL Server as a backup type in the Backup Wizard.
A: EMS SQL Backup performs log shipping using its compression and encryption features, which make this process faster and more secure.
A: When creating a policy, you can select whether a task on servers in different time-zones is launched at servers standard time or simultaneously against the console time. This option is called "Task Scheduling in different time zones" at Step 1 of the Policy Wizard.
A: EMS SQL Backup Policy Engine provides the following features:
- Using EMS SQL Backup backup functionality
- Ability to deploy and monitor policies on multiple servers of different versions simultaneously
- Easy-to-use policy monitoring mechanism
- Ability to use templates
A: A policy can contain both multiple tasks of different types and multiple tasks of the same type.
A: Yes, each task can have one or more schedules.
A: Yes, you can perform a maintenance task using the "Quick Maintenance Actions" context menu item of the Server tree.
A: Several policies can be deployed to a single server, their runtime can be the same and the execution time can intersect. However, 2 tasks of backup/recovery/log shipping can not be executed simultaneously on a single SQL Server instance.
A: You can convert SQL Server maintenance plans into EMS SQL Backup policies using the Maintenance Plan Conversion Wizard ("Maintenance Policies | Convert from Maintenance Plan" context menu of the Server tree).
A: EMS SQL Backup has the e-mail notification mechanism informing of the policy execution results. Also EMS SQL Backup Console displays statuses and results of policies while connecting to a server.
A: Yes, you can. However, your EMS SQL Backup Console configuration must be accessible to all your computers. The configuration can be stored both in a file and in a database on any SQL Server. In this case it is recommended to store the configuration on SQL Server. To change the configuration storage location, call "Options | Save Configuration", specify a new location and enable the "Switch to saved configuration" option to use a new location. In EMS SQL Backup Console, installed on other computers, you should switch to the new location using the "Options | Switch Configuration" dialogue.
A: Servers can be located anywhere. If you are able to connect to your servers using SQL Server Management Studio, EMS SQL Backup is able to work with them too.
A: It is neither necessary to open additional ports nor enable protocols beyond those already used by your SQL Server Management Studio.
A: Yes, you can install EMS SQL Backup server components remotely from EMS SQL Backup Console. In the Server tree, select SQL Server, on which you want to install the components, and click "Install server-side EMS SQL Backup Components" in the context menu. Then follow the instructions of the wizard.
The following conditions must be met for remote installation:
- Installing via SQL Server:
- You must have an account with SQL Server System Administrator Privileges, such as sa.
- SQL Server service must be run under an account with Windows Local Administrator Privileges, such as LocalSystem.
- Installing via NETBIOS:
- You must have Windows System Administrator Privileges on remote computer.
- You must have an account with SQL Server System Administrator Privileges, such as sa.
Q: I failed to install server components remotely from EMS SQL Backup Console due to insufficient privileges or errors on installation. Can I run the installation wizard on the server machine to install server components?
A: Yes, you can use the special mode for EMS SQL Backup installation program:
- Copy the installation package (SQLBackupSetup-1.x.x.xxxx.msi) to the server machine.
- Run the following command as Administrator: SQLBackupSetup.exe -var:"ServerInstall=1"
- Follow the steps of the installation wizard. It will automatically find all local server instances for installing server components.
A: To run EMS SQL Backup you can use any account with the following privileges:
- Access to SQL Server with Server Administrator Privileges.
- Write access to a directory which is used for creating backups.
- Ability of authorization on another computer on a network for read/record access to a general directory while log shipping process.
For example, a system domain user with all the mentioned above privileges can be used. If log shipping process is not planned, Local System embedded account can be used as a system user account.
A: This error occurs when SQL Server Agent receives wrong information about the user privileges set of NT AUTHORITY\SYSTEM that is the owner of the executing task. The problem can be solved in one of the following ways:
- Change EMS SQL Backup service account to any other one that has all the task run privileges on the server. Recreate a policy.
- Change the owner of SqlBackup_XXXXXXXX_Task to another user having the permissions to run tasks.
- If BUILTIN\Administrators account was removed from the server, restore it using the administrator privileges.
A: You can view the list of all functional differences between EMS SQL Backup versions in the Feature Matrix.
A: The basic price of EMS SQL Backup includes 1 Year Maintenance. Once the Maintenance term expires, you will be able to continue using the software without any limitations; however, you won’t have access to any product updates released after your maintenance expiration date.
A: First of all, make sure that the specified account has local Administrator privileges on the machine where the SQL Server service is running.
If you still have this problem then one of the solutions is to disable Remote UAC on the target system. It prevents local administrative accounts from accessing ADMIN$ shared folder and running installation process. To disable Remote UAC you need to add an entry in the registry of the target computer:
- open the registry,
- navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System,
- create a DWORD value called LocalAccountTokenFilterPolicy,
- assign this parameter a value of 1.
If you still have any questions, contact us at our Support Center.