Veeam Backup Replication Best Practices - LearnVMware.online

1 Of ContentsVeeam Backup & Replication best PracticesIntroductionContacting Veeam SoftwareArchitecture OverviewDNS ResolutionVeeam Backup ServerDeployment MethodBackup Server PlacementSizing and System RequirementsVeeam Backup & Replication DatabaseProtecting Veeam Backup & Replication ConfigurationVeeam Enterprise ManagervCloud Director Self Service PortalSearch Server and IndexingProxy ServersTransport ModesDirect Storage AccessVirtual Appliance ModeNetwork ModeBackup from Storage SnapshotsNetApp Data ONTAP integrationNimble Storage integrationSelecting a Transport ModeSizing a Backup ProxyBackup RepositoryRepository TypesSMBD eduplication specificsWindows Server 2012 DeduplicationRepository PlanningSizingPer VM Backup FilesScale-out Backup RepositoryWAN AccelerationAnaysing Wan Acceleration WorkloadComparing WAN Acceleration ModesSizing For WAN AccelerationSizing Targets for WAN Accereration RelationshipDeployments For WAN AccelerationIs WAN Acceleration Right For meTape SupportTape Support DeploymentsTape Support Media InformationTape Support Config RequirementsTape Support Parallel ProcessingTape Support Virtual FullTape Support Writing to TapeTape Support RestoresVeeam ExplorersInteraction with vSphereHyper-V ConcernsOperational GuidelinesJob ConfigurationBackup MethodsEncryptionDeduplication and CompressionBackup JobBackup Copy JobReplication Image ProcessingData Verification Using Virtual LabsApplicationsOverview of Applications SupportActive DirectoryMicrosoft ExchangeMicrosoft SQL ServerMicrosoft SharePoint ServerOracle DatabaseMySQLIBM Notes/DominoSAP HANAP roof of Concept GuidelinesPOC GuideAssessmentAccelerated EvaluationEnhanced EvaluationWorkshop ExamplePreparationAutomationInfrastructu re HardeningBackup & Replication AnatomyBackupVM RestoreInstant VM RecoveryWindows File-Level SummaryNetworking DiagramsBackup ServerProxy ServerRepository ServerStorage IntegrationData

2 ValidationApplication-aware Image ProcessingEnterprise Manager5 Veeam Backup & Replication BestPracticesVersion Update 1 Build generation time: Thu Jan 11 2018 15:15:27 GMT+0000 (UTC)All rights reserved. All trademarks are the property of their respective ! Please read the End User Software License Agreement before using theaccompanying software program(s). Using any part of the software indicates that you acceptthe terms of the End User Software License Backup & Replication best Practices6 IntroductionWelcome to the best Practices guide for Veeam Backup & This GuideThis guide is developed by Veeam architects, and its content is also validated by support,developers and QA departments to ensure highest possible quality. If you have anyquestions or comments, please reach out the authors directly, or via your local VeeamSoftware you possess a downloaded version of this e-book, you will notice many references toexternal resources for additional e-book is optimized for digital consumption, and the most recent copy is alwaysavailable AudienceThis guide is intended for Backup administrators or consultants managing Veeam Backup & Replication on a daily sections of this guide assume you already have hands on experience with Backup & Replication , and will serve as an "advanced user guide", meaning that more basic usageinformation, system requirements and the like must be found in User Guide in providers delivering BaaS and DRaaS with Veeam Cloud Connect should refer tothe corresponding Veeam Cloud Connect Reference Berg (@poulpreben)Andreas Neufert (@AndyandtheVMs)Tom SightlerPascal di MarcoIntroduction7 Stanislav Simakov (@ssimakov)Paul Szelesi (@PSzelesi)

3 Luca Dell'Oca (@dellock6)Edwin Weijdema (@viperian)Introduction8 Contacting Veeam SoftwareAt Veeam Software we value the feedback from our customers. It is important not only tohelp you quickly with technical issues, but it is our mission to listen to your input, and buildproducts that incorporate your SupportIf you have any questions about Veeam solutions, you may use the following resources: Veeam Helpcenter at Community Forums at SupportShould you have any technical concerns, suggestions or questions, please visit the VeeamCustomer Portal at to open a case, search our knowledge base, referencedocumentation, manage your licenses or obtain the latest product ContactsFor the most up-to-date information about company contacts and office locations, pleasevisit Veeam Software9 DNS ResolutionDomain Name System (DNS) resolution is critical for Veeam Backup & Replicationdeployment (VBR) and configuration. All infrastructure components should be resolvablethrough a fully qualified domain name (FQDN).

4 This is especially important forvSphere/Hyper-V hosts and clusters. resolvable means that components are accessiblethrough both forward (A) and reverse (PTR) that the Veeam Backup & Replication server is installed on a machine that has aresolvable fully qualified domain name (FQDN). To check that the FQDN is resolvable, type nslookup at a command line prompt. If the FQDN isresolvable, the nslookup command returns the IP and name of the Veeam Backup & Replication if DNS resolution is not available you may add the infrastructure components like vCenter, ESXi and managed Veeam servers to the local hosts file on all managedVeeam servers. When using this workaround it is recommended to add both short name andfully qualified domain name in the hosts ESXi hosts are added to vCenter it is recommended to use FQDN. When backing upthrough the network with the Network Block Device (NBD) transport mode, the FQDN isreturned via VMware API for Data Protection (VADP) so the Backup proxy server must beable to resolve the FQDN via DNS.

5 Using the hosts file the data transport path can bealtered for NBD see the example hosts vcenter # esx1 # commented out management interface# esx2 # commented out management esx1 # dedicated 10 GbE Backup esx2 # dedicated 10 GbE Backup networkTo explicitly alter the data transport path, the hosts file must be deployed on all backupproxy servers. For easier management, please see the Carbon module and Set-HostsEntry by Aaron Resolution10 DNS Resolution11 Backup ServerVeeam Backup & Replication is a modular solution that lets you build a scalable availabilityinfrastructure for environments of different sizes and configurations. The Backup Server isthe core component. Features & component requirements will affect your decision how youinstall the Backup server one datacenter or multiple locations. It could mean that youchoose to install additional Backup servers or services in remote locations to optimize thedata installing the Veeam Backup & Replication server it is important to understand thedifferent data streams generated by the Veeam Backup Server (VBR) Backup Server12 Deployment MethodYou may deploy the Veeam Backup & Replication server as either a physical or virtualserver.

6 It will run on any server with Windows Server 2008 R2 or higher installed (64-bitonly). Install Veeam Backup & Replication and its components on dedicated infrastructure component roles can be co-installed. The following guidelines mayhelp in deciding which deployment type is the best fit for your deploymentFor most cases, virtual is the recommended deployment. As it provides high availability forthe Backup server component via features like vSphere High Availability, vSphere FaultTolerance or Hyper-V Failover Clustering. It also provides great flexibility in sizing andscaling as the environment VM can also be replicated to a secondary location such as a DR site. If the virtualmachine itself should fail or in the event of a datacenter/infrastructure failure, the replicatedVM can be powered on. best practice in a two-site environment is to install the Backupserver in the DR site, in the event of a disaster it is already available to start the deploymentIn small-medium environments (up to 500 VMs) it is common to see an all-in-one physicalserver running the Backup & Replication server, Backup proxy and Backup repositorycomponents.

7 This is also referred to as an "Appliance Model" large environments (over 2,500 VMs) installing Backup & Replication services onseparate servers either virtual or physical will provide better performance. When runningmany jobs simultaneously, consuming large amounts of CPU and RAM, scaling up thevirtual Backup & Replication server to satisfy the system requirements may advantage of running the Veeam Backup & Replication server on a physical server is thatit runs independently from the virtual platform. This might be an ideal situation whenrecovering the virtual platform from a disaster. Should the physical server itself fail, there areadditional steps to take before reestablishing operations:1. Install and update the operating system on a new server2. Install Veeam Backup & ReplicationDeployment Method133. Restore the configuration backupIn an enterprise environment, you may choose to install an additional Backup server tospeed up the recovery process during a disaster.

8 You may re-use existing availabilitycomponents such as a proxy or repository server for the standby Backup & Replicationserver. During a disaster the configuration Backup can easily be restored to this : It is recommended to store the configuration Backup , using a file copy job, in a locationthat is always available to this standby Backup & Replication Method14 Backup Server PlacementThe Backup server runs a number of processes, the Backup Service, Backup Managerservices and in some scenarios a Mount Server as well. In this chapter we will evaluate howeach of those components are affected by placement of the Backup & Replication evaluating the roles and understanding the data flow between the services it is possibleto optimize overall Backup performance and restore throughput and Storage DiscoveryTo collect information about the virtual infrastructure all managed vCenters and theirconnected hosts and datastores are periodically rescanned. This rescan process is visible inthe History tab > System section in the Veeam Backup & Replication console.

9 As seenhere, the Host discovery process runs every four hours. All the collected information isstored within the configuration amount of collected information is typically very small however the Host discoveryprocess may take longer or even exceed the default schedule in highly distributedenvironments. If hosts or clusters are connected to vCenter over a high-latency link youmay consider deploying a Backup server locally on the ROBO, then you can create avCenter service account with a limited scope to that particular location in order to reduce thewindow of the Host discovery process. If the ROBO uses a stand-alone host it is possible toadd the host as a managed server directly instead of through : Avoid adding individual hosts to the Backup infrastructure if using shared storage in avSphere Server Placement15If storage with advanced integration (HPE, NetApp, EMC, Nimble) are added to the StorageIntegration tab there will additionally be a Storage discovery process periodicallyrescanning storage hourly.

10 This process checks all snapshots for virtual machine restorepoints for usage within Veeam Explorer for Storage Snapshots. The Veeam Backup & Replication server itself will not perform the actual scanning of volumes but it will use themanagement API's of the storage controller to read information about present proxy servers with required storage paths available will be used for the actual storagerescanning following table shows the three different scanning workflows:2 Backup Server Placement16 Adding new storagecontrollerCreating new snapshotAutomatic scanning1. Collect specific storageinformation1. Creating new Snapshot1. Storage Monitor runs inbackground2. List of volumes,snapshots, LUNs and NFSexports2. Lists initiators2. Detecting new volumes3. Checking licenses, FCand iSCSI server3. Testing iSCSI, NFS andFC from proxies3. Scanning volumes forsnapshots every 10minutes4. Lists initiators4. Searching storageexports in VMware4. Lists initiators5.