If you want to use CentOS 7 as a Veeam repository, the basic requirements are not enough, and you have to adjust the installation a little bit.
When you upgrade Veeam Backup & Replication to V8, you have available the new Forward forever-incremental mode for your backups. This is the default method for all newly created jobs, but the already existing backup jobs are not changed, because we do not want to change the user experience or create issues to I/O profiles, backup windows and such.
This great powershell script will take all your existing forward incremental backup jobs and reconfigure them to use the new forward forever-incremental mode.
When it comes to choosing a backup mode in Veeam Backup & Replication,there is a constant trade-off between space efficiency and I/O efficiency. Forward mode is I/O efficient, while Reversed is space efficient. The new method coming in v8 will combine the pros of each, to offer an even better backup experience.
One of the biggest misconceptions about Veeam Backup & Replication, often fueled by competitors, is that it requires the complete server installation in order to run restores. So, this becomes a Single Point of Failure, just like many other solutions from competitors. This is completely untrue: there are two main features in Veeam that make restores possible even without the server installation.
PernixData is, as of today, the only server-side caching solution for VMware offering write-back capabilities, that is the possibility to accelerate write operations. This feature is extremely helpful in increasing performances in virtualized environments running write intensive applications like databases, mail servers and others. However, the usage of this feature requires some proper configuration in order to correctly protect VM with Veeam Backup
In a previous post, I described how you can configure a virtual proxy to access an iSCSI storage, in order to test DirectSAN backups. Veeam has an additional functionality, called Storage Snapshots, that improves even more DirectSAN backups performances when you have a supported storage. I’m going to show you in this post how you can configure it in your lab.
One of the nice features of Veeam Backup & Replication, when it comes to backup speed, is the possibility to use DirectSAN as its backup method on vSphere environments. This option offers the best performances, but has some precise requirements at the hardware level. It could be easy to comply with them in a production environment, but what if you want to test it in your lab, where usually hardware options are limited? Don’t worry, there is a solution!
One of the new features introduced in Veeam Backup & Replication 7.0 is the new “Backup Copy” job type. With it, an administrator can create a secondary location for his backups, without having to clone large backup files from the primary backups using tools like rsync or robocopy.
If you plan to use an external USB drive as your target for this kind of jobs, be sure to check the file system in use, before runnng into problems.