Let s manage agents Tom Sightler, Principal Solutions Architect Dmitry Popov, Product Management
Agenda Inventory management Job management Managed by backup server jobs Managed by agent jobs Recovery Recovery media Restore options
Inventory management
Inventory Former virtual machines Objects to protect Create protection groups
Physical infrastructure System groups Unmanaged Manually added System filters Offline Update required Untrusted
Protection group Individual computers Active Directory Computers from CSV file
Protection group Active Directory Not possible to mix objects from multiple domains Admin account is not required to view the domain
Exclusions Components are not installed Works for Active Directory
Credentials Administrator account is required Account is used for rescan, deployment and backup (application processing) For CSV and Active Directory protection group
Setup tips
Tip #1 You can use localhost\administrator
Tip #2 Validation is not real time
Tip #3.CSV file can be deleted
Tip #4 VMs are excluded by default
Tip #5 Test credentials will start rescan without deployment
Deployment
Distribution server Windows host Can be combined with other roles
Distribution server: Components Installer service Redistributables: Veeam Agents for Microsoft Windows and Linux Distribution service
Agent redistributable C:\ProgramData\Veeam\Agents\ vaw.msi is pushed to the client
System requirements: Veeam Agent for Microsoft Windows Windows backup agent Windows 7 SP1 and above Windows Server 2008 R2 SP1 and above Windows CBT driver Windows Server 2008 R2 SP1 and above
System requirements: Veeam Agent for Linux Deploy and manage Debian Ubuntu CentOS RHEL SLES Oracle
Backup agent Installer service Backup agent CBT driver (Windows)
Lightweight agent Installer service Backup agent
Lightweight agent No UI and SQL DB Default for protection group Used for managed by backup server and failover cluster jobs
Rescan
Linux fingerprints
Rescan tips
Tip #null Installer service is installed anyway
Tip #0 Agent can be managed by only one backup server
Tip #1 - Discovery issue? - RESCAN!
Tip #2 - Installation issue? - REBOOT and then RESCAN!
Tip #3 You can DISABLE periodic RESCAN
Tip #4 You can MOVE UNMANAGED AGENTS to custom protection groups
Tip #5 You can EDIT Manually Added protection group
Job management
Job type Workstation Server Failover cluster
Job mode Managed by backup server (job) Managed by agent (policy)
Managed by backup server
Managed by backup server Default lightweight agent No UI and SQL DB Job is controlled by backup server Host should be online
Managed by backup server
Managed by backup server Real-time stats Real-time email reports
Repository Simple repository Scale-Out Backup Repository TM
Managed by agent
Managed by agent Full agent installation in Read Only mode UI and SQL DB Job is controlled by agent Backup server controls job configuration
Managed by agent
Managed by agent
Managed by agent: History Configuration upload Job stats download
Managed by agent Configuration is pushed from Veeam Backup & Replication TM to the agent Stats downloaded periodically by rescan job
Repository Local storage Shared folder Backup repository
Backup job tips
TIP #0 No mapping from standalone jobs No way to migrate standalone job to Veeam Backup & Replication
TIP #1 Windows agent: Multiple jobs are supported for backup server mode
TIP #2 Backup agent is licensed based on job type Failover cluster node is licensed per node (server counter)
TIP #3 Operating system volume as a source automatically adds system reserved / EFI partition to backup scope
TIP #4 Account from protection group is used for application-aware processing
Recovery
Recovery options Bare metal recovery Export as virtual disk Instant recovery to Hyper-V Application item recovery Restore guest files Veeam Restore to Microsoft Azure
Recovery options: Cluster Bare metal restore of a cluster node works Instant restore to Hyper-V skips clustered volumes during recovery Export as virtual disk functionality restores volume residing on a clustered disk as simple volume File-level and application item-level recoveries work as expected
Veeam recovery media OS volume backup is required Components are collected during full backup Encryption password is not included You can create recovery media via remote console to a local device
BMR: Cluster node Non-authoritative restore: Restoring the node to normal function, but not rolling back the cluster configuration. When the restored node begins functioning and joins the cluster, the latest cluster configuration automatically replicates to that node.
BMR: Shared disks Shared disks are hidden from the BMR UI, so it s impossible to restore clustered disk via Bare Metal Recovery.
Q&A
Thank you