Veeam Agent for Windows 2.0 is today available as a public beta, and it’s soon to be officially released. One of the most awaited features is for sure the possibility to send backups over the Internet to Veeam Cloud Connect, and the feedback we’ve seen during the public beta period has been great so far. There’s actually however one limit in v2: users can only choose one destination for their backups. So, if you want to consume Cloud Connect, this is going to be your only traget and you will have no local backups, and viceversa. Two different policies cannot be configured in the interface, but this doesn’t mean it cannot be done!
Search Results for: repository
An example for a Veeam backup repository using Windows 2016
In my previous article Windows 2016 and Storage Spaces as a Veeam backup repository I talked about the advantages that Veeam Backup & Replication can bring when combined with Windows Server 2016 and the new ReFS 3.1 filesytem. Several people have asked already about some practical examples about how to design a solution using these technologies, so I thought it was time to give you one storage design.
Windows 2016 and Storage Spaces as a Veeam backup repository
As Microsoft Windows 2016 is now finally generally available, people are starting to seriously looking at its features, and no doubt S2D together with the new ReFS 3.1 is one of the hot topics. I’ve first of all updated my lab with the final version of Windows 2016 in order to have my cluster in a “stable” state, than I started to focus on the different topics related to Windows 2016 and its usage as a Veeam repository. And I started to ask How can we leverage ReFS BlockCloning and Storage Spaces to make Windows 2016 the best solution for Veeam repositories? What about Storage Spaces Direct?”.
A deep look at Veeam Scale-out Backup Repository
It’s no doubt Scale-out Backup Repository is one of the biggest and most talked new feature of Veeam Backup & Replication v9. I wrote a new whitepaper to guide readers in exploring and learning how to get the best out of this new exciting technology.
An example of Veeam Scale-Out Backup Repository mixing whitebox servers
Since Veeam announced the Scale-Out Backup Repository technology coming in Veeam Backup & Replication v9, I’ve been asked already multiple times to give some practical examples on how to leverage it. Let’s see together one interesting way to leverage the “performance” policy available in Scale-Out Backup Repository.
Scale-Out Backup Repository is coming in Veeam Availability Suite v9
A new species of Backup Repository is coming from Veeam: Scale-Out Backup Repository. With it, users will be able to simplify backup job management, improve backup performance, and spend less on backup storage. Veeam’s new Scale-out Backup Repository delivers these benefits by providing an abstraction layer over individual storage devices, effectively creating a single virtual pool of backup storage to which you can assign backup jobs, and offering the freedom to easily extend capacity as needed by simply adding additional storage devices into the existing pool.
Deep Dive: Memory consumption of a Veeam repository
Veeam repositories, both Windows and Linux based, are running a software component responsible for receiving and storing data as they are processed by proxies. One of the most important parameter when sizing a repository is its expected memory consumption. Here are some informations for its proper configuration.
My adventures with Ceph Storage. Part 8: Veeam clustered repository
In the last months, I’ve refreshed my knowledge on Ceph storage, an open source scale out storage entirely made in software. As I’ve walked through my own learning path, I’ve created a series of blog posts explaining the basics, how to deploy and configure it, and my use cases. In this 8th part: Veeam clustered repository.