Keep your data safe with Cloud Backup Solutions


Cloud Backup Solution Provider | Dubai UAE

Almost 50,000+ businesses chose Veeam® to protect their business-critical virtual servers and data over the last 12 months. Veeam provides fully integrated, quick and secure way to backup, replicate and restore from the cloud. Being, Veeam Partner in Dubai, we have provided our services all over UAE.

Looking for a Fast, flexible and reliable recovery of virtualized applications and data? With Veeam you can easily backup & replicate quickly and reliably in a single software solution.

Sit and relax-your data is protected and can easily be recovered when you need it the most – both on-premise and offsite.

In Today's business environment, every company needs to have a reliable and secure data backup and recovery solution. Taking the example of a situation in which a fire has occurred at your primary data center. The outcome is predictable and can bring your business to a grinding halt. It leads to loss of millions of dollars in terms of productivity, loss of important files and documents. Therefore the need to go for a robust and reliable offsite backup strategy is vital for all businesses no matter how small your business is. 

Veeam users should have already taken their peaceful mind-phase as they know their business-critical virtual servers and machines can b recovered and restored within minutes when required. Have you ever thought of a situation in which a disaster strikes in and you end up losing your onsite backup?.Applicom, being a cloud backup provider in Dubai, UAE makes sure that all your data and backups are secure.


Best practices for Veeam Backup Server configuration

The Backup Server serves the main role where Veeam Backup & Replication is installed and the tips below will help you to have a good experience with this critical component. Let's have a look into the best practices for the backup server in VMware environment:

  • Disable the default roles of making the console a proxy and repository. For very small environments, these may make sense to keep around, but for any installation of size let the backup server do its job of managing the jobs and other components rather than doing the actual work of backing up.
  • v9 removed the limit of 100 jobs in a backup server. This makes the point above a lot cleaner for installations with many jobs and the preference to have only one console.
  • A few thousand VMs per server are reasonable. There are no hard or soft limits, but this becomes a good working number for how many VMs you can protect in one console. Other factors like number of sites, security zones and business requirements may introduce non-technical reasons to have more servers however.
  • Allocate plenty of memory on the backup server. You can find these requirements in the Veeam Help Center, and the important thing to remember is to have a base of 4 GB RAM plus 500 MB RAM for each concurrent job. Additionally, don’t omit the memory requirements for other roles should they be on the backup server (Proxy, repository, WAN Accelerator, etc.).


Physical or virtual: Where to install your Veeam Backup Server?

It's a tough task to decide whether to have the backup server physical or virtual. Below mentioned are some benefits of having a virtual and physical Veeam backup server.



Benefits of Physical 

  • Best practice for any disaster recovery (DR) solution: Your DR system should not rely on the system – it is designed to protect and recover.
  • Use configuration backup or remote SQL server to protect data.
  • Install Veeam Endpoint Backup FREE to protect the Veeam Backup server (if required to have a complete backup image of it).


Benefits of Virtual 

  • Enables 100% virtual data center (or gets you there closer).
  • More protection options ‒ back up or replicate the entire VM (the backup server VM) with Veeam.
  • Think through and test thoroughly your DR plan.


If there is only one VSphere Cluster, it's always advised to make the Veeam backup infrastructure physical.In addition to the reasons mentioned above, a benefit of the backup infrastructure (including the backup server, proxies, repositories, etc.) being physical is to avoid any “skew” of vSphere DRS during the backup window. It can take a good amount of CPU and RAM to perform the actual backup, so if you can do it without affecting everything else from a CPU and RAM perspective and avoid unnecessary vMotion events, that is a positive. When multiple vSphere clusters are in place, a virtualized backup server becomes a great choice as long as it is not managing the Availability of the cluster it is in.

Backup Server dependencies

Much like deciding where to place the backup server in regards to having the highest levels of Availability, the same goes for any dependencies that may be in place. Here is a list of best practices to avoid issues due to dependencies:

  • Think through the dependencies. Take a good look at your VMware environment as much as you can to ensure nothing could be required that you don’t have, in the event of a restore. Also, ask another opinion to try to identify an unforeseen dependency.
  • Do a DR test. This goes without saying anyway, and we have big plans in this space with Veeam Availability Orchestrator, but using the backup server on a totally different site will make you find out what you need that you don’t have.
  • Local accounts. These become a good idea when you are performing a restore of some type without Active Directory.
  • SQL authentication. Much like the reasoning above, if the Active Directory domain isn’t available, you may have trouble accessing the SQL Server database that hosts the backup server’s database.
  • Workgroup vs. Domain decisions. If you have a separate “management domain” of Active Directory that is completely isolated from a security and infrastructure perspective of what the backup server is protecting, then using a domain set of accounts (including for the previous two points) can be advisable. When there is only one Active Directory domain and Veeam is backing it up, it is more advisable to use local system workgroup credentials for the Veeam configuration of the backup server, as the domain becomes a dependency otherwise.
  • Back to the physical vs. virtual server discussion. A dependency may be realized when considering the points above, which is why the broad consensus is to use a physical server.


Backup Server placement best practices

When there are backups and replications in use, a lot of factors come into play in deciding where to place the backup server. It's generally recommended to have the backup server on the same site as the VMs it is backing up, especially when the vCenter Server is on that site. vCenter communication over the WAN may be slow.

With respect to Disaster recovery, having the backup server in the production site is a good decision because the DR situation means we are going to failover to a replica. As such, the recovery time objectives (RTO) of the replicated VM(s) are very quick. Additionally, with an extra backup server at the DR site to manage the failover, you’ll be in good shape (discussed next). 

If replication is used, it’s recommended to put a backup server in the DR site and have this server manage the replication jobs. This ensures that you can have one-click failover when the production site is down. Additionally, there is no recovery point objective (RPO) impact as replicas inherently have a less-frequent RPO than backups.

If you do virtualize your backup server on the production site, you have one additional point here in that you can replicate it to your DR site like any other VM. If you are concerned about the backup files themselves, the backup copy job is your friend and we'll cover that in another post of this series.


it company in dubaiWhy Choose Applicom 

  • Applicom helps you by delivering top-notch Computer And Storage Infrastructure Designed to scale and grow With Your Business requirements.
  • Over21 years of experience as a trusted IT services & solutions provider in the UAE , We have helped customers to achieve high levels of data backup and protection.