UPDATE: There’s now an FAQ section in the Veeam Forums for Veeam Backup & Replication v5: The following screen shots are taken from an early “Alpha” build of Veeam Backup & Replication v5 featuring our patent pending vPower technology. While the functionality is there, some of the dialog boxes and text will change before the official release of Veeam Backup & Replication v5. The screen shots and wizards are very self-explanatory, I have provided additional text where needed.
SureBackup: Recovery Verification
This is just a quick preview of Recovery Verification, you can check out a more in-depth video preview for more information. Step 1, Create an application Group and set options Create a verification job using the application group. This can be scheduled to run or run manually: Real-Time statistics of the Verification Job
U-AIR: Active Directory Restore Wizard
Create an AD restore lab request Once the request is created, the work-flow engine starts. Lab requests can either be approved or denied. Approving the Lab Request With Veeam’s Advanced VSS integration, when the domain controller starts in the virtual lab, it is first started in “Safe Mode” for directory services restore, and then automatically rebooted into normal mode. This is done to ensure the consistency of Active Directory when recovering from a VSS aware snapshot. As the lab is starting, the administrator can track progress and will be notified once the lab is ready. The AD restore wizard connects to both the production domain controller as well as the domain controller in the virtual lab. In this example there are no differences between what’s in the backup and what’s in production for the selected user:
InstantRecovery: Instant VM Recovery
The process of Instant VM Recovery is wizard driven and takes just a few minutes to complete. Once finished, the VM is live on the production network but running from the Veeam Backup Server’s datastore. You can easily Storage vMotion the VM to a production datastore or use Veeam Backup & Replication to replicate the VM to a production datastore.