Inspired by the publication
“Squeezing all the juices from the free version of Veeam Backup & Replication” , I decided to write my HowTo how to fully use Veeam.

This is not an advertising article, there are no thousands and one colorful screen. It is also not a review of products, of which enough is enough. Just useful information how to fully use the free solutions from Veeam in a corporate environment. Dry commands and tips. Everything described below is my personal experience and, in some places, links to representatives of Veeam, the official forum and habrauser.
Automatic installation of Veeam Endpdoint Backup
I'll start with Veeam Endpdoint Backup, because This is a relatively new product designed to simplify the life of the IT sector and users. Installation is never easier:
')
EndpointBackup.exe / silentNaturally, it is better to use the automatic installation tools. Choose your favorite, for example, you can
put from the "exe" through WSUS . I do not recommend disassembling the installation file on MSI, since there are a lot of manifestos, it all works as an assembly. Unfortunately, after studying the VEEAM forum, I found out that there is no sane solution for automatic configuration, and I did not find it myself, but I got the impression that the settings of the backup rules are stored in the MSSQL database (UPD: the
guess was confirmed ).
Veeam Endpoint Backup e-mail notifications
In the current version there is no possibility to create Veeam Endpoint Backup alerts (hereinafter referred to as VEB) out of the box. But the email solution is, especially, lying on the surface. This is the eventlog monitoring, in this case with PowerShell tools:
Topic on the Veeam forum .
I deliberately do not provide a ready-made PS-script, because It is better to study the above link and create the necessary solution on its base. I, for example, have this sharpened zabbiks. Let the alert be sent by the one who is trained, and no matter where, what on the soap, what on the SMS, that in other contact.
UPD: in version 1.5 of 03/17/2016 they wrote down alerts, albeit in a limited way, admins are indignant, but
we are looking for optionsVeeam Endpdoint Backup works fine with some server solutions.
Here I asked a question about backup and restore domain controllers. Having a rather pitiable experience in restoring the CD system from the backup image of
another vendor , I caught the USN Rollback. After that, I swore to restore only from "state systems". I must say that the negative experience was 10 years ago, on Win2k3. I am sure that now everything would be fine, but as they say, the sediment remained and I did not trust Veeam either. So, it is known that CD is an fastidious enough entity for restoration options, but VEB did the job perfectly well. VSS is used correctly, the USN RollBack did not catch it, but I think my small tupnet about booting in safe mode is forgivable.
I will add that there is no
official support for backup and recovery using VEB AD, SQL, Exchange, etc. So use rather as an additional option.
For those who did not follow the link above, I would say that in my case the CD was a backup, on Win2k12R2, with the role of GC, DNS, DHCP, File Services. Spinning inside ESXi 5.5. For recovery, it was loaded from a VEB ISO image created in the same environment. Although it was possible ...
VEB loading with PXE
We have Acronis purchased for several workstays, through it there is a regular backup of super-critical workstations. It is clear that VEB does not know how to centrally admin or even alert for soap without crutches, but with the advent of the Veeam solution, the idea to backup absolutely all stations in case the system partition fails to “disk D” has matured. Yes, in case of failure of the entire hard disk, this will not help, but if the “Tse disk” fails, it will still be faster to restore the backup than to lift the system through WDS and roll up some specific things, such as client banks. By the way, WDS is a great tool ... And then it dawned on why to create ISO Recovery Media ISO images for each workshop, then store and burn somewhere on a CD / USB flash drive, go on foot !!! to another floor ... In general, the VEB recovery boot image is WinRE of the version of Windows (EXTERNAL) in which it was created. Forgot to mention,
VEB supports only modern versions of Windows, starting with Win7 SP1. So, having created an ISO image with default settings on one of the machines in a virtual environment, I unpacked it and pulled out the boot.wim file. I put it in the WDS and ... downloaded over the network. From the first time, without tambourines. The network worked, was able to log in to the linux ball, where the backup files were located and roll back the backup. We go further. After several successful and not very successful experiences, I came to the conclusion that it is necessary to add to the WDS boot image typical network card drivers used by us. What I did immediately, directly in the WDS snap-in, the benefit of adding drivers to the boot image (boot.wim) does not require disassembly / assembly using DISM, unlike the installation image (install.wim). In general, everything is as usual, if you deploy Windows through WDS, you have already added drivers to the server. And also, let me remind you that the guys from Veeam added several useful pieces to the recovery boot image, such as resetting the local admin password or memory testing.
Spoon of
tar objectivity. As with the normal boot image, you should have multiple recovery images. For Win7 x32, Win 7 x64, Win2k8, Win2k12, etc. By the way, the option of restoring from a backup copy of Windows Backup is also there. And loading through WDS you
break nothing.
Launch Veeam Backup & Recovery Free from console
According to the link at the beginning of the article, the author made a little reservation, saying that VB & R Free can backup virtual machines via
Start-VBRZip . At that time, this was not the case, but here the Veeam employee promised that such functionality would be implemented. And at the end of April it happened.
Indeed, as many know, now
Start-VBRZip can be run under the FREE license, but with a number of restrictions. The main ones are only full backup, and only one virtual machine in one task. By the way, through the GUI you can run several backups at the same time, but in
different tasks. Not scary, I thought, and after reading the
instructions , in the simplest version implemented the script like this:
Script on PoSH. In this example for VMware.
# Initialize Veeam Toolkit & "C:\Program Files\Veeam\Backup and Replication\Backup\Initialize-VeeamToolkit.ps1" # Set Virtual Machines list $vmNames = 'vm1.domain.lcl', 'vm2.domain.lcl', 'vm3.domain.lcl', 'vmX.domain.lcl' # Start backup job for each VM from list foreach ($i in $vmNames) { $viObject = Find-VBRViEntity -Server vc1.domain.lcl -Name $i Start-VBRZip -BackupRepository "VeeamBackupRepo02" -Entity $viObject -Compression 5 }
I will explain:
$ vmNames - list of virtual machines for sequential backup.
Be sure to use a space, as it is written, otherwise Veeam will consider that this is a list of machines within one task, work it out correctly and send it ... indicating that there can be only one machine in one task.
vc1.domain.lcl is the address of the vCenter. You can cling directly to the host, but you remember that VB & R cannot work on the free version of vSphere. Minimum - vSphere Essentials. (I know that you can sort of like using Veeam on completely free ESXi 5.0, but nobody promises anything here).
VeeamBackupRepo02 - repository, where to backup machines. Where did the custom repository come from in the FREE version? About this below.
Email alerts.
In my case, the traffic regulations from Yandex are used, so I’ll just leave it here:
Menu -> Options -> E-mail Setting

In the case of another mail server it may be different. Google in Yandex and vice versa.
Manage additional chips.
Turn on the full VB & R FREE interface and do not turn it off. When loading a snap in the full interface will ask to buy a license or leave as is. I understand that this is a marketing lure. Let
sysmetic answer
better . Work does not interfere, and you can manage repositories, which is not available in the "poor" interface.
Run VB & R tasks through the scheduler.
I try for each task or service to create my own AD or local user with the minimum necessary rights. In the case of launching VB & R tasks from a specially trained account, I didn’t work:
Requested registry access is not allowedOne of the topics on the VEEAM forumRaising rights to the maximum in the domain did not lead to anything. As a result, through the Windows scheduler, I had to run the task from that user (to the word of the admin domain), under which VB & R was set. I know that when I change my password according to plan, the task will fly off, but for now it’s like that. All Veeam services run under the "system account", I could not find a solution.
In general, the task of running the PowerShell script from the Windows Task Scheduler should be created as follows:
Program or script:C: \ Windows \ System32 \ WindowsPowerShell \ v1.0 \ powershell.exeAdd arguments:-File "G: \ Backup \ Scripts \ VbrZip2.ps1"On this, really really fly in the ointment, I’m finishing my set of recommendations for a pair of FREE versions from Veeam. Once again I express my gratitude to Veeam for unique products and I wish everyone that the backups were complete, but they never had to be used in battle.