Knowledgebase:
Acronis Most Frequently Asked Questions
Posted by Rick Klemetson, Last modified by Rick Klemetson on Mar 27, 2015 11:38 AM

This Knowledgebase FAQ provides answers to frequent questions related to using Acronis.

Q: When multiple customers are provisioned for eFolder Acronis BDR, should I install the AMS on my computer, with only the agents on the customer computer?

A: We recommend having an AMS installed at each customer site. Having an AMS manage systems across the internet does not work well.

 

Q: Does Acronis Management Server install SQL or MySQL on the server? Will this new installation conflict with the SQL that is already on the server?

A: The Acronis Management Server installs SQL Express 2008 and there can be instances of conflict between the existing and the new SQL installations.

Note: If SQL is already installed on the machine, it is possible to use the existing installed copy for the Management Server. Create a new instance for Acronis first and then, during the installation, select that new instance instead of the AMS-installed SQL Express 2008.

 

Q: What is the recommended size of the target server compared to the source server? For example, if I have a 200 GB drive that has 100 GB of data, how large would my cloud server need to be for the backup with 60 days retention?

A:. The best practice for 60 days of retention would be to allow roughly 3x used space for backup space. While Acronis does a pretty good job of compressing backups, you should still allow a little extra space for incremental backup and differentials Also, ensure there is enough space to hold 3 base images. Why?

Retention policy deletes backups after 60 days. However, once your first full backup is 60 days old, it won’t be deleted (because there are still incremental backups relying on it.) You’ll have to wait another 30 days (until the last incremental backup of that first chain is 60 days old) before the full backup will be deleted. Since you will probably have accumulated another full backup by that time, we recommend allowing storage space for at least 3 full images.

Note: Remember, of course, any recommendations on space allowance are contingent on what sort of data change occurs. It’s entirely possible to experience one to five GB of data change in one day, which would require more space.

Also if you do granular exchange recoveries, a second information store backup for the exchange data is necessary to ensure enough space to hold several exchange database full images. Since these do not compress well, it is common to experience backup sizes similar to the actual size of the database.

 

Q: What is the difference between agent-less backup of a virtual machine and agent-based backup of a virtual machine?

A:. Agent-less backup takes place on a hypervisor level.  In version 11.5, the hypervisor level backup is not application-aware (although it is fully VSS-aware). Using a backup running on your Hyper-V host, your SQL machine can be fully backed-up in a consistent state and restored fully or partially (for example, restoring only specific files). However, with agent-less backup, SQL data is not treated separately. Functions like mounting or restoring a specific database directly into an SQL server are missing.

Agent-based backup happens from inside the guest OS. When using an agent-based backup method and installing the SQL agent, all these functions will be available. However, agent-based backup requires installation of an agent inside the guest OS and this VM must be treated as a "machines with Agents" type of resource.

Good news: A license for One Backup Advanced for Hyper-V allows (a) backup of one host, (b) backup of all VMs running on this host at a hypervisor level, and (c) all agents installed directly inside the guest OS.  So with this one license, you can use both methods of backup for any or all of your machines on your host.

Note: If you have a Hyper-V cluster, you will need to have a license for all hosts in this cluster.

 

(1 vote(s))
Helpful
Not helpful

Comments (0)