Veeam v10 NAS

Veeam v10 Roundup

Veeam Backup and Replication v10 has now been made publicly available.  The update contains 150 enhancements, let’s take a look at a few of them

NAS Protection

One of the most requested features from customers has been NAS protection, that is now available natively in V10.  The system is software based and hardware agnostic, able to backup SMB and NFS shares.  The NAS feature is also able to backup SMB file shares hosted on Windows systems and NFS shares on Linux servers.  The v10 implementation of NAS backup utilises changed file tracking allowing incremental jobs to backup only what has changed.

Veeam v10 NAS

Credit Veeam for image

Setting up NAS backups will look familiar to those already working with Veeam, file proxies act as the data movers, a new role the cache repository is responsible for the changed file tracking.  Backups can be stored like any other Veeam backup in repositories but can also be tiered to the public cloud for longer term retention

Multi-VM Instant Recovery

Instant Recovery has been available for some years now , this allows the immediate recovery of a VM by running it from the backup.  The updated VM Instant Recovery enhances performance by methods including caching to RAM and read ahead.  A knock on impact of this enhanced performance has been that multiple VM’s can now be instantly recovered in a single operation.

vSphere Any Backup Restore

It is now possible to restore any backups to your vSphere environment no matter what format the original backup was.  This for example allows you to restore backups of physical servers, Hyper-V VM’s or cloud backups to vSphere.

Veeam Cloud Tier

Veeam 9 update 4 added a move functionality to a cloud based capacity tier, this allowed older data to be aged off to the capacity tier. v10 adds a “copy” feature which allows backups to be copied to object storage as soon as the original backup is created. This allows data to be copied offsite for redundancy purposes and as the capacity tier is S3 object based this also acts as a secondary format to store backups.

Ransomware Protection

Given recent high profile ransomware cases v10 now offers the capability to store data online but in an immutable format to prevent attacks.  It is based on the new Veeam cloud tier copy facility, plus the immutable data option for S3. Once the data has been copied to S3 with the immutable option for S3 set it cannot be changed for the length of time specified, protecting backup data from any kind of change be that accidental, ransomware or a rouge admin.

Veeam v10

Credit Veeam for image

Linux Proxies

There is now greater flexibility for environments that favour Linux, allowing the deployment of backup proxies that are Linux based.

Vendor Integration

Good news for those using HPE storage, Primera is added as a supported primary storage array allowing all storage snapshot integration capabilities.  StoreOnce also added for support for catalyst copy.

Checkout this podcast with Rick Vanover and Calvin Zito for the full story on Veeam v10 and HPE integration.

To see all the new features check out the v10 what’s new document

Veeamon virtual

VeeamON Virtual

VeeamON virtual is due to hit screens near you shortly.  VeeamON is an online webinar held annually by Veeam covering data management tips and tricks, industry trends plus the latest product updates. The online webinar format makes it handy to fit around your work day, but like a transitional conference there will be a number of learning tracks available: Business, Technical or Cloud.

Veeamon virtual

My picks for the sessions to watch will include:

Veeam predictions 2020 – Backup used to be boring, not now with an ever changing landscape of multi-cloud and massive data growth, I will be tuning into this one to see what Veeam thinks is around the corner.

Designing for Veeam at scale – Organisations are facing increasing volumes of data, so how do you scale Veeam infrastructure when your environment runs into thousands of VMs.  This session provides best practices to ensure your infrastructure scales

Winning the war on ransomware – Backup is part of your defense– Ransomware continues to be a real threat to businesses, check in to this session to see if your strategy is sufficient to protect your organisation against Ransomware

There will also be chat rooms where you can ask any questions you may have.  I will be helping out in the chat rooms so pop in and say hi.

Registration is free

Veeam sizing session from Veeamon

Veeam Infrastructure Sizing

One of the key decision you have to make in planning a new Veeam deployment is in sizing the infrastructure. Correctly sizing the infrastructure to ensure that each of the Veeam infrastructure components servers has sufficient resources to perform its role will allow an optimally configured and trouble free environment. During VeeamON I attended a session on Veeam sizing by Tim Smith, I have pulled together my notes from the session and reviewed the Veeam documentation to give the following template for considering Veeam sizing decisions.  

Veeam sizing session from Veeamon

Veeam Components

The key components of the Veeam infrastructure you will have to consider in your sizing exercise are as follows:

  • Veeam backup server
  • Database server
  • Proxy Server
  • Repository server
  • Enterprise Manager server

Information Required

In order to plan your Veeam backup sizing you will need to gather some information

  • Size of source data – Required to calculate size of full backup
  • Daily rate of change – This is required to understand the size of an incremental backup. Can either be calculated assuming change rate as 10% of your total data size or from existing backup software
  • Number of VMs and disks to be protected and number of retention points required will also be needed for disk capacity planning which I will cover in a future post.

Sizing Veeam Considerations

Some considerations when sizing your Veeam environment:

  • All sizing information is contained in the user guide and best practice guide
  • Some sizing requirements refer to “Per Task”. Each disk that is backed up is a task this is not a per VM measure
  • Sizing requirements are specific to each Veeam infrastructure component
  • Sizing for each role is cumulative. For example if the server is both a Proxy and Tape server you will need to add the resource requirements for both together
  • The sizing information given in the user guide are minimums
  • The best practice guide estimates that doubling resources will half the backup window. Although this will of course be dependent on an any other bottlenecks
  • Staggering jobs can help to reduce resource requirements since some components are sized on the basis of number of concurrent jobs
  • Exact requirements will be specific to your environment, start with the recommended values access if it is meeting your requirements and amend as necessary. Then retest until you are satisfied with the result

Veeam Component Resource Requirements

Backup Server

  • 1 CPU core for every 10 actively running jobs
  • 4 GB RAM for every 10 actively running jobs
  • Minimum is 2 CPU cores and 8 GB RAM.
  • Disk space
    • Installation – 40GB
    • Logs – 3 GB log files generated per 100 protected instances, with a 24 hour RPO

Database Server

SQL Express is bundled with Veeam.  Consider using the full blown SQL if:

  • Protecting more than 500 VMs
  • Using files to tape extensively

When using the full version of SQL:

  • Up to 25 concurrent jobs – 2 CPUs, 4GB RAM
  • Up to 50 concurrent jobs – 4 CPUs, 8GB RAM
  • Up to 25 concurrent jobs – 8 CPUs, 16GB RAM

Backup and Replication Console

  • 1 CPU
  • 2 GB RAM

Backup Proxy Server

The proxy server is sized per task, a task is defined as a VM hard drive.  In effect this setting will determine the number of disks and therefore VMs that can be backed up at once

  • 1 CPU core per task
  • 2GB per task
  • 500MB of disk space per task

Backup Repository Server

This is again sized per task

  • 1 CPU core per task
  • 4GB per task
  • Detailed sizing will

Veeam Backup Enterprise Manager

  • Memory 4GB minimum
  • 2GB of hard disk space

Final Thoughts

Remember these figures are general guidelines ensure you account for time in your project to test and optimise resource allocation.

I will cover sizing for backup repositories in a future post.